Reference implementation of the HISO/Aduro standard
- 1. HieGen - a reference implementation of the HISO/Aduro standard Chandan Datta (Chandan.datta@healthlink.net) 1 March 2017
- 2. Talk outline • Overview of Aduro • Why develop a reference implementation • Business value of HieGen • Explanation of how it would work in terms of existing business processes • Benefits in terms of business process improvements • Benefits to all HL teams
- 4. Defining Aduro Aduro EMR EMR EMR EMREMR SmartForm SmartForm SmartForm SmartForm
- 5. App engineer (e.g HL SmartForms) API designer (e.g HL design team) Data provider (e.g EMR) High level view of the integration
- 6. Defining HieGen Next Gen Health Information Exchange
- 7. Why develop HieGen • See working software first • Understand implementation architecture and new components upfront • Profile how much of the standard you need for your customers • Get implementation correct the first time • Reduce integration testing cycles • Get implementation correct the first time • Simplify the integration • Developer first approach – technical leadership • Improve business processes for integration • Ensure standard implementation correctness • Reduce internal friction internal between teams • Teams who need features for the standard own and maintain the standard and it’s test cases • Reduce integration testing cycles • Reduce HealthLink technical support during implementation • Improve overall quality of implementations
- 8. Demo Aduro integration with Medtech Provide SOAPUI as the mock EMR Develop software referring to specifications HL provide technical support on queries Demo Aduro integration with reference platform Provide reference platform as the model implementation Develop software referring to specifications HL provide technical support on queries Now Proposed
- 9. HieGen Software goals 1. Provide the minimal set of functionality of an EMR system that can help test the HISO/Aduro specifications 2. Provide a more comprehensive simulation facility to the HealthLink forms developers and QA to launch multiple forms and provide dynamic features absent in the SOAPUI web service simulation tool 3. Verify that HISO/Aduro specification is implementable. Hence, it helps to clarify intent of specification where conformance tests are inadequate 4. Automated tests are accurate and precise for the desired essential behaviour 5. Core multi-layered interface oriented architecture is completely reusable and readily customizable to be deployed as an web app and even on Android 6. Continuous integration ready using build scripts. One click deployment makes it runs on multiple platforms - Mac, Windows and Linux
- 10. Overview of components HieGen Lightweight EMR shell Patient database Aduro SOAP Web service Embedded browser Configuration UI Stored form search and display
- 11. HieGen technical component diagram
- 12. HieGen Demo
- 13. Contract agreement Release update Form’s requirement Workshop Implementation guidance Tech support Implement the specs Update EMR software VVT testing Vendor team testing QA testing Update Forms Server Update deployment sites VI+Design+ITS Aduro implementation process
- 14. HL Aduro technical workshop with EMR HL dev setup EDI and EMR dev access HL dev setup SOAPUI on EMR dev HL dev setup Forms Director config for test forms access HL dev setup VVT EMR start development Development initiation process for Aduro EMR alpha release to HLK vendor team for VVT testing EMR Fix issues from HLK VI team HLK QA form testing EMR & HLK fix issues Release to production
- 15. Resources
- 16. Thanks • Comments and feedback to chandan.datta@healthlink.net