description: Base StructureDefinition for Encounter Resource package_name: hl7.fhir.core derivation: specialization name: Encounter type: null elements: patient: {short: The patient present at the encounter, comments: 'While the encounter is always about the patient, the patient may not actually be known in all contexts of use.', type: Reference, isSummary: true, index: 8} appointment: {type: Reference, short: The appointment that scheduled this encounter, isSummary: true, index: 15} indication: {short: Reason the encounter takes place (resource), comments: 'For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).', type: Reference, array: true, index: 19} serviceProvider: {type: Reference, short: The custodian organization of this Encounter record, index: 36} episodeOfCare: {type: Reference, short: Episode(s) of care that this encounter should be recorded against, isSummary: true, array: true, index: 9} type: {short: Specific type of encounter, comments: 'Since there are many ways to further classify encounters, this element is 0..*.', type: CodeableConcept, array: true, isSummary: true, index: 6} participant: type: BackboneElement short: List of participants involved in the encounter isSummary: true array: true index: 11 elements: type: {short: Role of participant in encounter, comments: 'The participant type indicates how an individual partitipates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.', type: CodeableConcept, array: true, isSummary: true, index: 12} period: {type: Period, short: Period of time during the encounter participant was present, index: 13} individual: {type: Reference, short: Persons involved in the encounter other than the patient, isSummary: true, index: 14} incomingReferral: {type: Reference, short: The ReferralRequest that initiated this encounter, array: true, index: 10} reason: {short: Reason the encounter takes place (code), comments: 'For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).', type: CodeableConcept, array: true, isSummary: true, index: 18} priority: {type: CodeableConcept, short: Indicates the urgency of the encounter, index: 7} status: {isModifier: true, short: planned | arrived | in-progress | onleave | finished | cancelled, type: code, isSummary: true, index: 1} class: {short: inpatient | outpatient | ambulatory | emergency +, type: code, isSummary: true, index: 5} length: {type: Quantity, short: Quantity of time the encounter lasted (less time absent), comments: May differ from the time the Encounter.period lasted because of leave of absence., index: 17} identifier: {type: Identifier, short: Identifier(s) by which this encounter is known, isSummary: true, array: true, index: 0} hospitalization: type: BackboneElement short: Details about the admission to a healthcare service comments: |- An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record. index: 20 elements: dischargeDisposition: {type: CodeableConcept, short: Category or kind of location after discharge, index: 30} preAdmissionIdentifier: {type: Identifier, short: Pre-admission identifier, index: 21} admittingDiagnosis: {type: Reference, short: The admitting diagnosis as reported by admitting practitioner, array: true, index: 24} specialArrangement: {type: CodeableConcept, short: 'Wheelchair, translator, stretcher, etc.', array: true, index: 28} dietPreference: {short: Diet preferences reported by the patient, comments: For example a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive)., type: CodeableConcept, array: true, index: 26} admitSource: {type: CodeableConcept, short: 'From where patient was admitted (physician referral, transfer)', index: 23} specialCourtesy: {type: CodeableConcept, short: 'Special courtesies (VIP, board member)', array: true, index: 27} reAdmission: {type: CodeableConcept, short: 'The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission', index: 25} origin: {type: Reference, short: The location from which the patient came before admission, index: 22} dischargeDiagnosis: {type: Reference, short: 'The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete', array: true, index: 31} destination: {type: Reference, short: Location to which the patient is discharged, index: 29} period: {type: Period, short: The start and end time of the encounter, comments: 'If not (yet) known, the end of the Period may be omitted.', index: 16} partOf: {type: Reference, short: Another Encounter this encounter is part of, index: 37} location: type: BackboneElement short: List of locations where the patient has been comments: Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". array: true index: 32 elements: location: {type: Reference, short: Location the encounter takes place, index: 33} status: {type: code, short: planned | active | reserved | completed, comments: 'When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.', index: 34} period: {type: Period, short: Time period during which the patient was present at the location, index: 35} required: [location] statusHistory: type: BackboneElement short: List of past encounter statuses comments: The current status is always found in the current version of the resource, not the status history. array: true index: 2 elements: status: {type: code, short: planned | arrived | in-progress | onleave | finished | cancelled, index: 3} period: {type: Period, short: The time that the episode was in the specified status, index: 4} required: [status, period] package_version: 1.4.0 class: resource kind: resource url: http://hl7.org/fhir/StructureDefinition/Encounter base: http://hl7.org/fhir/StructureDefinition/DomainResource version: null required: [status]