| HOME | ABOUT | MEMBERSHIP | NEWS & ANNOUNCEMENTS | MEETINGS | FAQ | CONTACT US | | Powered by American National Standards Institute |
![]() |
Return to detail page at www.hitsp.org | HITSP/C35 |
| Prev TOC Next |
The purpose of this document is to define the vocabulary for either message-based or document-based laboratory results reporting. The goals supported by this terminology Component specification are stated in the AHIC Electronic Health Records (EHR) Laboratory Results Reporting Use Case:
Deploy standardized, widely available, secure solutions for accessing laboratory results and interpretations in a patient-centric manner for clinical care by authorized parties
Provide the following functionality for laboratory results reporting and notification, and is applicable to many types of laboratory tests, including but not limited to: clinical chemistry, hematology, serology and microbiology
The Use Case notes that there are obstacles to achieving the stated goals. In particular, the following obstacle is delineated:
Lack of harmonization among data interoperability standards including vocabulary, laboratory and other messaging standards
This Lab Result Terminology Component is the result of a considered assessment of the terminologies available and the current practices in electronic laboratory results reporting for the purpose of moving forward in the harmonization of those terminologies. Without standard terminologies, interoperability is severely limited. This specification describes the vocabularies needed to implement the communication of an electronic standards-based laboratory result. A guiding principle for these selections was to follow the Consolidated Heath Informatics (CHI) Initiative standards selections as appropriate. The following sections describe the selected terminologies, the events that are supported by those standards and the reason for their selection. Also described are the organizations that maintain the standards and where to obtain more information.
This Component specification is part of a series of documents to establish Interoperability Standards for laboratory results reporting.
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.
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.
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 actor 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/C35 |
| Prev TOC Next |