With integration taking on a critical role due to Meaningful Use and related initiatives, hospital CIOs and healthcare information exchange (HIE) leaders are seeking ways to cost-effectively build out the HL7 interfacing that underpins integration projects.
Decision-makers can opt for the interface engine or other integration technology with the most advanced mapping, filtering, and throughput capabilities on the market. But none of these features matters unless the integration analysts who code the engine can accurately scope the interfaces they need to build. Poor scoping can lead to extended go-live periods, significant maintenance at increased cost, and unhappy clinician end-users who are unable to access the data they need for appropriate patient care.
This white paper covers the following:
- The interfacing lifecycle and why scoping is critical
- Why gaps occur and what to do about them
- The 4 gap types
- How to conduct a gap analysis
- Gap analysis pitfalls and how to avoid them