US Core Implementation Guide STU 2

This page is part of the US Core (v2.0.0: STU2) based on FHIR R3. The current version which supercedes this version is 5.0.1. For a full list of available versions, see the Directory of published versions

StructureDefinition-us-core-observationresults

Laboratory results are grouped and summarized using the DiagnosticReport resource which reference Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) which references other observations, or rarely a laboratory test with component result values. This profile sets minimum expectations for the Observation resource resource to record, search and fetch laboratory test results associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.

Example Usage Scenarios:

The following are example usage scenarios for the US Core-Results profile:

  • Query for lab results belonging to a Patient
  • Record lab results belonging to a Patient
Mandatory Data Elements and Terminology

The following data-elements are mandatory (i.e data MUST be present). These are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each Observation must have:

  1. a status
  2. a category code of ‘laboratory’
  3. a LOINC code, if available, which tells you what is being measured
  4. a patient
  5. a result value and, if the result value is a numeric quantity, a standard UCUM unit

Each Observation should have:

  1. a time indicating when the measurement was taken
  2. a reference range if available

Profile specific implementation guidance:

  • Additional codes that translate or map to the Observation code or category codes are allowed. For example:
    • providing both a local code and LOINC code
    • providing a more specific category codes such as ‘chemistry’, SNOMED CT concept, or system specific codes in addition to the ‘laboratory’ category code.
  • An Observation without a value must include an absent reason or group other results. When it groups results, the composite values or references to other Observations will be populated.
  • See the General Guidance Section for further guidance on using UCUM

Examples

Formal Views of Profile Content

Description of Profiles, Differentials, and Snapshots.

The official URL for this profile is: http://hl7.org/fhir/us/core/StructureDefinition/us-core-observationresults

Published on Mon Aug 01 00:00:00 AEST 2016 as a draft by HL7 US Realm Steering Committee.

This profile builds on Observation

Complete Summary of the Mandatory Requirements

  1. One status in Observation.status which has a required binding to ObservationStatus
  2. A category in Observation.category which must have:
  3. One code in Observation.code which has an extensible binding to LOINC Observation Codes
    • Other additional codes are allowed - e.g. system specific codes. All codes SHALL have a code system value
  4. One patient in Observation.subject
  5. Either one Observation.value[x] or one code in Observation.DataAbsentReason (unless Observation.component or Observation.related is present)

Each Observation SHOULD have:

  1. A date and time in effectiveDateTime or effectivePeriod
  2. A reference range if applicable in Observation.referenceRange
NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*US Core Result Observation
us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present
... status S1..1codeBinding: ObservationStatus (required)
... category SI1..*CodeableConceptus-core-5: Must have a category of 'laboratory' and a code system 'http://hl7.org/fhir/observation-category'
... code S1..1CodeableConceptLaboratory Test Name
Binding: LOINC Codes (extensible)
... subject S1..1Reference(US Core Patient Profile)
... effective[x] SI0..1dateTime, Periodus-core-1: Datetime must be at least to day.
... value[x] SI0..1Quantity, CodeableConcept, string, boolean, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodResult Value
us-core-4: SHOULD use Snomed CT for coded Results
us-core-3: SHALL use UCUM for coded quantity units.
... dataAbsentReason SI0..1CodeableConceptBinding: Observation Value Absent Reason (extensible)

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*US Core Result Observation
us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... based on Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ProcedureRequest | ReferralRequest)Fulfills plan, proposal or order
... status ?!SΣ1..1coderegistered | preliminary | final | amended +
Binding: ObservationStatus (required)
... category SI1..*CodeableConceptClassification of type of observation
Binding: Observation Category Codes (preferred)
us-core-5: Must have a category of 'laboratory' and a code system 'http://hl7.org/fhir/observation-category'
... code SΣ1..1CodeableConceptLaboratory Test Name
Binding: LOINC Codes (extensible)
... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what this is about
... context 0..1Reference(Encounter | EpisodeOfCare)Healthcare event during which this observation is made
... effective[x] SΣI0..1dateTime, PeriodClinically relevant time/time-period for observation
us-core-1: Datetime must be at least to day.
... issued Σ0..1instantDate/Time this was made available
... performer Σ0..*Reference(Practitioner | Organization | Patient | RelatedPerson)Who is responsible for the observation
... value[x] SΣI0..1Quantity, CodeableConcept, string, boolean, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodResult Value
us-core-4: SHOULD use Snomed CT for coded Results
us-core-3: SHALL use UCUM for coded quantity units.
... dataAbsentReason SI0..1CodeableConceptWhy the result is missing
Binding: Observation Value Absent Reason (extensible)
... interpretation 0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
... comment 0..1stringComments about result
... bodySite 0..1CodeableConceptObserved body part
Binding: SNOMED CT Body Structures (example)
... method 0..1CodeableConceptHow it was done
Binding: Observation Methods (example)
... specimen 0..1Reference(Specimen)Specimen used for this observation
... device 0..1Reference(Device | DeviceMetric)(Measurement) Device
... referenceRange I0..*BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... low I0..1SimpleQuantityLow Range, if relevant
.... high I0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: Observation Reference Range Meaning Codes (extensible)
.... appliesTo 0..*CodeableConceptReference range population
Binding: Observation Reference Range Applies To Codes (example)
.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... related ΣI0..*BackboneElementResource related to this observation
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... type 0..1codehas-member | derived-from | sequel-to | replaces | qualified-by | interfered-by
Binding: ObservationRelationshipType (required)
.... target 1..1Reference(Observation | QuestionnaireResponse | Sequence)Resource that is related to this one
... component ΣI0..*BackboneElementComponent results
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... code Σ1..1CodeableConceptType of component observation (code / type)
Binding: LOINC Codes (example)
.... value[x] Σ0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodActual component result
.... dataAbsentReason I0..1CodeableConceptWhy the component result is missing
Binding: Observation Value Absent Reason (extensible)
.... interpretation 0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
.... referenceRange 0..*Unknown reference to #Observation.referenceRange
Provides guide for interpretation of component result

doco Documentation for this format

Complete Summary of the Mandatory Requirements

  1. One status in Observation.status which has a required binding to ObservationStatus
  2. A category in Observation.category which must have:
  3. One code in Observation.code which has an extensible binding to LOINC Observation Codes
    • Other additional codes are allowed - e.g. system specific codes. All codes SHALL have a code system value
  4. One patient in Observation.subject
  5. Either one Observation.value[x] or one code in Observation.DataAbsentReason (unless Observation.component or Observation.related is present)

Each Observation SHOULD have:

  1. A date and time in effectiveDateTime or effectivePeriod
  2. A reference range if applicable in Observation.referenceRange

Differential View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*US Core Result Observation
us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present
... status S1..1codeBinding: ObservationStatus (required)
... category SI1..*CodeableConceptus-core-5: Must have a category of 'laboratory' and a code system 'http://hl7.org/fhir/observation-category'
... code S1..1CodeableConceptLaboratory Test Name
Binding: LOINC Codes (extensible)
... subject S1..1Reference(US Core Patient Profile)
... effective[x] SI0..1dateTime, Periodus-core-1: Datetime must be at least to day.
... value[x] SI0..1Quantity, CodeableConcept, string, boolean, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodResult Value
us-core-4: SHOULD use Snomed CT for coded Results
us-core-3: SHALL use UCUM for coded quantity units.
... dataAbsentReason SI0..1CodeableConceptBinding: Observation Value Absent Reason (extensible)

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*US Core Result Observation
us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... based on Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ProcedureRequest | ReferralRequest)Fulfills plan, proposal or order
... status ?!SΣ1..1coderegistered | preliminary | final | amended +
Binding: ObservationStatus (required)
... category SI1..*CodeableConceptClassification of type of observation
Binding: Observation Category Codes (preferred)
us-core-5: Must have a category of 'laboratory' and a code system 'http://hl7.org/fhir/observation-category'
... code SΣ1..1CodeableConceptLaboratory Test Name
Binding: LOINC Codes (extensible)
... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what this is about
... context 0..1Reference(Encounter | EpisodeOfCare)Healthcare event during which this observation is made
... effective[x] SΣI0..1dateTime, PeriodClinically relevant time/time-period for observation
us-core-1: Datetime must be at least to day.
... issued Σ0..1instantDate/Time this was made available
... performer Σ0..*Reference(Practitioner | Organization | Patient | RelatedPerson)Who is responsible for the observation
... value[x] SΣI0..1Quantity, CodeableConcept, string, boolean, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodResult Value
us-core-4: SHOULD use Snomed CT for coded Results
us-core-3: SHALL use UCUM for coded quantity units.
... dataAbsentReason SI0..1CodeableConceptWhy the result is missing
Binding: Observation Value Absent Reason (extensible)
... interpretation 0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
... comment 0..1stringComments about result
... bodySite 0..1CodeableConceptObserved body part
Binding: SNOMED CT Body Structures (example)
... method 0..1CodeableConceptHow it was done
Binding: Observation Methods (example)
... specimen 0..1Reference(Specimen)Specimen used for this observation
... device 0..1Reference(Device | DeviceMetric)(Measurement) Device
... referenceRange I0..*BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... low I0..1SimpleQuantityLow Range, if relevant
.... high I0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: Observation Reference Range Meaning Codes (extensible)
.... appliesTo 0..*CodeableConceptReference range population
Binding: Observation Reference Range Applies To Codes (example)
.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... related ΣI0..*BackboneElementResource related to this observation
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... type 0..1codehas-member | derived-from | sequel-to | replaces | qualified-by | interfered-by
Binding: ObservationRelationshipType (required)
.... target 1..1Reference(Observation | QuestionnaireResponse | Sequence)Resource that is related to this one
... component ΣI0..*BackboneElementComponent results
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... code Σ1..1CodeableConceptType of component observation (code / type)
Binding: LOINC Codes (example)
.... value[x] Σ0..1Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, PeriodActual component result
.... dataAbsentReason I0..1CodeableConceptWhy the component result is missing
Binding: Observation Value Absent Reason (extensible)
.... interpretation 0..1CodeableConceptHigh, low, normal, etc.
Binding: Observation Interpretation Codes (extensible)
.... referenceRange 0..*Unknown reference to #Observation.referenceRange
Provides guide for interpretation of component result

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON, CSV), Schema: XML Schematron

 

Quick Start

Below is an overview of the required set of RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.

GET [base]/Observation?patient=[id]&category=laboratory

Example: GET [base]/Observation?patient=1134281&category=laboratory

Support: Mandatory to support search by patient and category code = ‘laboratory’.

Implementation Notes: Search based on laboratory category code = “laboratory”. This fetches a bundle of all Observation resources with laboratory categories for the specified patient (how to search by reference) and (how to search by token).

GET [base]/Observation?patient=[id]&code=[LOINC{,LOINC2,LOINC3,...}]

Example:

  • Search for all blood glucose lab results (LOINC = 2339-0 Glucose [Mass/volume] in Blood) for a patient:
    • GET [base]/Observation?patient=1134281&code=2339-0
  • Search for all blood glucose, urine glucose (LOINC = 25428-4 Glucose [Presence] in Urine by Test strip) and urine ketones (LOINC = 2339-0 Ketones [Presence] in Urine by Test strip) for a patient
    • GET [base]/Observation?patient=1134281&code=2339-0,25428-4,2514-8

Support: Mandatory support search by a laboratory LOINC code. SHOULD support search by multiple LOINC codes.

Implementation Notes: 1) Search based on laboratory LOINC code(s). This fetches a bundle of all Observation resources for a specific observation LOINC code(s) for the specified patient (how to search by reference) and (how to search by token). 2) The Observation “code” parameter searches both in both Observation.code and Observation.component.code.

GET [base]/Observation?patient=[id]&category=laboratory&date=[date]{&date=[date]}

Example:

  • Find all the laboratory results after 2013-03-14
    • GET [base]Observation?patient=555580&category=laboratory&date=ge2015-01-14

Support: Mandatory support search by category code =”laboratory” and date or period

Implementation Notes: Search based on laboratory category code and date. This fetches a bundle of all Observation resources with category ‘laboratory’ for the specified patient for a specified time period (how to search by reference), (how to search by token) amd (how to search by date).