 Interoperability Specification
Transaction Package
Transaction
Component
Technical Note
Requirements Design and Standards Selcection
Reference
|
Interoperability Specification |
IS 01 | Electronic Health Record Laboratory Results Reporting
The goals supported by this Interoperability Specification are:
- Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician
- Transmission of complete, preliminary, final and updated laboratory result (or notification of laboratory result) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient)
|
IS 02 | HITSP Biosurveillance Interoperability Specification
This Interoperability Specification focuses on a set of constrained standards for 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. It prescribes the process or interaction that each primary stakeholder will invoke to capture, discover, anonymize and transmit relevant data. |
IS 03 | HITSP Consumer Empowerment Interoperability Specification
The HITSP Consumer Empowerment and Access to Clinical Information via Networks Interoperability Specification identifies a subset of the functional components of the healthcare enterprises and health information networks, called "HITSP actors," and specifies their interactions in terms of a set of coordinated, standards based transactions. This document defines specific implementations of established standards intended to achieve integration goals that promote appropriate exchange of a consumer’s personal health record information. |
IS 04 | HITSP Emergency Responder Electronic Health Record Interoperability Specification
The ER-EHR specification focuses on the use of standardized, widely available and secure solutions for accessing and exchanging current and patient-specific historical health information during emergency response situations. |
IS 05 | HITSP Consumer Empowerment and Access to Clinical Information via Media Interoperability Specification
This specification addresses the recording of an individual’s health information on portable media such as a CD or a USB key to achieve portability between the consumer’s PHR Systems and other information systems. This document defines specific implementations of established standards intended to achieve integration goals that promote appropriate exchange of a consumer’s personal health record information. As part of a personal health record (PHR), this specification addresses several key areas: the patient’s registration data and a healthcare summary including medication history, allergies, encounters, problems and conditions, immunizations and key laboratory tests results. |
IS 06 | HITSP Quality Interoperability Specification
This Quality Interoperability Specification is designed to enable interoperable, electronic quality (eQuality) monitoring. This process provides implementers with a set of standards and workflows to enable that eQuality monitoring. Specifically, it provides selected standards for encoding the data types required for encoding an electronic quality measure. |
IS 07 | HITSP Medication Management Interoperability Specification
The HITSP Medication Management Interoperability Specification describes the information flows, issues and system capabilities that apply to the multiple organizations participating in medication management. It is intended to facilitate access to necessary medication and allergy information for consumers, clinicians, pharmacists, health insurance agencies, inpatient and ambulatory care, etc. |
Transaction Package |
TP 13 | HITSP Manage Sharing of Documents Transaction Package
This Transaction Package supports the sharing of patient records in the form of source attested objects called documents. A healthcare document is a composite of structured and coded health information, both narrative and tabular, that describes acts, observations and services for the purpose of exchange. No assumption is made by this construct in terms of the format and structure of the content of documents shared. |
TP 14 | HITSP Send Laboratory Result Message to Ordering Clinician and Providers of Care Transaction Package
This Transaction Package specification supports:
- Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician
- Transmission of complete, preliminary, final and updated laboratory results (or notification of the availability of laboratory results) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient)
|
TP 20 | HITSP Access Control Transaction Package
The Access Control Transaction Package provides the mechanism to administer security authorizations which control the enforcement of security policies including: role-based access control; entity based access control; context based access control; and the execution of consent directives. In an emergency, this construct supports the capability to alter access privileges to the appropriate level (failsafe/emergency access), which may include override of non-emergency consents. |
TP 21 | HITSP Query for Existing Data Transaction Package
This Transaction Package enables interoperable systems, e.g. those supporting quality measurement, to query and retrieve data from another clinical system. |
TP 22 | HITSP Patient ID Cross-Referencing Transaction Package
This specification includes by reference the transactions and components that comprise the Patient ID Cross-Referencing Transaction Package. Source material is from the IHE IT Infrastructure (ITI) Technical Framework (TF), Volume 2 (ITI TF-2). The two transactions within this package are:
- The IHE Patient ID Cross-Referencing (PIX) transaction is described in IHE-ITI TF-2 §3.9.1
- The IHE Patient Identity Feed transaction is described in IHE-ITI TF-2 §3.8.1
|
TP 30 | HITSP Manage Consent Directives Transaction Package
The Manage Consent Directives Transaction Package describes the messages needed to capture, manage, and communicate rights granted or withheld by a consumer to one or more identified entities in a defined role to access, collect, use or disclose individually identifiable health information (IIHI), and also supports the delegation of the patient’s right to consent. The transactions described in this construct are intended to be carried out by HITSP/TP13 - Manage Sharing of Documents. |
TP 43 | HITSP Medication Orders Transaction Package
This Transaction Package is used to define Transactions between prescribers (who write prescriptions) and dispensers (who fill prescriptions). It is used for new prescriptions, refill requests, prescription change requests and prescription cancellations. Orders/prescriptions may occur in many different real world settings, such as inpatient, long term care and ambulatory settings. |
TP 46 | HITSP Medication Formulary and Benefits Information Transaction Package
The HITSP Medication Formulary and Benefits Information Transaction Package addresses two tasks. The first task is to perform an eligibility check for a specific patient’s pharmacy benefits. The second task is to obtain the medication formulary and benefit information. |
TP 49 | HITSP Sharing Radiology Results Transaction Package
This transaction package supports the sharing of radiology result data in a document sharing functional flow scenario. |
TP 50 | HITSP Retrieve Form for Data Capture Transaction Package
This Transaction Package enables capture of supplemental data variables not typically maintained in an electronic health record or laboratory information system through a more seamless integration with the local electronic management system. This allows for the local system to retrieve a form specific to the identified potential public health threat. |
Transaction |
T 14 | HITSP Send Laboratory Result Message Transaction
This Transaction specification supports:
- Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician
- Transmission of complete, preliminary, final and updated laboratory results (or notification of the availability of laboratory results) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient)
|
T 15 | HITSP Collect and Communicate Security Audit Trail Transaction
The Collect and Communicate Security Audit Trail Transaction is a means to provide assurance that security policies are being followed or enforced and that risks are being mitigated. This document describes the mechanisms to define and identify security relevant events and the data to be collected and communicated as determined by policy, regulation or risk analysis. It also provides the mechanism to determine the record format to support analytical reports that are needed. |
T 16 | HITSP Consistent Time Transaction
The Consistent Time Transaction provides a mechanism to ensure that all of the entities that are communicating within the network have synchronized system clocks. |
T 17 | HITSP Secured Communication Channel Transaction
The Secured Communication Channel Transaction provides the mechanisms to ensure the authenticity, integrity, and confidentiality of Transactions, and the mutual trust between communicating parties. It supports both application and machine credentials, and user machines (user nodes). |
T 18 | HITSP View Laboratory Results from a Web Application Transaction
This Transaction allows a user to view a laboratory report through a secure browser. This Transaction uses the HITSP/C44 - Secure Web Connection Component. It may not define all functions, constructs and standards necessary to implement a conforming system in a real world environment. 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. |
T 23 | HITSP Patient Demographics Query Transaction
This PDQ Transaction is intended to provide a ‘list patients and their demographics’ query / ‘patient(s) and their demographics identified’ response message pair (QBP^Q22, RSP^K22) for use wherever such needs exist. This Transaction document extracts the Health Level Seven (HL7) version 2.5 Query and Response data mapping. The underlying basis for this extraction can be found in the Integrating the Healthcare Enterprise IT Infrastructure Technical Framework, Volume 2 (ITI TF-2), Revision 3.0: “Patient Demographics Query.” |
T 24 | HITSP Pseudonymize Transaction
The purpose of this Transaction is to describe a framework for including Pseudonymization Services where the use of “dummy” or pseudo references to specific patients or providers is requred. Pseudo-identifiers are intended to allow accessibility to clinical information, while safeguarding any information that may compromise the privacy of the individual patient or provider. Using pseudo-identifiers can assist in compliance with HIPAA regulations regarding suppression of patient identification information. |
T 29 | HITSP Notification of Document Availability Transaction
The NAV Integration Profile introduces a mechanism allowing notifications to be sent point-to-point to systems within a Cross-Enterprise Document Sharing Affinity Domain (See “IHE IT Infrastructure Cross-Enterprise Document Sharing (XDS) Integration Profile”), eliminating the need for manual steps or polling mechanisms for a Document Consumer to be aware that documents of interest have been registered with an XDS Document Registry Actor. |
T 31 | Document Reliable Interchange
This Transaction uses the IHE Cross-Enterprise Document Reliable Interchange (XDR) Integration Profile, a companion to the IHE Cross-Enterprise Document Sharing (XDS) Integration Profile to support a healthcare delivery organization or clinician who may need to communicate a clinical document to a recipient through direct communication. |
T 33 | HITSP Transfer of Documents on Media Transaction
This Transaction uses the IHE Cross-Enterprise Document Media Interchange Integration Profile developed by Integrating the Healthcare Enterprise (IHE), a companion to the IHE Cross-Enterprise Document Sharing (XDS) Integration Profile to transport the information from a source to a destination. An example might be to transport data from one healthcare provider to another healthcare provider. |
T 40 | HITSP Patient Generic Health Plan Eligibility Verification Transaction
This Transaction is intended to provide the status of a health plan covering the individual, along with details regarding patient liability for deductible, co-pay and co-insurance amounts for a defined base set of Generic benefits or services. The base set of benefits includes, but is not limited to, coverage status and patient liability for medical, chiropractic, dental, hospital inpatient, hospital outpatient, emergency, professional physician office visit, pharmacy and vision services that are included in the patient’s generic health plan benefit. |
T 42 | HITSP Medication Dispensing Status Transaction
This Medication Dispensing Status Transaction provides a medication prescriber the dispensing status of an ordered prescription (dispensed, partially dispensed, not dispensed). This transaction is used for original prescriptions, refills and renewals. It uses the NCPDP SCRIPT Standard Implementation Guide Version 10.1 RXFILL message to provide the status. |
Component |
C 19 | HITSP Entity Identity Assertion Component
The Entity Identity Assertion Component provides the mechanisms to ensure that an entity is the person or application that claims the identity provided. An example of this Component is the validation and assertion of a consumer logging on to a Personal Health Record (PHR) system. |
C 25 | HITSP Anonymize Component
The HITSP Anonymize Component provides specific instruction for anonymizing data that are prepared for repurposing data created as part of routine clinical care delivery. This construct defines the Component specification that provides the ability to anonymize patient identifiable information. |
C 26 | HITSP Nonrepudiation of Origin Component
Provides the mechanisms to support Nonrepudiation of Origin, which refers to both the proof of the integrity and origin of documents in a high-assurance manner, which can be verified by any party. This Component does not provide Nonrepudiation of Receipt. |
C 28 | HITSP Emergency Care Summary Document Using IHE Emergency Department Encounter Summary (EDES) Component
An Emergency Department (ED) summary document is the collection of data from multiple sources (such as physicians, nurses, technologists, etc.) recording the assessments and care delivered by the ED team in response to an ED visit. It is a summary of the patient’s current health status and care tendered in the ED between arrival and ED departure. This Component specifies the use of the IHE Emergency Department Encounter Summary (EDES), Technical Framework Supplement, Volume I, Revision 3.0, 2007-2008. |
C 32 | HITSP Summary Documents Using HL7 Continuity of Care Document (CCD) Component
The Registration and Medication History Document Content Component describes the document content summarizing a consumer’s registration, medication and health data information contained within a Personal Health Record (PHR) for the purpose of information exchange. This component only deals with the exchange of summary information to and from the PHR. |
C 34 | HITSP Patient Level Quality Data Message Component
This Component supports the process of sending patient data from a Quality Message Sender to a Quality Message Receiver for further analysis and aggregation. Patient data are captured as part of the normal process of care performed by healthcare providers such as hospitals, emergency departments and outpatient clinics. |
C 35 | HITSP EHR Lab Result Terminology Component
This document defines the vocabulary for either message-based or document-based laboratory results reporting. |
C 36 | HITSP Lab Result Message Component
This document describes the use of a constrained Health Level Seven (HL7) Version 2.5.1 ORU – Unsolicited Observation Message for electronic laboratory results reporting. |
C 37 | HITSP Lab Report Document Component
This Component prescribes the use of the standard Clinical Document Architecture Release 2 (CDA R2), as in the HL7 V3 2006 normative edition profiled by IHE LAB TF-3 for:
- Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician
- Transmission of complete, preliminary, final and updated (or notification) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient)
- Transmit laboratory result data from electronically enabled healthcare delivery and public health systems in standardized and anonymized format to authorized Public Health Agencies with less than one day lag time.
|
C 38 | HITSP Patient Level Quality Data Document Using IHE Medical Summary (XDS-MS) Component
This Component supports the communication of patient level quality data for quality measurement in a document sharing environment. The HITSP Patient Level Quality Data Document Using IHE Medical Summary (XDS-MS) Component constrains the IHE Medical Summary to support the communication of quality data for analysis and measurement. The specification includes constraints of location and vocabulary. |
C 39 | HITSP Encounter Message Component
This Component supports the process of sending patient encounter data (excluding laboratory, radiology) from a Biosurveillance Message Sender to a Biosurveillance Message Receiver. |
C 41 | HITSP Radiology Result Message Component
This Component supports the process of sending radiology result data from a Biosurveillance Message Sender to a Biosurveillance Message Receiver. Radiology result data are captured as part of the normal process of care performed by healthcare providers. |
C 44 | HITSP Secure Web Connection Component
This component provides the capability to access documents through a secure web browser. |
C 47 | HITSP Resource Utilization Message Component
The Resource Utilization Component specifies the message and content necessary to report utilization and status of health provider resources to public health agencies. This specification reflects the current status of harmonization efforts between HL7 and OASIS. |
C 48 | HITSP Encounter Document Using IHE Medical Summary (XDS-MS) Component
This Component supports the process of sending patient encounter data (excluding laboratory, radiology) in a document sharing functional flow scenario. Patient encounter data are captured as part of the normal process of care performed by healthcare providers, such as hospitals, emergency departments and outpatient clinics. |
Technical Note |
TN 900 | HITSP Security and Privacy Technical Note
The HITSP Security and Privacy Technical Note addresses common data protection issues in a broad range of subject areas, including electronic delivery of lab results to a clinician, medication workflow for providers and patients, quality and consumer empowerment. |
Requirements Design and Standards Selcection |
RDSS 56 | Remote Monitoring Requirements, Design and Standards Selection
The Remote Monitoring RDSS addresses access to remote monitoring information within an electronic health record (EHR) or a consumer’s personal health record (PHR). It focuses on the communication of interoperable remote monitoring information from an ambulatory setting to the EHR and the PHR, and not on the communication and process by which data are captured and transmitted from the monitoring device itself. |
RDSS 57 | Patient-Provider Secure Messaging Requirements, Design and Standards Selection
The Patient-Provider Secure Messaging RDSS addresses the processes and information needs associated with secure messaging between patients and providers. It discusses scenarios in which patients interact remotely with their healthcare providers using common information technologies readily available in the home and other settings. |
RDSS 58 | Personalized Healthcare Requirements, Design and Standards Selection
The Personalized Healthcare RDSS focuses on the exchange of genetic/genomic test information, personal and family health history, and the use of analytical tools in electronic health records (EHRs) to support clinical decision-making. |
RDSS 59 | Consultations and Transfers of Care Requirements, Design and Standards Selection
The Consultations & Transfers of Care RDSS addresses the electronic exchange of information between clinicians, particularly between requesting and consulting clinicians, to support consultations, including specialty services and second opinions. It also addresses the exchange of clinical information needed during transfers of care. A transfer of care occurs when a patient is discharged or transferred from one health setting to another, such as to or from an acute care hospital, skilled nursing or rehabilitation facility, or to the home with or without home healthcare services. |
RDSS 60 | Immunizations and Response Management Requirements, Design and Standards Selection
The Immunizations and Response Management RDSS focuses on the information needs of consumers, clinicians, registries, public health, and inventory managers carrying out routine care activities associated with immunizations. The RDSS does not address all capabilities required for public health response planning or response management in emergency situations. |
RDSS 61 | Public Health Case Reporting Requirements, Design and Standards Selection
The Public Health Case Reporting RDSS addresses public health case reporting and also adverse event reporting constrained to post-market vaccines and medications. It focuses on using data in electronic health records (EHRs) and augmenting that data in order to assist those individuals or entities performing provider roles for reporting to public health, the Food and Drug Administration, manufacturers, etc. The RDSS also discusses the incorporation of reporting criteria into EHRs to assist in the possible identification and reporting of public health Cases and adverse events. |
Reference |
REF 01 | REFERENCE DOCUMENT: Access to Standards Referenced in IS 01 (version 2.1)
This reference document identifies each standard referenced in IS 01 (V2.1), the Interoperability Specification for Electronic Health Record (EHR) Laboratory Results Reporting. The file provides primary and secondary links, as appropriate, to facilitate access to the referenced standards. Note: Certain documents may be freely available while others may require a purchase decision. |
REF 02 | REFERENCE DOCUMENT: Access to Standards Referenced in IS 02 (version 2.1)
This reference document identifies each standard referenced in IS 02 (V2.1), the Interoperability Specification for Biosurveillance. The file provides primary and secondary links, as appropriate, to facilitate access to the referenced standards.
Note: Certain documents may be freely available while others may require a purchase decision. |
REF 03 | REFERENCE DOCUMENT: Access to Standards Referenced in IS 03 (version 2.1)
This reference document identifies each standard referenced in IS 03 (V2.1), the Interoperability Specification for Consumer Empowerment. The file provides primary and secondary links, as appropriate, to facilitate access to the referenced standards.
Note: Certain documents may be freely available while others may require a purchase decision. |