The Utah Department of Health (UDOH) Utah Statewide Immunization Information System (USIIS) is a software application that enables healthcare providers to enter and submit immunization records for persons in Utah. USIIS maintains immunization histories, consolidating information submitted across providers. The USIIS application also offers clinical decision support and vaccine inventory management modules. USIIS is a lifespan system, managing records for individuals of all ages.
Healthcare providers may submit immunization information to USIIS by two methods – by using the online web application and/or by submitting data from providers’ electronic health record (EHR) systems via electronic data interfaces.
This document provides an overview of:
The below USIIS HL7 Implementation Guides for immunization messaging describes the content and HL7 message mapping specifications for the set of data elements utilized to communicate information to USIIS.
USIIS supports the following options to accommodate a variety of EHR system and healthcare provider needs.
USIIS supports HL7 versions 2.3.1, 2.4 and 2.5.1.
USIIS does not develop new ASCII interfaces with EHR vendors, but continues to support some legacy interfaces.
USIIS supports uni-directional interfaces – i.e., data submitted to USIIS, and bi-directional interfaces – i.e., data submitted to USIIS with a full immunization history returned from USIIS.
USIIS accepts data in batches – i.e., one or more patient records submitted periodically via a file, and real-time – i.e., a record sent immediately from a source EHR system to USIIS.
Data submitted to USIIS must be transported by a secure, encrypted network connection. USIIS accepts data transferred manually via the USIIS File Transfer web application (HTTPS), or automated via SFTP, VPN, SOAP Web Service, and HTTP POST. Real-time interfaces must use VPN, SOAP Web Service, or HTTP POST connections. USIIS will also accept immunization data passed through the Utah Health Information Network’s (UHIN) Clinical Health Information Exchange (cHIE) if the interface meets specific criteria.
EHR vendors will undertake the following steps to develop and deploy a new interface with USIIS. This work must be completed prior to offering an EHR-USIIS interface to vendors’ customers in Utah.
Contact the USIIS Program to discuss and define the interface.
Does the EHR vendor provide a “hub” connection for interface data submission for their Utah customers? If so, determine the transport method.
Obtain the applicable USIIS implementation guide for HL7 messaging.
Develop the interface that will extract data from the EHR system and format according to the HL7 standard from the applicable implementation guide.
Submit test data to USIIS.
USIIS will first visually inspect test messages for accurate format and content.
USIIS will then process test messages into the USIIS test system.
The EHR vendor will update the interface based on USIIS feedback about the test data. This is usually an iterative process.
If there is an EHR vendor hub, configure the network connection.
Test the network connection and hub data submission to USIIS.
Select a customer pilot site at which to deploy and test the interface.
If the EHR vendor does not provide a hub connection, establish a secure network connection with the provider.
The EHR vendor will install and configure the interface to submit authentic pilot site data to USIIS for processing into its test system.
USIIS will assess the data to ensure the interface accurately processes authentic data.
The EHR vendor will update the interface to address any issues identified by the pilot test.
Determine the EHR-USIIS interface deployment processes.
Define how the EHR vendor will work with both USIIS and a customer when ready to implement the interface at a Utah customer’s location(s).
Define how the EHR vendor and USIIS Program will maintain the interface into the future – to accommodate enhancements and bug fixes.
Communicate to Utah customers the availability of the EHR-USIIS interface.
Provide instructions on how to request the interface.
Provide instructions on how to configure the interface, as applicable.
Provide instructions on how to turn on and run the interface, as applicable.
Providers will undertake the following process to implement an EHR-USIIS interface at their location(s).
Check the USIIS website or contact the USIIS Program if to find out if the EHR vendor has an USIIS interface.
If the EHR vendor has not yet developed a USIIS interface, request that they develop an interface to USIIS.
If the EHR vendor has an USIIS interface in production:
Follow the EHR vendor’s process for ordering the EHR-USIIS interface. Note: Some EHR vendors may charge for their interface software or the EHR-USIIS interface.
Provide the EHR vendor the USIIS Provider ID(s) of your facility locations. Note: This is the USIIS Provider ID, not your VFC PIN.
Work with the EHR vendor to get the interface installed and/or configured at your location(s).
If the EHR interface requires you to establish a secure network connection with USIIS – i.e., the vendor does not provide a vendor “hub,” contact USIIS to do this.
Work with the EHR vendor and USIIS Program to initiate sending patient data from the EHR system to USIIS via the interface.
USIIS will assess the data and process into the USIIS test system.
USIIS will contact the EHR vendor and customer if the EHR interface has not been configured accurately, causing inaccurate or incomplete data submission.
USIIS will contact the customer if data completeness or quality requires one of the following actions:
User-defined EHR table value (pick-list) seems to be inaccurate.
Important data is not being entered into the EHR system that is important for USIIS – especially if the provider participates in the VFC program, or uses USIIS Vaccine Inventory.
Once USIIS establishes the provider’s data is accurate and complete, it will move the interface to production, processing subsequent data to be processed into USIIS.
For more information about EHR-USIIS interfaces, Email: email@example.com