This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Orders and Observations ![]() | Maturity Level: 1 | Trial Use | Security Category: Business | Compartments: No defined compartments |
Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service.
An instance of ObservationDefinition represents the definitional aspects of a kind of observation. This resource is used in a catalog of products or services for healthcare. It represents a set of constraints applicable to the value produced by observations of this kind. It helps the consumer of the results of observations of that kind, to interpret properly these results. If one wants to technically constrain an Observation resource for a particular use case across implementers, a profile is the preferred option and may include profiling on ObservationDefinition and Observation.
For instance, in a catalog of laboratory in vitro diagnostic services, the ObservationDefinition resources describe the observations that should be provided by the orderer alongside with an ordered service (questions asked at order entry or at specimen collection, prior results) as well as the observations that will be reported once the service has been performed.
Observation Definition resources can be used to describe observations which may need to be evaluated in order to determine whether a specific medicine can be administered or held (e.g., weight, lab value result) and provide guidance on the dose to be administered (e.g., sliding scale insulin dose).
In the catalog of tests of an in vitro diagnostic device, ObservationDefinition resources can be used to characterize (absolute range, unit, decimal precision, critical values ...) the observations that will be produced by the IVD tests performed by the device.
ObservationDefinition may be used to characterize observations from any discipline.
An ObservationDefinition resource provides the definitional characteristics for a certain kind of observation. Each time that kind of observation is collected and recorded it is instantiated as an Observation resource, which conforms to these definitional characteristics. Thus, there is a relationship between ObservationDefinition and Observation: The latter may instantiate the former.
When an Observation instantiates an ObservationDefinition, the elements of the Observation resource are expected to inherit their content from the corresponding definitional elements declared in the ObservationDefinition resource:
ObservationDefinition can specify units allowed for the valueQuantity element by setting ObservationDefinition.permittedUnit.
ObservationDefinitions are only to be used when describing the contents of an observation (including observations in order catalogs or panels). When additional structure, sequence, or rules are needed, the Questionnaire resource should be used.
Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) , the spreadsheet version & the dependency analysis
Path | ValueSet | Type | Documentation |
---|---|---|---|
ObservationDefinition.versionAlgorithm[x] | VersionAlgorithm | Extensible | Indicates the mechanism used to compare versions to determine which is more current. |
ObservationDefinition.status | PublicationStatus | Required | The lifecycle status of an artifact. |
ObservationDefinition.jurisdiction | JurisdictionValueSet | Extensible | This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used. Note: The codes for countries and country subdivisions are taken from ISO 3166 |
ObservationDefinition.category | ObservationCategoryCodes | Example | Observation Category codes. |
ObservationDefinition.code | LOINCCodes (a valid code from LOINC ![]() |
Example | This value set includes all LOINC codes |
ObservationDefinition.permittedDataType | ObservationDataType | Required | Permitted data type for observation value. |
ObservationDefinition.bodySite | SNOMEDCTBodyStructures | Example | This value set includes all codes from SNOMED CT |
ObservationDefinition.method | ObservationMethods | Example | Observation Method codes from SNOMED CT |
ObservationDefinition.permittedUnit | UCUMCodes (a valid code from UCUM ![]() |
Preferred | Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes |
ObservationDefinition.qualifiedValue.context | ObservationReferenceRangeMeaningCodes | Extensible | This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population. |
ObservationDefinition.qualifiedValue.appliesTo | ObservationReferenceRangeAppliesToCodes | Example | This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to. |
ObservationDefinition.qualifiedValue.gender | AdministrativeGender | Required | The gender of a person used for administrative purposes. |
ObservationDefinition.qualifiedValue.rangeCategory | ObservationRangeCategory | Required | Codes identifying the category of observation range. |
ObservationDefinition.qualifiedValue.interpretation | ObservationInterpretationCodes (a valid code from ObservationInterpretation ![]() |
Extensible | A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. |
ObservationDefinition.component.code | LOINCCodes (a valid code from LOINC ![]() |
Example | This value set includes all LOINC codes |
ObservationDefinition.component.permittedDataType | ObservationDataType | Required | Permitted data type for observation value. |
ObservationDefinition.component.permittedUnit | UCUMCodes (a valid code from UCUM ![]() |
Preferred | Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes |
UniqueKey | Level | Location | Description | Expression |
![]() | Warning | (base) | Name should be usable as an identifier for the module by machine processing applications such as code generation | name.exists() implies name.matches('^[A-Z]([A-Za-z0-9_]){1,254}$') |
![]() | Rule | (base) | If permittedUnit exists, then permittedDataType=Quantity must exist. | permittedUnit.exists() implies permittedDataType.exists(value = 'Quantity') |
![]() | Rule | ObservationDefinition.component | If permittedUnit exists, then permittedDataType=Quantity must exist. | permittedUnit.exists() implies permittedDataType.exists(value = 'Quantity') |
Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
Name | Type | Description | Expression | In Common |
category | token | Category (class) of observation | ObservationDefinition.category | |
code | token | Observation code | ObservationDefinition.code | |
experimental | token | Not for genuine usage (true) | ObservationDefinition.experimental | |
identifier | token | The unique identifier associated with the specimen definition | ObservationDefinition.identifier | 35 Resources |
method | token | Method of observation | ObservationDefinition.method | |
status | token | Publication status of the ObservationDefinition: draft, active, retired, unknown | ObservationDefinition.status | 35 Resources |
title | string | Human-friendly name of the ObservationDefinition | ObservationDefinition.title | 28 Resources |
url | uri | The uri that identifies the observation definition | ObservationDefinition.url | 34 Resources |