eHealth Connector Convenience API

|

Introduction

Agenda

1. Context - eHealth in Switzerland

2. The eHealth Connector – a Convenience API

3. Supporting organizations

4. Unless one does it – ways for contribution

5. Conclusion

|

eHealth in Switzerland

eHealth architecture Switzerland summary

Source: eHealth Suisse

|

Standards and Implementation guides

The standards cloud

Communication Standards

Electronic Business StandardsebXML, SOAP …

Internet StandardsHTML, HTTP, ISO, PDF, JPEG …

Communication Standards

Electronic Business StandardsebXML, SOAP …

Internet StandardsHTML, HTTP, ISO, PDF, JPEG …

Content StandardsHealthcare Content Standards

HL7 CDA, CEN EHRcom, ASTM CCR, DICOM …

Content StandardsHealthcare Content Standards

HL7 CDA, CEN EHRcom, ASTM CCR, DICOM …

|

Standards and Implementation guides

Usage of IHE

Content profilesIHE PCC, LAB, RAD, …

Integration profilesIHE ITI: XDS, XCA, XCPD, …

|

Standards and Implementation guides

HL7 CDA Summary

|

eHealth in Switzerland

Current available HL7 CDA content profiles

|

eHealth in Switzerland

Current available HL7 CDA content profiles

Emergency Department SummaryNotfallaustrittsbericht

Rapport de sortie d'urgence

|

eHealth in Switzerland

Current available HL7 CDA content profiles

Medical summary for emergency treatmentMedizinische Notfalldaten

Données médicale pour le traitement d'urgence

|

eHealth in Switzerland

Current available HL7 CDA content profiles

Laboratory Reports for Public HealthMeldepflichtige Laborbefunde

Rapports de laboratoire soumis à déclaration

|

eHealth in Switzerland

Current available HL7 CDA content profiles

Laboratory Reports in the Transplantation ProcessLaborbefunde im Transplantationsprozess

Rapports de laboratoire dans le processus de transplantation

|

eHealth in Switzerland

Current available HL7 CDA content profiles

eVACDOCImmunization Content

Elektronischer ImpfausweisCarnet de vaccination numérique

|

eHealth in Switzerland

Current available HL7 CDA content profiles

coming soon: Social medical care plan

Sozialmedizinischer PflegeverlegungsberichtDocument médico-social de transmission (DMST)

|

eHealth in Switzerland

Observed market demand

• 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

Objective: An eHealth

Connector should encapsulate as much

functionality as possible

|

eHealth Connector API

Sample use case 1 - Vaccination

|

eHealth Connector API

Sample use case 2 – Laboratory

|

eHealth Connector API

Sample use case 3 – Emergency department

|

eHealth Connector API

Functionality for content

Export, import and validation

• Serializing and Deserialisierung of CDA-Documents following one of the CDA-CH-XXXX implementation guides. Payload provided by an easy to use object interface (IntelliSense)

• Validation of CDA-Documents following one of the CDA-CH-XXXX implementation guides. Schematrons must exist.

• Special functions depending on the implementation guide / use case

• Example:

• Transformation (mapping) of CDA-CH-VACD payload in an anonymized HL7 V3 message for the IHE Request Clinical Guidance [PCC-12] transaction

Notice: This functionality is planned and specified but it is not currently implemented. Therefore we are looking for contributors right now.

|

eHealth Connector API

Functionality for communication

Communication of any document (send and receive)

Support of IHE transactions

• Transformation (mapping) of CDA-CH-XXXX payload into the required metadata for transport using the IHE Provide and Register Document Set-b [ITI-41] or IHE Distribute Document Set on Media [ITI-32] transactions.

• Registry Stored Query [ITI-18]

• Retrieve Document Set [ITI-43]

• Encrypted transmission of CDA-CH-XXXX documents over the internet using the mentioned IHE transactions with transport layer security (TLS)

• Storage on IHE XDM-compatible media (CD-ROM, USB stick) including creation of required metadata

Notice: This functionality is planned and specified but it is not currently implemented. Therefore we are looking for contributors right now.

|

eHealth Connector API

Ready for future functionality requests

Possible upcoming feature requests

• Management of X.509 certificates for the access to the configured communication endpoints

• Support of policy enforcement rules according to the eHealth Suisse recommendations

• etc.

please contact us with your feature requests

|

eHealth Connector API

Technology

Base

• Open Health Tools framework (OHT)

• Model-Driven Health Tools (MDHT)

eHealth Connector API distribution

• Open source is public available

• Platform independent

• integration into all java development environments

• integration into .Net development environments using IKVM.NET (http://www.ikvm.net/)IKVM.NET is an implementation of Java for Mono and the Microsoft .NET Framework thatincludes the following components:

• A Java Virtual Machine implemented in .NET

• A .NET implementation of the Java class libraries

• Tools that enable Java and .NET interoperability

• Runtimes (Java JAR and .Net DLL) will be available for IHE Suisse members

|

eHealth Connector API

Architecture

|

eHealth Connector API

Integration scenario for CDA import

|

eHealth Connector API

Integration scenario for CDA export

|

eHealth Connector API

Current results

1. Documentation (in German)

• Concept for the integration of HL7 CDA into general practitioner software

• Concept for implementation and API specification (including Javadoc online Help)

License: Creative Commons License

See: http://medshare.net/publikationen

2. Code

• Proof of Concept including demo applications for Java and .NetSee: http://sourceforge.net/projects/ehealthconnector/

• Updated Javadoc online helpSee: http://www.medshare.net/fileadmin/eHealthConnectorAPI/doc/(Notice: This is currently a mix in German, French, English; will get improved ;-)

Licenses: Eclipse public license (EPL) and other open source Licenses (see OHT, IKVM.NET)

|

eHealth Connector API

Roadmap

History

• 2012: Concept for the integration of HL7 CDA into general practitioner software

• 2013: Concept for implementation and API specification (including Javadoc online Help)

Today

• 2014.02: Proof of concept and demo applications

Future

• 2014.Q1: Setup of organization for maintenance and third level support

Depends upon contribution commitments:

• 2014.Q2: eHealth Connector PoC enhancements for possible prototypes

• 2014.Q4: eHealth Connector R1 supporting your needs

|

Supporting organizations

Commitments

• IHE SuisseProviding long term support

• medshare Ltd.Maintenance and support organization, responsible for release management, third-level support, quality and conformity to the Swiss eHealth architecture

• eHealth SuisseFinancial contribution for the startup of the maintenance and support organization

|

Unless one does it

Ways for contribution

Strategy background:

The eHC aims to be a trusted component, providing quality, stability and conformity!

Source code contribution

• Usage (boosts supply-demand ratio): Open source allows public usage to everyone for free

• Implementation: You may submit patches and eventually get nominated as a committer, laterA maintenance fee will be charged

Financial contribution

• Ordering FunctionalityYour needs will be implemented based on a contractual relationship

• SponsoringSponsors will get the right for their logo publication on eHC publications

|

Unless one does it

Interested stakeholders – committed contribution !

• Bern University of Applied Sciences2014 Q1/Q2: Bachelor project for CDA-CH-LRTP (Laboratory reports in the transplantation process)

• <This is your place, please contact us>

• <This is your place, please contact us>

• <This is your place, please contact us>

|

Unless one does it

Interested stakeholders - without any commitment, yet !

Meetings planned with

These meetings are planned in February/March 2014

Users

- Government departments (Federal Office of Public Health FOPH, several Cantons)

- Hospitals (University hospitals, cantonal hospitals)

Vendors

- Product vendors

- Infrastructure vendors

- Software Development companies

|

Unless one does it

Sponsors

These organizations and people provided voluntary contribution in the form of labor or money

• Medizinisches Zentrum gleis d, Chur, Switzerland – Dr. med. Franz Marty

• medshare Ltd., Thun, Switzerland – Tony Schaller

• Open Connections Ltd, Oldenburg, Germany – Axel Helmer

Status: 2014-02-11

|

Conclusion

Take Home Message

• Documentation and source code are public available for free

• The eHealth Connector Convenience API

• is a sponsored open source project

• is based on the Open Health Tools (OHT) Framework

• provides convenience methods for the management of CDA-CH content

• provides convenience methods for the transmission of documents

• allows interoperability, harmonization and easy access to the Swiss eHealth trust space

• Supported by eHealth Suisse and IHE Suisse

• Support and third level support will be setup right now. Objective: long term support

• Functionality will be implemented as soon as commitments are there

Unless one does it ;-)

Just do it :-)