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: SubjectHdrEhnCz - Detailed Descriptions

Draft as of 2025-08-23

Definitions for the SubjectCz logical model.

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

0. SubjectCz
Definition

Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

ShortA.1.1 - Identification and A.1.2 - related contact information of the Patient/subject
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. SubjectCz.subjectIdentification
Definition

Identification of the patient/subject

ShortA.1.1 - Identification of the patient/subject
Control1..1
TypeBase
4. SubjectCz.subjectIdentification.given
Definition

The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.

ShortA.1.1.1 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. SubjectCz.subjectIdentification.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortA.1.1.2 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. SubjectCz.subjectIdentification.birthDate
Definition

Complete date, following the ISO 8601.

ShortA.1.1.3 - Date of birth
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. SubjectCz.subjectIdentification.identifier
Definition

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

ShortA.1.1.4 - National healthcare patient ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..*
TypeIdentifier
12. SubjectCz.subjectIdentification.citizenship
Definition

Citizenship of the patient.

ShortA.1.1.5 - Citizenship
Control0..*
TypeCodeableConcept
14. SubjectCz.subjectIdentification.gender
Definition

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

ShortA.1.1.6 - Gender
Control1..1
TypeCodeableConcept
16. SubjectCz.subjectIdentification.communication
Definition

A language which may be used to communicate with the patient about his or her health

ShortA.1.1.7 - Communication
Control0..1
TypeCodeableConcept
18. SubjectCz.subjectContact
Definition

Patient/subject related contact information

ShortA.1.2 - Patient/subject related contact information
Control0..1
TypeBase
20. SubjectCz.subjectContact.personalContact
Definition

Patient address

ShortA.1.2.1 - Patient address
Control0..1
TypeBase
22. SubjectCz.subjectContact.personalContact.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.2 - Patient contact
Control0..*
TypeContactPoint
24. SubjectCz.subjectContact.preferredHP
Definition

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

ShortA.1.2.3 - Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).
Control0..*
TypeBase
26. SubjectCz.subjectContact.preferredHP.identifier
Definition

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

ShortA.1.2.3.1 - Identifier of the HP
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
28. SubjectCz.subjectContact.preferredHP.name
Definition

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

ShortA.1.2.3.2 - Name of the HP
Control1..1
TypeHumanName
30. SubjectCz.subjectContact.preferredHP.role
Definition

Health professional role. Multiple roles could be provided.

ShortA.1.2.3.3 - Role of the HP
Control0..*
TypeCodeableConcept
32. SubjectCz.subjectContact.preferredHP.organization
Definition

Health professional organisation

ShortA.1.2.3.4 - HP Organisation
Control0..1
TypeBase
34. SubjectCz.subjectContact.preferredHP.address
Definition

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.3.5 - Address
Control0..1
TypeAddress
36. SubjectCz.subjectContact.preferredHP.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.3.6 - Telecom
Control0..*
TypeContactPoint
38. SubjectCz.subjectContact.contactPerson
Definition

Contact person/ legal guardian (multiple contacts could be provided)

ShortA.1.2.4 - Contact person/ legal guardian (multiple contacts could be provided)
Control0..*
TypeBase
40. SubjectCz.subjectContact.contactPerson.role
Definition

Role of the contact person: legal guardian, next of kin, other person to contact.

ShortA.1.2.4.1 - Role of that person
Control0..*
TypeCodeableConcept
42. SubjectCz.subjectContact.contactPerson.relationship
Definition

Relationship type with the patient (e.g. father, wife, daughter)

ShortA.1.2.4.2 - Relationship level
Control0..1
TypeCodeableConcept
44. SubjectCz.subjectContact.contactPerson.given
Definition

Given name of the contact person/guardian . This field can contain more than one element.

ShortA.1.2.4.4 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
46. SubjectCz.subjectContact.contactPerson.family
Definition

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

ShortA.1.2.4.5 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
48. SubjectCz.subjectContact.contactPerson.address
Definition

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.4.6 - Address
Control0..*
TypeAddress
50. SubjectCz.subjectContact.contactPerson.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.4.7 - Telecom
Control0..*
TypeContactPoint
52. SubjectCz.subjectContact.contactPerson.organization
Definition

Contact person organisation information.

ShortA.1.2.4.8 - Contact person organisation
Control0..1
TypeBase

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

0. SubjectCz
Definition

Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

ShortA.1.1 - Identification and A.1.2 - related contact information of the Patient/subject
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. SubjectCz.subjectIdentification
Definition

Identification of the patient/subject

ShortA.1.1 - Identification of the patient/subject
Control1..1
TypeBase
4. SubjectCz.subjectIdentification.given
Definition

The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.

ShortA.1.1.1 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. SubjectCz.subjectIdentification.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortA.1.1.2 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. SubjectCz.subjectIdentification.birthDate
Definition

Complete date, following the ISO 8601.

ShortA.1.1.3 - Date of birth
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. SubjectCz.subjectIdentification.identifier
Definition

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

ShortA.1.1.4 - National healthcare patient ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..*
TypeIdentifier
12. SubjectCz.subjectIdentification.citizenship
Definition

Citizenship of the patient.

ShortA.1.1.5 - Citizenship
Control0..*
TypeCodeableConcept
14. SubjectCz.subjectIdentification.gender
Definition

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

ShortA.1.1.6 - Gender
Control1..1
TypeCodeableConcept
16. SubjectCz.subjectIdentification.communication
Definition

A language which may be used to communicate with the patient about his or her health

ShortA.1.1.7 - Communication
Control0..1
TypeCodeableConcept
18. SubjectCz.subjectContact
Definition

Patient/subject related contact information

ShortA.1.2 - Patient/subject related contact information
Control0..1
TypeBase
20. SubjectCz.subjectContact.personalContact
Definition

Patient address

ShortA.1.2.1 - Patient address
Control0..1
TypeBase
22. SubjectCz.subjectContact.personalContact.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.2 - Patient contact
Control0..*
TypeContactPoint
24. SubjectCz.subjectContact.preferredHP
Definition

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

ShortA.1.2.3 - Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).
Control0..*
TypeBase
26. SubjectCz.subjectContact.preferredHP.identifier
Definition

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

ShortA.1.2.3.1 - Identifier of the HP
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
28. SubjectCz.subjectContact.preferredHP.name
Definition

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

ShortA.1.2.3.2 - Name of the HP
Control1..1
TypeHumanName
30. SubjectCz.subjectContact.preferredHP.role
Definition

Health professional role. Multiple roles could be provided.

ShortA.1.2.3.3 - Role of the HP
Control0..*
TypeCodeableConcept
32. SubjectCz.subjectContact.preferredHP.organization
Definition

Health professional organisation

ShortA.1.2.3.4 - HP Organisation
Control0..1
TypeBase
34. SubjectCz.subjectContact.preferredHP.address
Definition

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.3.5 - Address
Control0..1
TypeAddress
36. SubjectCz.subjectContact.preferredHP.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.3.6 - Telecom
Control0..*
TypeContactPoint
38. SubjectCz.subjectContact.contactPerson
Definition

Contact person/ legal guardian (multiple contacts could be provided)

ShortA.1.2.4 - Contact person/ legal guardian (multiple contacts could be provided)
Control0..*
TypeBase
40. SubjectCz.subjectContact.contactPerson.role
Definition

Role of the contact person: legal guardian, next of kin, other person to contact.

ShortA.1.2.4.1 - Role of that person
Control0..*
TypeCodeableConcept
42. SubjectCz.subjectContact.contactPerson.relationship
Definition

Relationship type with the patient (e.g. father, wife, daughter)

ShortA.1.2.4.2 - Relationship level
Control0..1
TypeCodeableConcept
44. SubjectCz.subjectContact.contactPerson.given
Definition

Given name of the contact person/guardian . This field can contain more than one element.

ShortA.1.2.4.4 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
46. SubjectCz.subjectContact.contactPerson.family
Definition

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

ShortA.1.2.4.5 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
48. SubjectCz.subjectContact.contactPerson.address
Definition

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.4.6 - Address
Control0..*
TypeAddress
50. SubjectCz.subjectContact.contactPerson.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.4.7 - Telecom
Control0..*
TypeContactPoint
52. SubjectCz.subjectContact.contactPerson.organization
Definition

Contact person organisation information.

ShortA.1.2.4.8 - Contact person organisation
Control0..1
TypeBase

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

0. SubjectCz
Definition

Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

ShortA.1.1 - Identification and A.1.2 - related contact information of the Patient/subject
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. SubjectCz.subjectIdentification
Definition

Identification of the patient/subject

ShortA.1.1 - Identification of the patient/subject
Control1..1
TypeBase
4. SubjectCz.subjectIdentification.given
Definition

The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.

ShortA.1.1.1 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. SubjectCz.subjectIdentification.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortA.1.1.2 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. SubjectCz.subjectIdentification.birthDate
Definition

Complete date, following the ISO 8601.

ShortA.1.1.3 - Date of birth
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. SubjectCz.subjectIdentification.identifier
Definition

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

ShortA.1.1.4 - National healthcare patient ID
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..*
TypeIdentifier
12. SubjectCz.subjectIdentification.citizenship
Definition

Citizenship of the patient.

ShortA.1.1.5 - Citizenship
Control0..*
TypeCodeableConcept
14. SubjectCz.subjectIdentification.gender
Definition

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

ShortA.1.1.6 - Gender
Control1..1
TypeCodeableConcept
16. SubjectCz.subjectIdentification.communication
Definition

A language which may be used to communicate with the patient about his or her health

ShortA.1.1.7 - Communication
Control0..1
TypeCodeableConcept
18. SubjectCz.subjectContact
Definition

Patient/subject related contact information

ShortA.1.2 - Patient/subject related contact information
Control0..1
TypeBase
20. SubjectCz.subjectContact.personalContact
Definition

Patient address

ShortA.1.2.1 - Patient address
Control0..1
TypeBase
22. SubjectCz.subjectContact.personalContact.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.2 - Patient contact
Control0..*
TypeContactPoint
24. SubjectCz.subjectContact.preferredHP
Definition

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

ShortA.1.2.3 - Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).
Control0..*
TypeBase
26. SubjectCz.subjectContact.preferredHP.identifier
Definition

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

ShortA.1.2.3.1 - Identifier of the HP
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
28. SubjectCz.subjectContact.preferredHP.name
Definition

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

ShortA.1.2.3.2 - Name of the HP
Control1..1
TypeHumanName
30. SubjectCz.subjectContact.preferredHP.role
Definition

Health professional role. Multiple roles could be provided.

ShortA.1.2.3.3 - Role of the HP
Control0..*
TypeCodeableConcept
32. SubjectCz.subjectContact.preferredHP.organization
Definition

Health professional organisation

ShortA.1.2.3.4 - HP Organisation
Control0..1
TypeBase
34. SubjectCz.subjectContact.preferredHP.address
Definition

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.3.5 - Address
Control0..1
TypeAddress
36. SubjectCz.subjectContact.preferredHP.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.3.6 - Telecom
Control0..*
TypeContactPoint
38. SubjectCz.subjectContact.contactPerson
Definition

Contact person/ legal guardian (multiple contacts could be provided)

ShortA.1.2.4 - Contact person/ legal guardian (multiple contacts could be provided)
Control0..*
TypeBase
40. SubjectCz.subjectContact.contactPerson.role
Definition

Role of the contact person: legal guardian, next of kin, other person to contact.

ShortA.1.2.4.1 - Role of that person
Control0..*
TypeCodeableConcept
42. SubjectCz.subjectContact.contactPerson.relationship
Definition

Relationship type with the patient (e.g. father, wife, daughter)

ShortA.1.2.4.2 - Relationship level
Control0..1
TypeCodeableConcept
44. SubjectCz.subjectContact.contactPerson.given
Definition

Given name of the contact person/guardian . This field can contain more than one element.

ShortA.1.2.4.4 - Given name
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
46. SubjectCz.subjectContact.contactPerson.family
Definition

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

ShortA.1.2.4.5 - Family name/surname
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
48. SubjectCz.subjectContact.contactPerson.address
Definition

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

ShortA.1.2.4.6 - Address
Control0..*
TypeAddress
50. SubjectCz.subjectContact.contactPerson.telecom
Definition

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

ShortA.1.2.4.7 - Telecom
Control0..*
TypeContactPoint
52. SubjectCz.subjectContact.contactPerson.organization
Definition

Contact person organisation information.

ShortA.1.2.4.8 - Contact person organisation
Control0..1
TypeBase