Germany
Nothing on this page is a claim of regulatory approval, compliance, deployment, or a partner in Germany. It describes, at website depth, what a jurisdiction pack for Germany would need to carry โ illustrated against the real fields the pack interface already defines โ and states plainly what has not been validated. This is the commercial roadmap. For developers interested in the free, source-available edition for eligible countries, see the open edition start here and the country pack template and examples.
Concept mockup. Synthetic data. Not a product available in Germany today โ no jurisdiction pack for Germany exists in code. Concept mockup by MOBLUEHQ; not a product available in this country today.
| Pack field | What we'd expect, to be validated in-country |
|---|---|
coding_system | ICD-10-GM (diagnoses) and OPS (procedures) in place of the US pack's ICD-10-CM/CPT. |
privacy_regime | A GDPR- and Bundesdatenschutzgesetz (BDSG)-shaped consent, retention and export posture in place of the US pack's HIPAA text. |
fhir_profile | A German national FHIR base-profile family in place of the US pack's US Core. |
payer_plan_vocabulary | GKV (statutory) / PKV (private) in place of the US pack's Medicare / Medicaid / commercial / self-pay. |
currency / locale / date_format | EUR ยท de-DE ยท DD.MM.YYYY |
data_residency_required | Data-residency requirement expected to be set true, unlike the US pack's โno residency requirement.โ |
Largest EU health market, with statutory utilization review (Medizinischer Dienst) and the EU AI Act's high-risk logging and traceability obligations (from August 2026) named in our market research as a driver for a receipt-shaped record.