HL7 Czech Hospital Discharge Report Implementation Guide
0.0.2 - ci-build Czechia flag

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

Logical Model: HospitalStayEhnCz - Detailed Descriptions

Draft as of 2025-08-23

Definitions for the HospitalStayCz logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. HospitalStayCz
Definition

Hospital Discharge Report - Hospital stay - A.2.6 eHN

ShortA.2.6 - Hospital stay (eHN)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. HospitalStayCz.diagnosticSummary
Definition

All problems/diagnoses that affect care during the inpatient case or are important to be recorded to ensure continuity of care. The diagnostic summary differentiates, in accordance with the international recommendation, between problems treated during hospital stay and other (untreated) problems. Treated problems are problems that were the subject of diagnostics, therapy, nursing, or (continuous) monitoring during the hospitalisation. Furthermore problems could be divided into three categories: problems present on admission (POA), conditions acquired during hospital stay (HAC) and problems that cannot be classified as being of any of the two (N/A). The diagnostic summary contains all conditions as they were recognised at the end of hospitalisation, after all examinations. This section contains concise, well specified, codeable, summary of problems. Problems are ordered by importance (main problems first) during hospital stay. Description of the problem might be completed with additional details in the medical history section and/or in the Synthesis section.

ShortA.2.7.1 - Diagnostic summary
Control1..*
TypeBase
4. HospitalStayCz.diagnosticSummary.problemDescription
Definition

Problem specification in narrative form

ShortA.2.7.1.1 - Problem description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. HospitalStayCz.diagnosticSummary.problemDetails
Definition

Problem details include code that identifies problem, specification of the body structure, laterality, and other aspects of the problem.

ShortA.2.7.1.2 - Problem details
Control0..*
TypeBase
8. HospitalStayCz.diagnosticSummary.onsetDate
Definition

Onset date of a problem/condition

ShortA.2.7.1.3 - Onset date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. HospitalStayCz.diagnosticSummary.endDate
Definition

The date or estimated date that the condition resolved or went into remission.

ShortA.2.7.1.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. HospitalStayCz.diagnosticSummary.category
Definition

Category of the problem allows flagging for conditions acquired during hospital stay.

ShortA.2.7.1.5 - Category
Control1..1
TypeCodeableConcept
14. HospitalStayCz.diagnosticSummary.treatmentClass
Definition

Class of the problem (treated, other) in relation to the hospital encounter. Treated problems were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the hospital encounter. At least one problem should be marked as Treated. Other problems are recorded only if they are important for continuity of care (after discharge).

ShortA.2.7.1.6 - Treatment class
Control1..1
TypeCodeableConcept
16. HospitalStayCz.diagnosticSummary.clinicalStatus
Definition

Status of the condition/problem (active, resolved, inactive, ...)

ShortA.2.7.1.7 - Clinical status
Control0..1
TypeCodeableConcept
18. HospitalStayCz.diagnosticSummary.resolution
Definition

Describes the reason for which the status of the problem changed from current to inactive (e.g. surgical procedure, medical treatment, etc.). This field includes 'free text' if the resolution circumstances are not already included in other fields such as surgical procedure, medical device, etc., e.g. hepatic cystectomy (this will be the resolution circumstances for the problem 'hepatic cyst' and will be included in surgical procedures).

ShortA.2.7.1.8 - Resolution circumstances
Control0..1
TypeBase
20. HospitalStayCz.diagnosticSummary.severity
Definition

A subjective assessment of the severity of the condition as evaluated by the clinician.

ShortA.2.7.1.9 - Severity
Control0..1
TypeCodeableConcept
22. HospitalStayCz.diagnosticSummary.stage
Definition

Stage/grade usually assessed formally using a specific staging/grading system. Multiple assessment systems could be used.

ShortA.2.7.1.10 - Stage
Control0..*
TypeCodeableConcept
24. HospitalStayCz.significantProcedures
Definition

Significant surgical and non-surgical procedures performed during hospitalisation which are significant for continuity of care, e.g. surgeries and other 'instrumental' interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. This section does not include purely diagnostic procedures (MRI, CT, etc.). If no significant performance has been performed, this fact must be explicitly stated using the IPS Absent and Unknown Data.

ShortA.2.7.2 - Significant procedures
Control1..*
TypeBase
26. HospitalStayCz.significantProcedures.procedureCode
Definition

Procedure code

ShortA.2.7.2.1 - Procedure code
Control0..*
TypeCodeableConcept
28. HospitalStayCz.significantProcedures.description
Definition

Narrative description of the procedure

ShortA.2.7.2.2 - Procedure description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. HospitalStayCz.significantProcedures.bodySite
Definition

Procedure target body site and laterality

ShortA.2.7.2.3 - Body site
Control0..1
TypeCodeableConcept
32. HospitalStayCz.significantProcedures.date
Definition

Date and time when procedure was performed

ShortA.2.7.2.4 - Procedure date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
34. HospitalStayCz.significantProcedures.reason
Definition

The coded reason why the procedure was performed. This may be a coded entity or may simply be present as text.

ShortA.2.7.2.5 - Procedure reason
Control0..*
TypeCodeableConcept
36. HospitalStayCz.significantProcedures.outcome
Definition

The outcome of the procedure - did it resolve the reasons for the procedure being performed?

ShortA.2.7.2.6 - Outcome
Control0..1
TypeCodeableConcept
38. HospitalStayCz.significantProcedures.complication
Definition

Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the procedure description, which will typically describe the procedure itself rather than any 'post procedure' issues.

ShortA.2.7.2.7 - Complication
Control0..*
TypeCodeableConcept
40. HospitalStayCz.significantProcedures.focalDevice
Definition

A reference to the device or devices that is/are implanted, removed, or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.

ShortA.2.7.2.8 - Focal device
Control0..*
TypeBase
42. HospitalStayCz.medicalDevices
Definition

Implants and used medical devices that affected or may affect the provision of health services (diagnosis and treatment). Also medical devices explanted, or its use was stopped during hospitalisation. If the section is blank, the reason must be explicitly stated using the IPS Absent and Unknown Data coding system

ShortA.2.7.3 - Medical devices and implants
Control1..*
TypeBase
44. HospitalStayCz.medicalDevices.description
Definition

Describes the patient's implanted and external medical devices and equipment upon which their health status depends. Includes devices such as cardiac pacemakers, implantable fibrillator, prosthesis, ferromagnetic bone implants, etc. of which the HP needs to be aware.

ShortA.2.7.3.1 - Device and implant description
Control1..1
TypeCodeableConcept
46. HospitalStayCz.medicalDevices.identifier
Definition

Normalised identifier of the device instance such as UDI according to REGULATION (EU) 2017/745

ShortA.2.7.3.2 - Device ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
48. HospitalStayCz.medicalDevices.implantDate
Definition

The date and time the device was implanted or when its use began.

ShortA.2.7.3.3 - Implant date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
50. HospitalStayCz.medicalDevices.endDate
Definition

Date and time when the device was explanted from the patient or the external device was no longer in use; likewise when the device is planned to be explanted

ShortA.2.7.3.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
52. HospitalStayCz.medicalDevices.reason
Definition

The medical reason for use of the medical device.

ShortA.2.7.3.5 - Reason
Control0..*
TypeCodeableConcept
54. HospitalStayCz.pharmacotherapy
Definition

Selected drug treatment during hospitalisation. Medicinal products that were administered during hospitalisation and whose administration has already been discontinued before discharge. Only products which are important for continuity of care (antibiotics other than completely routine, corticosteroids in high doses, etc.) will be listed. Products which administration will continue after discharge will be also recorder in the Medication summary section.Medicinal products, the administration of which was started during hospitalisation, but is also recommended after discharge, will be listed in the summary table in the recommendation section.

ShortA.2.7.5 - Pharmacotherapy
Control0..*
TypeBase
56. HospitalStayCz.pharmacotherapy.reason
Definition

The reason why the medication is or was prescribed or used. It provides a link to the Past or current health conditions or problems that the patient has had or has.

ShortA.2.7.5.1 - Medication reason
Control0..1
TypeCodeableConcept
58. HospitalStayCz.pharmacotherapy.productCode
Definition

Product code

ShortA.2.7.5.2 - Code
Control1..1
TypeCodeableConcept
60. HospitalStayCz.pharmacotherapy.intendedUse
Definition

Indication intended use as: prevention or treatment Example: prophylaxis, treatment, diagnostic, anaesthesia.

ShortA.2.7.5.3 - Intended use
Control0..*
TypeCodeableConcept
62. HospitalStayCz.pharmacotherapy.productName
Definition

Brand name if biological medicinal product or when justified by the health professional (ref. Commission Directive 2012/52/EU)

ShortA.2.7.5.4 - Brand name
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
64. HospitalStayCz.pharmacotherapy.activeIngredient
Definition

Substance that alone or in combination with one or more other ingredients produces the intended activity of a medicinal product. Example: 'paracetamol'

ShortA.2.7.5.5 - Active ingredient list
Control0..*
TypeCodeableConcept
66. HospitalStayCz.pharmacotherapy.strength
Definition

The content of the active ingredient expressed quantifiably per dosage unit, per unit of volume or per unit of weight, according to the pharmaceutical dose form. Example: 500 mg per tablet

ShortA.2.7.5.6 - Strength
Control0..*
TypeRatio
68. HospitalStayCz.pharmacotherapy.doseForm
Definition

The form in which a pharmaceutical product is presented in the medicinal product package (e.g. tablet, syrup)

ShortA.2.7.5.7 - Pharmaceutical dose form
Control0..1
TypeCodeableConcept
70. HospitalStayCz.pharmacotherapy.dosageRegimen
Definition

Number of units per intake and frequency of intake over a specified duration of time. Example: 1 tablet every 24h, for 10 days

ShortA.2.7.5.8 - Dosage Regimen
Control0..*
TypeBase
72. HospitalStayCz.pharmacotherapy.route
Definition

Path by which the pharmaceutical product is taken into or makes contact with the body.

ShortA.2.7.5.9 - Route of administration
Control0..1
TypeCodeableConcept
74. HospitalStayCz.pharmacotherapy.period
Definition

The time interval when the patient was, or was not, given the medication.

ShortA.2.7.5.10 - Period of treatment
Control0..1
TypePeriod
76. HospitalStayCz.significantResults
Definition

Results of significant functional, diagnostic, and imaging examinations to ensure continuity of care, performed during hospitalisation. Results of examinations ordered but not yet delivered should be presented separately from results already delivered.

ShortA.2.7.6 - Significant Observation Results
Control0..*
TypeBase
78. HospitalStayCz.significantResults.date
Definition

Date and time of the observation

ShortA.2.7.6.1 - Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
80. HospitalStayCz.significantResults.status
Definition

Status of the observation (e.g. registered, preliminary, final)

ShortA.2.7.6.2 - Observation status
Control1..1
TypeCodeableConcept
82. HospitalStayCz.significantResults.description
Definition

Narrative representation of the observation result and findings.

ShortA.2.7.6.3 - Result description
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
84. HospitalStayCz.significantResults.details
Definition

Observation details include code that identifies observation, specification of the observed body structure or specimen, date and time of the specimen collection, observation method or protocol used and other aspects of the observation.

ShortA.2.7.6.4 - Observation details
Control1..1
TypeBase
86. HospitalStayCz.significantResults.result
Definition

Result of the observation including numeric and coded results of the measurement, details about how the tests were done to get the result values, information about reference ranges and result interpretation. Content of the observation result will vary according to the type of the observation.

ShortA.2.7.6.5 - Observation result
Control0..1
TypeBase
88. HospitalStayCz.significantResults.reporter
Definition

With certain observation results, e.g. there may also be an interpreter or a person responsible for validation.

ShortA.2.7.6.7 - Reporter
Control0..*
TypeBase
90. HospitalStayCz.synthesis
Definition

This section provides clinical synthesis (e.g. description of reasons and course of hospital stay) clustered by managed conditions, Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.

ShortA.2.7.7 - Synthesis
Control1..1
TypeBase
92. HospitalStayCz.synthesis.description
Definition

Summary description of the reason and course of hospitalisation for a specific problem.

ShortA.2.7.7.1 - Problem synthesis
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
94. HospitalStayCz.synthesis.reasoning
Definition

The clinical summary can be concluded with a clinical consideration (diff. diagnosis, explanation of context, etc.) for clinically complex conditions.

ShortA.2.7.7.2 - Clinical reasoning
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. HospitalStayCz
Definition

Hospital Discharge Report - Hospital stay - A.2.6 eHN

ShortA.2.6 - Hospital stay (eHN)
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. HospitalStayCz.diagnosticSummary
Definition

All problems/diagnoses that affect care during the inpatient case or are important to be recorded to ensure continuity of care. The diagnostic summary differentiates, in accordance with the international recommendation, between problems treated during hospital stay and other (untreated) problems. Treated problems are problems that were the subject of diagnostics, therapy, nursing, or (continuous) monitoring during the hospitalisation. Furthermore problems could be divided into three categories: problems present on admission (POA), conditions acquired during hospital stay (HAC) and problems that cannot be classified as being of any of the two (N/A). The diagnostic summary contains all conditions as they were recognised at the end of hospitalisation, after all examinations. This section contains concise, well specified, codeable, summary of problems. Problems are ordered by importance (main problems first) during hospital stay. Description of the problem might be completed with additional details in the medical history section and/or in the Synthesis section.

ShortA.2.7.1 - Diagnostic summary
Control1..*
TypeBase
4. HospitalStayCz.diagnosticSummary.problemDescription
Definition

Problem specification in narrative form

ShortA.2.7.1.1 - Problem description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. HospitalStayCz.diagnosticSummary.problemDetails
Definition

Problem details include code that identifies problem, specification of the body structure, laterality, and other aspects of the problem.

ShortA.2.7.1.2 - Problem details
Control0..*
TypeBase
8. HospitalStayCz.diagnosticSummary.onsetDate
Definition

Onset date of a problem/condition

ShortA.2.7.1.3 - Onset date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. HospitalStayCz.diagnosticSummary.endDate
Definition

The date or estimated date that the condition resolved or went into remission.

ShortA.2.7.1.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. HospitalStayCz.diagnosticSummary.category
Definition

Category of the problem allows flagging for conditions acquired during hospital stay.

ShortA.2.7.1.5 - Category
Control1..1
TypeCodeableConcept
14. HospitalStayCz.diagnosticSummary.treatmentClass
Definition

Class of the problem (treated, other) in relation to the hospital encounter. Treated problems were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the hospital encounter. At least one problem should be marked as Treated. Other problems are recorded only if they are important for continuity of care (after discharge).

ShortA.2.7.1.6 - Treatment class
Control1..1
TypeCodeableConcept
16. HospitalStayCz.diagnosticSummary.clinicalStatus
Definition

Status of the condition/problem (active, resolved, inactive, ...)

ShortA.2.7.1.7 - Clinical status
Control0..1
TypeCodeableConcept
18. HospitalStayCz.diagnosticSummary.resolution
Definition

Describes the reason for which the status of the problem changed from current to inactive (e.g. surgical procedure, medical treatment, etc.). This field includes 'free text' if the resolution circumstances are not already included in other fields such as surgical procedure, medical device, etc., e.g. hepatic cystectomy (this will be the resolution circumstances for the problem 'hepatic cyst' and will be included in surgical procedures).

ShortA.2.7.1.8 - Resolution circumstances
Control0..1
TypeBase
20. HospitalStayCz.diagnosticSummary.severity
Definition

A subjective assessment of the severity of the condition as evaluated by the clinician.

ShortA.2.7.1.9 - Severity
Control0..1
TypeCodeableConcept
22. HospitalStayCz.diagnosticSummary.stage
Definition

Stage/grade usually assessed formally using a specific staging/grading system. Multiple assessment systems could be used.

ShortA.2.7.1.10 - Stage
Control0..*
TypeCodeableConcept
24. HospitalStayCz.significantProcedures
Definition

Significant surgical and non-surgical procedures performed during hospitalisation which are significant for continuity of care, e.g. surgeries and other 'instrumental' interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. This section does not include purely diagnostic procedures (MRI, CT, etc.). If no significant performance has been performed, this fact must be explicitly stated using the IPS Absent and Unknown Data.

ShortA.2.7.2 - Significant procedures
Control1..*
TypeBase
26. HospitalStayCz.significantProcedures.procedureCode
Definition

Procedure code

ShortA.2.7.2.1 - Procedure code
Control0..*
TypeCodeableConcept
28. HospitalStayCz.significantProcedures.description
Definition

Narrative description of the procedure

ShortA.2.7.2.2 - Procedure description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. HospitalStayCz.significantProcedures.bodySite
Definition

Procedure target body site and laterality

ShortA.2.7.2.3 - Body site
Control0..1
TypeCodeableConcept
32. HospitalStayCz.significantProcedures.date
Definition

Date and time when procedure was performed

ShortA.2.7.2.4 - Procedure date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
34. HospitalStayCz.significantProcedures.reason
Definition

The coded reason why the procedure was performed. This may be a coded entity or may simply be present as text.

ShortA.2.7.2.5 - Procedure reason
Control0..*
TypeCodeableConcept
36. HospitalStayCz.significantProcedures.outcome
Definition

The outcome of the procedure - did it resolve the reasons for the procedure being performed?

ShortA.2.7.2.6 - Outcome
Control0..1
TypeCodeableConcept
38. HospitalStayCz.significantProcedures.complication
Definition

Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the procedure description, which will typically describe the procedure itself rather than any 'post procedure' issues.

ShortA.2.7.2.7 - Complication
Control0..*
TypeCodeableConcept
40. HospitalStayCz.significantProcedures.focalDevice
Definition

A reference to the device or devices that is/are implanted, removed, or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.

ShortA.2.7.2.8 - Focal device
Control0..*
TypeBase
42. HospitalStayCz.medicalDevices
Definition

Implants and used medical devices that affected or may affect the provision of health services (diagnosis and treatment). Also medical devices explanted, or its use was stopped during hospitalisation. If the section is blank, the reason must be explicitly stated using the IPS Absent and Unknown Data coding system

ShortA.2.7.3 - Medical devices and implants
Control1..*
TypeBase
44. HospitalStayCz.medicalDevices.description
Definition

Describes the patient's implanted and external medical devices and equipment upon which their health status depends. Includes devices such as cardiac pacemakers, implantable fibrillator, prosthesis, ferromagnetic bone implants, etc. of which the HP needs to be aware.

ShortA.2.7.3.1 - Device and implant description
Control1..1
TypeCodeableConcept
46. HospitalStayCz.medicalDevices.identifier
Definition

Normalised identifier of the device instance such as UDI according to REGULATION (EU) 2017/745

ShortA.2.7.3.2 - Device ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
48. HospitalStayCz.medicalDevices.implantDate
Definition

The date and time the device was implanted or when its use began.

ShortA.2.7.3.3 - Implant date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
50. HospitalStayCz.medicalDevices.endDate
Definition

Date and time when the device was explanted from the patient or the external device was no longer in use; likewise when the device is planned to be explanted

ShortA.2.7.3.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
52. HospitalStayCz.medicalDevices.reason
Definition

The medical reason for use of the medical device.

ShortA.2.7.3.5 - Reason
Control0..*
TypeCodeableConcept
54. HospitalStayCz.pharmacotherapy
Definition

Selected drug treatment during hospitalisation. Medicinal products that were administered during hospitalisation and whose administration has already been discontinued before discharge. Only products which are important for continuity of care (antibiotics other than completely routine, corticosteroids in high doses, etc.) will be listed. Products which administration will continue after discharge will be also recorder in the Medication summary section.Medicinal products, the administration of which was started during hospitalisation, but is also recommended after discharge, will be listed in the summary table in the recommendation section.

ShortA.2.7.5 - Pharmacotherapy
Control0..*
TypeBase
56. HospitalStayCz.pharmacotherapy.reason
Definition

The reason why the medication is or was prescribed or used. It provides a link to the Past or current health conditions or problems that the patient has had or has.

ShortA.2.7.5.1 - Medication reason
Control0..1
TypeCodeableConcept
58. HospitalStayCz.pharmacotherapy.productCode
Definition

Product code

ShortA.2.7.5.2 - Code
Control1..1
TypeCodeableConcept
60. HospitalStayCz.pharmacotherapy.intendedUse
Definition

Indication intended use as: prevention or treatment Example: prophylaxis, treatment, diagnostic, anaesthesia.

ShortA.2.7.5.3 - Intended use
Control0..*
TypeCodeableConcept
62. HospitalStayCz.pharmacotherapy.productName
Definition

Brand name if biological medicinal product or when justified by the health professional (ref. Commission Directive 2012/52/EU)

ShortA.2.7.5.4 - Brand name
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
64. HospitalStayCz.pharmacotherapy.activeIngredient
Definition

Substance that alone or in combination with one or more other ingredients produces the intended activity of a medicinal product. Example: 'paracetamol'

ShortA.2.7.5.5 - Active ingredient list
Control0..*
TypeCodeableConcept
66. HospitalStayCz.pharmacotherapy.strength
Definition

The content of the active ingredient expressed quantifiably per dosage unit, per unit of volume or per unit of weight, according to the pharmaceutical dose form. Example: 500 mg per tablet

ShortA.2.7.5.6 - Strength
Control0..*
TypeRatio
68. HospitalStayCz.pharmacotherapy.doseForm
Definition

The form in which a pharmaceutical product is presented in the medicinal product package (e.g. tablet, syrup)

ShortA.2.7.5.7 - Pharmaceutical dose form
Control0..1
TypeCodeableConcept
70. HospitalStayCz.pharmacotherapy.dosageRegimen
Definition

Number of units per intake and frequency of intake over a specified duration of time. Example: 1 tablet every 24h, for 10 days

ShortA.2.7.5.8 - Dosage Regimen
Control0..*
TypeBase
72. HospitalStayCz.pharmacotherapy.route
Definition

Path by which the pharmaceutical product is taken into or makes contact with the body.

ShortA.2.7.5.9 - Route of administration
Control0..1
TypeCodeableConcept
74. HospitalStayCz.pharmacotherapy.period
Definition

The time interval when the patient was, or was not, given the medication.

ShortA.2.7.5.10 - Period of treatment
Control0..1
TypePeriod
76. HospitalStayCz.significantResults
Definition

Results of significant functional, diagnostic, and imaging examinations to ensure continuity of care, performed during hospitalisation. Results of examinations ordered but not yet delivered should be presented separately from results already delivered.

ShortA.2.7.6 - Significant Observation Results
Control0..*
TypeBase
78. HospitalStayCz.significantResults.date
Definition

Date and time of the observation

ShortA.2.7.6.1 - Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
80. HospitalStayCz.significantResults.status
Definition

Status of the observation (e.g. registered, preliminary, final)

ShortA.2.7.6.2 - Observation status
Control1..1
TypeCodeableConcept
82. HospitalStayCz.significantResults.description
Definition

Narrative representation of the observation result and findings.

ShortA.2.7.6.3 - Result description
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
84. HospitalStayCz.significantResults.details
Definition

Observation details include code that identifies observation, specification of the observed body structure or specimen, date and time of the specimen collection, observation method or protocol used and other aspects of the observation.

ShortA.2.7.6.4 - Observation details
Control1..1
TypeBase
86. HospitalStayCz.significantResults.result
Definition

Result of the observation including numeric and coded results of the measurement, details about how the tests were done to get the result values, information about reference ranges and result interpretation. Content of the observation result will vary according to the type of the observation.

ShortA.2.7.6.5 - Observation result
Control0..1
TypeBase
88. HospitalStayCz.significantResults.reporter
Definition

With certain observation results, e.g. there may also be an interpreter or a person responsible for validation.

ShortA.2.7.6.7 - Reporter
Control0..*
TypeBase
90. HospitalStayCz.synthesis
Definition

This section provides clinical synthesis (e.g. description of reasons and course of hospital stay) clustered by managed conditions, Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.

ShortA.2.7.7 - Synthesis
Control1..1
TypeBase
92. HospitalStayCz.synthesis.description
Definition

Summary description of the reason and course of hospitalisation for a specific problem.

ShortA.2.7.7.1 - Problem synthesis
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
94. HospitalStayCz.synthesis.reasoning
Definition

The clinical summary can be concluded with a clinical consideration (diff. diagnosis, explanation of context, etc.) for clinically complex conditions.

ShortA.2.7.7.2 - Clinical reasoning
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. HospitalStayCz
Definition

Hospital Discharge Report - Hospital stay - A.2.6 eHN

ShortA.2.6 - Hospital stay (eHN)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. HospitalStayCz.diagnosticSummary
Definition

All problems/diagnoses that affect care during the inpatient case or are important to be recorded to ensure continuity of care. The diagnostic summary differentiates, in accordance with the international recommendation, between problems treated during hospital stay and other (untreated) problems. Treated problems are problems that were the subject of diagnostics, therapy, nursing, or (continuous) monitoring during the hospitalisation. Furthermore problems could be divided into three categories: problems present on admission (POA), conditions acquired during hospital stay (HAC) and problems that cannot be classified as being of any of the two (N/A). The diagnostic summary contains all conditions as they were recognised at the end of hospitalisation, after all examinations. This section contains concise, well specified, codeable, summary of problems. Problems are ordered by importance (main problems first) during hospital stay. Description of the problem might be completed with additional details in the medical history section and/or in the Synthesis section.

ShortA.2.7.1 - Diagnostic summary
Control1..*
TypeBase
4. HospitalStayCz.diagnosticSummary.problemDescription
Definition

Problem specification in narrative form

ShortA.2.7.1.1 - Problem description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. HospitalStayCz.diagnosticSummary.problemDetails
Definition

Problem details include code that identifies problem, specification of the body structure, laterality, and other aspects of the problem.

ShortA.2.7.1.2 - Problem details
Control0..*
TypeBase
8. HospitalStayCz.diagnosticSummary.onsetDate
Definition

Onset date of a problem/condition

ShortA.2.7.1.3 - Onset date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. HospitalStayCz.diagnosticSummary.endDate
Definition

The date or estimated date that the condition resolved or went into remission.

ShortA.2.7.1.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. HospitalStayCz.diagnosticSummary.category
Definition

Category of the problem allows flagging for conditions acquired during hospital stay.

ShortA.2.7.1.5 - Category
Control1..1
TypeCodeableConcept
14. HospitalStayCz.diagnosticSummary.treatmentClass
Definition

Class of the problem (treated, other) in relation to the hospital encounter. Treated problems were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the hospital encounter. At least one problem should be marked as Treated. Other problems are recorded only if they are important for continuity of care (after discharge).

ShortA.2.7.1.6 - Treatment class
Control1..1
TypeCodeableConcept
16. HospitalStayCz.diagnosticSummary.clinicalStatus
Definition

Status of the condition/problem (active, resolved, inactive, ...)

ShortA.2.7.1.7 - Clinical status
Control0..1
TypeCodeableConcept
18. HospitalStayCz.diagnosticSummary.resolution
Definition

Describes the reason for which the status of the problem changed from current to inactive (e.g. surgical procedure, medical treatment, etc.). This field includes 'free text' if the resolution circumstances are not already included in other fields such as surgical procedure, medical device, etc., e.g. hepatic cystectomy (this will be the resolution circumstances for the problem 'hepatic cyst' and will be included in surgical procedures).

ShortA.2.7.1.8 - Resolution circumstances
Control0..1
TypeBase
20. HospitalStayCz.diagnosticSummary.severity
Definition

A subjective assessment of the severity of the condition as evaluated by the clinician.

ShortA.2.7.1.9 - Severity
Control0..1
TypeCodeableConcept
22. HospitalStayCz.diagnosticSummary.stage
Definition

Stage/grade usually assessed formally using a specific staging/grading system. Multiple assessment systems could be used.

ShortA.2.7.1.10 - Stage
Control0..*
TypeCodeableConcept
24. HospitalStayCz.significantProcedures
Definition

Significant surgical and non-surgical procedures performed during hospitalisation which are significant for continuity of care, e.g. surgeries and other 'instrumental' interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. This section does not include purely diagnostic procedures (MRI, CT, etc.). If no significant performance has been performed, this fact must be explicitly stated using the IPS Absent and Unknown Data.

ShortA.2.7.2 - Significant procedures
Control1..*
TypeBase
26. HospitalStayCz.significantProcedures.procedureCode
Definition

Procedure code

ShortA.2.7.2.1 - Procedure code
Control0..*
TypeCodeableConcept
28. HospitalStayCz.significantProcedures.description
Definition

Narrative description of the procedure

ShortA.2.7.2.2 - Procedure description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. HospitalStayCz.significantProcedures.bodySite
Definition

Procedure target body site and laterality

ShortA.2.7.2.3 - Body site
Control0..1
TypeCodeableConcept
32. HospitalStayCz.significantProcedures.date
Definition

Date and time when procedure was performed

ShortA.2.7.2.4 - Procedure date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
34. HospitalStayCz.significantProcedures.reason
Definition

The coded reason why the procedure was performed. This may be a coded entity or may simply be present as text.

ShortA.2.7.2.5 - Procedure reason
Control0..*
TypeCodeableConcept
36. HospitalStayCz.significantProcedures.outcome
Definition

The outcome of the procedure - did it resolve the reasons for the procedure being performed?

ShortA.2.7.2.6 - Outcome
Control0..1
TypeCodeableConcept
38. HospitalStayCz.significantProcedures.complication
Definition

Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the procedure description, which will typically describe the procedure itself rather than any 'post procedure' issues.

ShortA.2.7.2.7 - Complication
Control0..*
TypeCodeableConcept
40. HospitalStayCz.significantProcedures.focalDevice
Definition

A reference to the device or devices that is/are implanted, removed, or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.

ShortA.2.7.2.8 - Focal device
Control0..*
TypeBase
42. HospitalStayCz.medicalDevices
Definition

Implants and used medical devices that affected or may affect the provision of health services (diagnosis and treatment). Also medical devices explanted, or its use was stopped during hospitalisation. If the section is blank, the reason must be explicitly stated using the IPS Absent and Unknown Data coding system

ShortA.2.7.3 - Medical devices and implants
Control1..*
TypeBase
44. HospitalStayCz.medicalDevices.description
Definition

Describes the patient's implanted and external medical devices and equipment upon which their health status depends. Includes devices such as cardiac pacemakers, implantable fibrillator, prosthesis, ferromagnetic bone implants, etc. of which the HP needs to be aware.

ShortA.2.7.3.1 - Device and implant description
Control1..1
TypeCodeableConcept
46. HospitalStayCz.medicalDevices.identifier
Definition

Normalised identifier of the device instance such as UDI according to REGULATION (EU) 2017/745

ShortA.2.7.3.2 - Device ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
48. HospitalStayCz.medicalDevices.implantDate
Definition

The date and time the device was implanted or when its use began.

ShortA.2.7.3.3 - Implant date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
50. HospitalStayCz.medicalDevices.endDate
Definition

Date and time when the device was explanted from the patient or the external device was no longer in use; likewise when the device is planned to be explanted

ShortA.2.7.3.4 - End date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
52. HospitalStayCz.medicalDevices.reason
Definition

The medical reason for use of the medical device.

ShortA.2.7.3.5 - Reason
Control0..*
TypeCodeableConcept
54. HospitalStayCz.pharmacotherapy
Definition

Selected drug treatment during hospitalisation. Medicinal products that were administered during hospitalisation and whose administration has already been discontinued before discharge. Only products which are important for continuity of care (antibiotics other than completely routine, corticosteroids in high doses, etc.) will be listed. Products which administration will continue after discharge will be also recorder in the Medication summary section.Medicinal products, the administration of which was started during hospitalisation, but is also recommended after discharge, will be listed in the summary table in the recommendation section.

ShortA.2.7.5 - Pharmacotherapy
Control0..*
TypeBase
56. HospitalStayCz.pharmacotherapy.reason
Definition

The reason why the medication is or was prescribed or used. It provides a link to the Past or current health conditions or problems that the patient has had or has.

ShortA.2.7.5.1 - Medication reason
Control0..1
TypeCodeableConcept
58. HospitalStayCz.pharmacotherapy.productCode
Definition

Product code

ShortA.2.7.5.2 - Code
Control1..1
TypeCodeableConcept
60. HospitalStayCz.pharmacotherapy.intendedUse
Definition

Indication intended use as: prevention or treatment Example: prophylaxis, treatment, diagnostic, anaesthesia.

ShortA.2.7.5.3 - Intended use
Control0..*
TypeCodeableConcept
62. HospitalStayCz.pharmacotherapy.productName
Definition

Brand name if biological medicinal product or when justified by the health professional (ref. Commission Directive 2012/52/EU)

ShortA.2.7.5.4 - Brand name
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
64. HospitalStayCz.pharmacotherapy.activeIngredient
Definition

Substance that alone or in combination with one or more other ingredients produces the intended activity of a medicinal product. Example: 'paracetamol'

ShortA.2.7.5.5 - Active ingredient list
Control0..*
TypeCodeableConcept
66. HospitalStayCz.pharmacotherapy.strength
Definition

The content of the active ingredient expressed quantifiably per dosage unit, per unit of volume or per unit of weight, according to the pharmaceutical dose form. Example: 500 mg per tablet

ShortA.2.7.5.6 - Strength
Control0..*
TypeRatio
68. HospitalStayCz.pharmacotherapy.doseForm
Definition

The form in which a pharmaceutical product is presented in the medicinal product package (e.g. tablet, syrup)

ShortA.2.7.5.7 - Pharmaceutical dose form
Control0..1
TypeCodeableConcept
70. HospitalStayCz.pharmacotherapy.dosageRegimen
Definition

Number of units per intake and frequency of intake over a specified duration of time. Example: 1 tablet every 24h, for 10 days

ShortA.2.7.5.8 - Dosage Regimen
Control0..*
TypeBase
72. HospitalStayCz.pharmacotherapy.route
Definition

Path by which the pharmaceutical product is taken into or makes contact with the body.

ShortA.2.7.5.9 - Route of administration
Control0..1
TypeCodeableConcept
74. HospitalStayCz.pharmacotherapy.period
Definition

The time interval when the patient was, or was not, given the medication.

ShortA.2.7.5.10 - Period of treatment
Control0..1
TypePeriod
76. HospitalStayCz.significantResults
Definition

Results of significant functional, diagnostic, and imaging examinations to ensure continuity of care, performed during hospitalisation. Results of examinations ordered but not yet delivered should be presented separately from results already delivered.

ShortA.2.7.6 - Significant Observation Results
Control0..*
TypeBase
78. HospitalStayCz.significantResults.date
Definition

Date and time of the observation

ShortA.2.7.6.1 - Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
80. HospitalStayCz.significantResults.status
Definition

Status of the observation (e.g. registered, preliminary, final)

ShortA.2.7.6.2 - Observation status
Control1..1
TypeCodeableConcept
82. HospitalStayCz.significantResults.description
Definition

Narrative representation of the observation result and findings.

ShortA.2.7.6.3 - Result description
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
84. HospitalStayCz.significantResults.details
Definition

Observation details include code that identifies observation, specification of the observed body structure or specimen, date and time of the specimen collection, observation method or protocol used and other aspects of the observation.

ShortA.2.7.6.4 - Observation details
Control1..1
TypeBase
86. HospitalStayCz.significantResults.result
Definition

Result of the observation including numeric and coded results of the measurement, details about how the tests were done to get the result values, information about reference ranges and result interpretation. Content of the observation result will vary according to the type of the observation.

ShortA.2.7.6.5 - Observation result
Control0..1
TypeBase
88. HospitalStayCz.significantResults.reporter
Definition

With certain observation results, e.g. there may also be an interpreter or a person responsible for validation.

ShortA.2.7.6.7 - Reporter
Control0..*
TypeBase
90. HospitalStayCz.synthesis
Definition

This section provides clinical synthesis (e.g. description of reasons and course of hospital stay) clustered by managed conditions, Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.

ShortA.2.7.7 - Synthesis
Control1..1
TypeBase
92. HospitalStayCz.synthesis.description
Definition

Summary description of the reason and course of hospitalisation for a specific problem.

ShortA.2.7.7.1 - Problem synthesis
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
94. HospitalStayCz.synthesis.reasoning
Definition

The clinical summary can be concluded with a clinical consideration (diff. diagnosis, explanation of context, etc.) for clinically complex conditions.

ShortA.2.7.7.2 - Clinical reasoning
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension