Home | About | Membership | News & Announcements | Meetings | Education & Outreach | Faq | Contact Us | Powered by American National Standards Institute
Healhcare Information Technology Standards Panel
HealthCare Information Technology Standards Panel
Did You Know....

Over 700 organizations now participate in the HITSP and its committees.

Welcome to www.HITSP.org

The Healthcare Information Technology Standards Panel (HITSP) is a cooperative partnership between the public and private sectors. The Panel was formed for the purpose of harmonizing and integrating standards that will meet clinical and business needs for sharing information among organizations and systems.

* UPDATE:
HITSP’s contract with HHS concluded on April 30, 2010. Dr. David Blumenthal, the National Coordinator for Healthcare Information Technology, thanked the Panel for their contributions.
To read his letter, click here
.

 

Program of Work

   View by Topic     View by Status      View Complete Library  
 Interoperability Specification
 Capability
 Service Collaboration
 Transaction Package
 Transaction
 Component
 Technical Note
 Requirements Design and Standards Selection
 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 and Access to Clinical Information via Networks 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.

IS 08

Personalized Healthcare Interoperability Specification
The Personalized Healthcare Interoperability Specification focuses on the exchange of clinically useful 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. View the most current version as HTML here.

IS 09

Consultations and Transfers of Care Interoperability Specification
The Consultation and Transfers of Care Interoperability Specification focuses on the electronic exchange of information between requesting clinicians and consulting clinicians, to support consultations, including specialty services and second opinions. This specification also focuses on the exchange of clinical information needed during transfers of care. View the most current version as HTML here.

IS 10

Immunizations and Response Management Interoperability Specification
The Immunizations and Response Management Interoperability Specification focuses on: 1) providing information about individuals who need to receive specific vaccines, drugs, or other interventions; 2) the ability to report, track, and manage administration of vaccines, drugs, isolation, and quarantine; 3) the ability to identify and electronically exchange information describing the treatment or prophylaxis status of populations; 4) the ability to exchange specific resource and supply chain data from public and private sectors. View the most current version as HTML here.

IS 11

Public Health Case Reporting Interoperability Specification
The Public Health Case Reporting Interoperability Specification supports the bi-directional information exchanges of the Public Health Case Reporting process. It focuses on enabling more efficient data capture at the point of care while allowing for optimizing the information delivery format and content allowing for current SDO efforts to be finalized. In the absence of standards in structured content and associated Clinical Decision Support for alerts and information reporting criteria, this Interoperability Specification provides options for the secure communication of basic presentation preserving content to better automate the current paper-based information flows. View the most current version as HTML here.

IS 12

Patient-Provider Secure Messaging Interoperability Specification
The Patient-Provider Secure Messaging Interoperability Specification describes the information flows, issues, and system capabilities that apply to patients and providers that are required for patients to interact with their healthcare clinicians remotely using common computer technologies readily available in homes and other settings. View the most current version as HTML here.

IS 77

Remote Monitoring (RMON) Interoperability Specification
The Remote Monitoring Interoperability Specification addresses the data and information exchange requirements for the transfer of remote monitoring information from a device physically attached to or used by a patient in a location that is remote to the clinician. View the most current version as HTML here.

IS 91

Maternal and Child Health Interoperability Specification
The Maternal and Child Health Interoperability Specification addresses the ability to exchange obstetric and pediatric patient information between Electronic Health Records (EHRs), the ability to incorporate pediatric assessment tools, guidelines and assessment schedules into EHRs, and the ability to exchange standardized patient assessments for antenatal care, pre-natal care, labor and delivery and post-partum care between EHRs. It also addresses the ability to incorporate assessment tools, guidelines and assessment schedules into EHRs for antenatal care, pre-natal care, labor and delivery and post-partum care, as well as the ability to exchange this information with appropriate Public Health programs.

IS 92

Newborn Screening Interoperablity Specification
The Newborn Screening Interoperability Specification describes the information flows, issues, and system capabilities supporting newborn screening reporting and information exchanges among clinical care settings and public health.

IS 98

Medical Home Interoperability Specification
The Medical Home Interoperability Specification focuses on the information received by the Medical Home (MH) for care coordination and the manner in which this information supports individual patient needs and co-morbidity management.

IS 107

EHR Centric Interoperability Specification
This Interoperability Specification consolidates all information exchanges and standards that involve an EHR System amongst the thirteen HITSP Interoperability Specifications in place as of the February 13, 2009 enactment of the American Recovery and Reinvestment Act (ARRA). This Interoperability Specification is organized as a set of HITSP Capabilities, with each Capability specifying a business service that an EHR system might address in one or more of the existing HITSP Interoperability Specifications (e.g., the Communicate Hospital Prescriptions Capability supports electronic prescribing for inpatient prescription orders). Greater detail on these Capabilities is provided as part this Interoperability Specification, with their underlying HITSP constructs referenced in the Complete Library on HITSP.org. View the most current version as HTML here.

IS 158

Clinical Research Interoperablity Specification
The Clinical Research Interoperability Specification covers clinical research in all its forms as it interoperates with healthcare systems, particularly EHRs. The specification spans two industries, healthcare and clinical research, and incorporates standards from healthcare (HL7 and IHE) and research (CDISC). The design leverages existing HITSP constructs and communication methodologies where applicable, and lays out new constructs as needed. The design also leverages the current players in the clinical research industry such as Electronic Data Capture (EDC) systems and research registries.
Capability

CAP 00

HITSP EHR-Centric Capabilities
This Reference Document provides a central location for, and all inclusive list of, current HITSP Capabilities. These Capabilities were developed as a part of the HITSP/IS107 EHR-Centric Interoperability Specification. HITSP/IS107 consolidates all information exchanges that involve an Electronic Health Record (EHR) System within any of the thirteen HITSP Interoperability Specifications existing as of February 13, 2009, the enactment date of the American Recovery and Reinvestment Act (ARRA).

CAP 93

Scheduling
This document facilitates the electronic exchange of scheduling information between a provider and a consumer by defining the interface options and the data requirements for each information exchange.

CAP 99

HITSP Communicate Lab Order Message Capability Specification
The Communicate Lab Order Message Capability satisfies the information exchange requirements for the sending and receiving of a set of laboratory order, control and status messages. Laboratory orders may be from an inpatient or outpatient (e.g.,: Clinic, ER, office, etc) environment.

CAP 117

Communicate Ambulatory and Long Term Care Prescription
This Capability addresses interoperability requirements that support electronic prescribing in the ambulatory and long term care environment. The capability supports: • Transmittal of new or modified prescriptions • Transmittal of prescription refills and renewals • Communication of dispensing status • Request for Benefit Eligibility Determination

CAP 118

Communicate Hospital Prescription
This capability addresses interoperability requirements that support electronic prescribing for inpatient orders that can occur within an organization or between organizations. The capability supports the transmittal of a new or modified prescription from a Hospital to an internal or external pharmacy. It also includes the optionality to access formulary and benefit information.

CAP 119

Communicate Structured Document
Communicate Structured Document (CAP119) addresses interoperability requirements that support the communication of structured health data related to a patient in a context determined by the author of the document. This Capability supports the exchange of all CDA documents. The following are examples of the type of CDA structured data that are supported: • Continuity of Care Document (CCD) • Emergency Department Encounter Summary • Discharge Summary (In-patient encounter and/or episodes of care) • Referral Summary Ambulatory encounter and/or episodes of care • Consultation Notes • History and Physical • Personal Health Device Monitoring Document • Healthcare Associated Infection (HAI) Report Document

CAP 120

Communicate Unstructured Document
The Communicate Unstructured Document Capability addresses interoperability requirements that support the communication of a set of unstructured health data related to a patient in a context set by the source of the document who is attesting to its content. Two types of specific unstructured content are supported, both with a structured CDA header: • PDF-A supporting long-term archival • UTF-8 text

CAP 121

Communicate Clinical Referral Request
The Communicate Clinical Referral Request Capability addresses interoperability requirements that support provider-to-provider (clinical) referral request interaction. It allows the bundling of the referral request document with other relevant clinical documents of interest by referencing such documents as shared by other Capabilities such as: HITSP/CAP119 Communicate Structured Document; HITSP/CAP120 Communicate Unstructured Document; or HITSP/CAP133 Communicate Immunization Summary

CAP 122

Retrieve Medical Knowledge
The Retrieve Medical Knowledge Capability addresses the requirements to retrieve medical knowledge that is not patient-specific based on context parameters. The actual content delivered is not constrained by this Capability; this Capability focuses on providing the mechanism to ask for (query) and receive the medical knowledge

CAP 123

Retrieve Existing Data
The Retrieve Existing Data Capability supports queries for clinical data (e.g., common observations, vital signs, problems, medications, allergies, immunizations, diagnostic results, professional services, procedures and visit history)

CAP 126

Communicate Lab Results Message
The Communicate Lab Results Message Capability addresses interoperability requirements that support the sending of a set of laboratory test results. Ordering Providers of Care receive results as a laboratory results message. The communication of the order is out of scope for this Capability. The content of these test results may be either or both: General Laboratory Test Results; Microbiology Test Results. This Capability may use content anonymization

CAP 127

Communicate Lab Results
The Communicate Lab Results Capability addresses interoperability requirements that support the communication of a set of structured laboratory results related to a patient in a context set by the source of the document who is attesting to its content. Non-ordering Providers of Care access historical laboratory results as documents and "copy-to" Providers of Care may receive document availability notifications to retrieve such lab report documents. Lab Report content creators shall support HITSP specified coded terminologies as defined by specific content subsets specified in this Capability for: General Laboratory Test Results; Microbiology Test Results. This Capability may use content anonymization

CAP 128

Communicate Imaging Information
The Communicate Imaging Information Capability addresses interoperability requirements that support the communication of a set of imaging results (i.e., reports, image series from imaging studies) related to a patient in a context set. This is done by an Imaging System acting as the information source attesting to its content. This Capability may use content anonymization

CAP 129

Communicate Quality Measure Data
This Capability addresses interoperability to support hospital and clinician collection and communication of patient encounter data to support the analysis needed to identify a clinician or hospital’s results relative to an EHR-compatible, standards-based quality measure. Quality measures may include: • Patient-level clinical detail from which to compute quality measures. Patient level clinical data is compiled from both the local systems and from longitudinal data available through other sources such as a Health Information Exchange (HIE) • Patient-level quality data based upon clinical detail. The “patient-level quality data reports” are exported from EHRs or quality-monitoring applications at the point of care This Capability may use content anonymization. Pseudonymization, if needed, is supported by the HITSP/CAP138 - Retrieve Pseudonym. This Capability may use Value Set Sharing

CAP 130

Communicate Quality Measure Specification
This Capability addresses interoperability requirements for an EHR-compatible, standards-based quality measure. In the measure specification, needed patient encounter data elements are identified so they can be extracted from local systems and from longitudinal data available through other sources such as a Health Information Exchange (HIE). The measure specification also includes various sets of exclusion/inclusion criteria to identify which patients to include in calculation of the measure. This Capability may use Value Set Sharing

CAP 135

Retrieve and Populate Form
This Capability addresses interoperability requirements to support the upload of specific captured data (e.g. public health surveillance reportable conditions, healthcare associated infection reporting) to Public Health Monitoring Systems and Quality Organizations Systems. The forms presented may be pre-populated by information provided by the clinical or laboratory information systems to avoid manual re-entry. A number of supplemental information variables may be captured from within the user’s clinical information system to improve the workflow and timeliness of required reporting. One or more types of form content may be supported: • Pre-population for Public Health Case Reports from Structured Documents using CDA • Pre-population for Quality Data from Structured Documents using CDA • No pre-population content Systems may optionally support the means to retrieve request for clarifications

CAP 136

Communicate Emergency Alert
The Communicate Emergency Alert Capability addresses interoperability requirements to support multicast of non-patient specific notification messages about emergencies events, alerts concerning incidence of communicable diseases, alerts concerning population needs for vaccines and other generic alerts sent to an identified channel. The intended recipients are populations such as “all emergency departments in XXX county”, “within a geographic area”, etc.

CAP 138

Retrieve Pseudonym
This Capability addresses interoperability requirements to support a particular type of anonymization that both removes the association with a data subject, and adds an association between a particular set of characteristics relating to the data subject and one or more pseudonyms. This enables a process of supplying an alternative identifier, which permits a patient to be referred to by a key that suppresses his/her actual identification information. The purpose of this Capability is to offer a pseudonymization framework for situations that require the use of specific data without disclosing the specific identity of patients or providers. 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. However, unlike anonymization, the alternative identifier key can be used to re-identify the individuals whose data was used

CAP 140

Communicate Benefits and Eligibility
This Capability addresses interoperability requirements that support electronic inquiry and response about a patient’s eligibility for health insurance benefits. The information exchanged includes the following: • A patient’s identification (e.g., name, date of birth, and the health plan’s member identification number) • Communication of a member’s status of coverage and benefit information and financial liability • Access to information about types of services, benefits and coverage for various medical care and medications This Capability provides clinicians and healthcare providers with information about their patient’s health insurance coverage and benefits.

CAP 141

Communicate Referral Authorization
This Capability addresses interoperability requirements that support electronic inquiry and response to authorizing a patient (health plan member) to be referred for service by another provider or to receive a type of service or medication under the patient’s health insurance benefits. The Capability supports the transmittal of a patient’s name and insurance identification number with the request for the type of service. It also includes the following optional requirements: • Identification of the type of service or medication requested for benefit coverage (does not guarantee payment by insurance provider) • Communication of a referral notification number or authorization number from the Payer System to the Provider System It provides clinicians and pharmacists with information about each patient’s medical insurance coverage and benefits. It may include information on referral or authorization permission.

CAP 142

Retrieve Communications Recipient
This Capability addresses interoperability requirements that support access to a directory to identify one or more communication recipients in order to deliver alerts and bi-directional communications (e.g., public health agencies notifying a specific group of service providers about an event). The method and criteria by which individuals are added to a directory is a policy decision, which is out of scope for this construct

CAP 143

Manage Consumer Preference and Consents
This Capability addresses management of consumer preferences and consents as an acknowledgement of a privacy policy. This Capability is used to capture a patient or consumer agreement to one or more privacy policies; where examples of a privacy policy may represent a consent, dissent, authorization for data use, authorization for organizational access, or authorization for a specific clinical trial. This Capability also supports the recording of changes to prior privacy policies such as when a patient changes their level of participation or requests that data no-longer be made available because they have left the region
Service Collaboration

SC 108

Access Control Service Collaboration
The Access Control service provides the mechanism for 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. View the most current version as HTML here.

SC 109

Security Audit Service Collaboration
The Security Audit Service Collaboration describes the mechanism to record security relevant events in support of policy, regulation, or risk analysis. It also provides the mechanism to determine the record format to support analytical reports that are needed. View the most current version as HTML here.

SC 110

Patient Identification Management Service Collaboration
The Patient Identification Management Service Collaboration provides the ability to lookup and/or cross-reference patient identities. View the most current version as HTML here.

SC 111

Knowledge and Vocabulary Service Collaboration
The Knowledge and Vocabulary Service Collaboration provides the ability to retrieve medical knowledge and terminology. View the most current version as HTML here.

SC 112

Healthcare Document Management Service Collaboration
The Healthcare Document Management Service Collaboration provides the ability to share healthcare documents using a set of topologies, such as Media, e-Mail, Point-to-Point, Shared within a Health Information Exchange, and Shared within a larger community (made up of potentially diverse Health Information Exchanges). View the most current version as HTML here.

SC 113

Query for Existing Data Service Collaboration
The Query for Existing Data service collaboration provides the capability to query and retrieve data from another clinical system, and the capability to respond to same queries. It applies the necessary Security and Privacy constructs and supports all the queries found in TP21. View the most current version as HTML here.

SC 114

Administrative Transport to Health Plan Service Collaboration
The Administrative Transport to Health Plan service collaboration provides the transport mechanism for conducting administrative transactions with health plans. View the most current version as HTML here.

SC 115

HL7 Messaging Service Collaboration
The HL7 Messaging service collaboration provides the capability to send and receive HL7 messages. The Service Collaboration applies the necessary Security and Privacy constructs. View the most current version as HTML here.

SC 116

Emergency Message Distribution Service Collaboration
Emergency Message Distribution performs a multicast notification to specifically identified populations, such as emergency departments. View the most current version as HTML here.
Transaction Package

TP 13

HITSP Manage Sharing of Documents Transaction Package
The Manage Sharing of Documents 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
The Send Laboratory Result Message Transaction supports: transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician; and 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 for 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. An example of this is a functional role that has the permission to perform an act (e.g., consumer updating a Personal Health Record (PHR). In an emergency, this construct must support 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
The Query for Existing Data Transaction Package is based on the IHE Query for Existing Data Integration Profile (QED) which supports dynamic queries for clinical data, including vital signs, problems, medications, immunizations, diagnostic results, procedures and visit history. A wide variety of systems often needs access to dynamic clinical information stored and maintained in an EMR system or other clinical data repository. The construct makes the information widely available to other systems within and across enterprises to support provision of better clinical care.

TP 22

HITSP Patient ID Cross-Referencing Transaction Package
The Patient ID Cross-Referencing Transaction Package is used for identifying and cross-referencing different attributes for the same patient. It contains a query for cross-reference and patient identity feed transactions. These transactions are used to identify patients from a list of potentials, and/or to communicate patient demographic data.

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
The Medication Orders 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. View the most current version as HTML here.

TP 46

HITSP Medication Formulary and Benefits Information Transaction Package
The 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
The Sharing Imaging Results 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
The Retrieve Form for Data Capture 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 information system. This allows for the local system to retrieve a form specific to the identified potential public health threat. In the context of quality, it allows for the local system to capture supplemental data elements required for quality reporting that may not be available to the electronic health record.

TP 89

Sharing Imaging Results Transaction Package
The Sharing Imaging Results Transaction Package supports the process of sharing medical imaging results data. Imaging results data are captured as part of the normal process of care performed by healthcare providers. This data can be made available through document sharing for both clinical care and public health purposes. View the most current version as HTML here.
Transaction

T 14

HITSP Send Laboratory Result Message Transaction
The Send Laboratory Result Message Transaction supports: transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician; and 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). View the most current version as HTML here.

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 transmissions, and the mutual trust between communicating parties. Its objectives include providing: mutual node authentication to assure each node of the others’ identity; transmission integrity to guard against improper information modification or destruction while in transit; and transmission confidentiality to ensure that information in transit is not disclosed to unauthorized individuals, entities, or processes.

T 18

HITSP View Laboratory Results from a Web Application Transaction
The View Laboratory Results from a Web Application 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
The Patient Demographics Query 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, Patient Demographics Query integration profile.

T 24

HITSP Pseudonymize Transaction
The Pseudonymize Transaction describes 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
The Document Reliable Interchange Transaction provides a standards-based mechanism for conveying a set of medical documents in a point-to-point network-based communication. 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. Cross-Enterprise Document Reliable Interchange (XDR) uses the XDS defined metadata formats in a simpler environment in which the communicating parties have agreed to a point-to-point interchange rather than communicating via document sharing.

T 33

HITSP Transfer of Documents on Media Transaction
The Transfer of Documents on Media Transaction describes both the type of media (CD-ROM, USB Memory, and e-Mail) that may be used to write the documents and provides a directory structure that must be followed in order for the contents to be successfully accessed and processed by systems. An example might be to transport data from one healthcare provider to another healthcare provider, or a healthcare consumer may wish to move the contents of a Personal Health Record (PHR) using physical media or e-Mail. 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.

T 40

HITSP Patient Generic Health Plan Eligibility Verification Transaction
The Patient Health Plan Eligibility Verification 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, 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.

T 63

Emergency Message Distribution Element Transaction
The Emergency Message Distribution Element Transaction selects the Emergency Data Exchange Language (EDXL) Distribution Element (DE) v1.0 standard, and is a multicast notification message sent to an identified population (assume this is not to the general public, but to specifically identified populations, such as emergency departments). View the most current version as HTML here.

T 64

Identify Communication Recipients Transaction
The Identify Communication Recipients Transaction is intended to serve the purpose of identification of communication recipients and the subsequent purpose of delivery of alerts and bi-directional communications (e.g., public health agencies notifying a specific group of service providers about an event.) The method and criteria by which individuals are added to a directory is a policy decision, which is out of scope for this construct. It uses the Integrating the Healthcare Enterprise (IHE) Personnel White Pages profile which provides access to basic directory information for identifying one or more recipients. View the most current version as HTML here.

T 66

Retrieve Value Set Transaction
The Retrieve Value Set Transaction is used to transform human or computer vocabularies. For example, it can be used to convert the initial capture of a human-readable concept into a computer vocabulary captured in a document or message that will be communicated. It may also be used in the reverse, to take computer vocabulary and convert to human-readable form. View the most current version as HTML here.

T 67

Clinical Referral Request Transport Transaction
The Clinical Referral Request Transport Transaction will be used to transport the provider to provider (clinical) referral request interaction. It is based on the Integrating the Healthcare Enterprise (IHE) Document-based Referral Request (DRR) profile which is used to bundle a referral request document with other relevant clinical documents of interest and optionally to send a trigger message to the receiving provider system. View the most current version as HTML here.

T 68

Patient Health Plan Authorization Request and Response Transaction
The Patient Health Plan Authorization Request and Response Transaction provides a mechanism for a healthcare provider (other than a retail pharmacy) to request approval from a health plan to authorize certain healthcare services, when required by the patient’s health plan contract. The information exchanged includes, but is not limited to, approval status for coverage, allowed service provider(s), and certification dates for services that are included in the patient’s health plan benefits. The response from the health plan indicates that the health plan has determined that the particular service(s) will or will not be covered, and what is the level of coverage if that information is available from the health plan. View the most current version as HTML here.

T 79

Pharmacy to Health Plan Authorization Request and Response Transaction
The Pharmacy to Health Plan Authorization Request and Response Transaction provides a mechanism for a pharmacy to request approval from a health plan to authorize certain healthcare products and services, as required by the patient’s health plan contract. The health plan responds to the pharmacy’s request for the approval of products and/or services. The information exchanged includes, but is not limited to, approval status for coverage of the products and/or services that are included in the patient’s health plan benefits and/or authorization limitations. View the most current version as HTML here.

T 81

Retrieval of Medical Knowledge Transaction
The Retrieval of Medical Knowledge Transaction enables the request and receipt of additional knowledge about a medical concept based on specific context parameters. This transaction does not prescribe the knowledge content of the message returned but provides the specifications for the query for and receipt of additional knowledge. It uses the Health Level 7 (HL7) Context-Aware Information Retrieval (Infobutton) Specification: URL Implementation Guide as the base standard for implementation. View the most current version as HTML here.

T 85

Administrative Transport to Health Plan
The Administrative Transport to Health Plan Transaction will be used as the transport for administrative transactions between a provider and a health plan. Examples include a pharmacy obtaining health plan eligibility, and a physician requesting referral or authorization information from a health plan. This construct is based on the CAQH Phase II CORE #270 Connectivity Rule v2.0.0, which addresses the message envelope metadata, the message envelope standards, and the submitter authentication standards for administrative transactions, as well as communications-level errors, and acknowledgements. View the most current version as HTML here.
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 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
The 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
The Emergency Care Summary Document Using IHE Emergency Department Encounter Summary (EDES) Component 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 Summary Documents Using HL7 Continuity of Care Document (CCD) Component describes the document content summarizing a consumer's medical status for the purpose of information exchange. The content may include administrative (e.g., registration, demographics, insurance, etc.) and clinical (problem list, medication list, allergies, test results, etc) information. This Component defines content in order to promote interoperability between participating systems such as Personal Health Record Systems (PHRs), Electronic Health Record Systems (EHRs), Practice Management Applications and others.

C 34

HITSP Patient Level Quality Data Message Component
The Patient Level Quality Data Message 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
The Lab Result Terminology Component defines the vocabulary for either message-based or document-based laboratory results reporting.

C 36

HITSP Lab Result Message Component
The Lab Result Message Component 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
The Lab Report Document 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); transmission of 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
The Patient Level Quality Data Document Using IHE Medical Summary (XDS-MS) 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
The Encounter Message 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
The Radiology Result Message 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
The Secure Web Connection 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
The Encounter Document Using IHE Medical Summary (XDS-MS) Component supports the process of sending patient encounter data (excluding laboratory and 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.

C 62

Unstructured Document Component
The Unstructured Document Component is provided for the capture and storage of patient identifiable, unstructured document content, such as text, PDF, and images rendered in PDF. It is based on the Cross-Enterprise Sharing of Scanned Documents (XDS-SD) profile from the Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF). View the most current version as HTML here.

C 70

Immunization Query and Response
The Immunization Query and Response Component is used for a message based exchange of immunization information.  It specifies the use of HL7 Version 2.3.1 Query for Vaccination Record (VXQ), to send a query from the message sender (clinician system, schools, IIS) to the message receiver (immunization registry).

C 72

Immunization Message Component
The Immunization Message Component provides the capability to communicate an update to a patient's vaccination record. It is based upon the Centers for Disease Control and Prevention Implementation Guide for Immunizations Data Transaction using Version 2.3.1 of the Health Level Seven (HL7) Standard Protocol Implementation Guide Version 2.2 June 2006.

C 74

Remote Monitoring Observation Document Component
The Remote Monitoring Observation Document Component describes the document content to convey medical information collected by remote monitoring management systems from monitorng devices and/or device intermediaries for the purpose of information exchange. The content may include administrative (e.g., registration, demographics, insurance, etc.) and clinical (results, vital signs, etc) information. This specification defines content in order to promote interoperability between participating systems. Such systems may include Remote Monitoring Management Systems, Personal Health Record Systems (PHRs), Electronic Health Record Systems (EHRs), Health Information Exchange infrastructure services and other persons and systems as identified and permitted. View the most current version as HTML here.

C 75

Healthcare Associated Infection (HAI) Report Component
The Healthcare Associated Infection (HAI) Report Component specifies a standard for electronic submission of Healthcare Associated Infection (HAI) Reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). HITSP has adopted the HL7 Implementation Guide for CDA Release 2: NHSN Healthcare Associated Infection (HAI) Reports, Release 1 for this construct. View the most current version as HTML here.

C 76

Case Report Pre-Populate Component
The Case Report Pre-Populate Component supports the Data Mapping needed for Public Health Case Reports. Initially the Component supports only those data attributes that are universal or pertain to Drug Safety reporting. For those attributes that are universal in case reporting, this component may be used in support of pre-populating the remaining report types. However, other public health specific attributes will be addressed in subsequent releases. View the most current version as HTML here.

C 78

Immunization Document Component
The Immunization Document Component defines the immunization data content to be exchanged between healthcare entities such as immunization information systems, electronic medical records systems, personal healthcare record systems and other stakeholders. It is based upon the IHE Patient Care Coordination (PCC) Technical Framework Supplement 2008-2009, Immunization Content (IC), Trial Implementation Version 1.0. View the most current version as HTML here.

C 80

Clinical Document and Message Terminology Component
The Clinical Document and Message Terminology Component defines the vocabularies and terminologies utilized by HITSP specifications for Clinical Documents and Messages used to support the interoperable transmission of information. View the most current version as HTML here.

C 82

Emergency Common Alerting Protocol Component
The Emergency Common Alerting Protocol Component selects the OASIS Common Alerting Protocol (CAP) v1.1 standard, and is used as a multicast notification message sent to an identified channel. The intended recipients are populations such as “all emergency departments in XXX county”, “within a geographic area”, etc. View the most current version as HTML here.

C 83

CDA Content Modules Component
The CDA Content Modules Component defines the content modules for document based HITSP constructs utilizing clinical information. These Content modules are based on IHE PCC Technical Framework Volume II, Release 4. That technical framework contains specifications for document sections that are consistent with all implementation guides for clinical documents currently selected for HITSP constructs. View the most current version as HTML here.

C 84

Consult and History & Physical Note Component
The Consult and History & Physical Note Component supports two types of commonly used clinical notes, a consult note, and a history and physical note. It is intended for use to support the exchange of information from a consulting provider to a referring provider; and may also be used to provide background information from a referring provider to a consulting provider (e.g., prior reports). View the most current version as HTML here.

C 87

Anonymize Public Health Case Reporting Data Component
The Anonymize Public Health Case Reporting Data Component provides specific instructions for anonymizing data that was created as part of routine clinical care data delivery in preparation for repurposing data for public health case reporting. This construct defines the Component specification that provides the ability to anonymize patient identifiable information. Anonymization, according to the International Organization for Standardization (ISO), is the process that removes the association between the identifying data set and the data subject. View the most current version as HTML here.

C 88

Anonymize Immunizations and Response Management Data Component
The Anonymize Immunizations and Response Management Data Component provides the ability to anonymize patient identifiable information for Immunization and Response Management. It provides specific instruction for anonymizing data that was created as part of routine clinical care delivery in preparation for repurposing the data . Anonymization, according to the International Organization for Standardization (ISO), is the process that removes the association between the identifying data set and the data subject. View the most current version as HTML here.

C 90

Clinical Genomic Decision Support Component
The Family History Decision Support for Genetic Risk Analysis Component is used to communicate genetic and family history information from healthcare IT applications to a clinical decision support system that provides an assessment of genetic risk of disease for a patient. It uses the HL7 Version 3 Standard: Clinical Genomics; Pedigree, Release 1 to support the communication of genetic and family history information to the clinical decision support system, and to support the communication of risk information from that system back to the originator. View the most current version as HTML here.

C 105

Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture (QRDA) Component
The HITSP Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture Component supports the communication of patient level quality data for quality measurement in a document sharing environment. Patient encounter data are compiled from both the local systems and from longitudinal data available through a Health Information Exchange (HIE) prior to communicating the retrieved data described in this construct for analysis.

C 106

Measurement Criteria Document Component
This Component supports communication of a quality measure (aka an "eMeasure"). Clinical concepts (e.g. "atrial fibrillation", "coronary artery disease") and parameters (e.g. "numerator", "denominator") in an eMeasure are formally defined to support consistent and unambiguous interpretation. The eMeasure is standardized as a structured document, where one can capture the complete narrative of the measureand a formalized computable representation of statements. View the most current version as HTML here.

C 148

EMS Transfer of Care Component
The EMS Transfer of Care Component defines a clinical document that enables the exchange of key clinical information between pre-hospital providers and emergency department personnel. It meets the needs for reporting information generated by emergency responders occurring during pre-hospital care.  It is based upon the Integrating the Healthcare Enterprise (IHE) Patient Care Coordination (PCC) Technical Framework Supplement EMS Transfers of Care, Trial Implementation.

C 151

Clinical Research Document Component
The Clinical Research Document (CRD) Component profile describes the content and format to be used for pre-population data within the Retrieve Form transaction described within the IHE Retrieve Form for Data-Capture (RFD) Integration Profile. The purpose of the CRD profile is to support a standard set of data in the HL7 Continuity of Care Document (CCD) format which the Form Filler provides for use in Clinical Research

C 152

Labor and Delivery Report Component
The Labor and Delivery Record Component contains information of the course of labor and delivery of a mother and her fetus(es). It can include such information as the relevant maternal history and physical exams, evaluations, laboratory studies and plans of care. This Component supports this information via delivery record documents and a Labor and Delivery Summary document. The Labor and Delivery Record (LDR) is a continuation of the Antepartum Record (APR)

C 154

HITSP Data Dictionary
The HITSP Data Dictionary defines the library of Data Elements that may be used by HITSP constructs in standards based exchanges. The Data Elements are organized into modules to simplify navigation, such as Medications, Advance Directives, Immunizations, etc.

C 156

Clinical Research Workflow Component
The Clinical Research Workflow Component describes the data elements that allow the RFD system roles Form Filler and Form Manager to identify what needs to be done. Clinical Research Workflow defines the content and format of the workflow data to be used within the Retrieve Form transaction described within the RFD Integration Profile. The purpose of Clinical Research Workflow is to support a standard set of data specific to research usage, as found in CDISC CDASH standard

C 161

Antepartum Record Component
The Antepartum Record Component contains information of the antepartum care of a mother and fetus(es). It can include such information as the patient history and physical examinations, evaluations, laboratory studies and plans of care. This Component supports this information via antepartum record documents and an Antepartum Summary document. The Antepartum Summary represents a summary of the most critical information to an antepartum care provider regarding the status of a patient’s pregnancy. The APS document is a medical summary and inherits all header constraints from Medical Summaries

C 162

Plan of Care Component
The Plan of Care Component defines a clinical document that enables the exchange of the ongoing plan of care for a patient.  The plan includes problem issues (nursing diagnoses), expected healthcare outcomes, implementable interventions, and evaluation of progress toward outcomes based on follow-up assessments. It is based upon the Integrating the Healthcare Enterprise (IHE) Patient Care Coordination (PCC) Technical Framework Supplement Patient Plan of Care, Trial Implementation.

C 163

Laboratory Order Message Component
The Laboratory Order Message Component describes the specification for a lab order message and a general laboratory response message. This Lab Order Message Component is the result of a considered assessment of the current practices in electronic laboratory order management and the requirements of the Use Case. In order to encourage rapid and widespread adoption of this Component, HITSP placed emphasis on the message content in current implementations and the ease with which current implementations can become compliant

C 164

Anonymize Newborn Screening Data Component
The Anonymize Newborn Screening Results 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 individually identifiable health information for Newborn Screening reporting data

C 165

Anonymize Long Term and Post Acute Care Data Component
The Anonymize Long Term and Post Acute Care Data 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 for Long Term Care reporting data.

C 166

Operative Note Document Component
The Operative Note Document Component defines a clinical document that enables the exchange of information related to a surgical procedure.  It is created following a surgical or other high-risk procedure and records the pre- and post-surgical diagnosis, pertinent events of the procedure, as well as the condition of the patient following the procedure. It is based upon the HL7 Implementation Guide for CDA Release 2: Operative Notes Draft Standard for Trial Use.

C 168

Long Term and Post Acute Care Assessments Component
The Long Term and Post Acute Care Assessments Component describes how information contained in common long term and post acute care assessment tools are exchanged.  It describes standardized question/answer type assessment or assessment tool using the appropriate universal LOINC ® codes and also supports the local exchange of question/answer type assessments.   It is based upon the Implementation Guide for CDA Release 2: CDA Framework for Questionnaire Assessments (Universal Realm) and CDA Representation of the Minimum Data Set Questionnaire Assessment (U.S. Realm) Based on HL7 CDA Release 2.0 Draft Standard for Trial Use.

C 170

Vital Records Pre-Populate Component
The Vital Records Pre-Populate Component specifies data content and data standards for use in the electronic collection and reporting of birth, death, and fetal death information.
Technical Note

TN 900

HITSP Security and Privacy Technical Note
The Security and Privacy Technical Note was 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 View the most current version as HTML here.

TN 901

Technical Note for Clinical Documents
The Technical Note for Clinical Documents serves as the top-level reference for the HITSP constructs using the HL7 Clinical Document Architecture (CDA) Release 2.0. It includes a design map of existing standards and specifications that are used to meet the stated requirements of the AHIC Use Cases. As additional Use Cases are provided to HITSP, the Technical Note will be updated to address consequent updates to the design and relationship of the associated HITSP constructs. View the most current version as HTML here.

TN 903

Data Architecture Technical Note
The HITSP Technical Note describes the HITSP Data Architecture and the related processes and tools that HITSP uses to identify the data elements, templates and value sets used in Information Exchanges. It explains how within HITSP Specifications: base and composite standards are related to the data architecture; data elements are harmonized across various standards; constraints are applied within HITSP Specifications; and metadata registries support development and implementation. View the most current version as HTML here.

TN 904

Harmonization Framework and Exchange Architecture Technical Note
The Harmonization Framework and Exchange Architecture (HF&EA) Technical Note (TN) defines the terms, concepts, relationships, and associations that are realized in the artifacts that comprise the primary work product of the Panel, e.g., an Interoperability Specification (IS), Capability (CAP), Component (C), Transaction (T), Transaction Package (TP) and Service Collaboration (SC). Further, it organizes the terms and concepts into a HITSP model based on information exchanges specific to data, context, business process, and workflow. The Exchange Architecture defines the fundamental topologies that can be used in implementing the HITSP Interoperability Specifications in configurations such as EHR systems directly connected or connected to Health Information Exchanges (HIEs). View the most current version as HTML here.

TN 905

Device Connectivity
This Technical Note is intended to act as a framing document to provide a high-level perspective on device connectivity requirements, to propose a roadmap for how HITSP might address these requirements, and to indicate how it might work with other external organizations to resolve standardization gaps. The specific requirements to be addressed in the roadmap are only those arising from the Harmonization Requests assigned to HITSP that include device connectivity elements, especially the Common Device Connectivity (CDC) AHIC Extension/Gap December, 2008. This includes the generic types of devices that shall be considered (e.g., ventilators or infusion pumps).

TN 906

TN906 - Quality Measures Technical Note
This document provides several examples of quality measures specified based on information available within electronic data sources as specified using the HITSP IS06 Quality Interoperability Specification. The examples include measures in the Stroke, Venous Thromboembolism and Emergency Department sets of quality measures provided to HITSP by CMS. These examples includes a description of the measures, the sets of data elements needed to address each measure (including any derived data elements), the associated value sets, the eMeasure representation, and the QRDA representation required to report performance based on these measures. Note that QRDA is the HL7 Quality Reporting Document Architecture that enables providers to use the same data constructs developed for information exchange to report on quality measures directly out of the EHR. This document also provides an example of the XML emeasure populated with sample data from the examples. This document is intended to exemplify the use of the HITSP specifications in specifying and reporting on a quality measure. This document is also intended to serve as guidance for the implementation of the example measures using the HITSP standards.

TN 907

Common Data Transport Technical Note
The Common Data Transport Technical Note provides guidance on how HITSP does and/or will provide support for the requirements identified in the Common Data Transport Office of the National Coordinator (ONC) Gap/Extension document.
Requirements Design and Standards Selection

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.

RDSS 144

HITSP Clinical Research Requirements, Design and Standards Selection
This Requirements, Design, Standards Selection document focuses on ways in which electronic health record (EHR) data can support global clinical research activities. Specifically, the exchange of a core set of patient-level clinical information between EHRs and clinical research (CR) systems. This HITSP work product was informed by the prior work of HL7, CDISC, and IHE; testing and demonstrations of EHR and clinical research cooperation at four IHE Connectathons and three HIMSS Interoperability Showcase demonstrations, two real world implementations, and the functional profile developed by the EHR-CR collaborative of PhRMA and eClinical Forum.

RDSS 153

Newborn Screening
The HITSP Newborn Screening Requirements and Design will describe the information flows, issues, and system capabilities supporting newborn screening reporting and information exchanges among clinical care settings and public health. The Use Case upon which this specification is created is focused upon: • The ability to communicate initial screening results, confirmatory testing orders, and results and information specific to referral and management of the patient • The ability to report newborn screening information to Public Health

RDSS 155

Maternal and Child Health
This Requirements and Design (RDSS) addresses the ability to exchange obstetric and pediatric patient information between Electronic Health Records (EHRs), the ability to incorporate pediatric assessment tools, guidelines and assessment schedules into EHRs, the ability to exchange standardized patient assessments for antenatal care, pre-natal care, labor and delivery and post-partum care between EHRs and the ability to incorporate assessment tools, guidelines and assessment schedules into EHRs for antenatal care, pre-natal care, labor and delivery and post-partum care, as well as the ability to exchange this information with appropriate Public Health programs. Maternal and child health can be defined as multiple programs serving various populations of consumers. For the purposes of this Extension/Gap document, the period of time included in maternal and child health is from the determination of pregnancy for the mother-to-be continuing throughout early childhood.

RDSS 157

Medical Home
The Medical Home Requirements, Design, and Standards Selection focuses on information received by the Patient-Centered Medical Home (PCMH) for care coordination and the manner in which this information supports individual patient needs and co-morbidity management. The PCMH represents a shifting paradigm in the practice of medicine characterized by care that is accessible, comprehensive and coordinated and delivered in the context of family and community.
Reference

REF 04

HITSP Acronyms List
View the most current version as HTML here.

REF 06

HITSP Glossary
View the most current version as HTML here.

REF 11

HITSP Versioning Verbiage

REF 12

Quality Reference Document
A Reference Document which provides a full example of the use of the Quality Interoperability Specification to express one of the Stroke quality measures (STK-3) provided to HITSP by CMS. View the most current version as HTML here.

HITSP Member Workspace
(password required)

Public Review and Comment

HITSP and its Stakeholders
Learn more about how HITSP interacts with . . .

HITSP Free Webinars
HITSP Membership
HITSP Harmonization Framework
HITSP Real Life Stories

 

HITSP icon
    | Site Map | Copyright & Disclaimers | Privacy Policy | Terms of Use | © 2009 American National Standards Institute | American National Standards Institute