...
Perhaps a ternary valued response of "valid", "matches inactive description", and "invalid" would solve this issue...but adds complexity for something that is perhaps an edge case.
Questions
- what are the use cases for $validate-code involving validating the term?
- based on that, what should be considered "valid" for an input code and term generally for a FHIR CodeSystem and ValueSet combination?
- then specifically, for SNOMED CT what should the interpretation be and is any supporting clarification necessary in the Using SNOMED CT with FHIR page?
Group Discussion
26 June 2018
In general, valid codes should return "valid = true" and term issues should be identified as a warning in the message. Any matching term should result in positive validation.
RH: If we had an option to specify a "strict" flag, then we could validate the term in a more exacting way.
DM: Developers want finer grained responses to enumerate the validation result of the term, distinct from the code.
PJ: The value-set will define the language used, but this would not apply when validating against the code-system.
If the URI that is passed is an edition, then hopefully we could look up a default (set?) of language reference sets.
Specifying language reference sets
Case sensitivity: