5.9 Encounter リソース
Home ＞ Administrative ＞ Encounter [encounter]
Resource Encounter - Content5.9
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
The resource name as it appears in a RESTful URL is [root]/encounter/
A patient encounter is further characterized by the setting in which it takes place, amongst them are ambulatory, emergency, home health, inpatient and virtual encounters. An Encounter encompasses the lifecycle from pre-admission, the actual encounter (for ambulatory encounters), and admission, stay and discharge (for inpatient encounters). During the encounter the patient may move from practitioner to practitioner and location to location.
Because of the broad scope of Encounter, not all elements will be relevant in all settings. For this reason, admission/discharge related information is kept in a separate Hospitalization component within Encounter. The class element is used to distinguish between these settings, which will guide further validation and application of business rules.
There is also substantial variance from organization to organization (and between jurisdictions and countries) on which business events translate to the start of a new Encounter, or what level of aggregation is used for Encounter. I.e. Each single visit of a practitioner during a hospitalization may lead to a new instance of Encounter, but depending on use and systems involved, it may well be that this is aggregated to a single instance for the whole hospitalization. Even more aggregation may occur where jurisdictions introduce groups of Encounters for financial or other reasons. Encounters can be aggregated or grouped under other Encounters using the partOf element.
Encounter instances may exist before the actual encounter takes place to convey pre-admission information, including using Encounters elements to reflect the planned start date, planned accommodation or planned encounter locations. In this case the status element is set to 'planned'.
Specifically outside the scope of Encounter are:
- Group encounters -
- Appointment information - use the Appointment resource (yet to be defined). Note that in many systems outpatient encounters (which are in scope for Encounter) and Appointment are used concurrently. In FHIR, Appointment is used for establishing a date for the encounter, while Encounter is applicable to information about the actual Encounter, i.e. the patient showing up.
Resource Content5.9.1
<Encounter xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, narrative, and contained --> <identifier><!-- 0..* Identifier Identifier(s) by which this encounter is known § --></identifier> <status value="[code]"/><!-- 1..1 E.g. active, aborted, finished § --> <class value="[code]"/><!-- 1..1 Inpatient | Outpatient etc § --> <type><!-- 0..* CodeableConcept Specific type of encounter § --></type> <subject><!-- 0..1 Resource(Patient) The patient present at the encounter § --></subject> <participant> <!-- 0..* List of participants involved in the encounter § --> <type value="[code]"/><!-- 0..* Role of participant in encounter § --> <practitioner><!-- 0..1 Resource(Practitioner) The practitioner that is involved § --></practitioner> </participant> <fulfills><!-- 0..1 Resource(Appointment) The appointment that scheduled this encounter § --></fulfills> <start value="[dateTime]"/><!-- 0..1 The date and time the encounter starts --> <length><!-- 0..1 Duration Quantity of time the encounter lasted --></length> <reason[x]><!-- 0..1 string|CodeableConcept Reason the encounter takes place § --></reason[x]> <indication><!-- 0..1 Resource(Any) Reason the encounter takes place --></indication> <priority><!-- 0..1 CodeableConcept Indicates the urgency of the encounter --></priority> <hospitalization> <!-- 0..1 Details about an admission to a clinic --> <preAdmissionIdentifier><!-- 0..1 Identifier Pre-admission identifier --></preAdmissionIdentifier> <origin><!-- 0..1 Resource(Location) The location the patient came from before admission --></origin> <admitSource><!-- 0..1 CodeableConcept Where patient was admitted from (physician referral, transfer) --></admitSource> <period><!-- 0..1 Period Period of hospitalization --></period> <accomodation> <!-- 0..* Where the patient stays during this encounter --> <bed><!-- 0..1 Resource(Location) Bed --></bed> <period><!-- 0..1 Period Period during which the patient was assigned the bed --></period> </accomodation> <diet><!-- 0..1 CodeableConcept Dietary restrictions for the patient --></diet> <specialCourtesy><!-- 0..* CodeableConcept Special courtesies (VIP, board member) --></specialCourtesy> <specialArrangement><!-- 0..* CodeableConcept Wheelchair, translator, stretcher, etc --></specialArrangement> <destination><!-- 0..1 Resource(Location) Location the patient is discharged to --></destination> <dischargeDisposition><!-- 0..1 CodeableConcept Disposition patient released to --></dischargeDisposition> <reAdmission value="[boolean]"/><!-- 0..1 Is readmission? --> </hospitalization> <location> <!-- 0..* List of locations the patient has been at --> <location><!-- 1..1 Resource(Location) The location the encounter takes place --></location> <period><!-- 1..1 Period Time period during which the patient was present at the location --></period> </location> <serviceProvider><!-- 0..1 Resource(Organization) Department or team providing care --></serviceProvider> <partOf><!-- 0..1 Resource(Encounter) Another Encounter this encounter is part of --></partOf> </Encounter>
Alternate definitions: Schema/Schematron, Resource Profile
Terminology Bindings 5.9.1.1
Notes:
- The class element describes the setting (in/outpatient etc.) in which the Encounter took place. Since this is important for interpreting the context of the encounter, choosing the appropriate business rules to enforce and management of the process, this element is required.
- The Location indicates where the patient has been during the encounter (he might visit multiple locations, e.g. to an MRI room for examinations, while Accommodation keeps information about the bed a patient stays at during a hospitalization.
Search Parameters 5.9.2
Search Parameters for RESTful searches. The standard parameters also apply. See Searching for more information.