In order to make the most out of your time and ultimately streamline the process of building an HL7 interface, there are some key things every interface developer and analyst should do. As a senior implementations consultant at Corepoint Health, Alex Lin offers his top three suggestions for interface developers and analysts:
Test – Early and often. Ask your vendors for a varying number of test messages and obtain up-to-date system specifications. (System specifications are particularly important for an interface developer as they can often be wrong or out-of-date.) It is important to always test interface connections prior to putting an interface into production. As you test, remember to save your work. Save early and often.
Talk to your vendor. Communicate with your vendors and test with them if possible. This not only streamlines the implementation process but helps build rapport and a healthy relationship. Moreover, be flexible and understanding. It is better to have problems identified early than to strain a relationship when things don’t work later on.
Document your changes. Sometimes you will establish an interface and not revisit it for a few years. Later on, it will be valuable (for you or whomever inherits that interface) to see what changes you made when you initially established the interface and why you did what you did.
For an interface developer or analyst, investing in the establishment of an interface by testing, saving and documenting your work, will not only help future interfacing needs, but also help preserve the long-term value of the interface connections.
Are there any additional actions you like to take when developing an HL7 interface?
Related posts:
- Getting Started with Your HL7 Interface
- HL7 Interface – An Overview
- Sending Text Documents or Reports via an HL7 Interface
- Two Basic Approaches to HL7 Interface Conversions
- HL7 3.0 Considerations for Healthcare Providers (Clinics, Hospitals, Labs, Diagnostic Imaging)
