The document discusses improving the process of HL7 integration projects from a trial and error approach to an interface lifecycle management approach. The current trial and error approach results in unpredictable timelines, costs, and risks as issues are discovered after interfaces go live. The proposed interface lifecycle management approach focuses on upfront scoping, configuration, validation, and monitoring to systematically discover and address gaps early. This evidence-based approach aims to save 30-60% of time on HL7 integration projects by reducing iterations after go-live.
21. Contact Information
Jean-Luc Morin
VP R&D, Caristix
jeanluc.morin@caristix.com
April 2012
Hinweis der Redaktion
Even when two hospitals are using the same version of an ADT system from the same vendor, they will most likely configure systems and interfaces differently. As a result of the many variances and adaptations of the HL7 standard, there’s no truly standard way that systems are implemented and data is handled. In response, analysts and interface engineers are forced to undertake manual, tedious work as part of implementation process.
Is there any way around these issues? Yes. Start by treating interfacing as a lifecycle, not a one-off deliverable. Analogous to Application Lifecycle Management – Interface Lifecycle Management.7 key stages that every healthcare organization goes through when implementing interfaces. Explain each step.Today’s integration technology and engines means that it’s pretty easy to configure an interface. No issues there, but the result is that all the work and the risk gets pushed to the validation stage. That’s where issue discovery typically happens, with the result that there is little visibility at the top of the cycle. This impacts project planning, timelines, risk management. When organizations focus on the scoping effort – which I’ll be getting into later – they can move the needle on driving higher-quality integration, faster and with reduced risk around delivery and resource allocation.
Is there any way around these issues? Yes. Start by treating interfacing as a lifecycle, not a one-off deliverable. Analogous to Application Lifecycle Management – Interface Lifecycle Management.7 key stages that every healthcare organization goes through when implementing interfaces. Explain each step.Today’s integration technology and engines means that it’s pretty easy to configure an interface. No issues there, but the result is that all the work and the risk gets pushed to the validation stage. That’s where issue discovery typically happens, with the result that there is little visibility at the top of the cycle. This impacts project planning, timelines, risk management. When organizations focus on the scoping effort – which I’ll be getting into later – they can move the needle on driving higher-quality integration, faster and with reduced risk around delivery and resource allocation.
Automate Scope AnalysisAnalysis real life system dataGaps found = TasksConfigure IE (filters, transformers, mapping, etc)Automate Interface Validation in simulated envRepeatable and traceableInclude real scenario in test envTests based on your discoveriesMonitor – Refine discoveries/test scenariosRestart the loop
Automate Scope AnalysisAnalysis real life system dataGaps found = TasksConfigure IE (filters, transformers, mapping, etc)Automate Interface Validation in simulated envRepeatable and traceableInclude real scenario in test envTests based on your discoveriesMonitor – Refine discoveries/test scenariosRestart the loop
Automate Scope AnalysisAnalysis real life system dataGaps found = TasksConfigure IE (filters, transformers, mapping, etc)Automate Interface Validation in simulated envRepeatable and traceableInclude real scenario in test envTests based on your discoveriesMonitor – Refine discoveries/test scenariosRestart the loop
Automate Scope AnalysisAnalysis real life system dataGaps found = TasksConfigure IE (filters, transformers, mapping, etc)Automate Interface Validation in simulated envRepeatable and traceableInclude real scenario in test envTests based on your discoveriesMonitor – Refine discoveries/test scenariosRestart the loop