This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
. Page versions: R4B R4 R3 R2
NI | OTH | NINF | PINF | UNK | ASKU | NAV | NASK | TRC | MSK | NA | QS
{
"resourceType": "ExtensionDefinition",
"id": "iso21090-nullFlavor",
"url": "http://hl7.org/fhir/ExtensionDefinition/iso21090-nullFlavor",
"name": "NI | OTH | NINF | PINF | UNK | ASKU | NAV | NASK | TRC | MSK | NA | QS",
"publisher": "HL7",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org"
}
]
}
],
"description": "If the value is not a proper value, indicates the reason.",
"status": "draft",
"date": "2012-06-24",
"mapping": [
{
"identity": "v2",
"uri": "http://hl7.org/v2",
"name": "HL7 v2"
},
{
"identity": "rim",
"uri": "http://hl7.org/v3",
"name": "RIM"
}
],
"contextType": "datatype",
"context": [
"Any"
],
"element": [
{
"path": "Extension",
"short": "NI | OTH | NINF | PINF | UNK | ASKU | NAV | NASK | TRC | MSK | NA | QS",
"definition": "If the value is not a proper value, indicates the reason.",
"comments": "Considerable care must be used when using nullFlavor in this context of FHIR - more than any other concept, this is tied to the way v3 works, and FHIR is quite different. For instance, there is no notion of a \"proper value\" as opposed to any other value in FHIR. a NullFlavor should be understood to mean, \"why information is missing\", and the nulFlavors OTH, NINF, PINF, and TRC should not be used.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "NullFlavor",
"isExtensible": false,
"conformance": "required",
"description": "A collection of codes specifying why a valid value is not present",
"referenceReference": {
"reference": "http://hl7.org/fhir/v3/vs/NullFlavor"
}
},
"mapping": [
{
"identity": "v2",
"map": "n/a"
},
{
"identity": "rim",
"map": "ANY.nullFlavor"
}
]
}
]
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.