Any (ANY)

These extensions may apply to any of the FHIR data types (complex or primitive). It can also appear on any resource element.

nullFlavor

This extension allows exceptional values to be conveyed, as well as for data to be flagged as "missing" for some reason.

In v3, null flavors were often required for data types when particular components were missing. In the FHIR core specification, there is never an automatic requirement to send a null flavor, though profiles may introduce such a requirement. As well, the need for null flavors is often made explicit in the specification by adding relevant null flavors to the value set for coded elements or by introducing a "choice" of data type such that either a normal value or a coded special value can be specified. For example, a resouce might have a quantity[x] element with a type of Quantity | code where the value set is limited to TRC, QS or UNK. In this way, only those null flavors that are relevant to the context are included.

Where null flavors are not supported as part of the core specification, extensions can be defined that expose only those null flavors that are relevant. This approach is preferred over referencing the full null flavor specification. (Note that the null flavor code system can be referenced in any value sets.)

Entity Name (EN)

These extensions apply to the HumanName data type.

• EN-use - allows a more refined statement of the intended use of a particular name
• EN-representation - is for a subset of EN-use and indicates the representation form of the name (this has specific use in east Asian countries)

This extension applies to HumanName parts - e.g. family and given :

• EN-qualifier - allows distinguishing initials, middle names, call-me names and other types of names

Note, however, that subsequent implementer experience has led to a new set of extensions being defined for most of the human name issues (see own-name , own-prefix , partner-name , partner-prefix , fathers-family and mothers-family ), and these should be used in preference to the ISO 21090 extensions, which are defined only for backwards compatibility.

Parametric Probability Distribution of a Physical Quantity (PPD<PQ>)

These extensions provide support for the probability distributions for the Quantity data type. There are two properties:

• uncertainty - Indicates the standard deviation associated with the extended quantity.
• uncertaintyType - Identifies the probability distribution associated with the uncertainty of the extended quantity.

Address (AD)

These extensions provide support for various additional properties of the Address data type. There are kinds of properties:

• address-use - Identifies additional usages not supported by the Address.use property
• Additional address parts not broken out as distinct elements in the Address data type, including:
  • address-part-additionalLocator - Additional information beyond the street number. E.g. apartment number
  • address-part-unitID - Number of a unit within a building
  • address-part-unitType - Type of unit. E.g. appartment, floor
  • address-part-deliveryAddressLine - Delivery to an installation rather than a physical address. E.g. PO box, depot, station
  • address-part-deliveryInstallationType - Lype of delivery site (PO Box, depot, station)
  • address-part-deliveryInstallationArea - The jurisdiction in which the delivery address is located
  • address-part-deliveryInstallationQualifier - A number or letter identifying the delivery site. E.g. Station "A", Rural Route "104"
  • address-part-deliveryMode - Type of delivery. E.g. rural route, post office box
  • address-part-deliveryModeIdentifier - Routing information such as route number, box number
  • address-part-streetAddressLine - A type of address identifying a building located by street name
  • address-part-houseNumber - The number of the building on the street
  • address-part-buildingNumberSuffix - The non-numeric portion of a building number. E.g. "A" in 103A Some Street
  • address-part-postBox - A post office box number
  • address-part-houseNumberNumeric -The numeric portion of a building number. E.g. "103" in 103A Some Street
  • address-part-streetName - The name of a street (distinct from the building number)
  • address-part-streetNameBase - The name of a street excluding type and direction. E.g. "Main" in Main Street NW
  • address-part-streetNameType - The type of a street. E.g. "Street" in Main Street NW
  • address-part-direction - The direction of a street. E.g. "NW" in Main Street NW
  • address-part-careOf - The name of a person to take receipt at the specified address who is responsible for ensuring final deliver
  • address-part-censusTract - A geographic region delineated for demographic purposes
  • address-part-delimiter - A separator such as a carrage return, dash, comma, etc.
  • address-part-precinct - A subsection of a municipality

These additional elements of Address will be ignored by applications that do not support them, so any information in them should also be duplicated in the Address.line to which they are attached.