Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

answerValueSet with a canonical URL doesn't work #34

Open
vadi2 opened this issue Feb 17, 2022 · 1 comment
Open

answerValueSet with a canonical URL doesn't work #34

vadi2 opened this issue Feb 17, 2022 · 1 comment

Comments

@vadi2
Copy link

vadi2 commented Feb 17, 2022

If I specify "answerValueSet": "<canonical URL>", and upload the valueset and questionnaire to the same FHIR server, the SDC Questionnaire App will render it fine (good) but neither the form builder nor beta version load the valueset (bad).

I'm aware there's an extension to explicitly specify the terminology server explicitly, but I just want to have a self-contained bundle of my questionnaire+terminology resources, no external dependency on a terminology server needed.

Sample bundle -
Bundle-DebugBundleSACQPatientComorbidity.json.zip

@plynchnlm
Copy link
Member

Sorry for the very delayed reply to this. It is been on our list to look at for a while, and we are just now getting to it. If you want a self-contained bundle, I think it is better to put the ValueSet under Questionnaire.contained. Otherwise, the Questionnaire will need to access a FHIR/terminology server to get the ValueSet. In the SDC Questionnaire App, it guesses that it should look for the ValueSet on the same server from which the Questionnaire was loaded. I suppose the form builder could make the same guess, if the Questionnaire was loaded from a FHIR server, which I think it usually is not, because I expect most users would load a Questionnaire from a file, or be starting from scratch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants