Health Tech Companies · healthtech-wellness-app
Wellness app data obligations
We have a fitness/wellness app that collects health data
EHDS basis
Chapter III — wellness applications claiming interoperability
Workflow
-
Push wellness observations
in HAPI FHIR
As a wellness app would.
- Map into the CDR in openFHIR
-
Compare with clinical data
in EHRBase
Provenance keeps them distinguishable.
-
Where the citizen sees it
in PHR (my record)
Wellness data next to clinical data, marked as such, in my PHR.
-
The labelling obligation
Triggered by the interoperability claim.
Sandbox applications used
PHR (my record)
The citizen's personal health record: access, consent, opt-out, proxies, requests
https://phr.sandbox.ehds.technicise.eu/
HAPI FHIR
Exchange layer — EEHRxF / FHIR R4
https://fhir.sandbox.ehds.technicise.eu/
openFHIR
Bidirectional FHIR ↔ openEHR mapping
https://map.sandbox.ehds.technicise.eu/
EHRBase
openEHR clinical data repository (JVM)
https://cdr.sandbox.ehds.technicise.eu/
Scenario healthtech-wellness-app from the
EHDS Regulation Explorer (MIT).