Immunization Registry
VITL is working with the Vermont Department of Health to develop HL7 interfaces for the Vermont Immunization Registry. This will enable physician practices and hospitals with electronic health records systems to submit data to the Vermont Immunization Registry directly from the EHR system via the interface.
The benefits of submitting data to the Vermont Immunization Registry via an interface include:
- Reduced data entry
- Improved data accuracy
- Faster data delivery
- Fulfill data reporting requirements
- Improved patient care
For information about syndromic surveillance, contact Eileen Underwood at the Vermont Department of Health.
Current immunization project status (last updated 2/8/12):
We are currently working on the infrastructure to support the submission of immunizations using HL7 to the Vermont Immunization Registry via the Vermont Health Information Exchange. The original timelines for this project have been affected due to the Medicity transition.
We do not currently have any committed timelines but will post updates as we have them.
Important notes:
Requirements: The immunization interface project requires that you install the following:
- Patient demographics (ADT) interface
- Immunization (VXU) interface
Readiness by vendor:
Allscripts: If you are an Allscripts customer, you must upgrade to the version of Allscripts Enterprise, Professional, or MyWay that supports a connection to the Allscripts immunization hub in order to be eligible to start this project. If you are not sure if you are on the right version, you should talk to your vendor. VITL is currently working with Allscripts on connectivity between the hub and Medicity.
- Allscripts Enterprise - Version 11.2 or greater should support an immunization hub connection
- Allscripts Professional - The Allscripts immunization hub won't be able to start connections for Pro until Allscripts adds support for Pro. We have not yet heard from Allscripts if this is available yet. The hub connection is the preferred method based on timing, cost, and maintenance.
- Allscripts MyWay - We expect this to be done via the Allscripts immunization hub, but that is still to be determined.
CPSI: CPSI and VITL have begun immunization project work for some sites. Additional sites will be considered once those sites are live.
eClinicalWorks: eClinicalWorks and VITL have begun immunization project work for a pilot practice. Additional practices will be considered once that pilot site is live. eClinicalWorks is planning to use an immunization hub model.
Medent: The functionality required for this project is currently under development by Medent. Medent and VITL have been in regular contact, and VITL will reach out to Medent clients when functionality is in place to begin actual project work.
Physician’s Computer Company (PCC): PCC and VITL have begun immunization project work for a pilot practice. Additional practices will be considered once that pilot site is live.
McKesson Practice Partner: Initial analysis work has begun. Practices will be considered once the vendor is ready.
Not listed: VITL has not yet engaged with your vendor or your vendor does not yet support HL7 messaging for immunizations. Please refer your vendor to the technical specifications links below.
Practice incentives:
No new incentives are available at this time. The cost of EHR interfaces can be reimbursed with pre-approval by VITL.
Other:
- Technical specifications: Please refer to our support site for all currently available VITL interface specifications.
- Historical immunizations: Historical immunizations can be accepted as long as your vendor can send them. Vendor capabilities for loading historical immunizations and logistics of switching over from a monthly batch file will be discussed with your vendor when VITL initiates an immunization project with your site.
- Loading data from the Registry into your EHR: The Immunization Registry can provide batch files for one time historical loads into your EHR. This info generally only includes immunizations performed at your practice. We expect to be able to support this in an automated fashion in the future (AKA "bi-directional"), but no timelines have been committed yet.
