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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. If the element is present, it must have either a @value, an @id, or extensions Identifier(s) by which this encounter is known. The current state of the encounter (not the state of the patient within the encounter - that is subjectState). A granular, workflows specific set of statuses that apply to the encounter. Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. Indicates the urgency of the encounter. 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). The patient or group related to this encounter. In some use-cases the patient MAY not be present, such as a case meeting about a patient between several practitioners or a careteam. The subjectStatus value can be used to track the patient's status within the encounter. It details whether the patient has arrived or departed, has been triaged or is currently in a waiting status. 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 group(s) of individuals, organizations that are allocated to participate in this encounter. The participants backbone will record the actuals of when these individuals participated during the encounter. Another Encounter of which this encounter is a part of (administratively or in time). 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 colonoscopy example on the Encounter examples tab. The list of people responsible for providing the service. The appointment that scheduled this encounter. Connection details of a virtual service (e.g. conference call). The actual start and end time of the encounter. The planned start date/time (or admission date) of the encounter. The planned end date/time (or discharge date) of the encounter. Actual quantity of time the encounter lasted. This excludes the time during leaves of absence. When missing it is the time in between the start and end values. The list of medical reasons that are expected to be addressed during the episode of care. The list of diagnosis relevant to this encounter. The set of accounts that may be used for billing for this Encounter. Diet preferences reported by the patient. Any special requests that have been made for this encounter, such as the provision of specific equipment or other things. Special courtesies that may be provided to the patient during the encounter (VIP, board member, professional courtesy). Details about the stay during which a healthcare service is provided. This does not describe the event of admitting the patient, but rather any information that is relevant from the time of admittance until the time of discharge. List of locations where the patient has been during this encounter. 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. The current business status. The kind of workflow the status is tracking. The date/time when the encounter entered this business 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. 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. Person involved in the encounter, the patient/group is also included here to indicate that the patient was actually participating in the encounter. Not including the patient here covers use cases such as a case meeting between practitioners about a patient - non contact times. 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. What the reason value should be used as e.g. Chief Complaint, Health Concern, Health Maintenance (including screening). Reason the encounter takes place, expressed as a code or a reference to another resource. For admissions, this can be used for a coded admission diagnosis. 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. The coded diagnosis or a reference to a Condition (with other resources referenced in the evidence.detail), the use property will indicate the purpose of this specific diagnosis. Role that this diagnosis has within the encounter (e.g. admission, billing, 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. Pre-admission identifier. The location/organization from which the patient came before admission. From where patient was admitted (physician referral, transfer). Indicates that this encounter is directly related to a prior admission, often because the conditions addressed in the prior admission were not fully addressed. 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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities. 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 In Progress On Hold Discharged Completed Cancelled Discontinued Entered in Error Unknown If the element is present, it must have either a @value, an @id, or extensions