German Practice Management Shared Semantics (R4)
0.102.3 - release
Germany
German Practice Management Shared Semantics (R4) - Downloaded Version null See the Directory of published versions
This page defines how a FHIR R4 consumer distinguishes a clinical assertion
accepted by a physician from a billing diagnosis and from an unaccepted source
statement. The contract uses base R4 (hl7.fhir.r4.core 4.0.1) and codes from
the installed hl7.terminology.r4 7.4.0 package only. It adds no profile,
extension, CodeSystem, ValueSet, NamingSystem or SearchParameter, and it does
not change existing billing resources.
A clinical record and a billing record are separate records with separate identities, acceptance events and lifecycles. Accepting one never writes a record in the other domain. An ICD-10-GM record establishes no clinical acceptance, whatever its Diagnosesicherheit, status, Dauerdiagnose marker or number of quarterly copies. Codes, coding positions and status values never establish acceptance; only the acceptance evidence below does.
Physician acceptance is recorded as one base R4 Provenance per accepted
operation. No further adoption or examination step is required. The
Provenance is acceptance evidence only when all of the following hold:
Provenance.target references the accepted clinical resource with the
unversioned reference Condition/{id}, written in the same transaction as
the version it accepts. A version-specific target
Condition/{id}/_history/{version} is a contract defect and not acceptance.
A reference may be relative or absolute on the same server base.Provenance.reason contains v3-ActReason#TREAT
(http://terminology.hl7.org/CodeSystem/v3-ActReason), the clinical purpose
from the extensible PurposeOfUse binding. It does not contain the billing
purpose v3-ActReason#HPAYMT.Provenance.agent has Provenance.agent.type
provenance-participant-type#verifier, Provenance.agent.role containing
practitioner-role#doctor, and Provenance.agent.who referencing the
accepting Practitioner or PractitionerRole. This agent is the physician
acceptance.Provenance.activity is exactly one of v3-DataOperation#CREATE for the
first acceptance and v3-DataOperation#UPDATE for an accepted change,
including a later coding.Provenance.recorded is the acceptance time.Provenance.entity with role source references the source
DocumentReference. An accepted update carries exactly one entity with role
revision that references the prior version
Condition/{id}/_history/{version}; a first acceptance carries none. This
entity is the version linkage of the acceptance.Source extraction remains a separate fact. Extraction agents of type
assembler, transformer, author or enterer, and separate lineage
Provenances, never establish acceptance. A Provenance without TREAT, with
HPAYMT, without a verifier agent, or whose verifier lacks the doctor
role or references a Device, Patient or Organization is not acceptance. The
existing document attribution through Provenance and DocumentReference stays
the single provenance mechanism. Billing writers may record billing acceptance
with HPAYMT; they are not required to change.
The doctor role is asserted by the accepting system from its authenticated
user at the time of acceptance, and consumers trust that system's writes. The
contract does not prove a physician qualification by itself. When
Provenance.agent.who references a PractitionerRole, a consumer that reads
the stored record also requires that PractitionerRole.code contains
practitioner-role#doctor; a contradicting role is not acceptance.
An accepted clinical Condition carries:
Condition.subject referencing the Patient.Condition.code.text with the original wording, always present.
Condition.code.coding is optional; when present it uses SNOMED CT
(http://snomed.info/sct) only. A clinical assertion may be accepted
without a suitable code; a code added later is a separately accepted update
of the same record.Condition.verificationStatus with exactly one
condition-ver-status coding, independent of ICD qualifiers: a confirmed
assertion uses confirmed, a documented suspicion uses provisional or
differential, and a documented exclusion uses refuted without
Condition.clinicalStatus. An entered-in-error coding anywhere in
Condition.verificationStatus marks the record as retracted and never
satisfies the accepted predicate.Condition.onset[x] and Condition.abatement[x], the
first recording in Condition.recordedDate, and each acceptance time in its
Provenance.recorded.Condition.identifier with system urn:ietf:rfc:3986 and a
urn:uuid: value, plus a stable resource id. Updates keep both; the server
history keeps the prior versions. A distinct episode is a distinct Condition
with its own identity. Repeated mentions in sources or a new quarter do not
create a reassessment.A clinical Condition carries no billing marker:
http://fhir.de/CodeSystem/bfarm/icd-10-gm,
http://fhir.de/CodeSystem/dimdi/icd-10-gm,
http://hl7.org/fhir/sid/icd-10-gm or http://hl7.org/fhir/sid/icd-10;http://fhir.de/StructureDefinition/icd-10-gm-diagnosesicherheit or
http://fhir.de/StructureDefinition/seitenlokalisation extension;https://fhir.cognovis.de/praxis/StructureDefinition/dauerdiagnose
extension.These markers make a record a billing record. The dauerdiagnose extension
keeps its meaning for billing Conditions and grants no carry-over permission
to clinical records.
Consumers classify a stored record from its full version history and the Provenances that target it. Codes and status never grant acceptance.
| Classification | Condition |
|---|---|
accepted-clinical |
Acceptance evidence exists, the content rules above hold, and version integrity holds. |
accepted-clinical-unaccepted-revision |
Acceptance evidence exists, but a version was written without its own accepted operation. The current content is not accepted. |
contract-violation |
Acceptance evidence targets a record that carries a billing marker in any of its versions. |
billing |
No acceptance evidence, and the record carries an ICD-10-GM coding or another billing marker. Legacy records with additional SNOMED CT codings are included. |
source-assertion |
Anything else that is not accepted, including imported or extracted statements, author-only Provenance, version-specific targets, retracted records, records whose identifier or subject differs between versions, and records whose content rules fail. |
Version integrity means that every version of a clinical record is created by
exactly one accepted operation. A CREATE acceptance covers the first
version, and an UPDATE acceptance covers the version that follows the prior
version named by its revision entity. Condition.identifier and
Condition.subject are identical in every version. Consumers check this
through the record's complete _history, read across all result pages and
ordered oldest first; a history whose order is ambiguous is not classified.
Only accepted clinical operations write clinical records, and each writes the record together with its acceptance Provenance in one transaction. Synchronisation, quarterly copies, quarter changes and billing writers never write or rewrite clinical records and never write acceptance evidence. A read-and-write-back round trip therefore manufactures no acceptance.
The clinical record id is derived from its identity and the acceptance
Provenance id from the accepted operation. A first acceptance creates the
record and its Provenance create-only: the transaction fails as a whole when
either already exists. An accepted update carries an If-Match precondition
on the version the accepted proposal was based on, and its Provenance is
create-only, so a proposal based on an older version is a conflict and never
reverts a later change. After a failed commit the writer reads the stored
state: the operation is a replay, and writes nothing, only when the stored
acceptance Provenance equals the submitted one and the version that operation
produced equals the submitted content. A different change under an existing
operation id is a conflict. Concurrent submissions therefore leave one record
version and one unversioned acceptance Provenance per accepted operation. The
writer refuses an accepted operation on a stored record that carries a
billing marker, and an accepted update keeps the record's security labels and
tags (meta.security, meta.tag).
The acceptance predicate applies to every clinical-assertion row in the
same way as to Condition: acceptance evidence, no billing marker, not
entered-in-error in the named status element, and version integrity.
reference rows describe things that actions refer to, and
source-container rows carry sources and attribution; neither is an accepted
clinical assertion.
| Resource | Role | Documented statement | Discriminating native elements | Not |
|---|---|---|---|---|
Condition |
clinical-assertion | diagnosis, problem or health concern of the patient, with clinical certainty | verificationStatus, clinicalStatus, code, subject, onset[x], abatement[x] |
Not a relative's condition (FamilyMemberHistory) and not a billing record (ICD-10-GM coding or Dauerdiagnose marker). |
Observation |
clinical-assertion | measured or observed finding | status, code, value[x], effective[x] |
Not a diagnosis (Condition) and not a report (DiagnosticReport). |
DiagnosticReport |
clinical-assertion | report that interprets findings | status, code, result, conclusion |
Not the individual measured finding (Observation). |
Procedure |
clinical-assertion | performed intervention | status, code, performed[x] |
Not a requested or planned intervention (ServiceRequest, CarePlan). |
ServiceRequest |
clinical-assertion | requested or ordered service | status, intent, code |
Not a performed intervention (Procedure). |
CarePlan |
clinical-assertion | treatment plan with intended activities | status, intent, activity |
Not a performed act (Procedure, MedicationAdministration, Immunization). |
Goal |
clinical-assertion | intended health objective | lifecycleStatus, description, target |
Not an observed outcome (Observation) and not a performed act (Procedure). |
Task |
clinical-assertion | workflow step to be done or in progress | status, intent, code, focus |
Not the request it fulfils (ServiceRequest) and not a performed act (Procedure). |
MedicationRequest |
clinical-assertion | prescription or medication order | status, intent, medication[x], dosageInstruction |
Not a statement of use (MedicationStatement) and not a given dose (MedicationAdministration). |
MedicationStatement |
clinical-assertion | statement that the patient takes or took a medication | status, medication[x], effective[x], informationSource |
Not a prescription (MedicationRequest) and not a given dose (MedicationAdministration). |
MedicationAdministration |
clinical-assertion | medication dose actually given | status, medication[x], effective[x], performer |
Not a prescription (MedicationRequest) and not a statement of use (MedicationStatement). |
Medication |
reference | medication product definition referenced by medication actions | code, form, ingredient |
Not a medication action (MedicationRequest, MedicationStatement, MedicationAdministration). |
AllergyIntolerance |
clinical-assertion | allergy or intolerance assertion | clinicalStatus, verificationStatus, code, reaction |
Not a diagnosis (Condition) and not a single reaction finding (Observation). |
Immunization |
clinical-assertion | vaccination given or reported | status, vaccineCode, occurrence[x], primarySource |
Not a recommendation (ImmunizationRecommendation). |
ImmunizationRecommendation |
clinical-assertion | vaccination recommendation or forecast | recommendation.vaccineCode, recommendation.forecastStatus, recommendation.dateCriterion |
Not an administered vaccination (Immunization). |
FamilyMemberHistory |
clinical-assertion | health history of a relative | status, relationship, condition.code |
Not the patient's own diagnosis (Condition). |
Device |
reference | device identity and characteristics | type, udiCarrier, status |
Not the patient's use of the device (DeviceUseStatement). |
DeviceUseStatement |
clinical-assertion | use of a device by the patient | status, device, timing[x] |
Not the device definition (Device). |
DocumentReference |
source-container | source document and its renditions | status, type, content.attachment, subject |
Not an accepted clinical assertion (Condition and the other clinical rows). |
Composition |
source-container | structured document that organizes sections | status, type, section |
Not an accepted clinical assertion (Condition and the other clinical rows). |
Provenance |
source-container | origin, extraction and acceptance attribution | target, agent, entity, reason, activity |
Not a clinical assertion (Condition and the other clinical rows). |
Local persistence eligibility and export conformance are separate checks. Local persistence of an accepted clinical record needs physician acceptance and the original wording; it never needs a code.
Export to the International Patient Summary uses Condition-uv-ips from
hl7.fhir.uv.ips 2.0.1, where Condition.code is required with a preferred
binding. A text-only Condition.code is therefore structurally permitted.
Where a target export profile requires a coding, an uncoded record is not
exported in that coded form. A code is never fabricated, and IPS absent or
unknown codes never stand for an uncoded clinical statement.