HL7 Interface Lifecycle Management at Interconnected Health 2012

2,273 views

Published on

http://caristix.com

HL7 Integration: From Trial and Error to Predictable Project Outcomes

By nature, an HL7interfacing project consists of many unknown unknowns. And far too many teams rely on trial and error and drawn-out iterative processes to get projects completed. Unfortunately, those in charge often lack the transparency into accurate information about project status. With complex projects, the result all too often is an inability to predictably hit a target go-live date, impacting planning and the ability of leadership to extract the maximum value from project resources.

This presentation introduces a new concept, Interface Lifecycle Management, which covers 7 key stages that every healthcare organization goes through when implementing interfaces. These steps are: scoping, configuration, validation, go-live, monitoring, maintenance and support, and finally, an upgrade decision when sending systems change. Using examples drawn from providers and HIT vendors, the presenter will cover best practices and automation strategies that leadership can implement during each step regardless of interface engine or integration technology in use.

Published in: Health & Medicine, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,273
On SlideShare
0
From Embeds
0
Number of Embeds
1,088
Actions
Shares
0
Downloads
50
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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
  • HL7 Interface Lifecycle Management at Interconnected Health 2012

    1. 1. Interconnected Health 2012HL7 Integration: From Trial and Error to Predictable Project OutcomesApril 2012
    2. 2. Agenda• HL7 is flexible• Current approach: trial & error• Proposed new approach: Interface Lifecycle Management2 © Caristix 2012. All rights reserved.
    3. 3. HL7 is Flexible – No Plug & Play Deployed interface Product A HL7 GAPS: Specification WORK REQUIRED HL7 v2.2 HL7 v2.3.1 Product B HL7 v2.4 Deployed HL7 v2.5.1 HL7 v2.6 interface HL7 v2.73 © Caristix 2012. All rights reserved.
    4. 4. Gaps: A Few Examples• Z-segments• User-defined Data Sets4 © Caristix 2012. All rights reserved.
    5. 5. Z-segmentsMSH|^~&|SPC|R|ENG|R|200609280101|43|ADT^A08|44859646|D|2.6|44859646||AL||EVN|A08|200609280101||PID||03777168|0001754426^^^R|9960^R17400|REGISTRATION^AMY^^||19601020|F||3|123 BOOGNK1|1|REGISTRATION^PAT|B^^|123 BOOGEY AVE^^NICECITY^MN^44444^US|(999)555-6879NK1|2|N^A|T^^|^^^^^|PV1||O|MRIR^^^R^^^|3|||16515^SMITH^JANE^S^^^DO|^REGISTRATION^MIKE^J^^^||IMG||||1||EPV2|||||N|||200609280800||||OPR RAT|||||||||*|||||""|||||||20060928||||||^MRIBRAINAL1|||^|||DG1|0|I9||HEADACHE||A||||||||DG1|99|I9||HEADACHE||WORKING||||||||GT1|1|9960|REGISTRATION^AMY^^||123 BOOGEY AVE^^NICECITY^MN^44444^US^C^25|(999)555-9IN1|1|100|800|SELF PAY|^^^^^^C^||||||ZZHEALTH^111^||||C^^|REGISTRATION^AMY^||196010IN2||569-33-8744||||||||||||||||||||||||||||ACC|200609241500|3|CLEVELAND AVE/FRANKLINUB1|1|||||||||45^15||||||05^20060924~^~^~^~^|||||||ZCA|||^^^ZCD||N|||^NEW LIFE^||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ZCE|15^SECRETARY^|""|111^ZZHEALTH^|1087 DENNISON AVE^^NICECITY^MN^43201^US^^25||||1ZCI|1|SELF PAY, NO INSURANCE||S|N|569-33-8744|N||P||||""||||""|||||||||||||||||1ZCV|||||FALL||PDR|0ZCM|N|||||||||*|||||||||||||^REGISTRATION^MIKE^J5 © Caristix 2012. All rights reserved.
    6. 6. User-defined Data Sets6 © Caristix 2012. All rights reserved.
    7. 7. User-defined Data Sets7 © Caristix 2012. All rights reserved.
    8. 8. User Defined Data SetsMSH|^~&|SPC|R|ENG|R|200609280101|43|ADT^A08|44859646|D|2.6|44859646||AL||EVN|A08|200609280101||PID||03777168|0001754426^^^R|9960^R17400|REGISTRATION^AMY^^||19601020|F||3|123 BOOGNK1|1|REGISTRATION^PAT|B^^|123 BOOGEY AVE^^NICECITY^MN^44444^US|(999)555-6879NK1|2|N^A|T^^|^^^^^|PV1||O|MRIR^^^R^^^|3|||16515^SMITH^JANE^S^^^DO|^REGISTRATION^MIKE^J^^^||IMG||||1||EPV2|||||N|||200609280800||||OPR RAT|||||||||*|||||""|||||||20060928||||||^MRIBRAINAL1|||^|||DG1|0|I9||HEADACHE||A||||||||DG1|99|I9||HEADACHE||WORKING|||||||| HL7 v2.6 suggests “2106-3”GT1|1|9960|REGISTRATION^AMY^^||123 BOOGEY AVE^^NICECITY^MN^44444^US^C^25|(999)555-9IN1|1|100|800|SELF PAY|^^^^^^C^||||||ZZHEALTH^111^||||C^^|REGISTRATION^AMY^||196010IN2||569-33-8744||||||||||||||||||||||||||||ACC|200609241500|3|CLEVELAND AVE/FRANKLINUB1|1|||||||||45^15||||||05^20060924~^~^~^~^|||||||ZCA|||^^^ZCD||N|||^NEW LIFE^||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ZCE|15^SECRETARY^|""|111^ZZHEALTH^|1087 DENNISON AVE^^NICECITY^MN^43201^US^^25||||1ZCI|1|SELF PAY, NO INSURANCE||S|N|569-33-8744|N||P||||""||||""|||||||||||||||||1ZCV|||||FALL||PDR|0ZCM|N|||||||||*|||||||||||||^REGISTRATION^MIKE^J8 © Caristix 2012. All rights reserved.
    9. 9. A Few Numbers• 60% of hospitals deal with 100+ systems.• 64% of hospitals increasing HL7 integration over 12 months.• In HL7 v2.6: – 370 trigger events – >500 data elements per message – >500 suggested code setsSources: HIMSS 2008 survey, Core Health Technologies 2011 survey. HL7 International.9 © Caristix 2012. All rights reserved.
    10. 10. Current ApproachRequirements based on:• Manual analysis (pipe counting)• Small data samples• Incomplete and/or outdated documentation: – Interface specifications – Ecosystem data flow10 © Caristix 2012. All rights reserved.
    11. 11. Current Approach: Results• Low-fidelity, low-trust requirements: – “What is connected here?” – “Which data structures?” – “What is optional in which scenario?” – “Which data sets? From when?” – Are the semantics consistent?” © Caristix 2012. All rights reserved.
    12. 12. Current Approach: Results“Let’s start with a best-guessinterface and fix issues whenthey pop up.”The Trial & Error loop starts... © Caristix 2012. All rights reserved.
    13. 13. Trial & Error Outcomes• Cannot predict effort, timeline and costs• Cannot evaluate risk• Continue iterating after go-live• Hard to capture and reuse issue discovery – With Colleagues – With Providers/Client teams13 © Caristix 2012. All rights reserved.
    14. 14. Proposed New Approach Interface Lifecycle Management14 © Caristix 2012. All rights reserved.
    15. 15. Interface Lifecycle Management• Understand gaps early• Work with real-life messages• Predictable• Focus on automation15 © Caristix 2012. All rights reserved.
    16. 16. Scoping• Automate as much as possible• Analyze real life data• Compare sending vs. receiving systems• Gaps found = Tasks16 © Caristix 2012. All rights reserved.
    17. 17. Configuration• Configure your integration engine – Filtering – Transformation – Mapping• Consider automation based on gaps17 © Caristix 2012. All rights reserved.
    18. 18. Validation• Build reusable and repeatable test scenarios based on gaps• Automate test scenarios• Run tests in test environment• Include real life data (de-identify if needed)• Refine test scenarios18 © Caristix 2012. All rights reserved.
    19. 19. Monitoring• Keep tracking any gaps that may appear• Refine scoping results, configuration and test scenarios19 © Caristix 2012. All rights reserved.
    20. 20. Evidence-based Decision-making Known vs. Unknown Gaps through Interfacing Project Current Approach Proposal 100% 100% 80% 80% 60% 60% 40% 40% 20% 20% 0% 0% Kick-Off Go Live Iter 1 Iter 2 Iter 3 Iter 5 Kick-Off Iter 1 Iter 2 Iter 3 Iter 4 Iter 6 Iter 7 Iter 8 Iter 9 Iter 10 Go Live 30-60% Time Savings20 © Caristix 2012. All rights reserved.
    21. 21. Contact Information Jean-Luc Morin VP R&D, Caristix jeanluc.morin@caristix.comApril 2012

    ×