Electronic Health Record (EHR) Electronic Data Exchange with CT WiZ
Connecticut’s Immunization Information System (CT WiZ)
HL7 Onboarding Process
On September 17, 2018, DPH migrated the data from the Connecticut Immunization Registry and Tracking System (CIRTS) into the new CT WiZ! This new Immunization Information System (IIS) enables bi-directional electronic data exchange between your electronic health record (EHR) and CT WiZ.
**Connecticut follows National Standards for Electronic Health Record (EHR) Reporting**
A provider/clinic who orders vaccines from the Connecticut Vaccine Program (CVP), reports immunizations administered to children ages 0 through 18 and is mandated to report immunizations to CT WiZ, you can apply for electronic data exchange with CT WiZ. DPH will send email notifications as you progress through each phase of the onboarding process. These email notifications can be used for Meaningful Use attestation.
Note: As CT WiZ accepts bi-directional data exchange with EHRs, if you are attesting to Meaningful Use (MU) and you are a CVP Provider, you may no longer use the MU exemption letter below to claim an exclusion for Public Health Reporting for Immunizations.
- A provider/clinic who does not vaccinate children ages 0 through 18 and is not mandated to report immunizations to CT WiZ, you do not need to report to CT WiZ. If you are attesting to Meaningful Use, click here for the exemption letter.
Meaningful Use Attestation Information Click here for more information on Meaningful Use.
Follow the steps below to establish an electronic interface between your EHR and CT WiZ. An interface with CT WiZ can be established for a single clinic (regardless of size) or an organization representing multiple clinics that will report through a single interface. The interface can be set up as uni-directional or bi-directional:
Uni-directional is data exchanged in one direction, from the EHR to the IIS. Data exchanged refers to Message Submission (VXU) and Acknowledgment (ACK).
Bi-directional is data exchanged in two directions, from the EHR to the IIS and from the IIS to the EHR. Data exchanged refers to Query (QBP) HL7 message submissions that are sent to an IIS and Response (RSP) HL7 message submissions that are returned by an IIS in response to a querying system.
EHR vendors who have onboarded. If your clinic has the same EHR vendor, establishing an interface with CT WiZ will be easier than ever for your clinic. Whether your vendor is on the list or not, just complete the CT WiZ HL7 application form to get started!
|1. Getting Started|
Before you start your application, review the following documents.
- The onboarding application and NIST reports
- Waiting for testing to begin
- Meetings throughout the process
- The configuration and connection of your EHR to CT WiZ
- The testing and validation of HL7 messages
- Data quality review of HL7 messages
- Going Live in Production
The CT WiZ Local Implementation Guide for HL7 2.5.1 Immunization Messaging Release 1.5 defines what fields and segments the Immunization Information System will and will not accept in an HL7 message.
The CT WiZ Immunization Information System HL7 2.5.1 Release 1.5 Local Delta Implementation Guide lists only the areas where CT WiZ deviates from or elaborates on the information contained in the national implementation guidance.
The NIST Cases Validation Instructions provides guidance on performing the necessary testing and validation of messages in the NIST Tool in order to demonstrate that your EHR System complies with the requirements of HL7 Version 2.5.1 for Immunization Messaging, Release 1.5.
The CVP Patient Eligibility Screening provides guidance on how the clinic should map the vaccine funding program eligibility and funding source for the vaccines in your EHR.
The Vaccines Supplied by CVP (November 2019) provides a list of vaccines supplied by the State of Connecticut. The report contains the vaccine name, brand name, packaging, NDC, manufacturer, CVX code and CT WiZ dropdown selection.
Uni-directional Exchange: VXU Messages documentation
Bi-directional Exchange: Query and Response documentation
|2. Complete the Application|
- Review the Onboarding Readiness Checklist to ensure you are ready to apply.
- Review the Query and Response Readiness Checklist to ensure you are ready to apply.
Ready to apply? Remember, you must successfully complete the NIST tests and save the reports.
Complete the CT WiZ HL7 Application Form. Review the 1st tab and complete the other 4 tabs in the spreadsheet.
Submit the completed Application Form and the NIST Reports to our Helpdesk. Select "EHR Data Exchange" as the category and "Establish an HL7 interface with CT WiZ" as the topic.
|3. Application Status|
|4. Testing Phase|
Phase 1: Confirm that CT WiZ can accept a test message from your EHR System.
Phase 2: Validate messages from your EHR that required fields are populated with proper codes.
Bi-directional Exchange: Query and Response
Once the interface has been configured, providers will actively participate in the testing process to ensure correct results and confirm that clinical records are properly updated.
Phase 1: Testing credentials/URL, connectivity test
Phase 2: Query and Response configuration and testing preparation
Phase 3: Workflow testing
Testing for QBP/RSP is typically composed of the following elements:
- Query from the provider organization (QBP) to CT WiZ
- Response (RSP) from CT WiZ to the provider organization
- Update (VXU) from the provider organization to CT WiZ
- Acknowledgement (ACK) from CT WiZ to the provider organization
Providers should apply multiple layers of testing:
- Submit 25-50 records via VXU to query against for a guaranteed response (exact match and forecast)
- Query using CT WiZ engineered test scenarios (multi-match or too many matches)
- Query CT WiZ for real patients receiving vaccinations at the clinic (match/no match, VXU update after vaccination)
|5. In Production|
- How to run the HL7 Context-based testing in NIST tool
- How to run the HL7 Context-free testing in NIST tool
- How to run the SOAP Envelope testing in NIST tool
- How to run the SOAP Connectivity testing in NIST tool
Connectivity and Transport (SOAP/WSDL)