Stream: questionnaire
Topic: Are codes case-sensitive?
Tilo Christ (Apr 01 2021 at 22:22):
I have a pair of a questionnaire and a questionnaireResponse. The questionnaire: http://build.fhir.org/questionnaire-example-bluebook.json.html
The response: https://www.hl7.org/fhir/questionnaireresponse-example-bluebook.json.html
I am currently failing on prepopulating the sex field, as it is declared with code 'F' in the questionnaire and 'f' in the response. Am I supposed to use case-insensitive behaviour for this match, or is this example a mismatch between the questionnaire and the response?
Tilo Christ (Apr 01 2021 at 23:05):
What is the process for reporting problems in these examples? In the pair I just mentioned there are also mismatches in the linkIds for the 2 vitamin K shots.
Tilo Christ (Apr 01 2021 at 23:22):
And last but not least: is an answer with a valueDate a valid answer for an item of type datetime?
Tilo Christ (Apr 03 2021 at 15:08):
Tilo Christ said:
And last but not least: is an answer with a valueDate a valid answer for an item of type datetime?
Ok, I found this https://github.com/HL7/fhir/pull/1120 which fixes the f vs F issue, must have downloaded a version of the example where this had not been reflected yet. @Lloyd McKenzie Is there a described procedure for how one goes about reporting and fixing such issues? I would gladly open issues and PRs.
Brian Postlethwaite (Apr 05 2021 at 01:53):
Case sensitivity is also defined by the codesystem. So no general answer too.
Tilo Christ (Apr 05 2021 at 10:19):
Brian Postlethwaite said:
Case sensitivity is also defined by the codesystem. So no general answer too.
Thanks for that pointer. I hadn't thought to look in CodeSystem. Interestingly, it seems to encourage code-insensitive for my particular use-case, unless otherwise specified: CodeSystem.caseSensitive: If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case.
In that sense the "broken" Bluebook response example might even serve as a test case for that subtlety.
Lloyd McKenzie (Apr 05 2021 at 13:59):
Can you submit a tracker item on this @Tilo Christ ?
Tilo Christ (Apr 05 2021 at 14:03):
@Lloyd McKenzie is there a Wiki page on the proper procedure? I am generally familiar with JIRA, Confluence etc. but have no experience with your governance rules. Will I have to attend certain meetings afterwards to present / discuss it?
Lloyd McKenzie (Apr 05 2021 at 15:19):
No requirement to attend meetings, though you're welcome to. If you mark the issue as "in person", then we'll do our best to make sure you can be there. There's a link to submit new trackers at the bottom of every page in the spec ("Propose a change"). You'll have to register, but that's free. (We have manual human review to try to make sure you're not a spammer.) Full documentation on the tracker process is here: https://confluence.hl7.org/display/HL7/Specification+Feedback
Tilo Christ (Apr 06 2021 at 17:15):
@Lloyd McKenzie https://jira.hl7.org/browse/FHIR-31710 since this is my first attempt please feel free to critique.
Lloyd McKenzie (Apr 06 2021 at 18:35):
Looks great :)
Last updated: Apr 12 2022 at 19:14 UTC
