A record of significant events/milestones key data throughout the history of an Encounter, often tracked for specific purposes such as billing. A record of significant events/milestones key data throughout the history of an Encounter, often tracked for specific purposes such as billing. If the element is present, it must have either a @value, an @id, or extensions The Encounter associated with this set of historic values. Identifier(s) by which this encounter is known. planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown. Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. 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. The start and end time associated with this set of values associated with the encounter, may be different to the planned times for various reasons. 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 location of the patient at this point in the encounter, the multiple cardinality permits de-normalizing the levels of the location hierarchy, such as site/ward/room/bed. A record of significant events/milestones key data throughout the history of an Encounter, often tracked for specific purposes such as billing. The location where the encounter takes place. This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.