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. 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. If the element is present, it must have either a @value, an @id, or extensions Identifier(s) by which this encounter is known. planned | arrived | triaged | in-progress | onleave | finished | cancelled +. The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient. Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Broad categorization of the service that is to be provided (e.g. cardiology). Indicates the urgency of the encounter. The patient or group present at the encounter. Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). The request this encounter satisfies (e.g. incoming referral or procedure request). The list of people responsible for providing the service. The appointment that scheduled this encounter. The start and end time of the encounter. Quantity of time the encounter lasted. This excludes the time during leaves of absence. Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. The list of diagnosis relevant to this encounter. The set of accounts that may be used for billing for this Encounter. Details about the admission to a healthcare service. List of locations where the patient has been during this encounter. The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy. Another Encounter of which this encounter is a part of (administratively or in time). 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. planned | arrived | triaged | in-progress | onleave | finished | cancelled +. The time that the episode was in the specified status. 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. inpatient | outpatient | ambulatory | emergency +. The time that the episode was in the specified class. 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. Role of participant in encounter. The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. Persons involved in the encounter other than the patient. 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. Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). Ranking of the diagnosis (for each role type). 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. Pre-admission identifier. The location/organization from which the patient came before admission. From where patient was admitted (physician referral, transfer). Whether this hospitalization is a readmission and why if known. Diet preferences reported by the patient. Special courtesies (VIP, board member). Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. Location/organization to which the patient is discharged. Category or kind of location after discharge. 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 location where the encounter takes place. The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. Time period during which the patient was present at the location. Planned Active Reserved Completed If the element is present, it must have either a @value, an @id, or extensions Planned Arrived Triaged In Progress On Leave Finished Cancelled Entered in Error Unknown If the element is present, it must have either a @value, an @id, or extensions