Making An Electronic Interface with IIS Most Useful for All Involved: Lessons Learned about Two-Way Electronic Exchange

Background:
The Kansas Immunization Registry (KSWebIZ) has implemented an HL7 interface exchange (both one-way and bi-directional) with multiple vendors. Development, testing, and implementation of the bi-directional interface have identified differences in user functionality among vendors. The differences highlighted gaps in overall usefulness for the provider, immunization program, IIS, and for data use in general.

Objectives:
Demonstrate lessons learned from implementation of a two way interface between provider sites and the IIS. Describe importance from a programmatic standpoint of assuring the interface incorporates the needs of the provider, immunization program, IIS, and all levels of data use.

Methods:
• Differences among the two types of exchange were assessed to determine usefulness on behalf of the provider, immunization program, IIS, and long-term data use.
• Differences in vendor system capabilities for processing interface data were and continue to be identified.
• Needs of the provider, immunization program, IIS, and long-term data use were evaluated to determine required data elements and standards.

Results:
• Vendor limitations were identified.
• General recommendations were developed for vendor interface functionality and usefulness.
• Developed basic data element requirements for exchange to cover ne

Conclusions:
In addition to the immunization program requirements, interface development should take into consideration the provider needs, system functionality, available resources, and long term data use.