Generated Narrative: StructureDefinition HospitalDischargeReportSK Name Flags Card. Type Description & Constraints HospitalDischargeReportSK 0..* Base Hospital Discharge Report (SK) #xD; header 1..1 BackboneElement A.1-Report header data element [Mandatory] #xD; subjectIdentification 1..1 BackboneElement A.1.1-Identification of the patient/subject [Mandatory] #xD; given 1..* string A.1.1.1-Given name [Mandatory] #xD; family 1..* string A.1.1.2-Family name/surname [Mandatory] #xD; birthDate 1..1 dateTime A.1.1.3-Date of birth [Required] #xD; identifier 1..* Identifier A.1.1.4-Personal identifier [Required] #xD; nationality 0..* CodeableConcept A.1.1.5-Nationality [Required] #xD; gender 1..1 CodeableConcept A.1.1.6-Gender [Mandatory] #xD; language 0..0 #xD; subjectContact 0..1 BackboneElement A.1.2-Patient/subject related contact information [Required] #xD; contactPoint 0..* BackboneElement A.1.2.1-Patient address [] #xD; <a href="StructureDefinition-HospitalDischargeReportSK-definitions.html#HospitalDischargeReportSK.header.subjectContact.contactPoint.address" title="Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, ZIP code, 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 [Required] #xD; telecom 0..* ContactPoint A.1.2.1.2-Telecom [Required] #xD; preferredHP 0..* BackboneElement A.1.2.2-Preferred healthcare professional (HP) [Optional] #xD; identifier 0..* Identifier A.1.2.2.1-Identifier [Required] #xD; <a href="StructureDefinition-HospitalDischargeReportSK-definitions.html#HospitalDischargeReportSK.header.subjectContact.contactPoint.preferredHP.name" title="Name of the Health Professional that has been treating or taking responsibility for the patient.#xA;This element can be repeated if several medical problems for the patient require multiple contact information, with references from individual entries.#xA;[the structure of the name will be the same as for the patient (given name, family name / surname)]">name 1..1 HumanName A.1.2.2.2-Name of the HP [Required] #xD; role 0..* CodeableConcept A.1.2.2.3-Role of the HP [Required] #xD; organization 0..1 BackboneElement A.1.2.2.4-HP Organisation [Required] #xD; <a href="StructureDefinition-HospitalDischargeReportSK-definitions.html#HospitalDischargeReportSK.header.subjectContact.contactPoint.preferredHP.address" title="Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, ZIP code, 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 [Optional] #xD; telecom 0..* ContactPoint A.1.2.2.6-Telecom [Required] #xD; person 0..* BackboneElement A.1.2.3-Contact person/ legal guardian [Required] #xD; role 0..0 #xD; relationship 0..0 #xD; identifier 0..0 #xD; given 1..* string A.1.2.3.4-Given name [Mandatory] #xD; name 1..* string A.1.2.3.5-Family name/surname [Mandatory] #xD; <span style="text-decoration:line-through" title="Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, ZIP code, 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..0 #xD; telecom 0..0 #xD; payer 0..1 BackboneElement A.1.3-Health insurance and payment information [Required] #xD; insuranceCode 0..1 Identifier A.1.3.1-Health insurance code [Mandatory] #xD; insuranceName 0..1 string A.1.3.2-Health insurance name [Required] #xD; insuranceNumber 0..1 Identifier A.1.3.3-Health insurance number [Mandatory] #xD; informationRecipient 0..0 #xD; author 1..* BackboneElement A.1.5-Author (by whom the Hospital discharge report was authored) [Mandatory] #xD; identifier 1..* Identifier A.1.5.1-Author identifier [Mandatory] #xD; name 1..1 HumanName A.1.5.2-Author name [Mandatory] #xD; organizationID 0..* Identifier A.1.5.3-Author organization ID [Required] #xD; organization 1..1 BackboneElement A.1.5.4-Author organization [Mandatory] #xD; dateTime 1..1 dateTime A.1.5.5-DateTime [Mandatory] #xD; attester 0..* BackboneElement A.1.6-Attester [Required] #xD; identifier 0..0 #xD; name 1..1 HumanName A.1.6.2-Attester name [Mandatory] #xD; organizationID 0..0 #xD; organization 0..0 #xD; dateTime 0..0 #xD; legalAuthenticator 0..1 BackboneElement A.1.7-Legal authenticator [Required] #xD; identifier 0..0 #xD; name 1..1 HumanName A.1.7.2-Legal authenticator name [Mandatory] #xD; organizationID 0..0 #xD; organization 0..0 #xD; dateTime 0..0 #xD; documentMetadata 0..0 #xD; digitalSignature 0..0 #xD; body 1..1 BackboneElement A.2-Body (missing elementy ?) [Mandatory] #xD; advanceDirectives 0..1 BackboneElement A.2.1-Advance directives [Required] #xD; emergencyInfos 1..1 BackboneElement A.2.2-Emergency information [Mandatory] #xD; encounter 1..1 BackboneElement A.2.3-Encounter [Mandatory] #xD; admissionEvaluation 0..1 BackboneElement A.2.4-Admission evaluation - Admission status should be reported exceptionally only if it is relevant to ensure continuity of care. [Optional] #xD; patientHistory 0..1 BackboneElement A.2.6-Patient history [Optional] #xD; hospitalStay 1..1 BackboneElement A.2.7-Hospital stay [Mandatory] #xD; dischargeDetails 1..1 BackboneElement A.2.8-Discharge details [Mandatory] #xD; recommendations 0..1 BackboneElement A.2.9-Recommendations [Required] #xD; Documentation for this format
Hospital Discharge Report SK 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-Report header data element [Mandatory]
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 [Mandatory]
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.
The date of birth of the patient [ISO TS 22220]. As age of the patient might be important for correct interpretation of the test result values, complete date of birth should be provided.
An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for 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.
A.1.1.7-Language communication [Optional]
Patient communication language. Multiple communication languages might be provided.
A.1.2-Patient/subject related contact information [Required]
Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, ZIP code, 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 to a person. Multiple telecommunication addresses might be provided.
A.1.2.2-Preferred healthcare professional (HP) [Optional]
- 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 healthcare professional that is unique within a defined scope. Example: National healthcare professional ID. Multiple identifiers could be provided.
Name of the Health Professional that has been treating or taking responsibility for the patient. This element can be repeated if several medical problems for the patient require multiple contact information, with references from individual entries. [the structure of the name will be the same as for the patient (given name, family name / surname)]
ISCO or SNOMED CT specialty - to be discussed
A.1.2.3-Contact person/ legal guardian [Required]
A.1.2.3.1-Role of that person [Required]
Role of the contact person: legal guardian, next of kin, other person to contact.
Relationship type with the patient (e.g. father, wife, daughter)
An identifier of the healthcare professional that is unique within a defined scope. Example: National personal ID, passport number etc. Multiple identifiers could be provided.
The first name of the contact person/guardian (example: Peter). This field can contain more than one element.
A.1.2.3.5-Family name/surname [Mandatory]
This field can contain more than one element. Example: Espa�ol Smith
Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, ZIP code, 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.
A.1.3-Health insurance and payment information [Required]
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.
A.1.3.1-Health insurance code [Mandatory]
Unique health insurance company identification code.
A.1.3.2-Health insurance name [Required]
Full, official name of the healthcare insurance provider.
A.1.3.3-Health insurance number [Mandatory]
Number or code under which the insured person is registered at the insurance provider.
intended recipient or recipients of the report, additional recipients might be identified by the ordering party, e.g. GP, other specialist
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 license or registration number. In case when recipient is not a health professional, e.g. patient, appropriate personal identifier should be used.
A.1.4.3-Recipient organization ID [Required]
The healthcare provider organization identifier if known. Identifier that is unique within a defined scope. Example: National healthcare provider ID. Multiple identifiers could be provided.
A.1.4.4-Recipient organization [Required]
The healthcare provider organization information.
A.1.5-Author (by whom the Hospital discharge report was authored) [Mandatory]
Author (by whom the Hospital discharge report was authored)
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 license or registration number.
A.1.5.3-Author organization ID [Required]
Date and time of the last modification of the document by its Author.
A.1.6.3-Attester organization ID [Required]
A.1.6.4-Attester organization [Mandatory]
A.1.6.5-Approval date and time [Mandatory]
Date and time of the approval of the document by Attester.
The person taking responsibility for the medical content of the document
A.1.7.1-Legal authenticator identifier [Mandatory]
A.1.7.2-Legal authenticator name [Mandatory]
-Legal authenticator organization�ID [Required]
The healthcare provider organization identifier if known. Identifier that is unique within a defined scope.�Example: National healthcare provider ID. Multiple identifiers could be provided.��
A.1.7.3-Legal authenticator organization [Mandatory]
A.1.7.4-Authentication date and time [Mandatory]
Date and time when the document was authorized.
A coded type of the document. Fixed value 'Hospital dicharge summary'
The status of the Hospital discharge report. E.g., preliminary, final.
A.1.8.4-Report date and time [Mandatory]
Date and time of the result report creation.
Document title, e.g. 'Hospital discharge report'
Organisation that is in charge of maintaining the report
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-Body (missing elementy ?) [Mandatory]
A.2.4-Admission evaluation - Admission status should be reported exceptionally only if it is relevant to ensure continuity of care. [Optional]
structured information should be provided, however if not available, at least a summary note should be present