Extensive and up to date

Since its first release in 2015, the eHealth Connector has been evolving constantly. The core remains stable, but the programming interface regularly adds new, quality-assured extensions and updates. It is available simultaneously in Java and .Net.

IHE applications

IHE (Integrating the Healthcare Enterprise) is a global initiative to improve interoperability in healthcare. The eHealth Connector handles numerous IHE transactions, for example storing or accessing documents in a community (Cross-Enterprise Document Sharing or IHE-XDS), authenticating and authorising users (Cross-Enterprise User Assertion Profile or IHE XUA), and formats for exchanging standardised document content (IHE Content Profiles).

Handling the HL7 CDA standard

CDA (Clinical Document Architecture) is a widespread international standard for exchanging and storing medical documents. The Connector simplifies the handling of such documents on multiple fronts: transmission, creation before sending, processing following receipt, validation, embedding PDFs or conversion from CDA to PDF/A.

Formats for exchange

In addition to exchange formats such as eMedikation (e-medication), eLaborbefund (e-lab findings) and eImpfdossier (e-vaccine records) which are subject to statutory regulation in Switzerland, other documents are available in the eHealth Connector as well. This simplifies the process of (de)serialisation. Contributions to exchange formats in other countries in the eHealth Connector are welcome.

Link to national patient records

Linking primary systems is crucial to the implementation of eHealth platforms such as the Electronic Patient Record (EPR) in Switzerland. The eHealth Connector provides valuable support to IT specialists in this respect, and can be deployed productively as a component. If other adapters are used, the eHealth Connector gives useful tips on the architecture and implementation, or can be used as a test component. The components of the Swiss EPR landscape currently supported by the eHealth Connector can be seen in this graphic (indicated in each case by the eHealth Connector logo).

Customising for national use

On both the content and communication side, generic international modules are available that can be further specified in accordance with national requirements (precisions only). Both the generic and the country-specific modules can be used selectively as autonomous packages.

Assistance for newcomers

Newcomers to the world of eHealth standards will also find the API easy to use. There are demo applications in Java and .Net for all functionalities, as well as detailed descriptions in the Wiki.

Open source code

The Connector encapsulates the complexity of the used standards in such a way that no in-depth knowledge is required to use the interface. However, it is fully accessible at all times, so you can always check out the open source code for inspiration.


Join in and contribute

Is a function missing? Have you found an error?  Sign into the “ehc-implementors” Google group or create a ticket. Even better, you can help create more interoperability in healthcare by contributing to the development of the eHealth Connector yourself.  

Handling the HL7 FHIR standard

Everyone’s talking about HL7 FHIR. The standard has many potential applications. Contributions to HL7 FHIR that accord with nationally approved or internationally accepted implementation guidelines are welcome in the eHealth Connector.