This
page
is
part
of
the
FHIR
Specification
(v1.0.2:
DSTU
2).
The
current
version
which
supercedes
this
version
is
This page is part of the FHIR Specification (v1.4.0:
STU
3 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
. For a full list of available versions, see the
Directory of published versions
Published
by:
HL7
Orders
and
Observations
Workgroup
Primary
Author/Editor:
Eric
M
Haas,
Health
eData
Inc.
Published by: HL7 Orders and Observations Workgroup
Primary Author/Editor: Eric M Haas, Health eData Inc.
A.2.0
US
Laboratory
Order
Implementation
US Laboratory Order Implementation
The
US
Laboratory
Order
Implementation
(USLabOrder)
consists
of
the
guidance
documentation,
profiles,
operations,
value
sets
and
conformance
statements
it
defines.
This
implementation
has
been
prepared
as
a
U.S.
Realm
Specification
on
behalf
of
the
HL7
Orders
and
Observation
Workgroup.
Laboratory
Test
Ordering
in
the
US
Realm
ambulatory
care
setting
(USLabOrder)-
This
use
case
is
based
upon
existing
regulatory
requirements
for
Laboratories
and
Electronic
Health
Record
Systems
(EHR-S)
for
ordering
clinical
laboratory
tests.
The
content
has
been
modeled
after
the
joint
HL7
and
The
Standards
and
Interoperability
(S&I)
Framework
Laboratory
Orders
Interface
(LOI)
Initiative
The
US Laboratory Order Implementation (USLabOrder)
consists of the guidance documentation, profiles, operations, value sets and conformance statements it defines. This implementation has been prepared as a U.S. Realm Specification on behalf of the HL7 Orders and Observation Workgroup.
Laboratory Test Ordering in the US Realm ambulatory care setting (USLabOrder)- This use case is based upon existing regulatory requirements for Laboratories and Electronic Health Record Systems (EHR-S) for ordering clinical laboratory tests. The content has been modeled after the joint HL7 and
The Standards and Interoperability (S&I) Framework Laboratory Orders Interface (LOI) Initiative
and
the
HL7
Lab
Order
Conceptual
Specification
and the
HL7 Lab Order Conceptual Specification
.
However,
much
of
the
content
is
likely
to
be
usable
outside
the
ambulatory
space
and
in
other
jurisdictions.
. However, much of the content is likely to be usable outside the ambulatory space and in other jurisdictions.
-
Purpose
-
How
this
project
came
to
be
and
what
it
is
trying
to
achieve
- How this project came to be and what it is trying to achieve
-
Use
case
Use case
-
Describes
the
Scope,
Assumptions,
Pre
and
Post
Conditions
and
Use
Cases
for
this
guide
- Describes the Scope, Assumptions, Pre and Post Conditions and Use Cases for this guide
-
Key
Technical
Decisions
Key Technical Decisions
-
List
of
key
technical
decisions
in
creating
this
guide
- List of key technical decisions in creating this guide
-
Additional
Guidance
Additional Guidance
-Information
on
CLIA
and
Glossary
of
laboratory
terms
defined
for
this
implementation
-Information on CLIA and Glossary of laboratory terms defined for this implementation
A.2.0.1
Specification
Specification
The
The
USLabOrder
is
built
on
top
of
the
HL7
FHIR
standard.
Basic
aspects
of
the
FHIR
protocol,
including
RESTful
operations
,
data
types
,
is built on top of the
HL7 FHIR
standard. Basic aspects of the FHIR protocol, including
RESTful operations
,
data types
,
search
,
etc.
apply.
, etc. apply.
Profiles
-The
current
focus
of
implementing
-The current focus of implementing
USLabOrder
is
using
a
FHIR
Bundle
Resource
to
exchange
a
DiagnosticOrder
Profile
and
the
Resource
Profiles
it
references.
This
FHIR
bundle
completely
defines
the
laboratory
order.
The
Resource
Profiles
that
may
be
used
in
the
bundle
are
outlined
below:
(This
list
is
not
meant
to
be
exhaustive
as
additional
resources
may
also
to
be
used)
US
Lab
DiagnosticOrder
constrains
and
extends
is using a FHIR
Bundle Resource
to exchange a
DiagnosticOrder Profile
and the Resource Profiles it references. This FHIR bundle completely defines the laboratory order. The Resource Profiles that may be used in the bundle are outlined below: (This list is not meant to be exhaustive as additional resources may also to be used)
In addition to defining the
USLabOrder
bundle
this
implementation
consists
of
the
following
components:
bundle this implementation consists of the following components:
-
Operations
-
None
Conformance
statements
-
Definitions
for
the
expected
capabilities
of
each
of
the
actors
involved
supporting
- None -
Conformance statements
- Definitions for the expected capabilities of each of the actors involved supporting
USLabOrder
functionality:
functionality: -
Value Sets
-
USLab Value Sets
-
Mappings
-
are
translation
of
the
concept
codes
for
LOI
to
- are translation of the concept codes for LOI to
USLabOrder
-
Note
this
is
a
stub
entry
for
future
work.
- Note this is a stub entry for future work. -
Examples
-
Example
instances
of
- Example instances of
USLabReport
Resources:
Note
these
have
not
yet
been
validated
by
profile
specific
schema
and
schematrons
and
are
provided
as
informational
only:
Resources: Note these have not yet been validated by profile specific schema and schematrons and are provided as informational only: