DSTU2 QA Preview

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

A.?? US Laboratory Patient Profile

Published by: HL7 Orders and Observations Workgroup

Primary Author: Eric M Haas, Health eData Inc.

A.?? Scope and Usage

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

There are two Patient profiles covering the use cases between Laboratory Order/Results Sender and Laboratory Order/Results Receiver and the use case between Laboratory Results Sender and Public Health Agency Receiver:

  • UsLabPatient is used when additional patient demographic data is not needed.
  • USlabPHPatient is used when additional patient demographic and contact data is needed such as for public health reporting.

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.

A.?? 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.

A.??.1 Content

Profiles:
USLab-PatientPatient
USLab-PHPatientPatient with expanded contact information