German Practice Management FHIR Profiles (R4)
0.49.0 - STU1
German Practice Management FHIR Profiles (R4)
0.49.0 - STU1
German Practice Management FHIR Profiles (R4) - Local Development build (v0.49.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This page documents the architectural decisions (ADRs) that shape the design of this Implementation Guide.
| Status: Accepted | Date: 2026-04-27 |
Summary: The IG separates Plan-Library resources (PlanDefinition, ActivityDefinition, CarePlan —
emitted by PVS adapters into FHIR servers) from downstream Rule-Execution services. Computability
slots (condition, applicability, dynamicValue) are intentionally not populated in plan-library
resources. Plan variants are differentiated via the praxis-plan-topic CodeSystem, not separate profiles.
Full ADR: ADR-001-plan-library-vs-rule-execution.md
| Decision | Rationale |
|---|---|
| Plan-Library in FHIR | Declarative, forward-directed templates belong in FHIR with mature profile support |
| Rule-Execution outside the IG | Billing validation rules are not necessarily CQL-shaped; operational stores can meet performance targets |
| No CPG adoption | EBM/BEMA/HZV rules are quartalsbezogen and Kassen-specific — not mappable to CQL phenotypes |
Single PraxisBillingPattern profile |
Job/Chain/DMP/HZV variants differ only in section composition — topic CodeSystem is sufficient |
No hkp-status extension |
Da Vinci PAS dual-lifecycle (CarePlan + Claim/ClaimResponse) is already present since v0.40.0 |
praxis-plan-topic and praxis-plan-section CodeSystems; empty computability slots are by designPraxisBillingPattern remains the single PlanDefinition emission target; topic from praxis-plan-topic