 |
Return to detail page at www.hitsp.org | HITSP/T14 |
| Prev TOC Next |
| HOME | ABOUT | MEMBERSHIP | NEWS & ANNOUNCEMENTS | MEETINGS | FAQ | CONTACT US | | Powered by American National Standards Institute |
|
Return to detail page at www.hitsp.org | HITSP/T14 |
| Prev TOC Next |
The goals supported by this Transaction specification are the following:
Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician and providers of care
Transmission of complete, preliminary, final and updated laboratory results (or notification of the availability of laboratory results) to the EHR system (local or remote)
This Transaction is the result of an assessment of the current practices in electronic laboratory results reporting and the requirements of the Electronic Health Records Laboratory Result Reporting Use Case. In order to encourage rapid and widespread adoption of this Transaction, HITSP placed emphasis on the operations and process flows of current implementations and the ease with which current implementations can become compliant. Health Level (HL7) Version 2.x [1] message-based laboratory result reporting is the most common electronic interface in existence today and HITSP did not want to invalidate those interfaces.
This Transaction is an initial step in establishing a baseline of performance for all stakeholders. It raises everyone to a modern version of HL7 2.x and establishes some discipline in identity management and vocabulary.
COPYRIGHT NOTICE
2009 ANSI. This material may be copied without permission from ANSI only if and to the extent that the text is not altered in any fashion and ANSIs copyright is clearly noted.
Certain materials contained in this Interoperability Specification are reproduced from Health Level Seven (HL7) Version 2.5.1 and HL7 Minimal Lower Layer Protocol (MLLP) Release 2 with permission of Health Level Seven, Inc. No part of the material may be copied or reproduced in any form outside of the Interoperability Specification documents, including an electronic retrieval system, or made available on the Internet without the prior written permission of Health Level Seven, Inc. Copies of standards included in this Interoperability Specification may be purchased from the Health Level Seven, Inc. Material drawn from these standards is credited where used.
IHE materials used in this document have been extracted from relevant copyrighted materials with permission of Integrating the Healthcare Enterprise (IHE) International. Copies of this standard may be retrieved from the IHE Web Site at www.ihe.net.
This section provides a list of key reference documents and background material.
A list of key reference documents and background material is provided in the table below. These documents can be retrieved from the www.hitsp.org Web Site.
Table 1-1 Reference Documents
|
Reference Document |
Document Description |
|
Lists and defines the acronyms used in this document |
|
|
Provides definitions for relevant terms used by HITSP documents |
|
|
TN900 is a reference document that provides the overall context for use of the HITSP Security and Privacy constructs |
This section describes the conformance criteria, which are objective statements of requirements that can be used to determine if a specific behavior, function, interface, or code set has been implemented correctly.
In order to claim conformance to this construct specification, an implementation must satisfy all the requirements and mandatory statements listed in this specification, the associated HITSP Interoperability Specification, its associated construct specifications, as well as conformance criteria from the selected base and composite standards. A conformant system must also implement all of the required interfaces within the scope, subset or implementation option that is selected from the associated Interoperability Specification.
Claims of conformance may only be made for the overall HITSP Interoperability Specification or Capability with which this construct is associated.
A HITSP Interoperability Specification must be implemented in its entirety for an implementation to claim conformance to the specification. HITSP may define the permissibility for interface scoping, subsetting or implementation options by which the specification may be implemented in a limited manner. Such scoping, subsetting and options may extend to associated constructs, such as this construct. This construct must implement all requirements within the selected scope, subset or options as defined in the associated Interoperability Specification to claim conformance.
|
Return to detail page at www.hitsp.org | HITSP/T14 |
| Prev TOC Next |