- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
StructureDefinition UKCore-Observation-Lab
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-Observation-Lab | active | 2.0.1 | 2024-07-23 | This profile defines the UK constraints and extensions on the International FHIR resource Observation, in order to represent an individual laboratory test and result value. These tests can be grouped together using the UKCore-Observation-Group-Lab profile. |
Profile_Purpose |
---|
To provide the minimum expectations for each individual laboratory test. |
Detailed Descriptions
Observation | |
Definition | Measurements and simple assertions made about a patient, device or other subject. |
Cardinality | 0...* |
Alias | Vital Signs, Measurement, Results, Tests |
Comments | Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc. |
Invariants |
|
Mappings |
|
Observation.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Observation.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Observation.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
Observation.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Invariants |
|
Mappings |
|
Observation.text | |
Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
Invariants |
|
Mappings |
|
Observation.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
Mappings |
|
Observation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5 | |
Definition | Identifies the observation(s) that triggered the performance of this observation. |
Cardinality | 0...* |
Type | Extension(Complex) |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.extension:triggeredByR5.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 2...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:observation | |
Definition | Reference to the triggering observation. |
Cardinality | 1...1 |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:observation.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.extension:triggeredByR5.extension:observation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:observation.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | observation |
Mappings |
|
Observation.extension:triggeredByR5.extension:observation.value[x] | |
Definition | A reference to the triggering observation. |
Cardinality | 1...1 |
Type | Reference(Observation) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:type | |
Definition | The type of trigger. Reflex | Repeat | Re-run. |
Cardinality | 1...1 |
Type | Extension |
Binding | http://hl7.org/fhir/ValueSet/observation-triggeredbytype (required) |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.extension:triggeredByR5.extension:type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:type.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | type |
Mappings |
|
Observation.extension:triggeredByR5.extension:type.value[x] | |
Definition | The type of trigger. Reflex | Repeat | Re-run |
Cardinality | 1...1 |
Type | code |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:reason | |
Definition | Provides the reason why this observation was performed as a result of the observation(s) referenced. |
Cardinality | 0...1 |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:reason.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.extension:triggeredByR5.extension:reason.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.extension:reason.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | reason |
Mappings |
|
Observation.extension:triggeredByR5.extension:reason.value[x] | |
Definition | Provides the reason why this observation was performed as a result of the observation referenced. |
Cardinality | 1...1 |
Type | string |
Invariants |
|
Mappings |
|
Observation.extension:triggeredByR5.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.triggeredBy |
Mappings |
|
Observation.extension:triggeredByR5.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 0...0 |
Type | base64Binary |
Invariants |
|
Mappings |
|
Observation.extension:bodyStructureR5 | |
Definition | Indicates the body structure on the subject's body where the observation was made (i.e. the target site). |
Cardinality | 0...1 |
Type | Extension(Reference(BodyStructure)) |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.identifier | |
Definition | A unique identifier assigned to this observation. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Requirements | Allows observations to be distinguished and referenced. |
Invariants |
|
Mappings |
|
Observation.basedOn | |
Definition | A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. |
Cardinality | 0...* |
Type | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) |
Summary | True |
Alias | Fulfills |
Requirements | Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Observation.partOf | |
Definition | A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. |
Cardinality | 0...* |
Type | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) |
Summary | True |
Alias | Container |
Comments | To link an Observation to an Encounter use |
Invariants |
|
Mappings |
|
Observation.status | |
Definition | The status of the result value. |
Cardinality | 1...1 |
Type | code |
Binding | Codes providing the status of an observation. |
Must Support | True |
Modifier | True |
Summary | True |
Requirements | Need to track the status of individual results. Some results are finalized before the whole report is finalized. |
Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
Observation.category | |
Definition | A code that classifies the general type of observation being made. |
Cardinality | 1...* |
Type | CodeableConcept |
Binding | Codes for high level observation categories. |
Must Support | True |
Requirements | Used for filtering what observations are retrieved and displayed. |
Comments | In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set. |
Slicing | Unordered, Open, by coding.code(Value) |
Invariants |
|
Mappings |
|
Observation.category:laboratory | |
Definition | A code that classifies the general type of observation being made. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Codes for high level observation categories. |
Must Support | True |
Requirements | Used for filtering what observations are retrieved and displayed. |
Comments | In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set. |
Invariants |
|
Mappings |
|
Observation.category:laboratory.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.category:laboratory.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.category:laboratory.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Observation.category:laboratory.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.category:laboratory.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.category:laboratory.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Fixed Value | http://terminology.hl7.org/CodeSystem/observation-category |
Mappings |
|
Observation.category:laboratory.coding.version | |
Definition | 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 exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Observation.category:laboratory.coding.code | |
Definition | 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). |
Cardinality | 0...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Fixed Value | laboratory |
Mappings |
|
Observation.category:laboratory.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Observation.category:laboratory.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Observation.category:laboratory.text | |
Definition | 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 user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Observation.code | |
Definition | Describes what was observed. Sometimes this is called the observation "name". |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A code from the SNOMED Clinical Terminology UK coding system regarding laboratory medicine test results |
Must Support | True |
Summary | True |
Alias | Name |
Requirements | Knowing what kind of observation is being made is essential to understanding the observation. |
Comments | All code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. |
Invariants |
|
Mappings |
|
Observation.subject | |
Definition | The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation. |
Cardinality | 0...1 |
Type | Reference(Patient) |
Summary | True |
Requirements | Observations have no value if you don't know who or what they're about. |
Comments | One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated. |
Invariants |
|
Mappings |
|
Observation.focus | |
Definition | The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus. |
Cardinality | 0...* |
Type | Reference(Resource) |
Summary | True |
Comments | Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use |
Invariants |
|
Mappings |
|
Observation.encounter | |
Definition | The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Summary | True |
Alias | Context |
Requirements | For some observations it may be important to know the link between an observation and a particular encounter. |
Comments | This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests). |
Invariants |
|
Mappings |
|
Observation.effective[x] | |
Definition | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Alias | Occurrence |
Requirements | Knowing when an observation was deemed true is important to its relevance as well as determining trends. |
Comments | At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the Timing datatype which allow the measurement to be tied to regular life events. |
Invariants |
|
Mappings |
|
Observation.issued | |
Definition | The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. |
Cardinality | 0...1 |
Type | instant |
Summary | True |
Comments | For Observations that don’t require review and verification, it may be the same as the |
Invariants |
|
Mappings |
|
Observation.performer | |
Definition | Who was responsible for asserting the observed value as "true". |
Cardinality | 0...* |
Type | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) |
Summary | True |
Requirements | May give a degree of confidence in the observation and also indicates where follow-up questions should be directed. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Observation.value[x] | |
Definition | The information determined as a result of making the observation, if the information has a simple value. |
Cardinality | 0...1 |
Type | Quantity |
Summary | True |
Requirements | An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. |
Comments | An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the Notes section below. |
Invariants |
|
Mappings |
|
Observation.dataAbsentReason | |
Definition | Provides a reason why the expected value in the element Observation.value[x] is missing. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes specifying why the result ( |
Requirements | For many results it is necessary to handle exceptional values in measurements. |
Comments | Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values. |
Invariants |
|
Mappings |
|
Observation.interpretation | |
Definition | A categorical assessment of an observation value. For example, high, low, normal. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes identifying interpretations of observations. |
Alias | Abnormal Flag |
Requirements | For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. |
Comments | Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. |
Invariants |
|
Mappings |
|
Observation.note | |
Definition | Comments about the observation or the results. |
Cardinality | 0...* |
Type | Annotation |
Requirements | Need to be able to provide free text additional information. |
Comments | May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. |
Invariants |
|
Mappings |
|
Observation.bodySite | |
Definition | Indicates the site on the subject's body where the observation was made (i.e. the target site). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. |
Comments | Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension bodySite. |
Invariants |
|
Mappings |
|
Observation.method | |
Definition | Indicates the mechanism used to perform the observation. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Methods for simple observations. |
Requirements | In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results. |
Comments | Only used if not implicit in code for Observation.code. |
Invariants |
|
Mappings |
|
Observation.specimen | |
Definition | The specimen that was used when this observation was made. |
Cardinality | 0...1 |
Type | Reference(Specimen) |
Comments | Should only be used if not implicit in code found in |
Invariants |
|
Mappings |
|
Observation.device | |
Definition | The device used to generate the observation data. |
Cardinality | 0...1 |
Type | Reference(Device | DeviceMetric) |
Comments | Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant. |
Invariants |
|
Mappings |
|
Observation.referenceRange | |
Definition | Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two `referenceRange` elements would be used. |
Cardinality | 0...* |
Type | BackboneElement |
Requirements | Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts. |
Comments | Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties. |
Invariants |
|
Mappings |
|
Observation.referenceRange.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.referenceRange.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.referenceRange.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.referenceRange.low | |
Definition | The value of the low bound of the reference range. The low bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the low bound is omitted, it is assumed to be meaningless (e.g. reference range is <=2.3). |
Cardinality | 0...1 |
Type | SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Observation.referenceRange.high | |
Definition | The value of the high bound of the reference range. The high bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the high bound is omitted, it is assumed to be meaningless (e.g. reference range is >= 2.3). |
Cardinality | 0...1 |
Type | SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Observation.referenceRange.type | |
Definition | Codes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Code for the meaning of a reference range. |
Requirements | Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation. |
Comments | This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed. |
Invariants |
|
Mappings |
|
Observation.referenceRange.appliesTo | |
Definition | Codes to indicate the target population this reference range applies to. For example, a reference range may be based on the normal population or a particular sex or race. Multiple `appliesTo` are interpreted as an "AND" of the target populations. For example, to represent a target population of African American females, both a code of female and a code for African American would be used. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes identifying the population the reference range applies to. |
Requirements | Need to be able to identify the target population for proper interpretation. |
Comments | This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed. |
Invariants |
|
Mappings |
|
Observation.referenceRange.age | |
Definition | The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so. |
Cardinality | 0...1 |
Type | Range |
Requirements | Some analytes vary greatly over age. |
Comments | The stated low and high value are assumed to have arbitrarily high precision when it comes to determining which values are in the range. I.e. 1.99 is not in the range 2 -> 3. |
Invariants |
|
Mappings |
|
Observation.referenceRange.text | |
Definition | Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" or a list or table of "normals". |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Observation.hasMember | |
Definition | This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. |
Cardinality | 0...* |
Type | Reference(Observation | QuestionnaireResponse | MolecularSequence) |
Summary | True |
Comments | When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see Notes below. Note that a system may calculate results from QuestionnaireResponse into a final score and represent the score as an Observation. |
Invariants |
|
Mappings |
|
Observation.derivedFrom | |
Definition | The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. |
Cardinality | 0...* |
Type | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) |
Summary | True |
Comments | All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see Notes below. |
Invariants |
|
Mappings |
|
Observation.component | |
Definition | Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Requirements | Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation. |
Comments | For a discussion on the ways Observations can be assembled in groups together see Notes below. |
Invariants |
|
Mappings |
|
Observation.component.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Observation.component.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Observation.component.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Observation.component.code | |
Definition | Describes what was observed. Sometimes this is called the observation "code". |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Codes identifying names of simple observations. |
Summary | True |
Requirements | Knowing what kind of observation is being made is essential to understanding the observation. |
Comments | All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. |
Invariants |
|
Mappings |
|
Observation.component.value[x] | |
Definition | The information determined as a result of making the observation, if the information has a simple value. |
Cardinality | 0...1 |
Type | Quantity |
Summary | True |
Requirements | An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. |
Comments | Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the Notes section below. |
Invariants |
|
Mappings |
|
Observation.component.dataAbsentReason | |
Definition | Provides a reason why the expected value in the element Observation.component.value[x] is missing. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes specifying why the result ( |
Requirements | For many results it is necessary to handle exceptional values in measurements. |
Comments | "Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "test not done". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Because of these options, use-case agreements are required to interpret general observations for exceptional values. |
Invariants |
|
Mappings |
|
Observation.component.interpretation | |
Definition | A categorical assessment of an observation value. For example, high, low, normal. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes identifying interpretations of observations. |
Alias | Abnormal Flag |
Requirements | For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. |
Comments | Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. |
Invariants |
|
Mappings |
|
Observation.component.referenceRange | |
Definition | Guidance on how to interpret the value by comparison to a normal or recommended range. |
Cardinality | 0...* |
Type | see (referenceRange) |
Requirements | Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts. |
Comments | Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties. |
Mappings |
|
Table View
Observation | .. | |
Observation.extension | Extension | .. |
Observation.extension.extension | .. | |
Observation.extension.extension.value[x] | .. | |
Observation.extension.extension | .. | |
Observation.extension.extension.value[x] | .. | |
Observation.extension.extension | .. | |
Observation.extension.extension.value[x] | .. | |
Observation.extension | Extension | .. |
Observation.status | .. | |
Observation.category | 1.. | |
Observation.category | 1..1 | |
Observation.category.coding | .. | |
Observation.category.coding.system | .. | |
Observation.category.coding.code | .. | |
Observation.code | .. | |
Observation.subject | Reference(Patient) | .. |
Observation.bodySite | .. | |
Observation.method | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-Observation-Lab" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-Observation-Lab" /> <version value="2.0.1" /> <name value="UKCoreObservationLab" /> <title value="UK Core Observation Lab" /> <status value="active" /> <date value="2024-07-23" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [Observation](https://hl7.org/fhir/R4/Observation.html), in order to represent an individual laboratory test and result value. These tests can be grouped together using the UKCore-Observation-Group-Lab profile." /> <purpose value="To provide the minimum expectations for each individual laboratory test." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Observation" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Observation" /> <derivation value="constraint" /> <differential> <element id="Observation"> <path value="Observation" /> <constraint> <key value="ukcore-obs-lab-001" /> <severity value="warning" /> <human value="Either `value`, `dataAbsentReason` or `note` SHOULD be populated" /> <expression value="value.exists() or dataAbsentReason.exists() or note.exists()" /> </constraint> </element> <element id="Observation.extension:triggeredByR5"> <path value="Observation.extension" /> <sliceName value="triggeredByR5" /> <short value="Triggering observation(s). This is a R5 backport." /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.triggeredBy" /> </type> </element> <element id="Observation.extension:triggeredByR5.extension:observation"> <path value="Observation.extension.extension" /> <sliceName value="observation" /> </element> <element id="Observation.extension:triggeredByR5.extension:observation.value[x]"> <path value="Observation.extension.extension.value[x]" /> <short value="Triggering observation." /> <definition value="A reference to the triggering observation." /> </element> <element id="Observation.extension:triggeredByR5.extension:type"> <path value="Observation.extension.extension" /> <sliceName value="type" /> </element> <element id="Observation.extension:triggeredByR5.extension:type.value[x]"> <path value="Observation.extension.extension.value[x]" /> <short value="The type of trigger. Reflex | Repeat | Re-run" /> <definition value="The type of trigger. Reflex | Repeat | Re-run" /> </element> <element id="Observation.extension:triggeredByR5.extension:reason"> <path value="Observation.extension.extension" /> <sliceName value="reason" /> </element> <element id="Observation.extension:triggeredByR5.extension:reason.value[x]"> <path value="Observation.extension.extension.value[x]" /> <short value="Reason that the observation was triggered." /> <definition value="Provides the reason why this observation was performed as a result of the observation referenced." /> </element> <element id="Observation.extension:bodyStructureR5"> <path value="Observation.extension" /> <sliceName value="bodyStructureR5" /> <short value="Observed body structure. This is a R5 backport." /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.bodyStructure" /> </type> </element> <element id="Observation.status"> <path value="Observation.status" /> <short value="The status of the result value." /> <mustSupport value="true" /> </element> <element id="Observation.category"> <path value="Observation.category" /> <slicing> <discriminator> <type value="value" /> <path value="coding.code" /> </discriminator> <rules value="open" /> </slicing> <short value="A code that classifies the general type of observation being made." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Observation.category:laboratory"> <path value="Observation.category" /> <sliceName value="laboratory" /> <short value="A mandatory code, to identify this observation as being Lab related." /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Observation.category:laboratory.coding.system"> <path value="Observation.category.coding.system" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/observation-category" /> </element> <element id="Observation.category:laboratory.coding.code"> <path value="Observation.category.coding.code" /> <fixedCode value="laboratory" /> </element> <element id="Observation.code"> <path value="Observation.code" /> <short value="The type of lab related observation (code / type)." /> <mustSupport value="true" /> <binding> <strength value="preferred" /> <description value="A code from the SNOMED Clinical Terminology UK coding system regarding laboratory medicine test results" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-PathologyAndLaboratoryMedicineObservables" /> </binding> </element> <element id="Observation.subject"> <path value="Observation.subject" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> </type> </element> <element id="Observation.bodySite"> <path value="Observation.bodySite" /> <binding> <strength value="preferred" /> </binding> </element> <element id="Observation.method"> <path value="Observation.method" /> <binding> <strength value="preferred" /> </binding> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-Observation-Lab", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-Observation-Lab", "version": "2.0.1", "name": "UKCoreObservationLab", "title": "UK Core Observation Lab", "status": "active", "date": "2024-07-23", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [Observation](https://hl7.org/fhir/R4/Observation.html), in order to represent an individual laboratory test and result value. These tests can be grouped together using the UKCore-Observation-Group-Lab profile.", "purpose": "To provide the minimum expectations for each individual laboratory test.", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Observation", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Observation", "derivation": "constraint", "differential": { "element": [ { "id": "Observation", "path": "Observation", "constraint": [ { "key": "ukcore-obs-lab-001", "severity": "warning", "human": "Either `value`, `dataAbsentReason` or `note` SHOULD be populated", "expression": "value.exists() or dataAbsentReason.exists() or note.exists()" } ] }, { "id": "Observation.extension:triggeredByR5", "path": "Observation.extension", "sliceName": "triggeredByR5", "short": "Triggering observation(s). This is a R5 backport.", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.triggeredBy" ] } ] }, { "id": "Observation.extension:triggeredByR5.extension:observation", "path": "Observation.extension.extension", "sliceName": "observation" }, { "id": "Observation.extension:triggeredByR5.extension:observation.value[x]", "path": "Observation.extension.extension.value[x]", "short": "Triggering observation.", "definition": "A reference to the triggering observation." }, { "id": "Observation.extension:triggeredByR5.extension:type", "path": "Observation.extension.extension", "sliceName": "type" }, { "id": "Observation.extension:triggeredByR5.extension:type.value[x]", "path": "Observation.extension.extension.value[x]", "short": "The type of trigger. Reflex | Repeat | Re-run", "definition": "The type of trigger. Reflex | Repeat | Re-run" }, { "id": "Observation.extension:triggeredByR5.extension:reason", "path": "Observation.extension.extension", "sliceName": "reason" }, { "id": "Observation.extension:triggeredByR5.extension:reason.value[x]", "path": "Observation.extension.extension.value[x]", "short": "Reason that the observation was triggered.", "definition": "Provides the reason why this observation was performed as a result of the observation referenced." }, { "id": "Observation.extension:bodyStructureR5", "path": "Observation.extension", "sliceName": "bodyStructureR5", "short": "Observed body structure. This is a R5 backport.", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.bodyStructure" ] } ] }, { "id": "Observation.status", "path": "Observation.status", "short": "The status of the result value.", "mustSupport": true }, { "id": "Observation.category", "path": "Observation.category", "slicing": { "discriminator": [ { "type": "value", "path": "coding.code" } ], "rules": "open" }, "short": "A code that classifies the general type of observation being made.", "min": 1, "mustSupport": true }, { "id": "Observation.category:laboratory", "path": "Observation.category", "sliceName": "laboratory", "short": "A mandatory code, to identify this observation as being Lab related.", "min": 1, "max": "1", "mustSupport": true }, { "id": "Observation.category:laboratory.coding.system", "path": "Observation.category.coding.system", "fixedUri": "http://terminology.hl7.org/CodeSystem/observation-category" }, { "id": "Observation.category:laboratory.coding.code", "path": "Observation.category.coding.code", "fixedCode": "laboratory" }, { "id": "Observation.code", "path": "Observation.code", "short": "The type of lab related observation (code / type).", "mustSupport": true, "binding": { "strength": "preferred", "description": "A code from the SNOMED Clinical Terminology UK coding system regarding laboratory medicine test results", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-PathologyAndLaboratoryMedicineObservables" } }, { "id": "Observation.subject", "path": "Observation.subject", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ] } ] }, { "id": "Observation.bodySite", "path": "Observation.bodySite", "binding": { "strength": "preferred" } }, { "id": "Observation.method", "path": "Observation.method", "binding": { "strength": "preferred" } } ] } }
Feedback
Click here to:Report issue for UKCore-Observation-Lab, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Example Usage Scenarios
The following are example usage scenarios for the UK Core Observation profile:
- Query and retrieve a patient's laboratory observations
- Record or update a patient's laboratory observations
The Observation-Lab profile is for individual laboratory tests (Observation-Lab) which may form a larger set of tests, for example a urea and electrolyte test that contains many sub tests, or as a single test, for example Serum ferritin level.
The workflow below shows a possible way to group a set of related laboratory observations into the derived Profile UKCore-Observation-Group-Lab, which is then referenced within a diagnostic report. Seperate laboratory observations MAY be directly referenced within the diagnostic report.
Depending upon the countries or trusts workflow, an alternative is to have any separate laboratory observations referenced in a Profile UKCore-Observation-Group-Lab before being referenced in the diagnostic report. Although this creates extra resources it standardises the workflow.
Profile Specific Implementation Guidance:
Mandatory and Must Support Data Elements
The following elements are identified as MustSupport, and it is expected that consumers and suppliers SHALL support these as per the MustSupport Guidance.
Element | Reason |
---|---|
Observation.status | The status of the result value. |
Observation.category | A code that classifies the general type of observation being made. |
Observation.category | A mandatory code, to identify this observation as being Lab related. |
Observation.code | The type of lab related observation (code / type). |
Extensions
More information about the extensions can be found using the links below.
Extension | Context | Link | Comment |
---|---|---|---|
bodyStructureR5 | Observation | Extension UKCore-ObservationBodyStructure | This is a pre-adopted R5 element, for more details, see Pre-adopted R5 Elements. |
triggeredByR5 | Observation | Extension UKCore-ObservationTriggeredBy | This is a pre-adopted R5 element, for more details, see Pre-adopted R5 Elements. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
Observation.code | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-PathologyAndLaboratoryMedicineObservables |
for more guidance see the dataAbsentReason section below
Constraints (differential)
More information about the constraints on the UKCore-Observation-Lab
profile can be found below.
Key | Severity | Expression | Human_Description |
---|---|---|---|
ukcore-obs-lab-001 | warning | value.exists() or dataAbsentReason.exists() or note.exists() | Either `value`, `dataAbsentReason` or `note` SHOULD be populated |
for more guidance see the dataAbsentReason section below
basedOn
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- UKCore-CarePlan (draft)
- DeviceRequest Resource
- ImmunizationRecommendation Resource
- Profile UKCore-MedicationRequest
- NutritionOrder Resource
- Profile UKCore-ServiceRequest
partOf
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- UKCore-ImagingStudy (draft)
- Profile UKCore-Immunization
- Profile UKCore-MedicationAdministration
- Profile UKCore-MedicationDispense
- Profile UKCore-MedicationStatement
- Profile UKCore-Procedure
category
This element has an open slice, differentiated by the value of Observation.category.coding.code
, and MAY be used to differentiate the specific laboratory's speciality. There is one defined mandatory slice Observation.category:laboratory
, with a fixed value, which SHALL be populated when this profile is used, and additional category code's can be populated.
Observation.category:laboratory
The following SHALL be used:
Observation.category.coding.system
=http://terminology.hl7.org/CodeSystem/observation-category
Observation.category.coding.code
=laboratory
Observation.category.coding.display
=Laboratory
focus
Where a UK Core profile exists the resource being referenced SHOULD conform to the profile.
encounter
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Encounter.
performer
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- UKCore-CareTeam (draft)
- Profile UKCore-Organization
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-PractitionerRole
- Profile UKCore-RelatedPerson
note
The resource being referenced by Observation.note.authorReference
SHALL conform to one of the following:
- Profile UKCore-Organization
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-RelatedPerson
specimen
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Specimen.
device
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
dataAbsentReason
The inclusion of the coded reason for data being absent is optional, and not currently recommended, because the ValueSet defined in FHIR is of limited benefit to UK laboratory use cases. It is recommended that if a data absent reason is to be included, then a text representation SHOULD be used (i.e. Observation.dataAbsentReason.text
).
Example of Observation.dataAbsentReason
usage:
Table View
Observation.id[0] | UKCore-Observation-Lab-Sn-AbsentData-Example |
Observation.status[0] | final |
Observation.category[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/observation-category |
Observation.category[0].coding[0].code[0] | laboratory |
Observation.category[0].coding[0].display[0] | Laboratory |
Observation.code[0].coding[0].system[0] | http://snomed.info/sct |
Observation.code[0].coding[0].code[0] | 58571000237106 |
Observation.code[0].coding[0].display[0] | Nucleated red blood cell count in blood |
Observation.subject[0].reference[0] | Patient/UKCore-Patient-RichardSmith-Example |
Observation.performer[0].reference[0] | Organization/UKCore-Organization-LeedsTeachingHospital-Example |
Observation.dataAbsentReason[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/data-absent-reason |
Observation.dataAbsentReason[0].coding[0].code[0] | as-text |
Observation.dataAbsentReason[0].text[0] | Specimen unsatisfactory for evaluation |
Observation.specimen[0].reference[0] | Specimen/UKCore-Specimen-BloodSpecimen-Example |
Tree View
Observation |
id : UKCore-Observation-Lab-Sn-AbsentData-Example |
status : final |
category |
coding |
system : http://terminology.hl7.org/CodeSystem/observation-category |
code : laboratory |
display : Laboratory |
code |
coding |
system : http://snomed.info/sct |
code : 58571000237106 |
display : Nucleated red blood cell count in blood |
subject |
reference : Patient/UKCore-Patient-RichardSmith-Example |
performer |
reference : Organization/UKCore-Organization-LeedsTeachingHospital-Example |
dataAbsentReason |
coding |
system : http://terminology.hl7.org/CodeSystem/data-absent-reason |
code : as-text |
text : Specimen unsatisfactory for evaluation |
specimen |
reference : Specimen/UKCore-Specimen-BloodSpecimen-Example |
XML View
<Observation xmlns="http://hl7.org/fhir"> <id value="UKCore-Observation-Lab-Sn-AbsentData-Example" /> <status value="final" /> <category> <coding> <system value="http://terminology.hl7.org/CodeSystem/observation-category" /> <code value="laboratory" /> <display value="Laboratory" /> </coding> </category> <code> <coding> <system value="http://snomed.info/sct" /> <code value="58571000237106" /> <display value="Nucleated red blood cell count in blood" /> </coding> </code> <subject> <reference value="Patient/UKCore-Patient-RichardSmith-Example" /> </subject> <performer> <reference value="Organization/UKCore-Organization-LeedsTeachingHospital-Example" /> </performer> <dataAbsentReason> <coding> <system value="http://terminology.hl7.org/CodeSystem/data-absent-reason" /> <code value="as-text" /> </coding> <text value="Specimen unsatisfactory for evaluation" /> </dataAbsentReason> <specimen> <reference value="Specimen/UKCore-Specimen-BloodSpecimen-Example" /> </specimen> </Observation>
JSON View
{ "resourceType": "Observation", "id": "UKCore-Observation-Lab-Sn-AbsentData-Example", "status": "final", "category": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/observation-category", "code": "laboratory", "display": "Laboratory" } ] } ], "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "58571000237106", "display": "Nucleated red blood cell count in blood" } ] }, "subject": { "reference": "Patient/UKCore-Patient-RichardSmith-Example" }, "performer": [ { "reference": "Organization/UKCore-Organization-LeedsTeachingHospital-Example" } ], "dataAbsentReason": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/data-absent-reason", "code": "as-text" } ], "text": "Specimen unsatisfactory for evaluation" }, "specimen": { "reference": "Specimen/UKCore-Specimen-BloodSpecimen-Example" } }
hasMember
This element SHOULD NOT be used, as this profile is used to represent individual test results. Where an Observation is being used to represent a group of tests (with Observation.hasMember
references), then Profile UKCore-Observation-Group-Lab SHOULD be used instead.
derivedFrom
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- UKCore-DocumentReference (draft)
- UKCore-ImagingStudy (draft)
- Media Resource
- MolecularSequence Resource
- Profile UKCore-Observation
- Profile UKCore-Observation-Group-Lab
- Profile UKCore-Observation-Lab
- UKCore-QuestionnaireResponse (draft)