XpanDH Hospital Discharge Report
0.1.0 - ci-build
150
XpanDH Hospital Discharge Report, published by XpanDH Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/xpandh-hdr/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.eu/fhir/ig/xpandh/hdr/ValueSet/hdr-encounterClass-xpandh-vs | Version: 0.1.0 | |||
Standards status: Draft | Maturity Level: 1 | Computable Name: HdrEncounterClassXpandhVS | ||
Copyright/Legal: Used by permission of the XpanDH project, all rights reserved Creative Commons License |
Hospital Discharge Report Encounter Class specifies a general class of inpatient encounter as being accute, nonaccute, emergency, short stay …
References
Generated Narrative: ValueSet hdr-encounterClass-xpandh-vs
http://terminology.hl7.org/CodeSystem/v3-ActCode
Code | Display | Definition |
IMP | inpatient encounter | A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service. |
ACUTE | inpatient acute | An acute inpatient encounter. |
NONAC | inpatient non-acute | Any category of inpatient encounter except 'acute' |
OBSENC | observation encounter | An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours. |
SS | short stay | An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours. |
Generated Narrative: ValueSet
Expansion based on codesystem ActCode v9.0.0 (CodeSystem)
This value set contains 5 concepts
Code | System | Display | Definition |
IMP | http://terminology.hl7.org/CodeSystem/v3-ActCode | inpatient encounter | A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service. |
ACUTE | http://terminology.hl7.org/CodeSystem/v3-ActCode | inpatient acute | An acute inpatient encounter. |
NONAC | http://terminology.hl7.org/CodeSystem/v3-ActCode | inpatient non-acute | Any category of inpatient encounter except 'acute' |
OBSENC | http://terminology.hl7.org/CodeSystem/v3-ActCode | observation encounter | An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours. |
SS | http://terminology.hl7.org/CodeSystem/v3-ActCode | short stay | An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |