IIS Health Level 7 (HL7) Implementation
|HL7 v2.5.1 Implementation Guide for Immunization Messaging, Release 1.5 [3.37 MB, 406 pages]
(Published Nov 5, 2014)
|This Release 1.5 document does not include the Addendum. Please note that the Addendum provides additional clarification of the implementation of the standard. Please send comments and suggestions to Heather Patrick, firstname.lastname@example.org.
|HL7 v2.5.1 Implementation Guide for Immunization Messaging, Release 1.5 [28 pages]
(Published July 1, 2015)
|This Addendum is a supplement to Release 1.5 and does not specify any additional requirements, but rather clarifies existing conformance requirements in Release 1.5. Value set requirements, general clarifications, and Immunization Implementation IG errata are also provided in this addendum. Please send comments and suggestions to Heather Patrick, email@example.com.
|HL7 v2.5.1 Implementation Guide for Immunization Messaging, Release 1.5
(Published October 15, 2018)
|Recommended Standard (consolidated)
|This document is a compilation of Release 1.5 and the Addendum. Release 1.5 continues to remain in effect and is currently the standard recognized by the CDC and AIRA for IIS implementation. Please send comments and suggestions to Heather Patrick, firstname.lastname@example.org.
- Guidance for HL7 RSP Messages to Support Interoperability
Issued on June 7, 2017 by AIRA
- Guidance for HL7 Acknowledgement Messages to Support Interoperability
Issued on October 1, 2015 by AIRA
- Query Responses and Patient Protection
Issued on July 6, 2017 by CDC, AIRA
- Guidance on Detailed Message Structure and the Use of Specific LOINC Codes
Issued on April 15, 2018 by AIRA
- Considerations for an IIS Implementing National Drug Codes
Issued on April 25, 2017
- Updated Guidance for Documenting Vaccine National Drug Codes and Lot Numbers in IIS and EHRs [3 pages]
Issued on June 2017
- Guidance on Indicating Preferable and Contraindicated Vaccines [3 pages]
Issued on September 6, 2019
- National Set of Error Codes
Issued on April 15, 2018
- Populating OBX-14
Issued on September 6, 2019
- Guidance on Unit of Sale/Unit of Use Lot Numbers
Issued on June 14, 2018
- Micro-Guide: Lot Number Validation Best Practices
Issued on May 8, 2014
- Immunization Test Suite
The immunization Test Suite provides tools to help implementers meet conformance to the National Implementation Guide Release 1.5
- Implementation Guide Authoring and Management Tool (IGAMT)
IGAMT provides implementation guide (IG) authors the ability to develop IGs through web-based tooling with HL7 Version 2 intelligence. By using the tool, authors can develop IGs that meet conformance and build directly from the National Implementation Guide.
- Test Case Authoring and Management Tool (TCAMT)
TCAMT provides the ability to develop HL7-focused test cases and expected outcomes. Test cases can be grouped into test plans and held to conformance defined in IGAMT profiles.
- HL7 v2.8.2 Implementation Guide for Immunization Messaging
This is an HL7 US Realm implementation guide for immunization messaging. This new standard is not yet recommended by the CDC and AIRA and is reserved for implementation at a future date. This document adopts many of the use cases and requirements of Release 1.5 IG and adapts them for v2.8.2 while simultaneously clarifying and enhancing the requirements. Several other Guidance Documents (e.g., ACK Guidance) are also now included in the 2.8.2 IG. The CDC and AIRA will issue guidance at a future date when trading partners may transition to the v2.8.2 standard. Please send comments and suggestions to Heather Patrick, email@example.com.
- FHIR Immunization Decision Support Forecast IG
Clinical Decision Support for Immunizations is increasingly being used in health information systems to indicate which vaccinations a patient is due for next. Many of these expert systems are built as stand-alone systems that respond to web service requests. While these independent systems have similar requirements and outputs they use different web service standards.
This project aims to create a common FHIR implementation guide that these expert systems may use to provide a common consistent interface. This common interface will be used for two main purposes:
- Provide a common interface that health information systems may write to and gain access to their choice of CDS engines.
- Provide a common interface that may be used for testing and verifying the output of CDS engines.