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 IG defines NamingSystems for identifier systems used in PVS (Praxisverwaltungssystem) synchronization. These naming systems establish canonical URIs for practice-management identifiers that flow between the FHIR adapter and PVS systems during bidirectional sync.
Generic, PVS-agnostic internal identifier for reverse-path synchronization between FHIR adapter and the PVS. Used whenever a practice management system needs to track a FHIR resource back to its originating PVS record without exposing PVS-specific primary key structures.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/pvs-id
PVS-internal patient number. The unique identifier a practice management system assigns to a patient record within its own database. Used in Patient.identifier to establish the bidirectional link for patient sync.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/pvs-patient-nummer
KV Abrechnungsnummer in full format — the complete coding of a practice's billing address with the insurance authority (Kassenärztliche Vereinigung). Includes region, site number, and practitioner identifier.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/abrechnungsnummer
Usage: Practitioner.identifier for the official billing identity with the KV.
Short-form alias for the billing number. Some practice management systems use a shorter representation of the KV billing address.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/abrechnungsnummer-kurz
Usage: Alternative identifier when PVS exposes only the short form.
Payment transaction ID generated by the practice management system. Used to link remittance data (Honorarbescheid, payment detail lines) to the PVS payment records.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/zahlung
Usage: ExplanationOfBenefit or related financial resources to track payments back to PVS records.
HVG (Hausarztzentrierte Versorgung / selective contract) contract type identifier. Distinguishes the type of contract (e.g., "HZV", "Facharztvertrag", "Besondere Versorgung") without identifying a specific contract instance.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/hvg-vertrag
Usage: Contract.type or Contract.identifier to tag which category of selective contract applies.
Unique identifier for a concrete HVG contract instance. Identifies not just the contract type, but the specific contract record in the PVS (e.g., "HZV with AOK Bayern 2025–2026").
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/hvg-vertrags-id
Usage: Contract.identifier to uniquely identify a single contract agreement.
Identifier-System für Scheindiagnosen (Diagnosen auf Abrechnungsscheinen). Dient der PVS-internen Verfolgung von Diagnosepositionen, die einem Schein zugeordnet sind.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/scheindiagnosen
Usage: Condition.identifier to link diagnosis records to billing forms (Scheine) for reverse-path synchronization.
GDT 3.5 Gerätekennung (Feldkennung 8402) — uniquely identifies a medical device or lab analyzer within GDT data streams. Used to link incoming GDT lab results (Satzart 6310) to the originating device and to maintain a PVS device registry.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/gdt-device-id
GDT Reference: FK 8402 (Gerätekennung) in GDT 3.5 specification
Usage: Device.identifier[gdtId] in the PraxisDevice profile to establish the bidirectional link between FHIR device records and PVS-managed devices. The practice management system uses this identifier to route lab orders to specific analyzers and to match results to devices.
LDT-Testkennungen (LDT laboratory test codes) als Identifier-System. Diese werden in Observation.code.coding verwendet, um LDT-spezifische Labortestergebnisse im Kontext von deutschen Laboratorien zu kodieren. Parallele LOINC-Kodierungen ermöglichen interoperable Mappings zu internationalen Standards.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/ldt-testkennungen
OID: 1.2.276.0.76.4.78 (Official LDT 3.2.19 test codes OID)
Kind: codesystem
Usage: Observation.code.coding for lab test results in LDT workflows. Often used alongside LOINC for dual coding (LDT-spezifisches System + internationales LOINC-Mapping).
Laborauftragsnummer (lab order/request identifier) nach LDT-Standard. Diese dient der Verfolgung von Laboraufträgen zwischen Praxis und Labor sowie für die Integration von Laborergebnissen mit dem ursprünglichen Auftrag.
Canonical URI: https://fhir.cognovis.de/praxis/NamingSystem/ldt-auftragsnummer
Kind: identifier
Usage: ServiceRequest.identifier to link lab orders and results back to the original request in LDT workflows.
All NamingSystems are defined with kind: identifier and use URI-based uniqueIds. They serve as metadata for the FHIR adapter to:
pvs-patient-nummer = "12345", the adapter resolves it against the NamingSystem to construct Patient.identifier[system="https://fhir.cognovis.de/praxis/NamingSystem/pvs-patient-nummer", value="12345"]NamingSystems are reference/metadata resources — they do not have distinct API endpoints. They are included in the published IG package and discoverable via the /fhir/NamingSystem?... search endpoint as part of the standard FHIR RESTful API.