DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.20.15 US Laboratory Observation Profile (Profile)

Published by: HL7 Orders and Observations Workgroup

Primary Author: Eric M Haas, Health eData Inc.

4.20.16 Scope and Usage

This Observation Profile is part of the The USLabOrder and USLabReport Implementation Guides. Its scope is US Realm ambulatory care and is based upon existing regulatory requirements for Laboratories and Electronic Health Record Systems (EHR-S) for ordering clinical laboratory results. The content has been modeled after the joint HL7 and The Standards and Interoperability (S and I) Framework Laboratory Orders and Results Interface Initiatives and the HL7 Lab Order Conceptual Specification and V3 Lab Normative Standard. However, much of the content is likely to be useable outside the ambulatory space and in other jurisdictions.

Four Observation profiles are defined to cover the various kinds of result values that are generated by laboratories and Ask at Order entry ('AOE') questions. These profiles are:

  • USLabObsQuantity for quantitative or numeric results with required units and reference ranges. For example, this profile would be used to record a Blood Glucose level measurement of 80 mg/dL.
  • USLabObsRange for quantitative results that are expressed as ranges with required reference ranges. For example, this profile would be used to record white blood cells (WBCs)in a urine analysis with a value range of 10-20 WBC/HPF.
  • USLabObsRatio for titers with required reference ranges. For example, this profile would be used to record an adenovirus total antibody of <1:8
  • USLabObsCoded for coded results. For example, this profile would be used to record a Chlamydia trachomatis RNA PCR result of "Not Detected"
  • USLabObsOther for the remaining result value datatypes
    • Attachment
    • dateTime
    • Period
    • SampleData
    • string
    • time
    For example, this profile would be used to record a free text entry of a cytology observation, or to record the date of last menstrual period for an ask at order entry question for a pap smear report.
  • USLabObsPanel for a panel/battery. This observation lists the set component observations from a panel or battery in the Observation.related element and does not have its own Observation.value. For example a Chyamydia trachomatis + Neisseria gonorrhoeae RNA PCR (GC/CT) panel would have two references to related observations for the Chlamydia trachomatis RNA PCR result and the Neisseria gonorrhoeae RNA PCR result.

These profile are referenced in the USLab DiagnosticReport profile for one or more lab test results. They are also referenced for ask at order ("AOE") questions, other clinically relevant questions and for reporting prior results when requesting a test order using the USLabOrder DiagnosticOrder. Although not specified in this implementation, it may be used in other resources as well.

For the purposes of this profile, all elements listed in the differential profile view are Supported which means that the Laboratory Order/Results Sender SHALL be capable of supplying these elements and or extensions to the Laboratory Order/Results Receiver if the data is available. For the Laboratory Order/Results Receiver Supported means they SHALL consuming the supplied the elements and or extensions sent by the Laboratory Order/Results Sender.

In addition, for the Observation.code element, Supported means that the Laboratory Order/Results Sender SHALL be capable of supplying both the LOINC and the local code if both exist and the Laboratory Order/Results Receiver SHALL be capable of consuming both if they exist. For the Observation.valueCodeableConcept, Supported means that the Laboratory Order/Results Sender SHALL be capable of supplying both the SNOMED CT and the local code if both exist and the Laboratory Order/Results Receiver SHALL be capable of consuming both if they exist.

Both the Laboratory Receiver and Laboratory Sender MAY use the information to control their display of the information.

4.20.16.1 Content

Profiles:
USLabObsCodeUS Realm laboratory result using CodeableConcept Data Type for non-numeric results
USLabObsQuantityUS Realm laboratory result using Quantity Data Type for numeric results
USLabObsOtherUS Realm laboratory result using one of Attachment|dateTime|Period|SampledData|string|timeData Type for results.
USLabObsRangeUS Realm laboratory result using Range Data Type for numeric results
USLabObsRatioUS Realm laboratory result using Ratio Data Type for numeric results
USLabObsPanelUS Realm panel observation
Extensions:
uslabspecimenrejectreasonSpecimen Rejection Reason :

This extension describes the reason if a test is cancelled for specimen related reason.

uslabobservationkindKind of observation :

This extension is used to classify the kind of observation in Observation.value for laboratory reporting and to differentiate between actual test results, responses to filler questions when ordering tests and other unsolicted responses. This may be required to drive operational functionality.

Examples:
obs-uslab-example1

USLab Quantitative Observation Profile Example: Capillary Blood Lead

obs-uslab-example2

USLab Coded Observation Profile Example: N gonorrhoeae PCR

obs-uslab-example3

USLab Other (string) Observation Profile Example: S.aureus

obs-uslab-example4

USLab Ratio Observation Profile Example: Dengue Titer

obs-uslab-example5

USLab Quantitative Observation Profile Example: Blood Lead

obs-uslab-example6

USLab Panel Observation Profile Example: GC/CT Aptima 2 Combo panel

obs-uslab-example7

USLab Coded Observation Profile Example: C trachomatis PCR

obs-uslab-example8

USLab Range Observation Profile Example: WBCs in Urine