Generated Narrative: StructureDefinition HospitalDischargeReport Name Flags Card. Type Description & Constraints HospitalDischargeReport 0..* Base A - Hospital Discharge Report (eHN) #xD; header 1..1 BackboneElement A.1 - Hospital Discharge Report header data element #xD; subjectIdentification 1..1 BackboneElement A.1.1 - Identification of the patient/subject #xD; given 1..* string A.1.1.1 - Given name #xD; family 1..* string A.1.1.2 - Family name/surname #xD; birthDate 1..1 dateTime A.1.1.3 - Date of birth #xD; identifier 1..* Identifier A.1.1.4 - National healthcare patient ID #xD; nationality 0..* CodeableConcept A.1.1.5 - Nationality #xD; gender 1..1 CodeableConcept A.1.1.6 - Gender #xD; countryOfAffiliation 0..1 CodeableConcept A.1.1.7 - Country of affiliation #xD; subjectContact 0..1 BackboneElement A.1.2 - Patient/subject related contact information #xD; personalContact 0..1 BackboneElement A.1.2.1 - Patient address #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.subjectContact.personalContact.address" title="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.">address 0..* Address A.1.2.1.1 - Address #xD; telecom 0..* ContactPoint A.1.2.1.2 - Telecom #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.subjectContact.preferredHP" title="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).">preferredHP 0..* BackboneElement A.1.2.2 - 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). #xD; identifier 0..* Identifier A.1.2.2.1 - Identifier of the HP #xD; name 1..1 HumanName A.1.2.2.2 - Name of the HP #xD; role 0..* CodeableConcept A.1.2.2.3 - Role of the HP #xD; organization 0..1 BackboneElement A.1.2.2.4 - HP Organisation #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.subjectContact.preferredHP.address" title="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.">address 0..1 Address A.1.2.2.5 - Address #xD; telecom 0..* ContactPoint A.1.2.2.6 - Telecom #xD; contactPerson 0..* BackboneElement A.1.2.3 - Contact person/ legal guardian (multiple contacts could be provided) #xD; role 0..* CodeableConcept A.1.2.3.1 - Role of that person #xD; relationship 0..1 CodeableConcept A.1.2.3.2 - Relationship level #xD; given 1..* string A.1.2.3.4 - Given name #xD; family 1..* string A.1.2.3.5 - Family name/surname #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.subjectContact.contactPerson.address" title="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.">address 0..* Address A.1.2.3.6 - Address #xD; telecom 0..* ContactPoint A.1.2.3.7 - Telecom #xD; organization 0..1 BackboneElement A.1.2.3.8 - Contact person organisation #xD; payer 0..1 BackboneElement A.1.3 - Health insurance and payment information - Health insurance information is not always required, however, in some jurisdictions, the insurance number is also used as the patient identifier. It is necessary not just for identification but also forms access to funding for care. #xD; insuranceCode 0..1 Identifier A.1.3.1 - Health insurance code #xD; insuranceName 0..1 string A.1.3.2 - Health insurance name #xD; insuranceNumber 0..1 Identifier A.1.3.3 - Health insurance number #xD; informationRecipient 0..* BackboneElement A.1.4 - Information recipient - (intended recipient or recipients of the report), if applicable #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.informationRecipient.identifier" title="The health professional or patient identifier. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the licence or registration number. In case when the recipient is not a health professional, e.g. patient, appropriate personal identifier could be used.">identifier 0..1 Identifier A.1.4.1 - Recipient identifier #xD; name 0..1 HumanName A.1.4.2 - Recipient name #xD; organizationID 0..* Identifier A.1.4.3 - Recipient organisation ID #xD; organization 0..1 BackboneElement A.1.4.4 - Recipient organisation #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.informationRecipient.address" title="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.">address 0..1 Address A.1.4.5 - Address #xD; country 1..1 CodeableConcept A.1.4.6 - Country #xD; telecom 0..* ContactPoint A.1.4.7 - Telecom #xD; author 1..* BackboneElement A.1.5 - Author (by whom the Hospital discharge report was/were authored). Multiple authors could be provided. #xD; <a href="StructureDefinition-HospitalDischargeReport-definitions.html#HospitalDischargeReport.header.author.identifier" title="The health professional identifier that will allow addressing recipients within a national or international data exchange infrastructure, such as the licence or registration number. In case when the recipient is not a health professional, e.g. patient, appropriate personal identifier should be used.">identifier 1..* Identifier A.1.5.1 - Author identifier #xD; name 1..1 HumanName A.1.5.2 - Author name #xD; organizationID 0..* Identifier A.1.5.3 - Author organisation ID #xD; organization 1..1 BackboneElement A.1.5.4 - Author organisation #xD; dateTime 1..1 dateTime A.1.5.5 - Date Time #xD; attester 0..* BackboneElement A.1.6 - Attester (multiple attesters could be provided) #xD; identifier 1..* Identifier A.1.6.1 - Attester identifier #xD; name 1..1 HumanName A.1.6.2 - Attester name #xD; organizationID 0..* Identifier A.1.6.3 - Attester organisation ID #xD; organization 1..1 BackboneElement A.1.6.4 - Attester organisation #xD; dateTime 1..1 dateTime A.1.6.5 - Approval date and time #xD; legalAuthenticator 0..1 BackboneElement A.1.7 - Legal authenticator (The person taking responsibility for the medical content of the document) #xD; identifier 1..* Identifier A.1.7.1 - Legal authenticator identifier #xD; name 1..1 HumanName A.1.7.2 - Legal authenticator name #xD; organizationID 0..* Identifier A.1.7.3 - Legal authenticator organisation ID #xD; organization 1..1 BackboneElement A.1.7.4 - Legal authenticator organisation #xD; dateTime 1..1 dateTime A.1.7.5 - Authentication date and time #xD; documentMetadata 1..1 BackboneElement A.1.8 - Document metadata #xD; identifier 1..1 Identifier A.1.8.1 - Document ID #xD; type 1..1 CodeableConcept A.1.8.2 - Document type #xD; status 1..1 CodeableConcept A.1.8.3 - Document status #xD; dateTime 1..1 dateTime A.1.8.4 - Report date and time #xD; title 1..1 string A.1.8.5 - Document title #xD; custodian 1..1 BackboneElement A.1.8.6 - Report custodian #xD; confidentiality 1..1 CodeableConcept A.1.8.7 - Confidentiality #xD; language 1..1 CodeableConcept A.1.8.8 - Language #xD; version 0..1 string A.1.8.9 - Version #xD; body 1..1 BackboneElement A.2 - Hospital Discharge Report body data element #xD; presentedForm 0..1 BackboneElement A.2.0 - Hospital Discharge Report in its narrative form #xD; advanceDirectives 0..1 HDRAdvanceDirectives A.2.1 - Advance directives #xD; alerts 1..1 HDRAlerts A.2.2 - Alerts #xD; encounter 1..1 HDREncounter A.2.3 - Encounter [Mandatory] #xD; admissionEvaluation 0..1 HDRAdmissionEvaluation A.2.4 - Admission evaluation - Admission status should be reported exceptionally only if it is relevant to ensure continuity of care. #xD; patientHistory 0..1 HDRPatientHistory A.2.6 - Patient history #xD; hospitalStay 1..1 HDRHospitalStay A.2.7 - Course of hospitalisation (Hospital stay) #xD; dischargeDetails 1..1 HDRDischargeDetails A.2.8 - Discharge details #xD; recommendations 0..1 HDRRecommendations A.2.9 - Care plan and other recommendations after discharge. #xD; Documentation for this format
Hospital Discharge Report Maturity Level: 0 Draft
Used by permission of the XpanDH project, all rights reserved Creative Commons License
Hospital Discharge Report model to FHIR R4 Map
A.1 - Hospital Discharge Report header data element
Hospital Discharge Report header data element
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
A.1.1 - Identification of the patient/subject
The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.
The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.
A.1.1.4 - National healthcare patient ID
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
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.
A.1.2 - Patient/subject related contact information
Patient/subject related contact information
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.
Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
A.1.2.2 - 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).
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).
An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
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)]
Health professional role. Multiple roles could be provided.
A.1.2.3 - Contact person/ legal guardian (multiple contacts could be provided)
Contact person/ legal guardian (multiple contacts could be provided)
Role of the contact person: legal guardian, next of kin, other person to contact.
Relationship type with the patient (e.g. father, wife, daughter)
Given name of the contact person/guardian . This field can contain more than one element.
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)]..
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.
Contact person organisation information.
A.1.3 - Health insurance and payment information - Health insurance information is not always required, however, in some jurisdictions, the insurance number is also used as the patient identifier. It is necessary not just for identification but also forms access to funding for care.
Health insurance and payment information - Health insurance information is not always required, however, in some jurisdictions, the insurance number is also used as the patient identifier. It is necessary not just for identification but also forms access to funding for care.
Unique health insurance company identification code.
Full, official name of the healthcare insurance provider.
Number or code under which the insured person is registered at the insurance provider.
A.1.4 - Information recipient - (intended recipient or recipients of the report), if applicable
Information recipient - (intended recipient or recipients of the report), if applicable
The health professional or patient identifier. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the licence or registration number. In case when the recipient is not a health professional, e.g. patient, appropriate personal identifier could be used.
Person name [the structure of the name will be the same as for the patient (given name, family name / surname)].
The healthcare provider organisation identifier. Identifier that is unique within a defined scope. Example: National healthcare provider ID. Multiple identifiers could be provided.
The healthcare provider organisation information.
Country of the intended recipient as part of the address.
Telecommunication contact information (addresses) associated to a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
A.1.5 - Author (by whom the Hospital discharge report was/were authored). Multiple authors could be provided.
Author (by whom the Hospital discharge report was/were authored). Multiple authors could be provided.
The health professional identifier that will allow addressing recipients within a national or international data exchange infrastructure, such as the licence or registration number. In case when the recipient is not a health professional, e.g. patient, appropriate personal identifier should be used.
Date and time of the last modification of the document by its Author.
A.1.6 - Attester (multiple attesters could be provided)
Attester (multiple attesters could be provided)
The health professional identification number. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the licence or registration number.
Date and time of the approval of the document by Attester.
A.1.7 - Legal authenticator (The person taking responsibility for the medical content of the document)
Legal authenticator (The person taking responsibility for the medical content of the document)
A.1.7.1 - Legal authenticator identifier
The health professional identification number. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the licence or registration number. Multiple identifiers could be provided.
A.1.7.3 - Legal authenticator organisation ID
A.1.7.4 - Legal authenticator organisation
Date and time when the document was authorised.
Identifies the type of document at hand, e.g. Hospital discharge report.
The status of the Hospital discharge report. E.g., preliminary, final.
Date and time of the Hospital discharge report creation.
Document title, fix value "Hospital discharge report".
Organisation that is in charge of maintaining the report [this element will include organisation ID, name, address etc., as other elements describing organisations].
Level of confidentiality of the document. Implicit value is normal.
Language in which the document is written. Language is expressed by the ISO language code.
A.2 - Hospital Discharge Report body data element
Hospital Discharge Report body data element
A.2.0 - Hospital Discharge Report in its narrative form
Hospital Discharge Report in its narrative form
A.2.4 - Admission evaluation - Admission status should be reported exceptionally only if it is relevant to ensure continuity of care.
Admission evaluation - Admission status should be reported exceptionally only if it is relevant to ensure continuity of care.
Patient history (might include information about provenance of the information)
A.2.7 - Course of hospitalisation (Hospital stay)
Course of hospitalisation (Hospital stay)
Discharge details (structured information should be provided, however if not available, at least a summary note should be present).
A.2.9 - Care plan and other recommendations after discharge.
Care plan and other recommendations after discharge.