FHIR Chat · Validation on simplifier failed · questionnaire

Stream: questionnaire

Topic: Validation on simplifier failed


view this post on Zulip Julia Schönmann (Aug 08 2019 at 10:53):

Hey everyone,
im over the profiling academy of simplifier atm and theres also a chapter about questionnaires.
https://simplifier.net/guide/ProfilingAcademy/SDCandquestionnaires

At the exercise at the end of the articel they also profil a questionnair response ressource with forge.
I tried to follow the steps and validate afterwards some JSON questionnair response to my own profil with the simplifier validation tool:
https://simplifier.net/validate

Link to my ressource:
https://simplifier.net/questionnairetest/myquestionnaireresponse-duplicate-3

My JSON code:
{ "resourceType": "QuestionnaireResponse", "id": "t1", "meta": { "profile": [ "http://example.org/fhir/StructureDefinition/MyQuestionnaireResponse4" ] }, "status": "completed", "item": [ { "linkId": "1", "item": [ { "linkId": "11", "answer": [{"valueString": "Not a Boolean" }], "text": "Not the right Text" }, { "linkId": "12", "answer": [{"valueString": "Correct String" }], "text": "Correct Text" } ] } ] }

Had first some problems with the correct way to slice the item, but this one is working pretty good, beside the fact that it wants every linkId the same number. But overall the validation tool notices the false answer in question one (string instead of boolean) and wrong question text.
But i dont know why it wants the linkId everyhwere to be "1".
This point makes no sense, as i set the linkId to be 11 for the first question and 12 for the second. If the validation tool wouldnt observe that, it couldnt notice that the first answer has a wrong value and text.

I know its not common to profil the questionnair (response) ressource, but theres still no standard operation for validating answers, so i want to give that a try.

Take a look here for the validation tools outcome messages:
XML
ISSUES

Does anyone know that issue? And how to fix it?


Last updated: Apr 12 2022 at 19:14 UTC