US Laboratory Specimen Profile (Conformance Package)

Published by: HL7 Orders and Observations Workgroup

Primary Author: Eric M Haas, Health eData Inc.

Scope and Usage

This Specimen 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.

A single specimen profile is defined to cover the use cases between Laboratory Order/Results Sender and Laboratory Order/Results Receiver and the use between Laboratory Results Sender and Public Health Agency Receiver. This profile is referenced if the specimen has already been obtained for the lab test request or as additional clinical information in the USLabOrder DiagnosticOrder and is always referenced in the DiagnosticReport profile. 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 save/print/archive/etc. the supplied the elements and or extensions sent by the Laboratory Order/Results Sender. Both the Laboratory Receiver and Laboratory Sender MAY use the information to control their display of the information.

Boundaries and Relationships

Explains how this resource relates to others. Particularly important is to differentiate between appropriate usages for related resources when an implementer might be confused about what to reference when.