Monday, October 27, 2003
3753

This presentation is part of : Poster Presentations

Electronic Submission to VAERS from Registries: Technical Lessons

Terence R Hughes, Health Division, Health Division, Scientific Technologies Corp, 67 E. Weldon, Suite 110, Phoenix, AZ, USA


KEYWORDS:
VAERS, electronic interface, API, code mapping

BACKGROUND:
Immunization registries collect a portion of the data needed by the Vaccine Adverse Events Reporting System (VAERS). Creating the ability to populate the VAERS form from registry data and allowing on-line data entry of the remainder of the form provides important new functionality to registries. An Application Program Interface (API) was created to allow a generic interface between NVAC compliant registries and VAERS. HL7 was not used due to limitations of the message content and the current VAERS system. The system provides concurrent notification of VAERS and the state immunization program manager when an adverse event is reported to VAERS through the registry, along with provision of the VAERS e-submission number which is stored on the registry (instead of the completed .pdf form.)

OBJECTIVE:
1.) Describe the technical challenges, including lack of standard code sets, that had to be addressed.
2.) Describe why HL7 was not used in this instance, and the value of the API method
3.) Describe the value of standards and the need for consistnecy that does not yet exist

METHOD:
Technical interchanges between VAERS and STC staff to define project scope and methods; mapping of disparate code sets; creation and testing of prototypes; validation and implementation in production environments

RESULT:
This system will be in production in Louisiana in early summer, 2003. Validation and testing will include paper vs. electronic methods to assure the completeness of the data. Timeliness and access will improve the ability to submit adverse event notifications.

CONCLUSION:
This project demonstrated the significant work necessary to map code sets and other technical issues involved in attempting to integrate with legacy information systems.

LEARNING OBJECTIVES:
1.) Name 2 reasons why HL7 was not used for this project.
2.) Describe 2 significant technical challenges that had to be addressed before data exchange could occur.
3.) Name 2 additional moves on the VAERS side that would make it easier for registries to submit data.

Back to Poster Presentations
Back to The 2003 Immunization Registry Conference (October 27-29, 2003)