HL7 Czech PS Implementation Guide
0.0.1 - ci-build CZ

HL7 Czech PS Implementation Guide, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/ps/ and changes regularly. See the Directory of published versions

Health Issues Relationships

Health Issues -> FHIR Profiles (CZ PS)
Note: This page provides a comprehensive mapping between the Logical Model for Health Issues and the FHIR profiles defined in this Patient Summary implementation guide.

Health Issues Mapping -> FHIR Profiles (CZ PS)

Below is a browsable diagram showing how the Health Issues model is realized by the HL7 FHIR profiles defined in this guide. The mapping covers all aspects of health problems, procedures, medical devices, and functional status assessment.

Model Overview

Health Issuescz-composition-pscz-condition-pscz-procedure-pscz-medical-devicecz-deviceUseStatement-hdrLogical ModelProfile

Primary Mappings - Composition Profile

Health Issues -> FHIR Profiles (CZ PS)
Health Issues (Logical Model) Relationship FHIR Target
Source Element Display Equivalence Target (Resource.Profile) Target Element Comments
problems A.2.4 - Current health problems equivalent (Composition.cz-composition-ps) Composition.section:sectionProblems.entry Maps to ofType(CZ_ConditionPs)
procedure A.2.4 - Procedures equivalent (Composition.cz-composition-ps) Composition.section:sectionProceduresHx.entry Maps to ofType(CZ_ProcedurePs)
device A.2.4 - Medical devices and implants equivalent (Composition.cz-composition-ps) Composition.section:sectionMedicalDevices.entry Maps to ofType(CZ_MedicalDevice)
functionalStatus A.2.4 - Functional status equivalent (Composition.cz-composition-ps) Composition.section:sectionFunctionalStatus.entry Maps to ofType(CZ_FunctionalStatusPs)

Health Problems Details - Condition Profile

Health Problems -> FHIR Profiles (CZ PS)
Health Problems (Logical Model) Relationship FHIR Target
Source Element Display Equivalence Target (Resource.Profile) Target Element Comments
problems.description A.2.4.1.1 Problem description equivalent (Condition.cz-condition-ps) Condition.code.text
problems.code A.2.4.1.2 Code equivalent (Condition.cz-condition-ps) Condition.code.coding
problems.onsetDate A.2.4.1.3 Date of onset equivalent (Condition.cz-condition-ps) Condition.onset Mapped to dateTime
problems.abatementDate A.2.4.1.4 Date of resolution or remission equivalent (Condition.cz-condition-ps) Condition.abatement Mapped to dateTime. Problems with active clinical status SHALL NOT have this element populated.
problems.abatementReason A.2.4.1.5 Circumstances of resolution equivalent (Condition.cz-condition-ps) Condition.note Mapped to note[+].text
problems.severity A.2.4.1.6 Severity equivalent (Condition.cz-condition-ps) Condition.severity
problems.stage A.2.4.1.7 Disease stage equivalent (Condition.cz-condition-ps) Condition.stage.summary
problems.verificationStatus A.2.4.1.8 Verification status of diagnosis equivalent (Condition.cz-condition-ps) Condition.verificationStatus

Procedures Details - Procedure Profile

Procedures -> FHIR Profiles (CZ PS)
Procedures (Logical Model) Relationship FHIR Target
Source Element Display Equivalence Target (Resource.Profile) Target Element Comments
procedure.code A.2.4.2.1 Procedure code equivalent (Procedure.cz-procedure-ps) Procedure.code.coding
procedure.description A.2.4.2.2 Procedure description equivalent (Procedure.cz-procedure-ps) Procedure.code.text
procedure.bodySite A.2.4.2.3 Body site equivalent (Procedure.cz-procedure-ps) Procedure.bodySite
procedure.performedDate A.2.4.2.4 Date performed equivalent (Procedure.cz-procedure-ps) Procedure.performed[] Mapped to performedDateTime
procedure.reasonCode A.2.4.2.5 Reason equivalent (Procedure.cz-procedure-ps) Procedure.reasonCode
procedure.outcome A.2.4.2.6 Outcome equivalent (Procedure.cz-procedure-ps) Procedure.outcome
procedure.complication A.2.4.2.7 Complication equivalent (Procedure.cz-procedure-ps) Procedure.complication
procedure.usedDevice A.2.4.2.8 Target medical device equivalent (Procedure.cz-procedure-ps) Procedure.focalDevice.manipulated It is RECOMMENDED to also populate Procedure.focalDevice.action to specify the type of device manipulation.
procedure.performedQuantity A.2.4.2.9 Number of occurrences equivalent (Procedure.cz-procedure-ps) Procedure.performedQuantity

Medical Devices - Device Profile

Medical Devices -> FHIR Profiles (CZ PS)
Medical Devices (Logical Model) Relationship FHIR Target
Element Description Relation Resource/Profile Element Description Notes
device.code A.2.4.3.1 Medical device equivalent (Device.cz-medical-device) Device.type
device.identifier A.2.4.3.2 Device identifier equivalent (Device.cz-medical-device) Device.udiCarrier

Device Use Statement - DeviceUseStatement Profile

Device Use Statement -> FHIR Profiles (CZ PS)
Device Use Statement (Logical Model) Relationship FHIR Target
Element Description Relation Resource/Profile Element Description Notes
device.useStartDate A.2.4.3.3 Implantation / start of use date equivalent (DeviceUseStatement.cz-deviceUseStatement-hdr) DeviceUseStatement.timingPeriod.start
device.useEndDate A.2.4.3.4 Explantation / end of use date equivalent (DeviceUseStatement.cz-deviceUseStatement-hdr) DeviceUseStatement.timingPeriod.end
device.reasonCode A.2.4.3.5 Reason equivalent (DeviceUseStatement.cz-deviceUseStatement-hdr) DeviceUseStatement.reasonCode
device.reasonCode A.2.4.3.5 Reason equivalent (DeviceUseStatement.cz-deviceUseStatement-hdr) DeviceUseStatement.reasonReference

Functional Status - Observation Profile

Functional Status -> FHIR Profiles (CZ PS)
Functional Status (Logical Model) Relationship FHIR Target
Element Description Relation Resource/Profile Element Description Notes
functionalStatus.effectiveDateTime A.2.4.4.1 Date and time equivalent (Observation.cz-observation-ps) Observation.effective[x] Mapped to effectiveDateTime
functionalStatus.performer A.2.4.4.2 Assessed by equivalent (Observation.cz-observation-ps) Observation.performer
functionalStatus.note A.2.4.4.3 Description equivalent (Observation.cz-observation-ps) Observation.value[x] Mapped to valueString
functionalStatus.assessment A.2.4.4.4 Formal assessment equivalent (Observation.cz-observation-ps) Observation.hasMember Contains references to individual formalized functional status assessment Observations.
functionalStatus.assessment.onsetDate A.2.4.4.4.1 Date of onset unmatched (Observation.cz-observation-ps) The onset date of functional limitation is currently not mapped in the CZ Patient Summary. This decision reflects the absence of harmonized guidance in the European Patient Summary Implementation Guide. The mapping will be revisited once a standardized approach is defined at the European level.
functionalStatus.assessment.valueText A.2.4.4.4.2 Assessment result (text) equivalent (Observation.cz-observation-ps) Observation.valueCodeableConcept.text
functionalStatus.assessment A.2.4.4.4.3 Assessment description equivalent (Observation.cz-observation-ps) Observation.code
functionalStatus.assessment.valueCodeableConcept A.2.4.4.4.4 Assessment result (coded) equivalent (Observation.cz-observation-ps) Observation.valueCodeableConcept.code