Vendors who wish to connect to registries have to solve two problems: (1) message format and (2) message transmission. The message format is pretty well defined by HL7 but the message transmission varies from registry to registry. Here are a few pointers to help in this process.
Message Format
HL7 defines the Unsolicited Vaccination Update (VXU) as the message of choice for submitting data to registries. The CDC requires that all registries support this format and have created the Implementation Guide for Immunization Data Transactions using Health Level Seven (HL7) Standard Protocol (download). Writing your interface to match this guide will insure the best support nationwide.
Message Transmission
HL7 informally defines a TCP/IP method (MLLP) to transmit HL7 data and this is widely supported by traditional HL7 applications. Many state registries do not support this method as it requires using a custom VPN connection in order to make the transmission secure. Instead registries provide various other methods including FTP(S), HTTPS, PHIN-MS and secure emails. Most also have a process for manual submission either through FTP(s) or by uploading via a web page.
It is recommended that vendor systems have the ability to export VXU messages and save them to a file. This minimum ability will work in most situations.
The various methods for automating will be discussed in a future post.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment