[go: up one dir, main page]

DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). 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: R5 R4B R4 R3 R2

1.19.0 Data Types

FHIR Infrastructure Work GroupMaturity Level: 3Ballot Status: DSTU 2

The FHIR specification defines a set of data types that are used for the resource elements. There are two categories of data types: simple / primitive types, which are single elements, and complex types, which are re-usable clusters of elements. This page describes the data types. See also the Examples, Detailed Descriptions and Mappings.

Table of Contents

Primitive Types
ElementinstanttimedatedateTimedecimalbooleanintegerstringuribase64BinarycodeidoidunsignedIntpositiveIntmarkdown
Complex Types
ElementIdentifierHumanNameAddressContactPointTimingQuantitySimpleQuantityAttachmentRangePeriodRatioCodeableConceptCodingSampledDataAgeDistanceDurationCountMoneyAnnotationSignature

White = abstract type. Light blue - types. Light Pink - Profile on Type. The data types are also available as a W3C Schema.

1.19.0.1 Primitive Types

ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*decimalActual value attribute of the data typevalue : xs:decimal 0..1integerActual value attribute of the data typevalue : xs:int 0..1booleanActual value attribute of the data typevalue : xs:boolean 0..1instantActual value attribute of the data typevalue : xs:dateTime 0..1dateActual value attribute of the data typevalue : xs:gYear|xs:gYearMonth|xs:date 0..1base64BinaryActual value attribute of the data typevalue : xs:base64Binary 0..1stringActual value attribute of the data typevalue : xs:string 0..1codedateTimeActual value attribute of the data typevalue : xs:gYear|xs:gYearMonth|xs:date|xs:dateTime 0..1iduriActual value attribute of the data typevalue : xs:anyURI 0..1oidtimeActual value attribute of the data typevalue : xs:time 0..1unsignedIntpositiveIntmarkdown

The following table describes the primitive types that are used in this specification. Primitive types are those with only a value, and no additional elements as children (though, like all types, they have extensions).

Primitive Types
FHIR Name Value Domain XML Representation JSON representation
boolean true | false xs:boolean, except that 0 and 1 are not valid values JSON boolean (true or false)
integer A signed 32-bit integer (for larger values, use decimal) xs:int, except that leading 0 digits are not allowed JSON number (with no decimal point)
string A sequence of Unicode characters xs:string JSON String
Note that strings SHALL NOT exceed 1MB in size
decimal Rational numbers that have a decimal representation. See below about the precision of the number xs:decimal, except that decimals may not use exponents, and leading 0 digits are not allowed A JSON number, except that exponents are not allowed
uri A Uniform Resource Identifier Reference (RFC 3986 ). Note: URIs are case sensitive. For UUID (urn:uuid:53fefa32-fcbb-4ff8-8a92-55ee120877b7) use all lowercase xs:anyURI A JSON string - a URI
URIs can be absolute or relative, and may have an optional fragment identifier
base64Binary A stream of bytes, base64 encoded (RFC 4648 ) xs:base64Binary A JSON string - base64 content
Todo: is it possible to impose an upper absolute limit on a base64Binary (for denial of service reasons, like on string)
instant An instant in time - known at least to the second and always includes a time zone. Note: This is intended for precisely observed times (typically system logs etc.), and not human-reported times - for them, use date and dateTime. instant is a more constrained dateTime xs:dateTime A JSON string - an xs:dateTime
Note: This type is for system times, not human times (see date and dateTime below).
date A date, or partial date (e.g. just year or year + month) as used in human communication. There is no time zone. Dates SHALL be valid dates union of xs:date, xs:gYearMonth, xs:gYear A JSON string - a union of xs:date, xs:gYearMonth, xs:gYear
Regex: -?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1]))?)?
dateTime A date, date-time or partial date (e.g. just year or year + month) as used in human communication. If hours and minutes are specified, a time zone SHALL be populated. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates. The time "24:00" is not allowed union of xs:dateTime, xs:date, xs:gYearMonth, xs:gYear A JSON string - a union of xs:dateTime, xs:date, xs:gYearMonth, xs:gYear
Regex: -?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?
time A time during the day, with no date specified (can be converted to a Duration since midnight). Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. The time "24:00" is not allowed, and neither is a time zone xs:time A JSON string - an xs:time
Regex: ([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?

Notes:

  • For all the types, the XML and JSON representations are the same except for different escaping in XML and JSON
  • Boolean values can also be represented using coded values (such as HL7 v2 Table 0136). See Observation for one such use
  • The regexes may allow a broader set of values than are actually valid (e.g. leap years) so additional validation is needed
  • The precision of the decimal value has signficance:
    • e.g. 0.010 is regarded as different to 0.01, and the original precision should be preserved
    • Implementations SHALL handle decimal values in ways that preserve and respect the precision of the value as represented for presentation purposes
    • Implementations are not required to perform calculations with these numbers differently, though they may choose to do so (i.e. preserve significance)
    • See implementation comments for XML, JSON and RDF
    • In object code, implementations that might meet this constraint are GMP implementations or equivalents to Java BigDecimal that implement arbitrary precision, or a combination of a (64 bit) floating point value with a precision field
    • Note that there is no absolute limit to the magnitude of the value, though large and/or highly precise values are extremely rare in medicine. One element where highly precise decimals may be encountered is the Location coordinates

1.19.0.1.1 XML and JSON representations

All elements using these primitive types have some combination of value as described above, an internal identity (e.g. xml:id), and extensions. The value is represented in XML as an attribute named "value":

  <count value="2"/>

and as the value of the property in JSON:

  "count" : 2

For additional details, including how the internal identity and extensions are represented, see the XML and JSON formats. When the value is missing, it is not represented in the instance; the XML value attribute or the JSON property are not represented at all. This means that in xml, attributes are never present with a length of 0 (value=""), and properties are never a 0 length string or null in JSON ("name" : "" is not valid). (note: there is one specific use of the null in the JSON representation).

According to XML schema, leading and trailing whitespace in the value attribute is ignored for the types boolean, integer, decimal, base64Binary, instant, uri, date, dateTime, oid, and uri. Note that this means that the schema aware XML libraries give different attribute values to non schema aware libraries when reading the XML instances. For this reason, the value attribute for these types SHOULD not have leading and trailing spaces. String values should only have leading and trailing spaces if they are part of the content of the value. In JSON, whitespace in string values is always significant. Primitive types other than string SHALL NOT have leading or trailing whitespace.

1.19.0.1.2 Simple Restrictions

In addition to the base primitive types, a few additional primitive types are defined as restrictions on one of the other primitive types.

FHIR NameBase FHIR TypeDescription
codestringIndicates that the value is taken from a set of controlled strings defined elsewhere (see Using codes for further discussion). Technically, a code is restricted to a string which has at least one character and no leading or trailing whitespace, and where there is no whitespace other than single spaces in the contents
regex: [^\s]+([\s]+[^\s]+)*
oiduriAn OID represented as a URI (RFC 3001 ); e.g. urn:oid:1.2.3.4.5
regex: urn:oid:[0-2](\.[1-9]\d*)+
idstringAny combination of upper or lower case ASCII letters ('A'..'Z', and 'a'..'z', numerals ('0'..'9'), '-' and '.', with a length limit of 64 characters. (This might be an integer, an un-prefixed OID, UUID or any other identifier pattern that meets these constraints.)
regex: [A-Za-z0-9\-\.]{1,64}
markdownstringA string that may contain markdown syntax for optional processing by a markdown presentation engine
unsignedIntintAny non-negative integer (e.g. >= 0)
regex: [0-9]+
positiveIntintAny positive integer (e.g. > 0)
regex: [1-9][0-9]*

Some additional notes about the id datatype:

  • Ids are case sensitive. UUIDs SHALL be sent using lowercase letters
  • The ID type includes identifiers consistent with ISO 18232 , but also includes other identifier formats as well, and is not case insensitive like ISO 18232.
  • In a typical FHIR URL, like http://example.com/fhir/Patient/1234, the last part "1234" (highlighted in red) is the part that is an id datatype
  • A full UUID is a uri, not an id. UUIDs in URIs SHALL also be represented in lowercase (urn:uuid:59bf0ef4-e89c-4628-9b51-12ae3fdbe22b)

Some additional notes about the markdown datatype:

DSTU Note: CommonMark is a new arrival but may gain sufficient impetus to be preferred in a future version.

Feedback is welcome here .


1.19.0.2 Complex Types

These types are represented as XML Elements with child elements with the name of the defined elements of the type. The name of the element is defined where the type is used. Any of the XML elements may have an id attribute. In JSON, the data type is represented by an object with properties named the same as the XML elements. The JSON representation is almost exactly the same, so only the first example has an additional JSON representation.

Complex data types may be "profiled". A Structure Definition or type "constraint" makes a set of rules about which elements SHALL have values and what the possible values are.

UML Diagrams of the Data types

ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*QuantityThe value of the measured amount. The value includes an implicit precision in the presentation of the valuevalue : decimal [0..1]How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value (this element modifies the meaning of other elements)comparator : code [0..1] « How the Quantity should be understood and represented. (Strength=Required)QuantityComparator! »A human-readable form of the unitunit : string [0..1]The identification of the system that provides the coded form of the unitsystem : uri [0..1]A computer processable form of the unit in some unit representation systemcode : code [0..1]AttachmentIdentifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriatecontentType : code [0..1] « The mime type of an attachment. Any valid mime type is allowed. (Strength=Required)MimeType! »The human language of the content. The value can be any valid value according to BCP 47language : code [0..1] « A human language. (Strength=Required)Language! »The actual data of the attachment - a sequence of bytes. In XML, represented using base64data : base64Binary [0..1]An alternative location where the data can be accessedurl : uri [0..1]The number of bytes of data that make up this attachmentsize : unsignedInt [0..1]The calculated hash of the data using SHA-1. Represented using base64hash : base64Binary [0..1]A label or set of text to display in place of the datatitle : string [0..1]The date that the attachment was first createdcreation : dateTime [0..1]RangeThe low limit. The boundary is inclusivelow : Quantity(SimpleQuantity) [0..1]The high limit. The boundary is inclusivehigh : Quantity(SimpleQuantity) [0..1]PeriodThe start of the period. The boundary is inclusivestart : dateTime [0..1]The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that timeend : dateTime [0..1]RatioThe value of the numeratornumerator : Quantity [0..1]The value of the denominatordenominator : Quantity [0..1]CodeableConceptA reference to a code defined by a terminology systemcoding : Coding [0..*]A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the usertext : string [0..1]CodingThe identification of the code system that defines the meaning of the symbol in the codesystem : uri [0..1]The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchangedversion : string [0..1]A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination)code : code [0..1]A representation of the meaning of the code in the system, following the rules of the systemdisplay : string [0..1]Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays)userSelected : boolean [0..1]SampledDataThe base quantity that a measured value of zero represents. In addition, this provides the units of the entire measurement seriesorigin : Quantity(SimpleQuantity) [1..1]The length of time between sampling times, measured in millisecondsperiod : decimal [1..1]A correction factor that is applied to the sampled data points before they are added to the originfactor : decimal [0..1]The lower limit of detection of the measured points. This is needed if any of the data points have the value "L" (lower than detection limit)lowerLimit : decimal [0..1]The upper limit of detection of the measured points. This is needed if any of the data points have the value "U" (higher than detection limit)upperLimit : decimal [0..1]The number of sample points at each time point. If this value is greater than one, then the dimensions will be interlaced - all the sample points for a point in time will be recorded at oncedimensions : positiveInt [1..1]A series of data points which are decimal values separated by a single space (character u20). The special values "E" (error), "L" (below detection limit) and "U" (above detection limit) can also be used in place of a decimal valuedata : string [1..1] ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*IdentifierThe purpose of this identifier (this element modifies the meaning of other elements)use : code [0..1] « Identifies the purpose for this identifier, if known . (Strength=Required)IdentifierUse! »A coded type for the identifier that can be used to determine which identifier to use for a specific purposetype : CodeableConcept [0..1] « A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. (Strength=Extensible)Identifier Type + »Establishes the namespace in which set of possible id values is uniquesystem : uri [0..1]The portion of the identifier typically displayed to the user and which is unique within the context of the systemvalue : string [0..1]Time period during which identifier is/was valid for useperiod : Period [0..1]Organization that issued/manages the identifierassigner : Reference [0..1] « Organization »HumanNameIdentifies the purpose for this name (this element modifies the meaning of other elements)use : code [0..1] « The use of a human name (Strength=Required)NameUse! »A full text representation of the nametext : string [0..1]The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his fatherfamily : string [0..*]Given namegiven : string [0..*]Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the nameprefix : string [0..*]Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the namesuffix : string [0..*]Indicates the period of time when this name was valid for the named personperiod : Period [0..1]AddressThe purpose of this address (this element modifies the meaning of other elements)use : code [0..1] « The use of an address (Strength=Required)AddressUse! »Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are bothtype : code [0..1] « The type of an address (physical / postal) (Strength=Required)AddressType! »A full text representation of the addresstext : string [0..1]This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address informationline : string [0..*]The name of the city, town, village or other community or delivery centercity : string [0..1]The name of the administrative area (county)district : string [0..1]Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes)state : string [0..1]A postal code designating a region defined by the postal servicepostalCode : string [0..1]Country - a nation as commonly understood or generally acceptedcountry : string [0..1]Time period when address was/is in useperiod : Period [0..1]ContactPointTelecommunications form for contact point - what communications system is required to make use of the contactsystem : code [0..1] « Telecommunications form for contact point (Strength=Required)ContactPointSystem! »The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address)value : string [0..1]Identifies the purpose for the contact point (this element modifies the meaning of other elements)use : code [0..1] « Use of contact point (Strength=Required)ContactPointUse! »Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher valuesrank : positiveInt [0..1]Time period when the contact point was/is in useperiod : Period [0..1]TimingIdentifies specific times when the event occursevent : dateTime [0..*]A code for the timing pattern. Some codes such as BID are ubiquitous, but many institutions define their own additional codescode : CodeableConcept [0..1] « Code for a known / defined timing pattern. (Strength=Preferred)TimingAbbreviation? »RepeatEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedulebounds[x] : Type [0..1] « Quantity(Duration)|Range|Period »A total count of the desired number of repetitionscount : integer [0..1]How long this thing happens for when it happensduration : decimal [0..1]The upper limit of how long this thing happens for when it happensdurationMax : decimal [0..1]The units of time for the duration, in UCUM unitsdurationUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »The number of times to repeat the action within the specified period / period range (i.e. both period and periodMax provided)frequency : integer [0..1]If present, indicates that the frequency is a range - so repeat between [frequency] and [frequencyMax] times within the period or period rangefrequencyMax : integer [0..1]Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the periodperiod : decimal [0..1]If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 daysperiodMax : decimal [0..1]The units of time for the period in UCUM unitsperiodUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »A real world event that the occurrence of the event should be tied towhen : code [0..1] « Real world event that the relating to the schedule. (Strength=Required)EventTiming! »SignatureAn indication of the reason that the entity signed this document. This may be explicitly included as part of the signature information and can be used when determining accountability for various actions concerning the documenttype : Coding [1..*] « An indication of the reason that an entity signed the object (Strength=Preferred)Signature Type ? »When the digital signature was signedwhen : instant [1..1]A reference to an application-usable description of the person that signed the certificate (e.g. the signature used their private key)who[x] : Type [1..1] « uri|Reference(Practitioner|RelatedPerson| Patient|Device|Organization) »A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jwt for JWT, and image/* for a graphical image of a signaturecontentType : code [1..1] « The mime type of an attachment. Any valid mime type is allowed. (Strength=Required)MimeType! »The base64 encoding of the Signature contentblob : base64Binary [1..1]AnnotationThe individual responsible for making the annotationauthor[x] : Type [0..1] « Reference(Practitioner|Patient| RelatedPerson)|string »Indicates when this particular annotation was madetime : dateTime [0..1]The text of the annotationtext : string [1..1]A set of rules that describe when the event should occurrepeat[0..1] 1.19.0.3 Attachment

See also Examples, Detailed Descriptions and Mappings.

This type is for containing or referencing attachments - additional data content defined in other formats. The most common use of this type is to include images or reports in some report format such as PDF. However it can be used for any data that has a MIME type.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Attachment Σ IElementContent in a format defined elsewhere
It the Attachment has data, it SHALL have a contentType
... contentType Σ0..1codeMime type of the content, with charset etc.
MimeType (Required)
... language Σ0..1codeHuman language of the content (BCP-47)
Language (Required)
... data Σ0..1base64BinaryData inline, base64ed
... url Σ0..1uriUri where the data can be found
... size Σ0..1unsignedIntNumber of bytes of content (if url provided)
... hash Σ0..1base64BinaryHash of the data (sha-1, base64ed)
... title Σ0..1stringLabel to display in place of the data
... creation Σ0..1dateTimeDate attachment was first created

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <contentType value="[code]"/><!-- 0..1 Mime type of the content, with charset etc.  -->
 <language value="[code]"/><!-- 0..1 Human language of the content (BCP-47)  -->
 <data value="[base64Binary]"/><!-- 0..1 Data inline, base64ed -->
 <url value="[uri]"/><!-- 0..1 Uri where the data can be found -->
 <size value="[unsignedInt]"/><!-- 0..1 Number of bytes of content (if url provided) -->
 <hash value="[base64Binary]"/><!-- 0..1 Hash of the data (sha-1, base64ed) -->
 <title value="[string]"/><!-- 0..1 Label to display in place of the data -->
 <creation value="[dateTime]"/><!-- 0..1 Date attachment was first created -->
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Attachment Σ IElementContent in a format defined elsewhere
It the Attachment has data, it SHALL have a contentType
... contentType Σ0..1codeMime type of the content, with charset etc.
MimeType (Required)
... language Σ0..1codeHuman language of the content (BCP-47)
Language (Required)
... data Σ0..1base64BinaryData inline, base64ed
... url Σ0..1uriUri where the data can be found
... size Σ0..1unsignedIntNumber of bytes of content (if url provided)
... hash Σ0..1base64BinaryHash of the data (sha-1, base64ed)
... title Σ0..1stringLabel to display in place of the data
... creation Σ0..1dateTimeDate attachment was first created

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <contentType value="[code]"/><!-- 0..1 Mime type of the content, with charset etc.  -->
 <language value="[code]"/><!-- 0..1 Human language of the content (BCP-47)  -->
 <data value="[base64Binary]"/><!-- 0..1 Data inline, base64ed -->
 <url value="[uri]"/><!-- 0..1 Uri where the data can be found -->
 <size value="[unsignedInt]"/><!-- 0..1 Number of bytes of content (if url provided) -->
 <hash value="[base64Binary]"/><!-- 0..1 Hash of the data (sha-1, base64ed) -->
 <title value="[string]"/><!-- 0..1 Label to display in place of the data -->
 <creation value="[dateTime]"/><!-- 0..1 Date attachment was first created -->
</[name]>

The actual content of an Attachment can be conveyed directly using the data element or a URL reference can be provided. If both are provided, the reference SHALL point to the same content as found in the data. The reference can never be reused to point to some different data (i.e. the reference is version specific). The URL reference SHALL point to a location that resolves to actual data; some URIs such as cid: meet this requirement. If the URL is a relative reference, it is interpreted in the same way as a resource reference.

The contentType element SHALL always be populated when an Attachment contains data, and MAY be populated when there is a url. It can include charset information and other mime type extensions as appropriate. If there is no character set in the contentType then the correct course of action is undefined, though some media types may define a default character set and/or the correct character set may be able to be determined by inspection of the content.

The hash is included so that applications can verify that the content returned by the URL has not changed.

In many cases where Attachment is used, the cardinality is >1. A valid use of repeats is to convey the same content in different mime types and languages. Guidance on the meaning of repeating elements SHALL be provided in the definition of the repeating resource element or extension that references this type. The language element describes the language of the attachment using the codes defined in BCP 47 .

Constraints

  • att-1: It the Attachment has data, it SHALL have a contentType (xpath: not(exists(f:data)) or exists(f:contentType))

If neither data nor a URL is provided, the value should be understood as an assertion that no content for the specified mimeType and/or language is available for the combination of language and contentType.

The context of use may frequently make rules about the kind of attachment (and therefore, the kind of mime types) that can be used.

Attachment is used in the following places: BodySite, Communication, CommunicationRequest, Contract, DiagnosticReport, DocumentManifest, DocumentReference, HealthcareService, ImagingStudy, Media, Observation, Patient, Person, Practitioner, QuestionnaireResponse and RelatedPerson

1.19.0.4 Coding

See also Examples, Detailed Descriptions and Mappings.

A Coding is a representation of a defined concept using a symbol from a defined "code system" - see Using Codes in resources for more details.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Coding ΣElementA reference to a code defined by a terminology system
... system Σ0..1uriIdentity of the terminology system
... version Σ0..1stringVersion of the system - if relevant
... code Σ0..1codeSymbol in syntax defined by the system
... display Σ0..1stringRepresentation defined by the system
... userSelected Σ0..1booleanIf this coding was chosen directly by the user

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <system value="[uri]"/><!-- 0..1 Identity of the terminology system -->
 <version value="[string]"/><!-- 0..1 Version of the system - if relevant -->
 <code value="[code]"/><!-- 0..1 Symbol in syntax defined by the system -->
 <display value="[string]"/><!-- 0..1 Representation defined by the system -->
 <userSelected value="[boolean]"/><!-- 0..1 If this coding was chosen directly by the user -->
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Coding ΣElementA reference to a code defined by a terminology system
... system Σ0..1uriIdentity of the terminology system
... version Σ0..1stringVersion of the system - if relevant
... code Σ0..1codeSymbol in syntax defined by the system
... display Σ0..1stringRepresentation defined by the system
... userSelected Σ0..1booleanIf this coding was chosen directly by the user

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <system value="[uri]"/><!-- 0..1 Identity of the terminology system -->
 <version value="[string]"/><!-- 0..1 Version of the system - if relevant -->
 <code value="[code]"/><!-- 0..1 Symbol in syntax defined by the system -->
 <display value="[string]"/><!-- 0..1 Representation defined by the system -->
 <userSelected value="[boolean]"/><!-- 0..1 If this coding was chosen directly by the user -->
</[name]>

The meaning of the Coding is defined by the code. The system provides the source of the definition of the code, along with an optional version reference. The display is a human display for the text defined by the system - it adds no other value.

The system is a URI that references the code system that defines the code. Choosing the correct system is important; for more information about the code system URI, read Managing Terminology System URIs. The system URI SHALL NOT contain a reference to a value set (e.g. ValueSet.url). If the code is taken from a ValueSet with an inline code system, ValueSet.codeSystem.system, is the correct value for the system uri.

A code system version may also be supplied. If the meaning of codes within the code system is consistent across releases, this is not required. The version SHOULD be exchanged when the system does not maintain consistent definitions across versions. Note that the following systems SHOULD always have a version specified:

  • National releases of SNOMED CT (consistency of definitions varies amongst jurisdictions, and some jurisdictions may make their own rules on this)
  • Various versions of ICD (note: the major releases are labeled as different code systems altogether, but there is variation within versions)

More generally, any classification (e.g. a code system that includes concepts with relative definitions such as "not otherwise coded" will require a version. See the discussion of code system versions in the Value Set resource for further discussion on versioning.

If present, the code SHALL be a syntactically correct symbol as defined by the system. In some code systems such as SNOMED CT, the symbol may be an expression composed of other predefined symbol (e.g. post-coordination). Note that codes are case sensitive unless specified otherwise by the code system. The display is a text representation of the code defined by the system and is used to display the meaning of the code by an application that is not aware of the system.

Where the code system defines multiple possible display strings, one of these SHALL be used in display. If one is labeled as preferred, it SHOULD be used. If the code system does not define a text representation (e.g. SNOMED CT Expressions) then display cannot be populated, and the meaning of the code won't be accessible to systems that don't understand the code expression.

In some cases, the system may not be known - only the code is known. In this case, no useful processing of the code may be performed unless the system can be safely inferred by the context. This practice should be avoided where possible, as information sharing in a wider context is very likely to arise eventually, and codes cannot be used in the absence of a known system.

If the system is present, and there is no code, then this is understood to mean that there is no suitable code in the system in which to represent the code.

If two codings have the same system, version and code then they have the same meaning. If the version information is missing, or the system, version or the code elements differ, then how the codes are related can only be determined by consulting the definitions of the system(s) and any mappings available.

A coding may be marked as a "userSelected" if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc.

Constraints

The context of use (as defined in the resource or applicable profile) usually makes rules about what codes and systems are allowed or required in a particular context by binding the element to a value set.

Coding is used in the following places: CodeableConcept, Signature, Account, AuditEvent, Claim, ClaimResponse, Conformance, Contract, Coverage, DocumentReference, EligibilityRequest, EligibilityResponse, EnrollmentRequest, EnrollmentResponse, ExplanationOfBenefit, ImagingStudy, MessageHeader, PaymentNotice, PaymentReconciliation, ProcessRequest, ProcessResponse, Provenance, Questionnaire, QuestionnaireResponse, StructureDefinition, Subscription, TestScript, ValueSet and VisionPrescription

Design Note: This specification defines two types for representing coded values:

  • Coding: a simple direct reference to a code defined by a code system
  • CodeableConcept: a text description and/or a list of Codings (i.e. a list of references to codes defined by code systems)

The Coding data type corresponds to the simple case of selecting a single code from a code list. However this type is rarely used in the FHIR specifications; long experience with exchanging coded values in HL7 shows that in the general case, systems need to able to exchange multiple translation codes, and/or an original text.

The Coding data type is used directly when there is certainty that the value must be selected directly from one of the available codes, and the list of possible codes is agreed to by all participants. This is not usually the case in the context of FHIR - general interoperability - so Coding is mostly used in extensions, which are usually intended to be defined for a well-controlled context of use.

1.19.0.5 CodeableConcept

See also Examples, Detailed Descriptions and Mappings.

A CodeableConcept represents a value that is usually supplied by providing a reference to one or more terminologies or ontologies, but may also be defined by the provision of text. This is a common pattern in healthcare data.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CodeableConcept ΣElementConcept - reference to a terminology or just text
... coding Σ0..*CodingCode defined by a terminology system
... text Σ0..1stringPlain text representation of the concept

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <coding><!-- 0..* Coding Code defined by a terminology system --></coding>
 <text value="[string]"/><!-- 0..1 Plain text representation of the concept -->
</[name]>

Each coding is a representation of the concept as described above. The concept may be coded multiple times in different code systems (or even multiple times in the same code systems, where multiple forms are possible, such as with SNOMED CT). The different codings may have slightly different granularity due to the differences in the definitions of the underlying codes. There is no meaning associated with the ordering of coding within a CodeableConcept. A typical use of CodeableConcept is to send the local code that the concept was coded with, and also one or more translations to publicly defined code systems such as LOINC or SNOMED CT. Sending local codes is useful and important for the purposes of debugging and integrity auditing.

Whether or not coding elements are present, the text is the representation of the concept as entered or chosen by the user, and which most closely represents the intended meaning of the user or concept. Very often the text is the same as a display of one of the codings. One of the codings may be flagged as the userSelected - the code or concept that the user actually selected directly. When none of the coding elements is marked as userSelected, the text (if present) is the preferred source of meaning.

Constraints

The context of use usually makes rules about what codes and systems are allowed or required in a particular context by binding the element to a value set.

CodeableConcept is used in the following places: Identifier, Account, AllergyIntolerance, Appointment, AppointmentResponse, AuditEvent, Basic, BodySite, CarePlan, ClinicalImpression, Communication, CommunicationRequest, Composition, ConceptMap, Condition, Conformance, Contract, DataElement, DetectedIssue, Device, DeviceComponent, DeviceMetric, DeviceUseRequest, DeviceUseStatement, DiagnosticOrder, DiagnosticReport, DocumentManifest, DocumentReference, Encounter, EpisodeOfCare, FamilyMemberHistory, Flag, Goal, Group, HealthcareService, ImagingObjectSelection, Immunization, ImmunizationRecommendation, ImplementationGuide, List, Location, Media, Medication, MedicationAdministration, MedicationDispense, MedicationOrder, MedicationStatement, MessageHeader, NamingSystem, NutritionOrder, Observation, OperationOutcome, Order, Organization, Patient, Practitioner, Procedure, ProcedureRequest, Provenance, ReferralRequest, RelatedPerson, RiskAssessment, Schedule, Slot, Specimen, StructureDefinition, Substance, SupplyDelivery, SupplyRequest, TestScript, ValueSet and VisionPrescription

1.19.0.6 Quantity

See also Examples, Detailed Descriptions and Mappings.

A measured amount (or an amount that can potentially be measured).

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Quantity Σ IElementA measured or measurable amount
If a code for the unit is present, the system SHALL also be present
... value Σ0..1decimalNumerical value (with implicit precision)
... comparator ?! Σ0..1code< | <= | >= | > - how to understand the value
QuantityComparator (Required)
... unit Σ0..1stringUnit representation
... system Σ I0..1uriSystem that defines coded unit form
... code Σ0..1codeCoded form of the unit

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <value value="[decimal]"/><!-- 0..1 Numerical value (with implicit precision) -->
 <comparator value="[code]"/><!-- 0..1 < | <= | >= | > - how to understand the value -->
 <unit value="[string]"/><!-- 0..1 Unit representation -->
 <system value="[uri]"/><!-- ?? 0..1 System that defines coded unit form -->
 <code value="[code]"/><!-- 0..1 Coded form of the unit -->
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Quantity Σ IElementA measured or measurable amount
If a code for the unit is present, the system SHALL also be present
... value Σ0..1decimalNumerical value (with implicit precision)
... comparator ?! Σ0..1code< | <= | >= | > - how to understand the value
QuantityComparator (Required)
... unit Σ0..1stringUnit representation
... system Σ I0..1uriSystem that defines coded unit form
... code Σ0..1codeCoded form of the unit

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <value value="[decimal]"/><!-- 0..1 Numerical value (with implicit precision) -->
 <comparator value="[code]"/><!-- 0..1 < | <= | >= | > - how to understand the value -->
 <unit value="[string]"/><!-- 0..1 Unit representation -->
 <system value="[uri]"/><!-- ?? 0..1 System that defines coded unit form -->
 <code value="[code]"/><!-- 0..1 Coded form of the unit -->
</[name]>

The value contains the numerical value of the quantity, including an implicit precision. If no comparator is specified, the value is a point value (i.e. '='). The comparator element can never be ignored.

The unit element contains a displayable unit that defines what is measured. The unit may additionally be coded in some formal way using the code and the system (see Coding for further information about how to use the system element).

If the unit is able to be coded in UCUM and a code is provided, it SHOULD be a UCUM code. If a UCUM unit is provided in the code then a canonical value can be generated for purposes of comparison between quantities. Note that the unit element will often contain text that is actually a valid UCUM unit, but it cannot be assumed that the unit actually contains a valid UCUM unit.

Constraints

  • qty-3: If a code for the unit is present, the system SHALL also be present (xpath: not(exists(f:code)) or exists(f:system))

The context of use may frequently define what kind of measured quantity this is and therefore what kind of unit can be used. The context of use may additionally require a code from a particular system. The context of use may also restrict the values for the value or range.

Quantity is used in the following places: Ratio, Group, Observation and QuestionnaireResponse

1.19.0.6.1 Defined Variations on Quantity

These are used as types in resource content models, but they are really just a Quantity with some rules:

AgeA duration (length of time) with a UCUM codeStructureDefinition (XML, JSON)Condition and FamilyMemberHistory
CountA count of a discrete element (no unit)StructureDefinition (XML, JSON)(not used as yet)
MoneyAn amount of money. With regard to precision, see [Decimal Precision](datatypes.html#precision)StructureDefinition (XML, JSON)Account, Claim, ClaimResponse, Contract and PaymentReconciliation
DistanceA measure of distanceStructureDefinition (XML, JSON)(not used as yet)
DurationA length of timeStructureDefinition (XML, JSON)Encounter, Goal and MedicationOrder
SimpleQuantityA fixed quantity (no comparator)StructureDefinition (XML, JSON)Range, SampledData, CarePlan, Claim, Contract, Immunization, Medication, MedicationAdministration, MedicationDispense, MedicationOrder, MedicationStatement, NutritionOrder, Observation, Specimen, Substance, SupplyDelivery and VisionPrescription
1.19.0.7 Range

See also Examples, Detailed Descriptions and Mappings.

A set of ordered Quantity values defined by a low and high limit.

A Range specifies a set of possible values; usually, one value from the range applies (e.g. "give the patient between 2 and 4 tablets"). Ranges are typically used in instructions.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Range Σ IElementSet of values bounded by low and high
If present, low SHALL have a lower value than high
... low Σ I0..1SimpleQuantityLow limit
... high Σ I0..1SimpleQuantityHigh limit

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <low><!-- ?? 0..1 Quantity(SimpleQuantity) Low limit --></low>
 <high><!-- ?? 0..1 Quantity(SimpleQuantity) High limit --></high>
</[name]>

JSON Template


{doco
  // from Element: extension
  "low" : { Quantity(SimpleQuantity) }, // C? Low limit
  "high" : { Quantity(SimpleQuantity) } // C? High limit
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Range Σ IElementSet of values bounded by low and high
If present, low SHALL have a lower value than high
... low Σ I0..1SimpleQuantityLow limit
... high Σ I0..1SimpleQuantityHigh limit

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <low><!-- ?? 0..1 Quantity(SimpleQuantity) Low limit --></low>
 <high><!-- ?? 0..1 Quantity(SimpleQuantity) High limit --></high>
</[name]>

JSON Template

{doco
  // from Element: extension
  "low" : { Quantity(SimpleQuantity) }, // C? Low limit
  "high" : { Quantity(SimpleQuantity) } // C? High limit
}

The unit and code/system elements of the low or high elements SHALL match. If the low or high elements are missing, the meaning is that the low or high boundaries are not known and therefore neither is the complete range.

The comparator flag on the low or high elements cannot be present. Note that the Range type should not be used to represent out of range measurements: A quantity type with the comparator element should be used instead.

The low and the high values are inclusive, and are assumed to have arbitrarily high precision; e.g. the range 1.5 to 2.5 includes 1.50, and 2.50 but not 1.49 or 2.51.

Constraints

  • rng-2: If present, low SHALL have a lower value than high (xpath: not(exists(f:low/f:value/@value)) or not(exists(f:high/f:value/@value)) or (number(f:low/f:value/@value) <= number(f:high/f:value/@value)))

Range is used in the following places: Condition, FamilyMemberHistory, Group, MedicationAdministration, MedicationDispense, MedicationOrder, MedicationStatement, Observation and RiskAssessment

1.19.0.8 Ratio

See also Examples, Detailed Descriptions and Mappings.

A relationship between two Quantity values expressed as a numerator and a denominator.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Ratio Σ IElementA ratio of two Quantity values - a numerator and a denominator
Numerator and denominator SHALL both be present, or both are absent. If both are absent, there SHALL be some extension present
... numerator Σ0..1QuantityNumerator value
... denominator Σ0..1QuantityDenominator value

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <numerator><!-- 0..1 Quantity Numerator value --></numerator>
 <denominator><!-- 0..1 Quantity Denominator value --></denominator>
</[name]>

JSON Template


{doco
  // from Element: extension
  "numerator" : { Quantity }, // Numerator value
  "denominator" : { Quantity } // Denominator value
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Ratio Σ IElementA ratio of two Quantity values - a numerator and a denominator
Numerator and denominator SHALL both be present, or both are absent. If both are absent, there SHALL be some extension present
... numerator Σ0..1QuantityNumerator value
... denominator Σ0..1QuantityDenominator value

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <numerator><!-- 0..1 Quantity Numerator value --></numerator>
 <denominator><!-- 0..1 Quantity Denominator value --></denominator>
</[name]>

JSON Template

{doco
  // from Element: extension
  "numerator" : { Quantity }, // Numerator value
  "denominator" : { Quantity } // Denominator value
}

Common factors in the numerator and denominator are not automatically cancelled out. The Ratio data type is used for titers (e.g. "1:128") and other quantities produced by laboratories that truly represent ratios. Ratios are not simply "structured numbers" - for example blood pressure measurements (e.g. "120/60") are not ratios. In addition, ratios are used where common factors in the numerator and denominator do not cancel out. The most common example of this is where the ratio represents a unit cost, and the numerator is a currency (e.g. 50/$10).

A proper ratio has both a numerator and a denominator; however these are not mandatory in order to allow an invalid ratio with an extension with further information.

Constraints

  • rat-1: Numerator and denominator SHALL both be present, or both are absent. If both are absent, there SHALL be some extension present (xpath: (count(f:numerator) = count(f:denominator)) and ((count(f:numerator) > 0) or (count(f:extension) > 0)))

The context of use may require particular types of Quantity for the numerator or denominator.

Ratio is used in the following places: Medication, MedicationAdministration, MedicationDispense, MedicationOrder, MedicationStatement, NutritionOrder, Observation and Substance

1.19.0.9 Period

See also Examples, Detailed Descriptions and Mappings.

A time period defined by a start and end date/time.

A period specifies a range of times. The context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the period applies (e.g. "give to the patient between 2 and 4 pm on 24-Jun 2013").

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Period Σ IElementTime range defined by start and end date/time
If present, start SHALL have a lower value than end
... start Σ I0..1dateTimeStarting time with inclusive boundary
... end Σ I0..1dateTimeEnd time with inclusive boundary, if not ongoing

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <start value="[dateTime]"/><!-- ?? 0..1 Starting time with inclusive boundary -->
 <end value="[dateTime]"/><!-- ?? 0..1 End time with inclusive boundary, if not ongoing -->
</[name]>

If the start element is missing, the start of the period is not known. If the end element is missing, it means that the period is ongoing, or the start may be in the past, and the end date in the future, which means that period is expected/planned to end at the specified time

The end value includes any matching date/time. For example, the period 2011-05-23 to 2011-05-27 includes all the times from the start of the 23rd May through to the end of the 27th of May.

Period is used in the following places: Identifier, Account, CarePlan, CommunicationRequest, Composition, Condition, Contract, Coverage, DeviceUseRequest, DeviceUseStatement, DiagnosticReport, DocumentReference, Encounter, EpisodeOfCare, FamilyMemberHistory, Flag, Group, HealthcareService, MedicationAdministration, MedicationOrder, MedicationStatement, NamingSystem, Observation, Patient, PaymentReconciliation, Practitioner, Procedure, ProcedureRequest, ProcessRequest, Provenance, ReferralRequest, RelatedPerson, RiskAssessment, Schedule, Specimen and SupplyDelivery

1.19.0.10 SampledData

See also Examples, Detailed Descriptions and Mappings.

Data that comes from a series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data.

A SampledData provides a concise way to handle the data produced by devices that sample a physical particular state at a high frequency. A typical use for this is for the output of an ECG or EKG device.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. SampledData ΣElementA series of measurements taken by a device
... origin Σ1..1SimpleQuantityZero value and units
... period Σ1..1decimalNumber of milliseconds between samples
... factor Σ0..1decimalMultiply data by this before adding to origin
... lowerLimit Σ0..1decimalLower limit of detection
... upperLimit Σ0..1decimalUpper limit of detection
... dimensions Σ1..1positiveIntNumber of sample points at each time point
... data Σ1..1stringDecimal values with spaces, or "E" | "U" | "L"

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <origin><!-- 1..1 Quantity(SimpleQuantity) Zero value and units --></origin>
 <period value="[decimal]"/><!-- 1..1 Number of milliseconds between samples -->
 <factor value="[decimal]"/><!-- 0..1 Multiply data by this before adding to origin -->
 <lowerLimit value="[decimal]"/><!-- 0..1 Lower limit of detection -->
 <upperLimit value="[decimal]"/><!-- 0..1 Upper limit of detection -->
 <dimensions value="[positiveInt]"/><!-- 1..1 Number of sample points at each time point -->
 <data value="[string]"/><!-- 1..1 Decimal values with spaces, or "E" | "U" | "L" -->
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. SampledData ΣElementA series of measurements taken by a device
... origin Σ1..1SimpleQuantityZero value and units
... period Σ1..1decimalNumber of milliseconds between samples
... factor Σ0..1decimalMultiply data by this before adding to origin
... lowerLimit Σ0..1decimalLower limit of detection
... upperLimit Σ0..1decimalUpper limit of detection
... dimensions Σ1..1positiveIntNumber of sample points at each time point
... data Σ1..1stringDecimal values with spaces, or "E" | "U" | "L"

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <origin><!-- 1..1 Quantity(SimpleQuantity) Zero value and units --></origin>
 <period value="[decimal]"/><!-- 1..1 Number of milliseconds between samples -->
 <factor value="[decimal]"/><!-- 0..1 Multiply data by this before adding to origin -->
 <lowerLimit value="[decimal]"/><!-- 0..1 Lower limit of detection -->
 <upperLimit value="[decimal]"/><!-- 0..1 Upper limit of detection -->
 <dimensions value="[positiveInt]"/><!-- 1..1 Number of sample points at each time point -->
 <data value="[string]"/><!-- 1..1 Decimal values with spaces, or "E" | "U" | "L" -->
</[name]>

The digits are a set of decimal values separated by a single space (Unicode character u20). In addition to decimal values, the special values "E" (error), "L" (below detection limit) and "U" (above detection limit) can also be used. If there is more than one dimension, the different dimensions are interlaced - all the data points for a particular time are represented together. The default value for factor is 1.

SampledData is used in the following places: Observation

1.19.0.11 Identifier

See also Examples, Detailed Descriptions and Mappings.

A numeric or alphanumeric string that is associated with a single object or entity within a given system. Typically, identifiers are used to connect content in resources to external content available in other frameworks or protocols. Identifiers are associated with objects, and may be changed or retired due to human or system process and errors.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Identifier ΣElementAn identifier intended for computation
... use ?! Σ0..1codeusual | official | temp | secondary (If known)
IdentifierUse (Required)
... type Σ0..1CodeableConceptDescription of identifier
Identifier Type Codes (Extensible)
... system Σ0..1uriThe namespace for the identifier
... value Σ0..1stringThe value that is unique
... period Σ0..1PeriodTime period when id is/was valid for use
... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 usual | official | temp | secondary (If known) -->
 <type><!-- 0..1 CodeableConcept Description of identifier --></type>
 <system value="[uri]"/><!-- 0..1 The namespace for the identifier -->
 <value value="[string]"/><!-- 0..1 The value that is unique -->
 <period><!-- 0..1 Period Time period when id is/was valid for use --></period>
 <assigner><!-- 0..1 Reference(Organization) Organization that issued id (may be just text) --></assigner>
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Identifier ΣElementAn identifier intended for computation
... use ?! Σ0..1codeusual | official | temp | secondary (If known)
IdentifierUse (Required)
... type Σ0..1CodeableConceptDescription of identifier
Identifier Type Codes (Extensible)
... system Σ0..1uriThe namespace for the identifier
... value Σ0..1stringThe value that is unique
... period Σ0..1PeriodTime period when id is/was valid for use
... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 usual | official | temp | secondary (If known) -->
 <type><!-- 0..1 CodeableConcept Description of identifier --></type>
 <system value="[uri]"/><!-- 0..1 The namespace for the identifier -->
 <value value="[string]"/><!-- 0..1 The value that is unique -->
 <period><!-- 0..1 Period Time period when id is/was valid for use --></period>
 <assigner><!-- 0..1 Reference(Organization) Organization that issued id (may be just text) --></assigner>
</[name]>

The system referred to by means of a URI defines how the identifier is defined (i.e. how the value is made unique). It might be a specific application or a recognized standard/specification for a set or identifiers or a way of making identifiers unique. The value SHALL be unique within the defined system and have a consistent meaning wherever it appears. Both system and value are always case sensitive.

In addition to the system (which provides a uniqueness scope) and the value, identifiers may also have a type, which may be useful when a system encounters identifiers with unknown system values. Note, however, that the type of an identifier is not a well controlled vocabulary with wide variations in practice. The type deals only with general categories of identifiers and SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to variations in common usage.

FHIR defines some useful URIs directly. OIDs (urn:oid:) and UUIDs (urn:uuid:) may be registered in the HL7 OID registry and should be if the content is shared or exchanged across institutional boundaries. If the identifier itself is naturally globally unique (e.g. an OID, a UUID, or a URI with no trailing local part), then the system SHALL be "urn:ietf:rfc:3986", and the URI is in the value.

In some cases, the system may not be known - only the value is known (e.g. a simple device that scans a barcode), or the system is known implicitly (simple exchange in a limited context, often driven by barcode readers). In this case, no useful matching may be performed using the value unless the system can be safely inferred by the context. This practice should be avoided where possible, as information sharing in a wider context is very likely to arise eventually, and values without a system are inherently limited in use.

The assigner is used to indicate what registry/state/facility/etc. assigned the identifier.

Identifier is used in the following places: Account, AllergyIntolerance, Appointment, AppointmentResponse, AuditEvent, Basic, BodySite, CarePlan, Claim, ClaimResponse, Communication, CommunicationRequest, Composition, ConceptMap, Condition, Contract, Coverage, DataElement, DetectedIssue, Device, DeviceComponent, DeviceMetric, DeviceUseRequest, DeviceUseStatement, DiagnosticOrder, DiagnosticReport, DocumentManifest, DocumentReference, EligibilityRequest, EligibilityResponse, Encounter, EnrollmentRequest, EnrollmentResponse, EpisodeOfCare, ExplanationOfBenefit, FamilyMemberHistory, Flag, Goal, Group, HealthcareService, ImagingStudy, Immunization, ImmunizationRecommendation, List, Location, Media, MedicationAdministration, MedicationDispense, MedicationOrder, MedicationStatement, NutritionOrder, Observation, Order, OrderResponse, Organization, Patient, PaymentNotice, PaymentReconciliation, Person, Practitioner, Procedure, ProcedureRequest, ProcessRequest, ProcessResponse, Provenance, Questionnaire, QuestionnaireResponse, ReferralRequest, RelatedPerson, RiskAssessment, Schedule, Slot, Specimen, StructureDefinition, Substance, SupplyDelivery, SupplyRequest, TestScript, ValueSet and VisionPrescription

1.19.0.12 HumanName

See also Examples, Detailed Descriptions and Mappings.

A name of a human with text, parts and usage information.

Names may be changed or repudiated. People may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts is not always significant. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems SHALL care about name parts around the world varies widely.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. HumanName ΣElementName of a human - parts and usage
... use ?! Σ0..1codeusual | official | temp | nickname | anonymous | old | maiden
NameUse (Required)
... text Σ0..1stringText representation of the full name
... family Σ0..*stringFamily name (often called 'Surname')
... given Σ0..*stringGiven names (not always 'first'). Includes middle names
... prefix Σ0..*stringParts that come before the name
... suffix Σ0..*stringParts that come after the name
... period Σ0..1PeriodTime period when name was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 usual | official | temp | nickname | anonymous | old | maiden -->
 <text value="[string]"/><!-- 0..1 Text representation of the full name -->
 <family value="[string]"/><!-- 0..* Family name (often called 'Surname') -->
 <given value="[string]"/><!-- 0..* Given names (not always 'first'). Includes middle names -->
 <prefix value="[string]"/><!-- 0..* Parts that come before the name -->
 <suffix value="[string]"/><!-- 0..* Parts that come after the name -->
 <period><!-- 0..1 Period Time period when name was/is in use --></period>
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. HumanName ΣElementName of a human - parts and usage
... use ?! Σ0..1codeusual | official | temp | nickname | anonymous | old | maiden
NameUse (Required)
... text Σ0..1stringText representation of the full name
... family Σ0..*stringFamily name (often called 'Surname')
... given Σ0..*stringGiven names (not always 'first'). Includes middle names
... prefix Σ0..*stringParts that come before the name
... suffix Σ0..*stringParts that come after the name
... period Σ0..1PeriodTime period when name was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 usual | official | temp | nickname | anonymous | old | maiden -->
 <text value="[string]"/><!-- 0..1 Text representation of the full name -->
 <family value="[string]"/><!-- 0..* Family name (often called 'Surname') -->
 <given value="[string]"/><!-- 0..* Given names (not always 'first'). Includes middle names -->
 <prefix value="[string]"/><!-- 0..* Parts that come before the name -->
 <suffix value="[string]"/><!-- 0..* Parts that come after the name -->
 <period><!-- 0..1 Period Time period when name was/is in use --></period>
</[name]>

This table summarizes where common parts of a person's name are found.

NameExampleDestination / Comments
SurnameSmithFamily Name
First nameJohnGiven Name
TitleMrPrefix
Middle NameSamuelSubsequent Given Names
Patronymicbin OsmanFamily Name
Multiple family namesCarreño QuiñonesFamily Name. See note below about repeats
InitialsQ.Given Name as initial ("." recommended)
Nick NameJockGiven name, with Use = common
QualificationsPhDSuffix
HonorificsSeniorSuffix

For further information, including all W3C International Examples , consult the examples.

The multiple given and family name parts combine to form a single name. Multiple given and family names are for when a person's name has multiple given names (relatively common across cultures) and multiple surnames (less common). Where a person has alternate names that may be used in place of each other, these are different instances of HumanName.

The text element specifies the entire name as it should be represented. This may be provided instead of or as well as specific parts, and can be built from the parts, though the correct order of assembly is culture dependent: the order of the parts within a given part type has significance and SHALL be observed. The appropriate order between family name and given names depends on culture and context of use.

The parts of a name SHOULD NOT contain whitespace. For family name, hyphenated names such as "Smith-Jones" are a single name, but names with spaces such as "Smith Jones" are broken into multiple parts. For given names, initials may be used in place of the full name if that is all that is recorded. Systems that operate across cultures should generally rely on the text form for presentation, and use the parts for index/search functionality. For this reasons, applications SHOULD populate the text element for future robustness.

Applications updating a name SHALL ensure either that the text and the parts are in agreement, or that only one of the two is present. Systems that do not support as many name parts as are provided in an instance may wish to append some of the parts together using spaces

HumanName is used in the following places: Organization, Patient, Person, Practitioner and RelatedPerson

1.19.0.13 Address

See also Examples, Detailed Descriptions and Mappings.

A postal address. There are a variety of postal address formats defined around the world. Postal addresses are often also used to record a location that can be visited to find a patient or person.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Address ΣElementA postal address
... use ?! Σ0..1codehome | work | temp | old - purpose of this address
AddressUse (Required)
... type Σ0..1codepostal | physical | both
AddressType (Required)
... text Σ0..1stringText representation of the address
... line Σ0..*stringStreet name, number, direction & P.O. Box etc.
... city Σ0..1stringName of city, town etc.
... district Σ0..1stringDistrict name (aka county)
... state Σ0..1stringSub-unit of country (abbreviations ok)
... postalCode Σ0..1stringPostal code for area
... country Σ0..1stringCountry (can be ISO 3166 3 letter code)
... period Σ0..1PeriodTime period when address was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 home | work | temp | old - purpose of this address -->
 <type value="[code]"/><!-- 0..1 postal | physical | both -->
 <text value="[string]"/><!-- 0..1 Text representation of the address -->
 <line value="[string]"/><!-- 0..* Street name, number, direction & P.O. Box etc. -->
 <city value="[string]"/><!-- 0..1 Name of city, town etc. -->
 <district value="[string]"/><!-- 0..1 District name (aka county) -->
 <state value="[string]"/><!-- 0..1 Sub-unit of country (abbreviations ok) -->
 <postalCode value="[string]"/><!-- 0..1 Postal code for area -->
 <country value="[string]"/><!-- 0..1 Country (can be ISO 3166 3 letter code) -->
 <period><!-- 0..1 Period Time period when address was/is in use --></period>
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Address ΣElementA postal address
... use ?! Σ0..1codehome | work | temp | old - purpose of this address
AddressUse (Required)
... type Σ0..1codepostal | physical | both
AddressType (Required)
... text Σ0..1stringText representation of the address
... line Σ0..*stringStreet name, number, direction & P.O. Box etc.
... city Σ0..1stringName of city, town etc.
... district Σ0..1stringDistrict name (aka county)
... state Σ0..1stringSub-unit of country (abbreviations ok)
... postalCode Σ0..1stringPostal code for area
... country Σ0..1stringCountry (can be ISO 3166 3 letter code)
... period Σ0..1PeriodTime period when address was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <use value="[code]"/><!-- 0..1 home | work | temp | old - purpose of this address -->
 <type value="[code]"/><!-- 0..1 postal | physical | both -->
 <text value="[string]"/><!-- 0..1 Text representation of the address -->
 <line value="[string]"/><!-- 0..* Street name, number, direction & P.O. Box etc. -->
 <city value="[string]"/><!-- 0..1 Name of city, town etc. -->
 <district value="[string]"/><!-- 0..1 District name (aka county) -->
 <state value="[string]"/><!-- 0..1 Sub-unit of country (abbreviations ok) -->
 <postalCode value="[string]"/><!-- 0..1 Postal code for area -->
 <country value="[string]"/><!-- 0..1 Country (can be ISO 3166 3 letter code) -->
 <period><!-- 0..1 Period Time period when address was/is in use --></period>
</[name]>

The text element specifies the entire address as it should be represented. This may be provided instead of or as well as the specific parts. Applications updating an address SHALL ensure either that the text and the parts are in agreement, or that only one of the two is present.

Constraints

Address is used in the following places: Location, Organization, Patient, Person, Practitioner and RelatedPerson

1.19.0.14 ContactPoint

See also Examples, Detailed Descriptions and Mappings.

Details for all kinds of technology-mediated contact points for a person or organization, including telephone, email, etc.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint Σ IElementDetails of a Technology mediated contact point (phone, fax, email, etc.)
A system is required if a value is provided.
... system Σ I0..1codephone | fax | email | pager | other
ContactPointSystem (Required)
... value Σ0..1stringThe actual contact point details
... use ?! Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
ContactPointUse (Required)
... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
... period Σ0..1PeriodTime period when the contact point was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <system value="[code]"/><!-- ?? 0..1 phone | fax | email | pager | other -->
 <value value="[string]"/><!-- 0..1 The actual contact point details -->
 <use value="[code]"/><!-- 0..1 home | work | temp | old | mobile - purpose of this contact point -->
 <rank value="[positiveInt]"/><!-- 0..1 Specify preferred order of use (1 = highest) -->
 <period><!-- 0..1 Period Time period when the contact point was/is in use --></period>
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint Σ IElementDetails of a Technology mediated contact point (phone, fax, email, etc.)
A system is required if a value is provided.
... system Σ I0..1codephone | fax | email | pager | other
ContactPointSystem (Required)
... value Σ0..1stringThe actual contact point details
... use ?! Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
ContactPointUse (Required)
... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
... period Σ0..1PeriodTime period when the contact point was/is in use

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <system value="[code]"/><!-- ?? 0..1 phone | fax | email | pager | other -->
 <value value="[string]"/><!-- 0..1 The actual contact point details -->
 <use value="[code]"/><!-- 0..1 home | work | temp | old | mobile - purpose of this contact point -->
 <rank value="[positiveInt]"/><!-- 0..1 Specify preferred order of use (1 = highest) -->
 <period><!-- 0..1 Period Time period when the contact point was/is in use --></period>
</[name]>

If capturing a phone, fax or similar contact point, the value should be a properly formatted telephone number according to ITU-T E.123 . However, this is frequently not possible due to legacy data and/or clerical practices when recording contact details. For this reason, phone, fax, page and email addresses are not handled as formal URLs. For other kinds of contacts, the system is "other" and the value SHOULD be a URL so that its use can be determined automatically. Typical URL schemes used in the value are http(s): for web addresses, and URL schemes for various kinds of messaging systems. If the value is not a URL, then human interpretation will be required.

The rank element can be used to specify a preference for the order in which a set of contacts is used. Contacts are ranked with lower values coming before higher values. Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Constraints

  • cpt-2: A system is required if a value is provided. (xpath: not(exists(f:value)) or exists(f:system))

ContactPoint is used in the following places: ConceptMap, Conformance, DataElement, Device, HealthcareService, ImplementationGuide, Location, MessageHeader, NamingSystem, OperationDefinition, Organization, Patient, Person, Practitioner, Questionnaire, RelatedPerson, SearchParameter, StructureDefinition, Subscription, TestScript and ValueSet

1.19.0.15 Timing

See also Examples, Detailed Descriptions and Mappings.

Specifies an event that may occur multiple times. Timing schedules are not used for recording when things did happen, but when they are expected or requested to occur. A Timing schedule can be a list of events and/or criteria for when the event is to happen, which can be expressed in a structured form and/or as a code. When both event and a repeating specification are provided, the list of events should be understood as an interpretation of the information in the repeat structure.

Many systems avoid the complexity of the Timing structure by using a text field for these things (e.g. "Dosage Text"). Those systems do not use the Timing data type. Other systems use a set of 'common' codes - including, but usually not limited to, widely understood acronyms such as "BID". A structured timing specification SHOULD be provided whenever possible, unless the code is BID, TID, QID, AM or PM, which have a ubiquitous meaning.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Timing ΣElementA timing schedule that specifies an event that may occur multiple times
... event Σ0..*dateTimeWhen the event occurs
... repeat Σ I0..1ElementWhen the event is to occur
Either frequency or when can exist, not both
if there's a duration, there needs to be duration units
if there's a period, there needs to be period units
If there's a periodMax, there must be a period
If there's a durationMax, there must be a duration
.... bounds[x] Σ0..1Length/Range of lengths, or (Start and/or end) limits
..... boundsQuantityDuration
..... boundsRangeRange
..... boundsPeriodPeriod
.... count Σ0..1integerNumber of times to repeat
.... duration Σ I0..1decimalHow long when it happens
duration SHALL be a non-negative value
.... durationMax Σ0..1decimalHow long when it happens (Max)
.... durationUnits Σ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
UnitsOfTime (Required)
.... frequency Σ0..1integerEvent occurs frequency times per period
.... frequencyMax Σ0..1integerEvent occurs up to frequencyMax times per period
.... period Σ I0..1decimalEvent occurs frequency times per period
period SHALL be a non-negative value
.... periodMax Σ0..1decimalUpper limit of period (3-4 hours)
.... periodUnits Σ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
UnitsOfTime (Required)
.... when Σ0..1codeRegular life events the event is tied to
EventTiming (Required)
... code Σ0..1CodeableConceptQD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM +
TimingAbbreviation (Preferred)

doco Documentation for this format

UML Diagram

ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*TimingIdentifies specific times when the event occursevent : dateTime [0..*]A code for the timing pattern. Some codes such as BID are ubiquitous, but many institutions define their own additional codescode : CodeableConcept [0..1] « Code for a known / defined timing pattern. (Strength=Preferred)TimingAbbreviation? »RepeatEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedulebounds[x] : Type [0..1] « Quantity(Duration)|Range|Period »A total count of the desired number of repetitionscount : integer [0..1]How long this thing happens for when it happensduration : decimal [0..1]The upper limit of how long this thing happens for when it happensdurationMax : decimal [0..1]The units of time for the duration, in UCUM unitsdurationUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »The number of times to repeat the action within the specified period / period range (i.e. both period and periodMax provided)frequency : integer [0..1]If present, indicates that the frequency is a range - so repeat between [frequency] and [frequencyMax] times within the period or period rangefrequencyMax : integer [0..1]Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the periodperiod : decimal [0..1]If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 daysperiodMax : decimal [0..1]The units of time for the period in UCUM unitsperiodUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »A real world event that the occurrence of the event should be tied towhen : code [0..1] « Real world event that the relating to the schedule. (Strength=Required)EventTiming! »A set of rules that describe when the event should occurrepeat[0..1]

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <event value="[dateTime]"/><!-- 0..* When the event occurs -->
 <repeat>  <!-- 0..1 When the event is to occur -->
  <bounds[x]><!-- 0..1 Quantity(Duration)|Range|Period Length/Range of lengths, or (Start and/or end) limits --></bounds[x]>
  <count value="[integer]"/><!-- 0..1 Number of times to repeat -->
  <duration value="[decimal]"/><!-- 0..1 How long when it happens -->
  <durationMax value="[decimal]"/><!-- 0..1 How long when it happens (Max) -->
  <durationUnits value="[code]"/><!-- 0..1 s | min | h | d | wk | mo | a - unit of time (UCUM) -->
  <frequency value="[integer]"/><!-- 0..1 Event occurs frequency times per period -->
  <frequencyMax value="[integer]"/><!-- 0..1 Event occurs up to frequencyMax times per period -->
  <period value="[decimal]"/><!-- 0..1 Event occurs frequency times per period -->
  <periodMax value="[decimal]"/><!-- 0..1 Upper limit of period (3-4 hours) -->
  <periodUnits value="[code]"/><!-- 0..1 s | min | h | d | wk | mo | a - unit of time (UCUM) -->
  <when value="[code]"/><!-- 0..1 Regular life events the event is tied to -->
 </repeat>
 <code><!-- 0..1 CodeableConcept QD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM + --></code>
</[name]>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Timing ΣElementA timing schedule that specifies an event that may occur multiple times
... event Σ0..*dateTimeWhen the event occurs
... repeat Σ I0..1ElementWhen the event is to occur
Either frequency or when can exist, not both
if there's a duration, there needs to be duration units
if there's a period, there needs to be period units
If there's a periodMax, there must be a period
If there's a durationMax, there must be a duration
.... bounds[x] Σ0..1Length/Range of lengths, or (Start and/or end) limits
..... boundsQuantityDuration
..... boundsRangeRange
..... boundsPeriodPeriod
.... count Σ0..1integerNumber of times to repeat
.... duration Σ I0..1decimalHow long when it happens
duration SHALL be a non-negative value
.... durationMax Σ0..1decimalHow long when it happens (Max)
.... durationUnits Σ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
UnitsOfTime (Required)
.... frequency Σ0..1integerEvent occurs frequency times per period
.... frequencyMax Σ0..1integerEvent occurs up to frequencyMax times per period
.... period Σ I0..1decimalEvent occurs frequency times per period
period SHALL be a non-negative value
.... periodMax Σ0..1decimalUpper limit of period (3-4 hours)
.... periodUnits Σ0..1codes | min | h | d | wk | mo | a - unit of time (UCUM)
UnitsOfTime (Required)
.... when Σ0..1codeRegular life events the event is tied to
EventTiming (Required)
... code Σ0..1CodeableConceptQD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM +
TimingAbbreviation (Preferred)

doco Documentation for this format

UML Diagram

ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*TimingIdentifies specific times when the event occursevent : dateTime [0..*]A code for the timing pattern. Some codes such as BID are ubiquitous, but many institutions define their own additional codescode : CodeableConcept [0..1] « Code for a known / defined timing pattern. (Strength=Preferred)TimingAbbreviation? »RepeatEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedulebounds[x] : Type [0..1] « Quantity(Duration)|Range|Period »A total count of the desired number of repetitionscount : integer [0..1]How long this thing happens for when it happensduration : decimal [0..1]The upper limit of how long this thing happens for when it happensdurationMax : decimal [0..1]The units of time for the duration, in UCUM unitsdurationUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »The number of times to repeat the action within the specified period / period range (i.e. both period and periodMax provided)frequency : integer [0..1]If present, indicates that the frequency is a range - so repeat between [frequency] and [frequencyMax] times within the period or period rangefrequencyMax : integer [0..1]Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the periodperiod : decimal [0..1]If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 daysperiodMax : decimal [0..1]The units of time for the period in UCUM unitsperiodUnits : code [0..1] « A unit of time (units from UCUM). (Strength=Required)UnitsOfTime! »A real world event that the occurrence of the event should be tied towhen : code [0..1] « Real world event that the relating to the schedule. (Strength=Required)EventTiming! »A set of rules that describe when the event should occurrepeat[0..1]

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <event value="[dateTime]"/><!-- 0..* When the event occurs -->
 <repeat>  <!-- 0..1 When the event is to occur -->
  <bounds[x]><!-- 0..1 Quantity(Duration)|Range|Period Length/Range of lengths, or (Start and/or end) limits --></bounds[x]>
  <count value="[integer]"/><!-- 0..1 Number of times to repeat -->
  <duration value="[decimal]"/><!-- 0..1 How long when it happens -->
  <durationMax value="[decimal]"/><!-- 0..1 How long when it happens (Max) -->
  <durationUnits value="[code]"/><!-- 0..1 s | min | h | d | wk | mo | a - unit of time (UCUM) -->
  <frequency value="[integer]"/><!-- 0..1 Event occurs frequency times per period -->
  <frequencyMax value="[integer]"/><!-- 0..1 Event occurs up to frequencyMax times per period -->
  <period value="[decimal]"/><!-- 0..1 Event occurs frequency times per period -->
  <periodMax value="[decimal]"/><!-- 0..1 Upper limit of period (3-4 hours) -->
  <periodUnits value="[code]"/><!-- 0..1 s | min | h | d | wk | mo | a - unit of time (UCUM) -->
  <when value="[code]"/><!-- 0..1 Regular life events the event is tied to -->
 </repeat>
 <code><!-- 0..1 CodeableConcept QD | QOD | Q4H | Q6H | BID | TID | QID | AM | PM + --></code>
</[name]>

If the timing schedule has repeating criteria, the repeat can occur a given number of times per the specified duration or in relation to some real world event. If no end condition is specified, the schedule will terminate on some criteria that are expressed elsewhere.

If duration is provided as a Range, the unit in the Range SHALL be a UCUM unit of time.

This table summarises some common uses of the Timing Data Type criteria.

description duration durationUnits frequency frequencyMax period periodUnits periodMax when bounds[x]
BID 2 1 d
TID 3 1 d
QID 4 1 d
Q6H 1 6 h
Every 8 hours 1 8 h
Every 7 days 1 7 d
3 times a day 3 1 d
3-4 times a day 3 4 1 d
Every 4-6 hours 1 4 h 6
Every 21 days for 1 hour 1 hr 1 21 d
Three times a week for ½ hour 0.5 hr 3 1 wk
With breakfast CM
For 5 minutes, 10 minutes before meals 5 min 10 min AC
TID, for 14 days 3 1 d Duration = 14 days
BID, start on 7/1/2015 at 1:00 PM 2 1 d Period, low = 2015-07-01T13:00:00

Constraints

  • tim-1: On Timing.repeat: if there's a duration, there needs to be duration units (xpath on f:Timing/f:repeat: not(exists(f:duration)) or exists(f:durationUnits))
  • tim-2: On Timing.repeat: if there's a period, there needs to be period units (xpath on f:Timing/f:repeat: not(exists(f:period)) or exists(f:periodUnits))
  • tim-3: On Timing.repeat: Either frequency or when can exist, not both (xpath on f:Timing/f:repeat: not((f:period or f:frequency) and f:when))
  • tim-4: On Timing.repeat.duration: duration SHALL be a non-negative value (xpath on f:Timing/f:repeat/f:duration: @value >= 0 or not(@value))
  • tim-5: On Timing.repeat.period: period SHALL be a non-negative value (xpath on f:Timing/f:repeat/f:period: @value >= 0 or not(@value))
  • tim-6: On Timing.repeat: If there's a periodMax, there must be a period (xpath on f:Timing/f:repeat: not(exists(f:periodMax)) or exists(f:period))
  • tim-7: On Timing.repeat: If there's a durationMax, there must be a duration (xpath on f:Timing/f:repeat: not(exists(f:durationMax)) or exists(f:duration))

Timing is used in the following places: CarePlan, DeviceMetric, DeviceUseRequest, DeviceUseStatement, MedicationDispense, MedicationOrder, MedicationStatement, NutritionOrder, Order, ProcedureRequest and SupplyRequest

1.19.0.16 Signature

See also Examples, Detailed Descriptions and Mappings.

A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWT), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Signature ΣElementA digital Signature - XML DigSig, JWT, Graphical image of signature, etc.
... type Σ1..*CodingIndication of the reason the entity signed the object(s)
Signature Type Codes (Preferred)
... when Σ1..1instantWhen the signature was created
... who[x] Σ1..1Who signed the signature
.... whoUriuri
.... whoReferenceReference(Practitioner | RelatedPerson | Patient | Device | Organization)
... contentType Σ1..1codeThe technical format of the signature
MimeType (Required)
... blob Σ1..1base64BinaryThe actual signature content (XML DigSig. JWT, picture, etc.)

doco Documentation for this format

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Signature ΣElementA digital Signature - XML DigSig, JWT, Graphical image of signature, etc.
... type Σ1..*CodingIndication of the reason the entity signed the object(s)
Signature Type Codes (Preferred)
... when Σ1..1instantWhen the signature was created
... who[x] Σ1..1Who signed the signature
.... whoUriuri
.... whoReferenceReference(Practitioner | RelatedPerson | Patient | Device | Organization)
... contentType Σ1..1codeThe technical format of the signature
MimeType (Required)
... blob Σ1..1base64BinaryThe actual signature content (XML DigSig. JWT, picture, etc.)

doco Documentation for this format

Constraints

Note: One consequence of signing the document is that URLs, identifiers and internal references are frozen and cannot be changed. This might be a desired feature, but it may also cripple interoperability between closed ecosystems where re-identification frequently occurs. For this reason, it is recommended that systems consider carefully the impact of any signature processes. The impact of signatures on Document bundles and their related processes is the most well understood use of digital signatures.

 

1.19.0.16.1 XML Signature rules

When the signature is an XML Digital Signature (contentType = application/signature+xml), the following rules apply:

  • The Signature.blob is base64 encoded XML-Signature
  • The XML-Signature is a Detached Signature (where the content that is signed is separate from the signature itself)
  • The Signature SHOULD conform to XAdES-X-L for support of Long Term signatures. The XAdES-X-L specification adds the timestamp of the signing, inclusion of the signing certificate, and statement of revocation
  • When FHIR Resources are signed, the signature is accross the Canonical XML form of the resource(s)
  • The Signature SHOULD use the hashing algorithm sha256. Signature validation policy will apply to the signature and determine acceptability
  • The Signature SHALL include a "CommitmentTypeIndication" element for the Purpose(s) of Signature. The Purpose can be the action being attested to, or the role associated with the signature. The value shall come from ASTM E1762-95(2013). The Signature.type shall contain the same values as committmentTypeIndication

There are three levels of signature verification:

  1. verifying that the Digital Signature block itself has integrity through verifying the signature across the XML-Signature,
  2. confirming that the signer was authentic, not revoked, and appropriate to the signature purpose,
  3. confirming that the signed content of interest is unmodified using the hash algorithm.

Deviations from these guidelines would need to be expressed in site policy, and would be enumerated in the XML-Signature block. For example some environments may choose a different XAdES profile, hashing algorithm, policy identifier, or signature purpose vocabulary.

Signature is used in the following places: Bundle and Provenance

1.19.0.17 Annotation

See also Examples, Detailed Descriptions and Mappings.

A text note which also contains information about who made the statement and when.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Annotation ΣElementText node with attribution
... author[x] Σ0..1Individual responsible for the annotation
.... authorReferenceReference(Practitioner | Patient | RelatedPerson)
.... authorStringstring
... time Σ0..1dateTimeWhen the annotation was made
... text Σ1..1stringThe annotation - text content

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <author[x]><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson)|string Individual responsible for the annotation --></author[x]>
 <time value="[dateTime]"/><!-- 0..1 When the annotation was made -->
 <text value="[string]"/><!-- 1..1 The annotation  - text content -->
</[name]>

JSON Template


{doco
  // from Element: extension
  // author[x]: Individual responsible for the annotation. One of these 2:
  "authorReference" : { Reference(Practitioner|Patient|RelatedPerson) },
  "authorString" : "<string>",
  "time" : "<dateTime>", // When the annotation was made
  "text" : "<string>" // R!  The annotation  - text content
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Annotation ΣElementText node with attribution
... author[x] Σ0..1Individual responsible for the annotation
.... authorReferenceReference(Practitioner | Patient | RelatedPerson)
.... authorStringstring
... time Σ0..1dateTimeWhen the annotation was made
... text Σ1..1stringThe annotation - text content

doco Documentation for this format

XML Template

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <author[x]><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson)|string Individual responsible for the annotation --></author[x]>
 <time value="[dateTime]"/><!-- 0..1 When the annotation was made -->
 <text value="[string]"/><!-- 1..1 The annotation  - text content -->
</[name]>

JSON Template

{doco
  // from Element: extension
  // author[x]: Individual responsible for the annotation. One of these 2:
  "authorReference" : { Reference(Practitioner|Patient|RelatedPerson) },
  "authorString" : "<string>",
  "time" : "<dateTime>", // When the annotation was made
  "text" : "<string>" // R!  The annotation  - text content
}

Systems that do not have structured annotations simply communicate a single annotation with no author or time.

This element may need to be included in narrative because of the potential for modifying information.

Annotations SHOULD NOT be used to communicate "modifying" information that could be computable (this is a SHOULD because enforcing user behavior is nearly impossible).

Annotation is used in the following places: AllergyIntolerance, CarePlan, Device, DiagnosticOrder, FamilyMemberHistory, Goal, Immunization, Procedure and ProcedureRequest

1.19.0.18 Open Type Element

Some elements do not have a specified type. The type is represented by the wildcard symbol "*". In these cases, the element type may be one of the following:

The element name ends with "[x]", and this is replaced with the Title cased name of the data type.

Open references are used in the following places: Parameters

1.19.0.19 Other Types

The following types are defined as part of the data types, but are documented elsewhere in the specification:

ElementExtensions - as described for all elements: additional information that is not part of the basic definition of the resource / typeextension : Extension 0..*ExtensionSource of the definition for the extension code - a logical name or a URLurl : uri [1..1]Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list)value[x] : * [0..1]NarrativeThe status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional datastatus : code [1..1] « The status of a resource narrative (Strength=Required)NarrativeStatus! »The actual narrative content, a stripped down version of XHTMLdiv : xhtml [1..1]ReferenceA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resourcesreference : string [0..1]Plain text narrative that identifies the resource in addition to the resource referencedisplay : string [0..1]
  • Resource - the conceptual base class for all resources
  • Reference - for references from one resource to another
  • Extension - used to convey additional data in a resource
  • Narrative - conveys a human-readable representation of the content of a resource