The eHealth Connector (eHC) is a convenience API for IHE transactions and HL7 CDA documents. It supports functionalities for cross-enterprise sharing of documents and master patient index (MPI) connection using IHE transactions and also supports content profiles based on the HL7 Clinical Document Architecture (CDA).
The architecture contains generic packages for all features that are common on the international level. In addition country specific precisions are available.
The eHC is built on the basis of the MDHT HITSP runtime libraries and the OHT IHE profiles (see "Resources" below).
eHealth Connector has been migrated to GitLab.
OHT is EOL. Therefore all relevant OHT sources will be integrated in the eHealth Connector, very soon.
A concept for dynamic value set handling in the eHealth Connector has been elaborated. It will be published, very soon. The implementation will be done with the next release.
MDHT is EOL. Therefore a concept for getting rid of MDHT will be elaborated in March/April. The main objective is to generate Java source code out of the ART-DECOR models. The implementation will prospectively be done with the next release.
A new CI/CD is developed and a professional website will be launched, soon.
eHealth Connector (eHC) objectives
facilitate networking of different stakeholders in the health sector
harmonization of data exchange between software systems that are used for healthcare data exchange
reduction of the effort for the integration of an information system in an eHealth community infrastructure
successful completion of tests for all relevant profiles at an IHE Connectathon
The following guidelines for the implementation of the eHC are derived from the mentioned objectives:
implementation of existing interoperability profiles
no development of new standards or proprietary formats
simple and convenient API for developers who use the eHC, minimizing the required specialized knowledge of HL7, IHE, OHT, MDHT and other standards and technologies (including their specialized datatypes and vocabularies)
the complexity of the used standards is encapsulated, but fully accessible for all cases where the convenience API is not (yet) sufficient.
open source development and compliance with requirements for the source code, documentation, and software testing
before releasing new features, a Quality audit has to be performed in order to keep the eHealth Connector a reliable toolbox.
Releases (history and future planning)
See releases for detailed description of functionality, use cases and technical descriptions. In general two releases are planned per year (spring and autumn).