5.18 5.20 Resource Encounter - Content Resource Encounter - Content

5.18.1 Scope and Usage 5.20.1 Scope and Usage 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

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. For example, each single visit of a practitioner during a hospitalization may lead to a new instance of Encounter, but depending on local practice and the systems involved, it may well be that this is aggregated to a single instance for a 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 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. For example, each single visit of a practitioner during a hospitalization may lead to a new instance of Encounter, but depending on local practice and the systems involved, it may well be that this is aggregated to a single instance for a 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. See element. See below for examples. 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 or planned encounter locations. In this case the for examples.

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 or planned encounter locations. In this case the status element is set to 'planned'. The Hospitalization component is intended to store the extended information relating to a hospitalization event. This is always expected to be the same period as the encounter itself, where this is different then another encounter is entered which captures this information which is a partOf this encounter instance. element is set to 'planned'.

The Hospitalization component is intended to store the extended information relating to a hospitalization event. This is always expected to be the same period as the encounter itself, where this is different then another encounter is entered which captures this information which is a partOf this encounter instance.

5.18.1.1 5.20.1.1 Status Management Status Management During the life-cycle of an encounter it will pass through many statuses. Typically these are in order or the organizations workflow: planned, in-progress, finished/cancelled. This status information is often used for other things, and often an analysis of the status history is required. This could be done by scanning through all the versions of the encounter and then checking the period of each, and doing some form of post processing. To ease the burden of this (or where a system doesn't support resource histories) a status history component is included. There is no direct indication purely by the status field as to if an encounter is considered "admitted". The context of the encounter and business practices/policies/workflows/types can influence this definition. (e.g., acute care facility, aged care center, outpatient clinic, emergency department, community based clinic). Statuses of "arrived" or "in progress" could be considered the start of the admission, and also have the presence of the hospitalization sub-component entered. The "on leave" status may or may not be a part of the admission, for example if the patient was permitted to go home for a weekend or some other form of external event. The location is also likely to be filled in with a location status of "present". For other examples such as an outpatient visit (Day Procedure - colonoscopy), the patient could also be considered to be admitted, hence the encounter doesn't have a fixed definition of admitted. At a minimum, we do believe that a patient IS admitted when the status is in-progress.

During the life-cycle of an encounter it will pass through many statuses. Typically these are in order or the organizations workflow: planned, in-progress, finished/cancelled.
This status information is often used for other things, and often an analysis of the status history is required. This could be done by scanning through all the versions of the encounter and then checking the period of each, and doing some form of post processing. To ease the burden of this (or where a system doesn't support resource histories) a status history component is included.

There is no direct indication purely by the status field as to if an encounter is considered "admitted".
The context of the encounter and business practices/policies/workflows/types can influence this definition. (e.g., acute care facility, aged care center, outpatient clinic, emergency department, community based clinic).
Statuses of "arrived" or "in progress" could be considered the start of the admission, and also have the presence of the hospitalization sub-component entered.

The "on leave" status may or may not be a part of the admission, for example if the patient was permitted to go home for a weekend or some other form of external event.
The location is also likely to be filled in with a location status of "present".
For other examples such as an outpatient visit (Day Procedure - colonoscopy), the patient could also be considered to be admitted, hence the encounter doesn't have a fixed definition of admitted. At a minimum, we do believe that a patient IS admitted when the status is in-progress.

5.18.2 Boundaries and Relationships 5.20.2 Boundaries and Relationships The Encounter resource is not to be used to store appointment information, the Appointment resource is intended to be used for that. 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. As such an encounter in the "planned" status is not identical to the appointment that scheduled it, but it is the encounter prior to its actual occurrence, with the expectation that encounter will be updated as it progresses to completion. Patient arrival at a location does not necessarily mean the start of the encounter (e.g. a patient arrives an hour earlier than he is actually seen by a practitioner). An appointment is normally used for the planning stage of an appointment, searching, locating an available time, then making the appointment. Once this process is completed and the appointment is about to start, then the appointment will be marked as fulfilled, and linked to the newly created encounter. This new encounter may start in an "arrived" status when they are admitted with a location of the facility, and then will move to the ward where another part-of encounter may begin. Communication resources are used for a direct simultaneous interaction between a practitioner and a patient where there is no direct contact. Such as phone message, or transmission of some correspondence documentation. There is no duration recorded for a communication resource, but could contain sent and received times. Standard Extension: Associated Encounter

The Encounter resource is not to be used to store appointment information, the Appointment resource is intended to be used for that. 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.
As such an encounter in the "planned" status is not identical to the appointment that scheduled it, but it is the encounter prior to its actual occurrence, with the expectation that encounter will be updated as it progresses to completion. Patient arrival at a location does not necessarily mean the start of the encounter (e.g. a patient arrives an hour earlier than he is actually seen by a practitioner).

An appointment is normally used for the planning stage of an appointment, searching, locating an available time, then making the appointment. Once this process is completed and the appointment is about to start, then the appointment will be marked as fulfilled, and linked to the newly created encounter.
This new encounter may start in an "arrived" status when they are admitted with a location of the facility, and then will move to the ward where another part-of encounter may begin.

Communication resources are used for a direct simultaneous interaction between a practitioner and a patient where there is no direct contact. Such as phone message, or transmission of some correspondence documentation.
There is no duration recorded for a communication resource, but could contain sent and received times.

Standard Extension: Associated Encounter This extension should be used to reference an encounter where there is no property that already defines this association on the resource. This resource is referenced by
This extension should be used to reference an encounter where there is no property that already defines this association on the resource.

• Structure
• UML
• XML
• JSON
• All

Structure

Name	Flags	Card.	Type	Description & Constraints Description & Constraints
Encounter			DomainResource	An interaction during which services are provided to the patient An interaction during which services are provided to the patient
identifier	Σ	0..*	Identifier	Identifier(s) by which this encounter is known Identifier(s) by which this encounter is known
status	?! ?! Σ	1..1	code	planned | arrived | in-progress | onleave | finished | cancelled planned | arrived | in-progress | onleave | finished | cancelled EncounterState ( ( Required )
statusHistory		0..*	BackboneElement	List of past encounter statuses List of past encounter statuses
status		1..1	code	planned | arrived | in-progress | onleave | finished | cancelled planned | arrived | in-progress | onleave | finished | cancelled EncounterState ( ( Required )
period		1..1	Period	The time that the episode was in the specified status The time that the episode was in the specified status
class	Σ	0..1	code	inpatient | outpatient | ambulatory | emergency + inpatient | outpatient | ambulatory | emergency + EncounterClass ( ( Required )
type	Σ	0..*	CodeableConcept	Specific type of encounter Specific type of encounter EncounterType ( ( Example )
priority		0..1	CodeableConcept	Indicates the urgency of the encounter Indicates the urgency of the encounter Encounter Priority ( Encounter Priority ( Example )
patient	Σ	0..1	Reference ( Patient )	The patient present at the encounter The patient present at the encounter
episodeOfCare	Σ	0..*	Reference ( EpisodeOfCare )	Episode(s) of care that this encounter should be recorded against Episode(s) of care that this encounter should be recorded against
incomingReferral		0..*	Reference ( ReferralRequest )	The ReferralRequest that initiated this encounter The ReferralRequest that initiated this encounter
participant	Σ	0..*	BackboneElement	List of participants involved in the encounter List of participants involved in the encounter
type	Σ	0..*	CodeableConcept	Role of participant in encounter Role of participant in encounter ParticipantType ( ( Extensible )
period		0..1	Period	Period of time during the encounter participant was present Period of time during the encounter participant was present
individual	Σ	0..1	Reference ( Practitioner | | RelatedPerson )	Persons involved in the encounter other than the patient Persons involved in the encounter other than the patient
appointment	Σ	0..1	Reference ( Appointment )	The appointment that scheduled this encounter The appointment that scheduled this encounter
period		0..1	Period	The start and end time of the encounter The start and end time of the encounter
length		0..1	Duration	Quantity of time the encounter lasted (less time absent) Quantity of time the encounter lasted (less time absent)
reason	Σ	0..*	CodeableConcept	Reason the encounter takes place (code) Reason the encounter takes place (code) Encounter Reason Codes ( Encounter Reason Codes ( Example )
indication		0..*	Reference ( Condition | | Procedure )	Reason the encounter takes place (resource) Reason the encounter takes place (resource)
hospitalization		0..1	BackboneElement	Details about the admission to a healthcare service Details about the admission to a healthcare service
preAdmissionIdentifier		0..1	Identifier	Pre-admission identifier Pre-admission identifier
origin		0..1	Reference ( Location )	The location from which the patient came before admission The location from which the patient came before admission
admitSource		0..1	CodeableConcept	From where patient was admitted (physician referral, transfer) From where patient was admitted (physician referral, transfer) AdmitSource ( ( Preferred )
admittingDiagnosis		0..*	Reference ( Condition )	The admitting diagnosis as reported by admitting practitioner The admitting diagnosis as reported by admitting practitioner
reAdmission		0..1	CodeableConcept	The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
dietPreference		0..*	CodeableConcept	Diet preferences reported by the patient Diet preferences reported by the patient Diet ( ( Example )
specialCourtesy		0..*	CodeableConcept	Special courtesies (VIP, board member) Special courtesies (VIP, board member) SpecialCourtesy ( ( Preferred )
specialArrangement		0..*	CodeableConcept	Wheelchair, translator, stretcher, etc. Wheelchair, translator, stretcher, etc. SpecialArrangements ( ( Preferred )
destination		0..1	Reference ( Location )	Location to which the patient is discharged Location to which the patient is discharged
dischargeDisposition		0..1	CodeableConcept	Category or kind of location after discharge Category or kind of location after discharge DischargeDisposition ( ( Preferred )
dischargeDiagnosis		0..*	Reference ( Condition )	The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
location		0..*	BackboneElement	List of locations where the patient has been List of locations where the patient has been
location		1..1	Reference ( Location )	Location the encounter takes place Location the encounter takes place
status		0..1	code	planned | active | reserved | completed planned | active | reserved | completed EncounterLocationStatus ( ( Required )
period		0..1	Period	Time period during which the patient was present at the location Time period during which the patient was present at the location
serviceProvider		0..1	Reference ( Organization )	The custodian organization of this Encounter record The custodian organization of this Encounter record
partOf		0..1	Reference ( Encounter )	Another Encounter this encounter is part of Another Encounter this encounter is part of
Documentation for this format Documentation for this format

<Encounter xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Identifier(s) by which this encounter is known --></identifier>
 <status value="[code]"/><!-- 1..1 planned | arrived | in-progress | onleave | finished | cancelled -->
 <statusHistory>  <!-- 0..* List of past encounter statuses -->
  <status value="[code]"/><!-- 1..1 planned | arrived | in-progress | onleave | finished | cancelled -->
  <period><!-- 1..1 Period The time that the episode was in the specified status --></period>
 </statusHistory>
 <class value="[code]"/><!-- 0..1 inpatient | outpatient | ambulatory | emergency + -->
 <type><!-- 0..* CodeableConcept Specific type of encounter --></type>
 <priority><!-- 0..1 CodeableConcept Indicates the urgency of the encounter --></priority>
 <patient><!-- 0..1 Reference(Patient) The patient present at the encounter --></patient>
 <episodeOfCare><!-- 0..* Reference(EpisodeOfCare) Episode(s) of care that this encounter should be recorded against --></episodeOfCare>
 <incomingReferral><!-- 0..* Reference(ReferralRequest) The ReferralRequest that initiated this encounter --></incomingReferral>
 <

 <participant>  <!-- 0..* List of participants involved in the encounter -->

  <type><!-- 0..* CodeableConcept Role of participant in encounter --></type>
  <period><!-- 0..1 Period Period of time during the encounter participant was present --></period>
  <individual><!-- 0..1 Reference(Practitioner|RelatedPerson) Persons involved in the encounter other than the patient --></individual>
 </participant>
 <appointment><!-- 0..1 Reference(Appointment) The appointment that scheduled this encounter --></appointment>
 <period><!-- 0..1 Period The start and end time of the encounter --></period>
 <length><!-- 0..1 Quantity(Duration) Quantity of time the encounter lasted (less time absent) --></length>
 <reason><!-- 0..* CodeableConcept Reason the encounter takes place (code) --></reason>
 <indication><!-- 0..* Reference(Condition|Procedure) Reason the encounter takes place (resource) --></indication>
 <hospitalization>  <!-- 0..1 Details about the admission to a healthcare service -->
  <preAdmissionIdentifier><!-- 0..1 Identifier Pre-admission identifier --></preAdmissionIdentifier>
  <origin><!-- 0..1 Reference(Location) The location from which the patient came before admission --></origin>
  <admitSource><!-- 0..1 CodeableConcept From where patient was admitted (physician referral, transfer) --></admitSource>
  <admittingDiagnosis><!-- 0..* Reference(Condition) The admitting diagnosis as reported by admitting practitioner --></admittingDiagnosis>
  <reAdmission><!-- 0..1 CodeableConcept The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission --></reAdmission>
  <dietPreference><!-- 0..* CodeableConcept Diet preferences reported by the patient --></dietPreference>
  <specialCourtesy><!-- 0..* CodeableConcept Special courtesies (VIP, board member) --></specialCourtesy>
  <specialArrangement><!-- 0..* CodeableConcept Wheelchair, translator, stretcher, etc. --></specialArrangement>
  <destination><!-- 0..1 Reference(Location) Location to which the patient is discharged --></destination>
  <dischargeDisposition><!-- 0..1 CodeableConcept Category or kind of location after discharge --></dischargeDisposition>
  <dischargeDiagnosis><!-- 0..* Reference(Condition) The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete --></dischargeDiagnosis>
 </hospitalization>
 <location>  <!-- 0..* List of locations where the patient has been -->
  <location><!-- 1..1 Reference(Location) Location the encounter takes place --></location>
  <status value="[code]"/><!-- 0..1 planned | active | reserved | completed -->
  <period><!-- 0..1 Period Time period during which the patient was present at the location --></period>
 </location>
 <serviceProvider><!-- 0..1 Reference(Organization) The custodian organization of this Encounter record --></serviceProvider>
 <partOf><!-- 0..1 Reference(Encounter) Another Encounter this encounter is part of --></partOf>
</Encounter>

{
  "resourceType" : "Encounter",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Identifier(s) by which this encounter is known
  "status" : "<code>", // R!  planned | arrived | in-progress | onleave | finished | cancelled
  "statusHistory" : [{ // List of past encounter statuses
    "status" : "<code>", // R!  planned | arrived | in-progress | onleave | finished | cancelled
    "period" : { Period } // R!  The time that the episode was in the specified status
  }],
  "class" : "<code>", // inpatient | outpatient | ambulatory | emergency +
  "type" : [{ CodeableConcept }], // Specific type of encounter
  "priority" : { CodeableConcept }, // Indicates the urgency of the encounter
  "patient" : { Reference(Patient) }, // The patient present at the encounter
  "episodeOfCare" : [{ Reference(EpisodeOfCare) }], // Episode(s) of care that this encounter should be recorded against
  "incomingReferral" : [{ Reference(ReferralRequest) }], // The ReferralRequest that initiated this encounter
  "

  "participant" : [{ // List of participants involved in the encounter

    "type" : [{ CodeableConcept }], // Role of participant in encounter
    "period" : { Period }, // Period of time during the encounter participant was present
    "individual" : { Reference(Practitioner|RelatedPerson) } // Persons involved in the encounter other than the patient
  }],
  "appointment" : { Reference(Appointment) }, // The appointment that scheduled this encounter
  "period" : { Period }, // The start and end time of the encounter
  "length" : { Quantity(Duration) }, // Quantity of time the encounter lasted (less time absent)
  "reason" : [{ CodeableConcept }], // Reason the encounter takes place (code)
  "indication" : [{ Reference(Condition|Procedure) }], // Reason the encounter takes place (resource)
  "hospitalization" : { // Details about the admission to a healthcare service
    "preAdmissionIdentifier" : { Identifier }, // Pre-admission identifier
    "origin" : { Reference(Location) }, // The location from which the patient came before admission
    "admitSource" : { CodeableConcept }, // From where patient was admitted (physician referral, transfer)
    "admittingDiagnosis" : [{ Reference(Condition) }], // The admitting diagnosis as reported by admitting practitioner
    "reAdmission" : { CodeableConcept }, // The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
    "dietPreference" : [{ CodeableConcept }], // Diet preferences reported by the patient
    "specialCourtesy" : [{ CodeableConcept }], // Special courtesies (VIP, board member)
    "specialArrangement" : [{ CodeableConcept }], // Wheelchair, translator, stretcher, etc.
    "destination" : { Reference(Location) }, // Location to which the patient is discharged
    "dischargeDisposition" : { CodeableConcept }, // Category or kind of location after discharge
    "dischargeDiagnosis" : [{ Reference(Condition) }] // The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
  },
  "location" : [{ // List of locations where the patient has been
    "location" : { Reference(Location) }, // R!  Location the encounter takes place
    "status" : "<code>", // planned | active | reserved | completed
    "period" : { Period } // Time period during which the patient was present at the location
  }],
  "serviceProvider" : { Reference(Organization) }, // The custodian organization of this Encounter record
  "partOf" : { Reference(Encounter) } // Another Encounter this encounter is part of
}

Structure

Name	Flags	Card.	Type	Description & Constraints Description & Constraints
Encounter			DomainResource	An interaction during which services are provided to the patient An interaction during which services are provided to the patient
identifier	Σ	0..*	Identifier	Identifier(s) by which this encounter is known Identifier(s) by which this encounter is known
status	?! ?! Σ	1..1	code	planned | arrived | in-progress | onleave | finished | cancelled planned | arrived | in-progress | onleave | finished | cancelled EncounterState ( ( Required )
statusHistory		0..*	BackboneElement	List of past encounter statuses List of past encounter statuses
status		1..1	code	planned | arrived | in-progress | onleave | finished | cancelled planned | arrived | in-progress | onleave | finished | cancelled EncounterState ( ( Required )
period		1..1	Period	The time that the episode was in the specified status The time that the episode was in the specified status
class	Σ	0..1	code	inpatient | outpatient | ambulatory | emergency + inpatient | outpatient | ambulatory | emergency + EncounterClass ( ( Required )
type	Σ	0..*	CodeableConcept	Specific type of encounter Specific type of encounter EncounterType ( ( Example )
priority		0..1	CodeableConcept	Indicates the urgency of the encounter Indicates the urgency of the encounter Encounter Priority ( Encounter Priority ( Example )
patient	Σ	0..1	Reference ( Patient )	The patient present at the encounter The patient present at the encounter
episodeOfCare	Σ	0..*	Reference ( EpisodeOfCare )	Episode(s) of care that this encounter should be recorded against Episode(s) of care that this encounter should be recorded against
incomingReferral		0..*	Reference ( ReferralRequest )	The ReferralRequest that initiated this encounter The ReferralRequest that initiated this encounter
participant	Σ	0..*	BackboneElement	List of participants involved in the encounter List of participants involved in the encounter
type	Σ	0..*	CodeableConcept	Role of participant in encounter Role of participant in encounter ParticipantType ( ( Extensible )
period		0..1	Period	Period of time during the encounter participant was present Period of time during the encounter participant was present
individual	Σ	0..1	Reference ( Practitioner | | RelatedPerson )	Persons involved in the encounter other than the patient Persons involved in the encounter other than the patient
appointment	Σ	0..1	Reference ( Appointment )	The appointment that scheduled this encounter The appointment that scheduled this encounter
period		0..1	Period	The start and end time of the encounter The start and end time of the encounter
length		0..1	Duration	Quantity of time the encounter lasted (less time absent) Quantity of time the encounter lasted (less time absent)
reason	Σ	0..*	CodeableConcept	Reason the encounter takes place (code) Reason the encounter takes place (code) Encounter Reason Codes ( Encounter Reason Codes ( Example )
indication		0..*	Reference ( Condition | | Procedure )	Reason the encounter takes place (resource) Reason the encounter takes place (resource)
hospitalization		0..1	BackboneElement	Details about the admission to a healthcare service Details about the admission to a healthcare service
preAdmissionIdentifier		0..1	Identifier	Pre-admission identifier Pre-admission identifier
origin		0..1	Reference ( Location )	The location from which the patient came before admission The location from which the patient came before admission
admitSource		0..1	CodeableConcept	From where patient was admitted (physician referral, transfer) From where patient was admitted (physician referral, transfer) AdmitSource ( ( Preferred )
admittingDiagnosis		0..*	Reference ( Condition )	The admitting diagnosis as reported by admitting practitioner The admitting diagnosis as reported by admitting practitioner
reAdmission		0..1	CodeableConcept	The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
dietPreference		0..*	CodeableConcept	Diet preferences reported by the patient Diet preferences reported by the patient Diet ( ( Example )
specialCourtesy		0..*	CodeableConcept	Special courtesies (VIP, board member) Special courtesies (VIP, board member) SpecialCourtesy ( ( Preferred )
specialArrangement		0..*	CodeableConcept	Wheelchair, translator, stretcher, etc. Wheelchair, translator, stretcher, etc. SpecialArrangements ( ( Preferred )
destination		0..1	Reference ( Location )	Location to which the patient is discharged Location to which the patient is discharged
dischargeDisposition		0..1	CodeableConcept	Category or kind of location after discharge Category or kind of location after discharge DischargeDisposition ( ( Preferred )
dischargeDiagnosis		0..*	Reference ( Condition )	The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
location		0..*	BackboneElement	List of locations where the patient has been List of locations where the patient has been
location		1..1	Reference ( Location )	Location the encounter takes place Location the encounter takes place
status		0..1	code	planned | active | reserved | completed planned | active | reserved | completed EncounterLocationStatus ( ( Required )
period		0..1	Period	Time period during which the patient was present at the location Time period during which the patient was present at the location
serviceProvider		0..1	Reference ( Organization )	The custodian organization of this Encounter record The custodian organization of this Encounter record
partOf		0..1	Reference ( Encounter )	Another Encounter this encounter is part of Another Encounter this encounter is part of
Documentation for this format Documentation for this format

UML Diagram UML Diagram

XML Template XML Template

<Encounter xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Identifier(s) by which this encounter is known --></identifier>
 <status value="[code]"/><!-- 1..1 planned | arrived | in-progress | onleave | finished | cancelled -->
 <statusHistory>  <!-- 0..* List of past encounter statuses -->
  <status value="[code]"/><!-- 1..1 planned | arrived | in-progress | onleave | finished | cancelled -->
  <period><!-- 1..1 Period The time that the episode was in the specified status --></period>
 </statusHistory>
 <class value="[code]"/><!-- 0..1 inpatient | outpatient | ambulatory | emergency + -->
 <type><!-- 0..* CodeableConcept Specific type of encounter --></type>
 <priority><!-- 0..1 CodeableConcept Indicates the urgency of the encounter --></priority>
 <patient><!-- 0..1 Reference(Patient) The patient present at the encounter --></patient>
 <episodeOfCare><!-- 0..* Reference(EpisodeOfCare) Episode(s) of care that this encounter should be recorded against --></episodeOfCare>
 <incomingReferral><!-- 0..* Reference(ReferralRequest) The ReferralRequest that initiated this encounter --></incomingReferral>
 <

 <participant>  <!-- 0..* List of participants involved in the encounter -->

  <type><!-- 0..* CodeableConcept Role of participant in encounter --></type>
  <period><!-- 0..1 Period Period of time during the encounter participant was present --></period>
  <individual><!-- 0..1 Reference(Practitioner|RelatedPerson) Persons involved in the encounter other than the patient --></individual>
 </participant>
 <appointment><!-- 0..1 Reference(Appointment) The appointment that scheduled this encounter --></appointment>
 <period><!-- 0..1 Period The start and end time of the encounter --></period>
 <length><!-- 0..1 Quantity(Duration) Quantity of time the encounter lasted (less time absent) --></length>
 <reason><!-- 0..* CodeableConcept Reason the encounter takes place (code) --></reason>
 <indication><!-- 0..* Reference(Condition|Procedure) Reason the encounter takes place (resource) --></indication>
 <hospitalization>  <!-- 0..1 Details about the admission to a healthcare service -->
  <preAdmissionIdentifier><!-- 0..1 Identifier Pre-admission identifier --></preAdmissionIdentifier>
  <origin><!-- 0..1 Reference(Location) The location from which the patient came before admission --></origin>
  <admitSource><!-- 0..1 CodeableConcept From where patient was admitted (physician referral, transfer) --></admitSource>
  <admittingDiagnosis><!-- 0..* Reference(Condition) The admitting diagnosis as reported by admitting practitioner --></admittingDiagnosis>
  <reAdmission><!-- 0..1 CodeableConcept The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission --></reAdmission>
  <dietPreference><!-- 0..* CodeableConcept Diet preferences reported by the patient --></dietPreference>
  <specialCourtesy><!-- 0..* CodeableConcept Special courtesies (VIP, board member) --></specialCourtesy>
  <specialArrangement><!-- 0..* CodeableConcept Wheelchair, translator, stretcher, etc. --></specialArrangement>
  <destination><!-- 0..1 Reference(Location) Location to which the patient is discharged --></destination>
  <dischargeDisposition><!-- 0..1 CodeableConcept Category or kind of location after discharge --></dischargeDisposition>
  <dischargeDiagnosis><!-- 0..* Reference(Condition) The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete --></dischargeDiagnosis>
 </hospitalization>
 <location>  <!-- 0..* List of locations where the patient has been -->
  <location><!-- 1..1 Reference(Location) Location the encounter takes place --></location>
  <status value="[code]"/><!-- 0..1 planned | active | reserved | completed -->
  <period><!-- 0..1 Period Time period during which the patient was present at the location --></period>
 </location>
 <serviceProvider><!-- 0..1 Reference(Organization) The custodian organization of this Encounter record --></serviceProvider>
 <partOf><!-- 0..1 Reference(Encounter) Another Encounter this encounter is part of --></partOf>
</Encounter>

JSON Template JSON Template

{
  "resourceType" : "Encounter",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Identifier(s) by which this encounter is known
  "status" : "<code>", // R!  planned | arrived | in-progress | onleave | finished | cancelled
  "statusHistory" : [{ // List of past encounter statuses
    "status" : "<code>", // R!  planned | arrived | in-progress | onleave | finished | cancelled
    "period" : { Period } // R!  The time that the episode was in the specified status
  }],
  "class" : "<code>", // inpatient | outpatient | ambulatory | emergency +
  "type" : [{ CodeableConcept }], // Specific type of encounter
  "priority" : { CodeableConcept }, // Indicates the urgency of the encounter
  "patient" : { Reference(Patient) }, // The patient present at the encounter
  "episodeOfCare" : [{ Reference(EpisodeOfCare) }], // Episode(s) of care that this encounter should be recorded against
  "incomingReferral" : [{ Reference(ReferralRequest) }], // The ReferralRequest that initiated this encounter
  "

  "participant" : [{ // List of participants involved in the encounter

    "type" : [{ CodeableConcept }], // Role of participant in encounter
    "period" : { Period }, // Period of time during the encounter participant was present
    "individual" : { Reference(Practitioner|RelatedPerson) } // Persons involved in the encounter other than the patient
  }],
  "appointment" : { Reference(Appointment) }, // The appointment that scheduled this encounter
  "period" : { Period }, // The start and end time of the encounter
  "length" : { Quantity(Duration) }, // Quantity of time the encounter lasted (less time absent)
  "reason" : [{ CodeableConcept }], // Reason the encounter takes place (code)
  "indication" : [{ Reference(Condition|Procedure) }], // Reason the encounter takes place (resource)
  "hospitalization" : { // Details about the admission to a healthcare service
    "preAdmissionIdentifier" : { Identifier }, // Pre-admission identifier
    "origin" : { Reference(Location) }, // The location from which the patient came before admission
    "admitSource" : { CodeableConcept }, // From where patient was admitted (physician referral, transfer)
    "admittingDiagnosis" : [{ Reference(Condition) }], // The admitting diagnosis as reported by admitting practitioner
    "reAdmission" : { CodeableConcept }, // The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
    "dietPreference" : [{ CodeableConcept }], // Diet preferences reported by the patient
    "specialCourtesy" : [{ CodeableConcept }], // Special courtesies (VIP, board member)
    "specialArrangement" : [{ CodeableConcept }], // Wheelchair, translator, stretcher, etc.
    "destination" : { Reference(Location) }, // Location to which the patient is discharged
    "dischargeDisposition" : { CodeableConcept }, // Category or kind of location after discharge
    "dischargeDiagnosis" : [{ Reference(Condition) }] // The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
  },
  "location" : [{ // List of locations where the patient has been
    "location" : { Reference(Location) }, // R!  Location the encounter takes place
    "status" : "<code>", // planned | active | reserved | completed
    "period" : { Period } // Time period during which the patient was present at the location
  }],
  "serviceProvider" : { Reference(Organization) }, // The custodian organization of this Encounter record
  "partOf" : { Reference(Encounter) } // Another Encounter this encounter is part of
}