ASIIS EHR Interoperability
Provider HIT Survey
HL7 Test Tool
Ask a Question
Welcome to ASIIS EHR Interoperability Home Page
Interoperability, as defined by www.Webster-dictionary.org is “the ability to exchange and use information…” Interoperability as applied to immunization record exchange between electronic health record (EHR) systems and statewide immunization information systems (IIS) means the ability to share patient immunization records electronically through HL7 standard communication protocols.
Immunization information systems (IIS), or registries, help providers and families by consolidating immunization information into one reliable source. They also save money by ensuring that children get only the vaccines they need and improve office efficiency by reducing the time needed to gather and review immunization records. Public health agencies use IIS to conduct surveillance, maintain high immunization coverage rates for the population, and for outbreak management and emergency response.
The Arizona State Immunization Information System (ASIIS) has developed an interoperability engine that will promote this meaningful exchange of patient and immunization record information between ASIIS and EHRs at immunization-reporting organizations (practices, hospitals, and clinics).
Interoperability with ASIIS - How can you get started?
The electronic exchange of “meaningful use” immunization data is enabled through the incorporation of data and messaging standards. Health Level Seven (HL7) is an accredited, nationally recognized standard for electronic data exchange for clinical and administrative messages in healthcare environments. Arizona's immunization registry, ASIIS, will support meaningful use stage 2 compliant data exchanges with EHR systems that have the capability to exchange Immunization data using HL7 version 2.5.1. HL7 version 2.3.1 may only be used to attest for meaningful use stage 1. The Centers for Disease Control and Prevention (CDC) has published an implementation guide for immunization transactions for version
of HL7 which should be used by providers seeking to establish an interface with ASIIS. Providers can interface electronically from their EHR to the ASIIS application and transfer patient and immunization record information. If interested, please complete this
Initial Interest Form
and send it to email@example.com or fax it to the number provided on the form. Submission of this Initial Interest Form does not guarantee that ASIIS will be able to set you up with a data exchange immediately. You will be prioritized and will hear back from the ASIIS office in a couple of days.
Why exchange data with an IIS?
Provider organizations from across the state are mandated by ARS §35-136, effective January 1, 1998 to submit immunization records to ASIIS. In 2009, another statute was added that requires pharmacist-administered vaccines given to adults also be reported to ASIIS. There are a number of good reasons why exchanging data electronically between an IIS and other systems (especially an EHR) is desirable:
Create a complete immunization record:
Probably the most compelling reason to exchange information with an IIS is to establish as complete an immunization record for a patient as possible. This reduces over- and under-immunization in the clinical setting (when data is retrieved from an IIS), and allows for population-based surveillance at the public health agency (when data is sent to an IIS).
Reduce the burden of on-line data entry:
As more and more electronic health record systems (EHRs) are deployed, more and more immunization data will already exist in electronic form even before it is ready to be sent to an IIS. Yet in many jurisdictions, users are forced to key-enter immunization data twice (or more): once in a local system, and then again in the IIS. This duplicative activity can be eliminated through proper implementation of electronic data exchange.
Enable special functions only found in an IIS:
Most IIS contain special functions not found in a typical EHRs. For example, IIS contains sophisticated algorithms for determining when immunizations are due or overdue for a patient. They also support reminder and recall functions that allow outreach to patients to encourage them to receive a needed immunization. Through data exchange these needed functions can be supported when an EHR might not normally be capable of performing them appropriately.
Pressure from some users to only use institutional applications:
Clinical practice and supporting clinical applications are equally complicated. Often, an IIS is perceived of as being more difficult to support. IIS typically look different, behave differently, and require different usernames and passwords than institutional systems. For this reason, an increasing number of institutions are discouraging their users from logging in to IIS while at the same time looking for alternative ways to provide the data and special features that IIS offers within their local systems. Electronic data exchange represents one key strategy in fulfilling the data needs of this growing set of organizations.
It's one of the Minimum Functional Standards for IIS:
Exchange of immunization records via the HL7 protocol is Minimum Functional Standard #7 for IIS as defined by the Centers for Disease Control and Prevention (CDC) and approved by the National Vaccine Advisory Committee (NVAC). Though there is no certification process as of yet for IIS, many projects are funded through by the CDC under Section 317 of the Public Health Service Act. Compliance with CDC minimum functional standards is certainly strongly advised, if not required, to receive these public funds.
150 N. 18th Avenue, Phoenix AZ 85007 Phone: (602) 542-1001 Fax: (602) 542-0883
©2014 Arizona Department of Health Services. All rights reserved. Unauthorized use of this System is prohibited.
ADHS Web Site
AZ.GOV Arizona's Official Web Site