Status by 30 th April 2016

Transcription

1 Status by 30 th April 2016

2 Observed market situation Usage of standards is widely welcome, accepted and also recommended by ehealth Suisse But Required know-how for software vendors is extremely high In-depth knowledge of known standards are often missing Thus, the entry barrier is too high right now Objective: An ehealth Connector should encapsulate as much functionality as possible

3 The project - spirit Free and Open Source Software (FOSS) Give and take Enable interoperability Reduce barriers

4 The project - yesterday : HL7 CDA in Arztpraxissoftware - Konzept zur Integration : Konzept zur Implementierung und API Spezifikation : ehealth Connector - Proof of concept Many thanks to - Franz Marty Documents in German, only: ehc - Proof of Concept:

5 The project end of March 2015 ehealth Connector Release R Communication Support for Document Source Actor IHE Transaction Provide & Register Document Set b [ITI-41] (used in IHE ITI XDS.b and XDR) Support for Master Patient Index Client (MPI Client) IHE Transaction "Patient Identity Feed HL7 V3 [ITI-44]" IHE Transaction "PIXV3 Query [ITI-45] (both used in IHE PIXv3) Content Support for Swiss evacdoc implementation guide of ehealth Suisse (CDA-CH-VACD) Serializing to file Deserializing from file Many thanks to - Ärztekasse - ehealth Suisse - Franz Marty - HCI Solutions - IHE Suisse - Viavac

6 The project end of October 2015 ehealth Connector Release R includes the following new features: Communication Support for Document Consumer Actor IHE Transactions Registry Stored Query [ITI-18] and Retrieve Document Set [ITI-43] (both used in IHE ITI XDS.b) Support for Master Patient Index Client (MPI Client) IHE Transaction Patient Demographics Query for HL7v3 [ITI-47] (used in IHE PDQv3) Support for Support for Portable Media Creator and Portable Media Importer IHE Transaction Distribute Document Set on Media [ITI-32] (used in IHE XDM) Content Support of the revised CDA-CH-VACD specification from September 9, 2015 available at ehealth Suisse Serializing to file Deserializing from file Many thanks to - ehealth Suisse - Franz Marty - IHE Suisse

7 The project end of April 2016 Support of the following CDA-CH specifications (Serializing to file and Deserializing from file): CDA-CH-EDES - Emergency Department Encounter Summary restrictions: sections in CDA body level 2 only vital signs section in CDA body level 3 is quality approved all other sections in CDA body level 3 are provided "as is" CDA-CH-LRPH - Laboratory reports for public health CDA-CH-LRQC - Laboratory reports for quality control CDA-CH-LRTP - Laboratory reports in the transplantation process CDA Validation Schema validation (W3C) Schematron (ISO Schematron) Optional: embedded PDF/A Validation (external license required) Mavenisation Many thanks to - ARPAGE, Switzerland - Berne University Hospital, Switzerland - ELGA, Austria - FAMH and SULM, Switzerland - IHE Suisse, Switzerland

8 The project - tomorrow Release R2016xx Autumn release 2016 (release date not fixed, yet) CDA-CH-MTPS - Medication treatment plan sharing Other potential evolution in upcoming releases IHE XUA Integration Many thanks in advance to - HUG Geneva University Hospitals - HIN Health Info Net AG - Infomed Canton of Wallis

9 The project - incubator The incubator is the entry path into ehealth Connector for projects and codebases wishing to become part of an official ehealth Connector release All external organizations and projects get access to the incubator on demand if they intend to contribute to the ehealth Connector The incubator has the following goal: Publication of efforts to a wide community Contributors provide as is, profiteers extend or adopt to their needs on their own costs Ideas may mature to features Please contribute populate our incubator

10 Who is on stage? Head medshare Ltd., Thun, Switzerland Project Team - Tony Schaller, medshare, Switzerland (Project Manager) - Franz Marty, Medizinisches Zentrum gleis d, Switzerland (Health Professional) - Oliver Egger, ahdis, Switzerland (Developer) - Axel Helmer, Open Connections, Germany (Developer) - Thomas Huster, Medevit, Austria (Developer) - Patrick Kistler, Arpage, Switzerland (Developer) - Igal Levy, Inselspital, Switzerland (Developer) - Roeland Luykx, Arpage, Switzerland (Developer) - Michael Onken, Open Connections, Germany (Development) Promoter - IHE Suisse - «ehealth Suisse»

11 Understanding and using the project logos Main project logo: Contributor indication: User indication: Disclaimer: ehealth Connector is a trademark, registered by medshare Ltd., Switzerland. The logo may be used under the Creative Commons Attribution-NoDerivatives 4.0 International License as long as it is used in conjunction with the ehealth Connector Open Source project. The usage for other products, services or projects is prohibited.

12 Architecture

13 Features in release

14 Features in release

15 Features in release

16 Implementing a CDA Template with MDHT MDHT uses models to generate Application Programming Interface (API) Validators Documentation (Spec., Javadoc) Implementation Example: Available Methods for the PN Object Example: Available Javadoc for the Method PN.addDelimiter() Knowledge you should have RIM, CDA, HL7v3, Clinical Terminology, IHE, UML Modeling, Ecore Modeling, MDD, MDHT Not convenient but mighty

17 ehealth Connector Convenience API Convenience API Fast results API is very easy to use Recommendation what should be implemented Guidance for application developers Javadoc that explains what you need to know Javadoc in your language Demo application for every template As few expert knowledge as possible Hide the complexity of CDA and MDHT But you can access underlying MDHT Objects at any time Convenient and mighty

18 Integration scenario for CDA import

19 Integration scenario for CDA export

20