Generated Narrative: StructureDefinition HDREncounter Name Flags Card. Type Description & Constraints HDREncounter 0..* Base A.2.3 - Encounter (eHN) #xD; type 1..1 CodeableConcept A.2.3.1 - Encounter type #xD; note 0..1 string A.2.3.2 - Encounter note #xD; admission 1..1 BackboneElement A.2.3.3 - Admission #xD; urgency 0..1 CodeableConcept A.2.3.3.1 - Admission urgency #xD; date 1..1 dateTime A.2.3.3.2 - Admission date #xD; admitter 0..1 BackboneElement Admitting professional #xD; identifier 0..1 Identifier A.2.3.3.3 - Admitting professional ID #xD; name 0..1 HumanName A.2.3.3.4 - Admitting professional name #xD; organizationID 0..1 Identifier A.2.3.3.5 - Admitting organisation ID #xD; organization 0..1 BackboneElement A.2.3.3.6 - Admitting organisation #xD; source 0..1 CodeableConcept A.2.3.3.7 - Admit Source #xD; referringHP 0..1 BackboneElement Referring professional #xD; identifier 0..1 Identifier A.2.3.3.8 - Referring professional ID #xD; name 0..1 HumanName A.2.3.3.9 - Referring professional name #xD; organizationID 0..1 Identifier A.2.3.3.10 - Referring organisation ID #xD; organization 0..1 BackboneElement A.2.3.3.11 - Referring organisation #xD; admissionReason 1..1 BackboneElement A.2.3.4 - Admission reason #xD; code 0..* CodeableConcept A.2.3.4.1 - Admission reason #xD; comment 0..1 string A.2.3.4.2 - Admission reason comment #xD; <a href="StructureDefinition-HDREncounter-definitions.html#HDREncounter.admissionReason.legalStatus" title="Legal status/situation at admission. The legal status indicates the basis on which the patient is staying in a healthcare organisation. This can be either voluntary or involuntary, however the legal status is always determined by a court. A patient can also receive healthcare based on a forensic status. (voluntary, involuntary, admission by legal authority).">legalStatus 0..1 CodeableConcept A.2.3.4.3 - Admission legal status #xD; discharge 1..1 BackboneElement A.2.3.5 - Discharge #xD; date 1..1 dateTime A.2.3.5.1 - Discharge date #xD; destinationType 0..1 CodeableConcept A.2.3.5.2 - Discharge destination type #xD; destinationLocation 0..1 CodeableConcept A.2.3.5.3 - Destination location #xD; location 0..* BackboneElement A.2.3.6 - Location - All locations/departments where the patient stayed (was boarded) within the hospital. #xD; period 1..1 Period A.2.3.6.1 - Period #xD; organization 1..1 BackboneElement Organization #xD; identifier 0..1 Identifier A.2.3.6.2 - Organisation Part ID #xD; name 1..1 string A.2.3.6.3 - Organisation Part Name #xD; details 0..1 BackboneElement A.2.3.6.4 - Organisation Part Details #xD; Documentation for this format
Hospital Discharge Report - Encounter - A.2.3 eHN 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
The type of the encounter whether inpatient or short stay encounter.
A narrative description of the encounter course.
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
Admission type, either emergency or planned
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.
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.
The healthcare provider organisation information.
From where the patient was admitted (e.g. physician referral, transfer).
Reason or reasons for admission, e.g. Problem, procedure or finding.
ICD-10* SNOMED CT Orphacode if rare disease is diagnosed
Explanation of the reason for the encounter.
Legal status/situation at admission. The legal status indicates the basis on which the patient is staying in a healthcare organisation. This can be either voluntary or involuntary, however the legal status is always determined by a court. A patient can also receive healthcare based on a forensic status. (voluntary, involuntary, admission by legal authority).
Type of location to which the patient will go after the encounter. E.g. home, hospital, nursing home, left against medical advice etc.
The location/organisation to which the patient will go after the encounter. Name, address and telecommunication contact.
A.2.3.6 - Location - All locations/departments where the patient stayed (was boarded) within the hospital.
Location - All locations/departments where the patient stayed (was boarded) within the hospital.
Time period during which the patient was present at the location
Organization or organization part (hospital department) where the patient was present.
Full name of the organisation part, e.g. Name of the department
Address, contact names and contact details, specialty of the organisation part.