 |
Return to detail page at www.hitsp.org | HITSP/IS02 |
| 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/IS02 |
| Prev TOC Next |
As an introduction to the Healthcare Information Technology Standards Panel Biosurveillance Interoperability Specification, this section provides a high level overview of the information sharing scenario enabled by following this specification, provides a document map of the construct relationships for the Interoperability Specification, acknowledges the copyright protections that pertain and provides a list of key reference documents and background material. If you are already familiar with this information, proceed to Section 2.0 Interoperability Requirements.
This section describes a high level definition of this Interoperability Specification and background information about the underlying Use Case that it is based upon.
Biosurveillance is an American Health Information Community (AHIC) breakthrough area defined as implementation of near real-time, nationwide public health event monitoring to support early detection, situational awareness and rapid response management across care delivery, public health, and other authorized government agencies. The Use Case describes the process or interaction that each primary stakeholder will invoke to capture, discover, anonymize and transmit relevant data.
The AHIC Biosurveillance Use Case that defines the scope of the Interoperability Specification describes the process or interaction that each primary stakeholder will invoke in the capture, discovery, anonymization and transmission of relevant data. In particular, an implementer must provide the technical infrastructure and security framework necessary to support operations in accordance with law, regulation, best practices and business agreements.
Each HITSPInteroperability Specification (IS)is comprised of a suite of constructs that, taken as a whole, define how to integrate and constrain existing standards and specifications to satisfy the requirementsimposed by a given Use Case. TheIS groups specific actions and actors to describe the relevant context(s) for the use ofHITSP constructs that further identify and constrain standards where necessary. In addition to ISs, there are three other types of HITSP constructs called Transaction Packages (TP), Transactions (T) andComponents (C). The document map depicted in Figure 1-1identifiesthe HITSP constructs used to meet the IS requirements. Implementers should read the documents that describe the constructs depicted in the diagram for their details and specific uses.
Figure 1-1 Interoperability Specification Document Map
The following table lists and describes the HITSP constructs that are shown in the Unified Modeling Language (UML) diagram above and are used by the Interoperability Specification. All references to HITSP specifications are to the current, and Panel approved Released for Implementation versions of the specifications.
Table 1-1 List of Constructs
|
Construct |
Description |
|
HITSP/C19 |
HITSP Entity Identity Assertion Component |
|
HITSP/C25 |
HITSP Anonymize Component |
|
HITSP/C26 |
HITSP Nonrepudiation of Origin Component |
|
HITSP/C35 |
HITSP Lab Result Terminology Component |
|
HITSP/C36 |
HITSP Lab Result Message Component |
|
HITSP/C37 |
HITSP Lab Report Document Component |
|
HITSP/C39 |
HITSP Encounter Message Component |
|
HITSP/C41 |
HITSP Radiology Result Message Component |
|
HITSP/C47 |
HITSP Resource Utilization Message Component |
|
HITSP/C48 |
HITSP Encounter Document Using IHE Medical Summary (XDS-MS) Component |
|
HITSP/T15 |
HITSP Collect and Communicate Security Audit Trail Transaction |
|
HITSP/T16 |
HITSP Consistent Time Transaction |
|
HITSP/T17 |
HITSP Secured Communications Channel Transaction |
|
HITSP/T24 |
HITSP Pseudonymize Transaction |
|
HITSP/T29 |
HITSP Notification of Document Availability Transaction |
|
HITSP/TP13 |
HITSP Manage Sharing of Documents Transaction Package |
|
HITSP/TP20 |
HITSP Access Control Transaction Package |
|
HITSP/TP22 |
HITSP Patient ID Cross-Referencing Transaction Package |
|
HITSP/TP30 |
HITSP Manage Consent Directives Transaction Package |
|
HITSP/TP49 |
HITSP Sharing Radiology Results Transaction Package |
|
HITSP/TP50 |
HITSP Retrieve Form for Data Capture Transaction Package |
COPYRIGHT NOTICE
2008 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.
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-2 Reference Documents
|
Reference Document |
Document Description |
|
HITSP Interoperability Specification Overview |
Provides background information about the HITSP and its role in the overall U.S. efforts to realize large scale interoperability of health information. The document also provides a description of the HITSP process for healthcare standards harmonization and explains how to use the Interoperability Specifications and other related documents to inform your health IT product development or product refinement |
|
HITSP Conventions List |
Describes the conventions that are used to convey the full descriptions and usage of standards in the HITSP specifications |
|
HITSP Acronyms List |
Lists and defines the acronyms used in this document |
|
HITSP Glossary |
Provides definitions for relevant terms used by HITSP documents |
|
HITSP Harmonization Framework |
Describes the current framework within which the Interoperability Specifications are built |
|
Harmonized Use Case for Biosurveillance (Visit, Utilization, and Lab Result Message), March 19, 2006 |
AHIC Use Case that is the basis of this Interoperability Specification |
|
TN900 - Security and Privacy Technical Note |
Developed as a reference document to provide the overall context for use of the HITSP Security and Privacy constructs. It includes the following: The scope, reference policy background, and Security and Privacy principles used in the development of the constructs A detailed description and schematics of the conceptual relationship between the Security and Privacy constructs A mapping of existing standards and constructs to be used in meeting the stated requirements of the AHIC Use Cases A list of identified gaps and the recommended approaches to resolving those gaps A roadmap for how the Security and Privacy constructs will evolve and eventually align with other HITSP Interoperability Specifications A conceptual framework for Security and Privacy management, including reference information on privacy policies, risk assessment, and risk management A glossary of terms used in all the Security and Privacy construct documents A description of the application of the Security and Privacy constructs to the HITSP Interoperability Specifications for the three initial AHIC Use Cases Biosurveillance, Electronic Health Records - Laboratory Results Reporting, and Consumer Empowerment HITSP will periodically update this Technical Note as required by the introduction of new contexts for use |
|
Return to detail page at www.hitsp.org | HITSP/IS02 |
| Prev TOC Next |