Where Does the ePA App Store Data?
The ePA record apps are per insurer under rise_world packages, separate from the eRezept app listing.
Last updated
Germany electronic patient record ships per insurer, not as one gematik app. Builds from rise_world carry insurer suffixes while sharing the ePA backend. The eRezept prescription app is a separate gematik listing entirely. Records live server side with providers. Local data holds session and cached docs.
Do not mix their data dirs. Pick the build matching your insurance card before troubleshooting paths. Install your insurer build and log in with health card. Check the record list inside the app after login. Clearing the folder while the app runs ends the session and drops cached views.
Where ePA stores this, by platform
/data/data/com.rise_world.epa.dakGesundheit
Per-insurer ePA builds, DAK example shown. Records sync from gematik servers; local holds session and cached docs. eRezept uses a different package.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container per insurer ePA build (DAK ePA App Store ID 1535046876). Choose your insurer listing; records pull after login.
Frequently asked questions
Is ePA the same app as eRezept?
Install your insurer ePA build (for example DAK ePA) and log in with health card. Records sync from gematik servers. The eRezept app at de.gematik.ti.erp.app is a different listing with its own data.
What is the ePA package for my insurer?
de.gematik.epa is a FHIR specification package, not an installable app. Store apps use com.rise_world.epa.<kasse> forms like dakGesundheit, sbk or boschBkk. Search your insurer name plus ePA.
Notice an outdated path? Let us know.