Stream: implementers
Topic: nullFlavor not allowed
SueAnn Svaby (Jun 24 2020 at 15:11):
US Core IG states that some elements may not use nullFlavor. For historical records the data may not have been captured. For instance, we are currently adding lifecycle status to our database, therefore many historical records for Goals will have null lifecycle status. How should we handle that?
US Core IG states:
"For the following status elements no appropriate “unknown” concept code is available, therefore the element must be populated:
AllergyIntolerance.clinicalStatus
Condition.clinicalStatus
DocumentReference.status
Immunization.status
Goal.lifecycleStatus"
If one of these a status code is missing, a 404 http error code and an OperationOutcome SHALL be returned in response to a query for the resource.
http://hl7.org/fhir/us/core/general-guidance.html
Lloyd McKenzie (Jun 24 2020 at 16:52):
@Brett Marquard @Eric Haas
Brett Marquard (Jun 24 2020 at 16:56):
You should consider an appropriate default, or return 404 that it's unavailable. FHIR base will hopefully add the unknown option to these fields.
Eric Haas (Jun 24 2020 at 16:59):
these are required bindings and according to FHIR binding rules you must provide a code. They are all inherited from base so the same thing applies in the base spec.
Last updated: Apr 12 2022 at 19:14 UTC
