SeHF 2014 | IHE-Thementrack: eHealth Connector - Eine "Convenience-API" für Softwarehersteller

eHealth Connector

A "Convenience-API" for Softwarevendors

Swiss eHealth Forum 2014 - IHE Thementrack - 7. März 2013

IHE Suisse │ Oberstrasse 222 | Postfach 51 | CH-9014 St. Gallen | www.ihe-suisse.ch

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

2


eHealth architecture Switzerland summary

3

Source: eHealth Suisse


The standards cloud

Standards and Implementation guides

4

Communication

StandardsElectronic Business Standards

ebXML, SOAP …

Internet Standards

HTML, HTTP, PDF, JPEG …

Content StandardsHealthcare Content Standards

HL7 CDA, CEN EHRcom,

ASTM CCR, DICOM …


Current available HL7 CDA content profiles

5



6

Emergency Department

Summary

Notfallaustrittsbericht

Rapport de sortie d'urgence



7

Medical summary for emergency treatment

Medizinische Notfalldaten

Données médicale pour le traitement

d'urgence



8

Laboratory Reports for Public Health

Meldepflichtige Laborbefunde

Rapports de laboratoire soumis à

déclaration



9

Laboratory Reports in the Transplantation Process

Laborbefunde im Transplantationsprozess

Rapports de laboratoire dans le processus de

transplantation



10

eVACDOC

Immunization Content

Elektronischer Impfausweis

Carnet de vaccination numérique



11

coming soon:

Social medical care plan

Sozialmedizinischer Pflegeverlegungsbericht

Document médico-social de transmission

(DMST)


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

12

Objective:

An eHealth

Connector should

encapsulate as

much functionality

as possible

Objective:

An eHealth

Connector should

encapsulate as

much functionality

as possible


Sample use case 1 - Vaccination

13


Sample use case 2 – Laboratory

14


Sample use case 3 – Emergency department

15


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.

16

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


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 including metadata

• Special functions depending on the implementation guide / use case

• IHE Request Clinical Guidance [PCC-12] transaction

17

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


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

• Support of IHE XUA Profile

• etc.

please contact us with your feature requests

18


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

IKVM.NET is an implementation of Java for Mono and the Microsoft

.NET Framework that includes 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 (JAR and DLL) will be available for IHE Suisse members

19


Architecture

20


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)

See: http://medshare.net/publikationen

2. Code

• Proof of Concept including demo applications for Java and .Net

See: http://sourceforge.net/projects/ehealthconnector/

• Updated Javadoc online help

See: http://www.medshare.net/fileadmin/eHealthConnectorAPI/doc/

(Notice: This is currently a mix in German, French, English; will get

improved ;-)

21

http://medshare.net/publikationen

http://sourceforge.net/projects/ehealthconnector/

http://www.medshare.net/fileadmin/eHealthConnectorAPI/doc/


Intentions without any contracts, yet

• IHE Suisse

Intention to provide long term support

• medshare Ltd.

Intention to provide maintenance and support

• eHealth Suisse

Intention to contribute to the maintenance, if

IHE Suisse decides to take its role

22


Ways for contribution

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,

later

A maintenance fee will be charged

• Financial contribution

– Ordering Functionality

Your needs will be implemented based on a contractual relationship

– Sponsoring

Sponsors will get the right for their logo publication on eHC publications

23


Interested stakeholders

• Bern University of Applied Sciences, Medical Informatics Biel

Source-Code contribution for CDA-CH-LRTP (Bachelor Project)

• Viavac

Source-Code contribution for CDA-CH-VACD

• Arpage

Financial contribution for CDA-CH-VACD

• Inselspital

Financial contribution for CDA-CH-EDES

• Geneva University Hospitals

Financial contribution for a new CDA-CH specification: Shared Medication Treatment Plan and its

integration in the eHealth Connector

• Infomed

Source-Code contribution for IHE XUA Integration

• HCI Solutions (Triamed)

Prototype-Integration of CDA-CH-VACD, CDA-CH-EDES and Shared Medication Treatment Plan

• Elexis

Prototype-Integration of CDA-CH-VACD, CDA-CH-EDES and Shared Medication Treatment Plan

(In order of commitment)

24


Further interviews

• Users

– Government departments (Federal Office of Public Health FOPH,

several Cantons)

– Hospitals (University hospitals, cantonal hospitals)

• Vendors

– Product vendors

– Infrastructure vendors

– Software Development companies

These meetings are planned in February/March 2014

25


Take Home Message

• Documentation and source code are public available for free

• Sponsored open source project

• Based on the Open Health Tools (OHT) Framework

• Convenience methods for the management of CDA-CH content

• Convenience methods for the transmission of documents

• Allows interoperability, harmonization

• 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

• Functionality will be implemented as soon as commitments are there

Unless one does it ;-)

Just do it :-)26


Question and Anwers

27

Upon questions

Tony Schaller, Technical Project Manager IHE Suisse

[email protected]

SeHF 2014 | IHE-Thementrack: eHealth Connector - Eine "Convenience-API" für Softwarehersteller

Health & Medicine

Transcript of SeHF 2014 | IHE-Thementrack: eHealth Connector - Eine "Convenience-API" für Softwarehersteller