Printer Friendly, PDF & Email Printer Friendly, PDF & Email

§170.315(f)(1) Transmission to immunization registries

Version 1.1 Updated on 10-06-2016
Revision History
Version # Description of Change Version Date
1.0

Final Test Procedure

01-20-2016
1.1

Updated NIST Normative Test Process Document link.

10-06-2016
Regulation Text
Regulation Text

§170.315 (f)(1) Transmission to immunization registries

  1. Create immunization information for electronic transmission in accordance with:
    1. The standard and applicable implementation specifications specified in §170.205(e)(4).
    2. At a minimum, the version of the standard specified in §170.207(e)(3) for historical vaccines.
    3. At a minimum, the version of the standard specified in §170.207(e)(4) for administered vaccines.
  2. Enable a user to request, access, and display a patient's evaluated immunization history and the immunization forecast from an immunization registry in accordance with the standard at §170.205(e)(4).
Standard(s) Referenced

Please consult the Final Rule entitled: 2015 Edition Health Information Technology (Health IT) Certification Criteria, 2015 Edition Base Electronic Health Record (EHR) Definition, and ONC Health IT Certification Program Modifications for a detailed description of the certification criterion with which these testing steps are associated. We also encourage developers to consult the Certification Companion Guide in tandem with the test procedure as they provide clarifications that may be useful for product development and testing.

Note: The order in which the test steps are listed reflects the sequence of the certification criterion and does not necessarily prescribe the order in which the test should take place.
 

Testing components

No GAP Icon No Documentation Icon Visual Inspection Icon Test Tool Icon ONC Supplied Test Data Icon

 

Paragraphs (f)(1)(i)

System Under Test Test Lab Verification

The Health IT Module creates immunization content using ONC Supplied Test data for each of the test cases from the Administration Test Group under the ONC 2015 Test Plan on the Context-Based Validation Tab of the NIST HL7 v2 Immunization Test Suite. All test cases are required. Input may be performed using manual or automated processes.

For each test case, the Health IT Module generates the indicated HL7 v2.5.1 Z22 VXU immunization information message.

For each test case, the Health IT Module consumes the associated acknowledgement message using the provided test data and according to the § 170.205(e)(4) HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5.

The vaccines in the historical vaccine records are represented using § 170.207(e)(3) HL7 Standard Code Set CVX— Vaccines Administered.

The vaccines in the administered vaccine records are represented using § 170.207(e)(4) National Drug Code (NDC) Directory– Vaccine NDC Linker.

Using the Normative Test Description section of the Normative Test Process Document:

The tester verifies that the Health IT Module creates the source immunization content correctly through visual inspection of the system under test using the test data specification of the Send Administration Message test step associated with the selected test case.

The tester imports the immunization message into the test tool for validation and uses the Validation Report produced by the test tool to verify that the Health IT Module passes without error to confirm that the immunization information messages are conformant to the HL7 v2.5.1 Z22 VXU Unsolicited Vaccine Update message of the § 170.205(e)(4) standard.

The tester verifies that the Health IT Module is able to receive and process a Return an Acknowledgement Z23 message (in response to a "Send Unsolicited Immunization Update Using a VXU" Z22 message) through visual inspection of the system under test using the Juror Document of the Consume Acknowledgement test step associated with the selected test cases.

The tester uses Test Tool Validation Report from (f)(1)(i)(B) test cases and visual inspection of both the Test Tool Validation Report and the Health IT configuration file to verify the historical vaccine records are represented using § 170.207(e)(3) standard.

The tester uses Test Tool Validation Report from (f)(1)(i)(C) test cases and visual inspection of both the Test Tool Validation Report and the Health IT configuration file to verify administered vaccine records are represented using § 170.207(e)(4) standard.


Paragraph (f)(1)(ii)

System Under Test Test Lab Verification
  1. The Health IT Module creates immunization query content using ONC Supplied Test data for each of the test cases from the Evaluate History and Forecast Test Group under the ONC 2015 Test Plan on the Context-Based Validation Tab of the NIST HL7 v2 Immunization Test Suite. All test cases are required. Input may be performed using manual or automated processes.
  2. For each test case, the Health IT Module generates the indicated HL7 v2.5.1 Z44 QBP query message.
  3. The Health IT Module electronically receives HL7 evaluated immunization history and forecast HL7 v2.5.1 Z42 RSP or HL7 v2.5.1 Z33 RSP response messages returned for each of the test cases from the Evaluated History and Forecast Test Group under the ONC 2015 Test Plan on the Context-Based Validation Tab of the NIST HL7 v2 Immunization Test Suite, which is in the Return response to the HL7 v2.5.1 Z44 QBP query message initiated in (f)(1)(ii) Request above, formatted according to the § 170.205(e)(4) HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5. The Health IT Module displays the response to the user.

Using the Normative Test Description section of the Normative Test Process Document:

  1. The tester verifies that the Health IT Module creates the source immunization query content correctly through visual inspection of the system under test using the test data specification of the Send Query test step associated with the selected test case.
  2. The tester imports the query message into the test tool for validation and uses the Validation Report produced by the test tool to verify that the Health IT Module passes without error to confirm that the query message is conformant to the HL7 v2.5.1 Z44 QBP Query for Evaluated History and Forecast message profile of the § 170.205(e)(4).
  3. The Tester verifies that the Health IT Module can process each of the following Test Case responses through visual inspection of the system under test using the Juror Document of the second test step (the Return response) associated with the selected test case from the NIST HL7 v2 Immunization Test Suite:
    1. The Tester verifies that the Health IT Module is able to display a response that contains evaluated history and forecast information for the test patient, through visual inspection of the system under test using the Juror Document of the Return response test step associated with the selected test case.
    2. The tester verifies that the Health IT Module can process a response with a notification indicating that the query for the Evaluated Immunization History and Immunization Forecast is complete but no matching records were found for the person in the query, through visual inspection of the system under test using the Juror Document of the Return response test step associated with the selected test case.
    3. The tester verifies that the Health IT Module can process a response with a notification indicating that the query for the Evaluated Immunization History and Immunization Forecast is complete but too many matches were found for the patient requested through visual inspection of the system under test using the Juror Document of the Return response test step associated with the selected test case.

Alternative Test Method

Summary Alternative Test Method File Test Tool Updated On

Supported by CDC, the Healthcare Information and Management Systems Society Immunization Integration Program (HIMSS-IIP) is a collaborative effort of HIMSS, Drummond Group, and Chickasaw Health Consulting, LLC. HIMSS-IIP was approved as an ONC-Approved Alternate Test Method on October 10, 2017 for testing § 170.315(f)(1).

HIMSS Immunization Integration Program

The ONC–Approved Alternative, HIMSS IIP, has its own set of testing artifacts. For additional information, contact HIMSS IIP.

Version 1.2 Updated on 03-17-2017
Revision History
Version # Description of Change Version Date
1.0

Initial Publication

10-29-2015
1.1

Updated the NIST Test Normative Test Process Document Link.

10-06-2016
1.2

Updated to include clarification to the CCG that compliance with the IG IM Release 1.5 addendum is required for testing and certification.

03-17-2017
Regulation Text
Regulation Text

§170.315 (f)(1) Transmission to immunization registries

  1. Create immunization information for electronic transmission in accordance with:
    1. The standard and applicable implementation specifications specified in §170.205(e)(4).
    2. At a minimum, the version of the standard specified in §170.207(e)(3) for historical vaccines.
    3. At a minimum, the version of the standard specified in §170.207(e)(4) for administered vaccines.
  2. Enable a user to request, access, and display a patient's evaluated immunization history and the immunization forecast from an immunization registry in accordance with the standard at §170.205(e)(4).
Standard(s) Referenced

Certification Companion Guide: Transmission to immunization registries

This Certification Companion Guide (CCG) is an informative document designed to assist with health IT product development. The CCG is not a substitute for the 2015 Edition final regulation. It extracts key portions of the rule’s preamble and includes subsequent clarifying interpretations. To access the full context of regulatory intent please consult the 2015 Edition final rule or other included regulatory reference. The CCG is for public use and should not be sold or redistributed.
 

 

Certification Requirements

Privacy and Security: This certification criterion was adopted at § 170.315(f)(1). As a result, an ONC-ACB must ensure that a product presented for certification to a § 170.315(f) “paragraph (f)” criterion includes the privacy and security criteria (adopted in § 170.315(d)) within the overall scope of the certificate issued to the product.

  • The privacy and security criteria (adopted in § 170.315(d)) do not need to be explicitly tested with this specific paragraph (f) criterion unless it is the only criterion for which certification is requested.
  • As a general rule, a product presented for certification only needs to be tested once to each applicable privacy and security criterion (adopted in § 170.315(d)) so long as the health IT developer attests that such privacy and security capabilities apply to the full scope of capabilities included in the requested certification. However, exceptions exist for § 170.315(e)(1) “VDT” and (e)(2) “secure messaging,” which are explicitly stated.

Design and Performance: The following design and performance certification criteria (adopted in § 170.315(g)) must also be certified in order for the product to be certified.

  • When a single quality management system (QMS) is used, the QMS only needs to be identified once. Otherwise, the QMS’ need to be identified for every capability to which it was applied.
  • When a single accessibility-centered design standard is used, the standard only needs to be identified once. Otherwise, the accessibility-centered design standards need to be identified for every capability to which they were applied; or, alternatively the developer must state that no accessibility-centered design was used.
Table for Privacy and Security
Technical Explanations and Clarifications

 

Applies to entire criterion

Clarifications:

  • For the public health certification criteria in § 170.315(f), health IT will only need to be certified to those criteria that are required to meet the measures the provider intends to report on to meet Objective 8: Public Health and Clinical Data Registry Reporting.
  • Any health IT can be certified to this criterion if it can meet all the requirements of the criterion, which include context exchange and vocabulary standards. There is no specified transport standard or mechanism required for this criterion. Consequently, any additional products used to facilitate immunization data submission in the manner required by the public health agency are not required to be included as part of Certified EHR Technology (CEHRT) implemented by eligible professionals, eligible hospitals, or critical access hospitals for those CMS programs requiring the use of CEHRT. Please consult CMS regulations for more specific requirements for meeting the CEHRT definition. [see also 80 FR 62663]
  • While no transport standard is required for this criterion, an expert panel convened by the CDC and the American Immunization Registry Association (AIRA) has recommended a SOAP-based standard for transport of immunization data. Developers have the discretion to decide which transport standard(s) to implement. [see also 77 FR 54240]
  • CDC issued an addendum to the HL7 2.5.1 Implementation Guide (IG) for Immunization Messaging (IM), Release 1.5. The addendum consolidates the IG IM Release 1.5 information that clarifies the conformance requirements, but does not specify additional substantive requirements. The addendum was adopted with the IG IM Release 1.5 for purposes of testing and certification to this criterion. [80 FR 62663]
  • The criterion is not intended to specify when submissions should be made or the periodicity of the submissions. Consequently, submitting batch files to an immunization registry, provided that they are formatted according to the adopted standards referenced by this certification criterion, is not prohibited by this certification criterion and would be acceptable. [see also FAQ #2]
  • The process for submitting immunization data often differs between public health agencies. We recommend developers work with the state or local immunization registry for guidance on how to submit the immunization data.
  • We provide the following OIDs to assist developers in the proper identification and exchange of health information coded to certain vocabulary standards.
    • HL7 Standard Code Set CVX – Vaccine Administered OID: 2.16.840.1.113883.12.292
    • National Drug Code Directory OID: 2.16.840.1.113883.6.69 [80 FR 62612]
  • Health IT Modules can present for certification to a more recent version of the CVX – Vaccines Administered and National Drug Code Directory – Vaccine Codes code sets than the August 17, 2015 updates per ONC’s policy that permits certification to a more recent version of certain vocabulary standards. [80 FR 62620]

Paragraph (f)(1)(i)

Technical outcome – The Health IT Module can create immunization information according to the IG) IM Release 1.5, and the July 2015 Addendum, using CVX codes for historical vaccines and NDC codes for newly administered vaccines.

Clarifications:

  • For the purposes of administered vaccines, when an immunization is reported at the time it is administered and the actual product is known, the NDC code must be sent. We clarify that for when sending historical vaccines and the actual NDC code is not available, CVX codes can be sent as this method would be supported by health IT certified to this criterion. [see also 80 FR 62663-62664]

Paragraph (f)(1)(ii)

Technical outcome – The Health IT Module enables a user to request, access and display the evaluated immunization history and forecast from an immunization registry for a patient in accordance with the HL7 2.5.1 standard, the HL7 2.5.1. IG for Immunization Messaging, Release 1.5, and July 2015 Addendum.

Clarifications:

  • Health IT (e.g., EHR products) may sometimes have a version of the immunization history that differs from the history in the immunization registry. Likewise, Health IT (e.g., EHR products) that includes immunization forecasting capabilities may produce a forecast that differs from one produced by the immunization registry. We still believe that it is important for an EHR to receive the history and forecast from the registry. Based on compliance with the Release 1.5 IG, a user would be able to see and compare the history and forecast from the certified health IT (e.g., EHR product) with the history and forecast from the immunization registry. However, we note that this criterion does not prescribe a particular workflow or reconciliation requirements. Providers and health IT developers may reconcile forecast and history information in a manner that best meets their needs for workflow and patient safety. [see also 80 FR 62664]

Regulation Text
Regulation Text

§170.315 (f)(1) Transmission to immunization registries

  1. Create immunization information for electronic transmission in accordance with:
    1. The standard and applicable implementation specifications specified in §170.205(e)(4).
    2. At a minimum, the version of the standard specified in §170.207(e)(3) for historical vaccines.
    3. At a minimum, the version of the standard specified in §170.207(e)(4) for administered vaccines.
  2. Enable a user to request, access, and display a patient's evaluated immunization history and the immunization forecast from an immunization registry in accordance with the standard at §170.205(e)(4).
Criterion Subparagraph Test Data
(f)(1)
Content last reviewed on September 21, 2018
Was this page helpful?