This library interacts with the Telematik-Infrastuktur (TI) via a Konnektor to write structured HL7/FHIR bundles for DiGA treatments into the electronic health record (ePA).
- Add the ePA Client Library
<dependency> <groupId>com.oviva.epa</groupId> <artifactId>diga-epa-client</artifactId> <version>${version}</version> </dependency>
- See KonnektorServiceAcceptanceTest on how to initialise the client.
- Access to a TI Konnektor, e.g. from RISE
- A valid Secure Module Card for your Institution (SMC-B)
- A card terminal paired with the Konnektor
- TLS Client certificate to authenticate the application to the Konnektor
NOTE: All of the above you can get from e.g. RISE
See KonnektorServiceAcceptanceTest.
sequenceDiagram
participant app as diga-epa-lib
participant konn as TI Konnektor
app ->>+konn: get card status
note over app,konn: the SMC-B card must be verified<br>before interacting with the ePA APIs
konn -->>-app: ok, verified
app ->>+konn: resolve hcid
note over app,konn: the home community id (hcid) must be<br>determined for a given patient in order<br>to write a document
konn -->>-app: hcid
app ->>+konn: resolve author institution
note over app,konn: our identity within the TI can be read<br> from the SMC-B card
konn -->>-app: telematik ID
app ->>+konn: write document
note over app,konn: writes a structured MIO 1.1 bundle<br> to the ePA of a given patient
konn -->>-app: ok
- Copy the required keystore received with the Konnektor
cp vKon_Client_*.p12 ./diga-epa-client/src/main/resources/keys
- Run the tests in the KonnektorServiceAcceptanceTest class
- You should be able to write an example file in the test environment (RU).
- Specifications ePA - 'Aktensystem ePA für alle'
- DiGA Leitfaden, 3.5 Interoperabilität
- DiGA Anwendungssteckbrief
- gematik/api-telematik
- gematik/api-ePA
- MIO DiGA Toolkit v1.1
- Gematik epa-ps-sim - The basis for this project.
- Gematik Confluence
- Gematik FAQ
- RISE Konnektor
health
check onKonnektorConnection