EPR programming aids
Here is an overview of current relevant specifications and the associated links:
Clarifications and corrections to the EPR specifications
The legal bases for the electronic patient record (EPR) contain detailed guidelines for the introduction. However, with the technical and organizational implementation, it is possible that gaps, ambiguities or errors appear that need to be filled, specified or corrected. Thanks in particular to the EPR Projectathon test events and collaboration with the working group on technical and semantic integration, these shortcomings can be identified and eliminated. The following documents show the working group’s main discussion topics and the degree of maturity of the individual IHE profiles and EPR components.
- Abstract Working Group TSI (in English, last update: 03.07.2019)209 KB12.09.2019
- Overview EPR Integration Profiles1.05 MB28.06.2019
- Maturity Level EPR Integrations Profiles0.92 MB28.06.2019
Central Services: HPD, CPI and MDI
A test system for central services has been available since June 2017. The test system includes the Health Provider Directory (HPD), Community Portal Index (CPI), and Metadata Index (MDI). Software suppliers of future communities that connect to the central services can apply informally to the Federal Office of Public Health at FOPH-Central Services for test access.
- Factsheet Central Services241 KB29.09.2017
Central Compensation Office: UPI
The Central Compensation Office (ZAS; CCO) assigns and manages the new patient identification number according to the EPRA (EPR-SPID), which is only linked internally in the CCO with the AHV number. It maintains the UPI identification database (Unique Personal Identifier Database), which the EPR communities may access.
The following interface standards describe the access to the web service of the UPI:
It is also possible to subscribe to the broadcast service. In this case, the UPI provides automatic notification if an EPR-SPID is cancelled, if there is an OASI (AHV) number with more than one active EPR-SPID and if one of these is deactivated:
Secure communication: SEDEX
For secure communication with the UPI, the SEDEX client (Secure Data Exchange) must be used in accordance with the certification requirements.
Software developers who need to establish the connection to the UPI for prospective EPR communities can order SEDEX test access at the address FOPH Central services. The costs are covered by the Federal Office of Public Health (FOPH).
Certified communities can apply to the FOPH for access to the productive SEDEX environment. This access must be paid for according SEDEX’s cost model.
If test access is no longer needed, the FOPH must also be informed promptly at FOPH Central services for withdrawal of the authorizations.
Test platform and Use Cases
During the EPR Projectathon, the legally required IHE profiles and communication with central services will be tested. To do this, application examples or "Use Cases" are defined; these will provide the basis for individual test scenarios. To enable communities to test the potential EPR applications, they are described on the EPR reference platform (Gazelle).