careTeamMemberPointer to Practitioner(s) who make up a team comprising multiple disciplines in order to provide holistic care for the patient.
comments confidentiallyCodeContains a set of values that control the disclosure of information about this patient
description"Contains a brief user-defined description of the visit." - HL7 Version 2.8, PV2-12.
diagnosisListPointer to a list of one or more diagnosis(es) for which the Patient is being treated during the Encounter."The list of diagnosis relevant to this encounter." - HL7 FHIR, Encounter.diagnosis
durationThis property contains the date/times that the Encounter began and ended. If the encounter is currently active, the end time may be blank. HL7 V3 suggests that for current encounters, the end date could be used to convey the anticipated end date/time, but FHIM discourages this usage and instead recommends leaving the end date/time blank."The time interval starting with the administrative onset of the encounter (e.g. admission, registration, patient arrival) and ending with the patient's departure (e.g. discharge). Note (1): for active encounters the end of the effectiveTime range is the anticipated end date-time. Note (2): all messages, except the "nullify" message, require at least a starting time." - HL7 V3"The start and end time of the encounter." - HL7 FHIR, Encounter.period
encounterClassIndicates what kind (i.e., subtype) of Encounter that an encounter instance is. This property is included for compatibility with FHIR, and is therefore both optional and marked as derived. In FHIM, the kind of Encounter is known by the subtype of Encounter that the instance instantiates. In other words, FHIM has an EmergencyEncounter class and it is therefore known that an EmergencyEncounter is an EmergencyEncounter, whereas in FHIR an EmergencyEncounter is an Encounter with type EmergencyEncounter."This field is used by systems to categorize patients by site. It does not have a consistent industry-wide definition. It is subject to site specific variations." - HL7 Version 2.8, PV1-2. HL7 Version 2 has the following suggested values (table 4): Emergency; Inpatient; Outpatient; Preadmit; Recurring patient; Obstetrics; Commercial Account; Not Applicable; Unknown."Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations." Possible values include: ambulatory; emergency; field; home health; inpatient encounter; inpatient acute; inpatient non-acute; observation encounter; pre-admission; short stay; virtual. - HL7 FHIR, Encounter.class"Encounter type...." - PCORnet Common Data Model, Encounter.Enc_Type. Possible values include: Ambulatory Visit; Emergency Department; Emergency Department Admit to Inpatient Hospital Stay; Inpatient Hospital Stay; Non-Acute Institutional Stay; Observation Stay; Institutional Professional Consult; Other Ambulatory Visit; No information; Unknown; Other.
encounterTypeA categorization of the Encounter. This optional property is included for compatibility to FHIR, but the kinds of categorizations that might be useful have not yet been identified."Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation)." - HL7 FHIR, Encounter.type
episodeOfCarePointer to a Service Episode (aka Episode Of Care) into which this Encounter can be aggregated. Note that ordinarily an Encounter will be aggregated into only one (if at all) Service Episode, this property is modeled as a zero-to-many relationship rather than zero-to-one for compatibility with FHIR."Contains the identifier of a Service Episode in or for which the visit occurs." - HL7 Version 2.8, PV1-54"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)." - HL7 FHIR, Encounter.episodeOfCare
identifierThis property uniquely identifies the Encounter. This property can be used, among other purposes, to associate the current Encounter with other Encounters, or with events that occurred during the Encounter."Contains the unique number assigned to each patient visit." - HL7 Version 2.8, PV1-19"Identifier(s) by which this encounter is known." - HL7 FHIR, Encounter.identifier"Arbitrary encounter-level identifier. Used to link across tables." - PCORnet Common Data Model, Encounter.EncounterId
lengthOfStay"Quantity of time the encounter lasted. This excludes the time during leaves of absence." - HL7 FHIR, Encounter.length
patientThe Person or Animal (playing the Role of Patient) who is the subject of the Encounter."The patient or group present at the encounter." - HL7 FHIR, Encounter.subject. Note that in FHIR, the subject can be a Patient (subjectPatient) or a Group (subjectGroup). In FHIM, these are two separate associations: patient and subjectGroup. If one association is not empty, the other association must be empty. Therefore, this property is marked as zero to one, whereas logically it should be one to one.
priority"Contains the priority of the visit." - HL7 Version 2.8, PV2-25. Possible values include (from HL7 Table 217): Emergency; Urgent; Elective"Indicates the urgency of the encounter." - HL7 FHIR, Encounter.priority
relatedEncounterPointer to another Encounter to which this Encounter is somehow related. The nature of the relationship is defined by the relatedEncounterCategory code."Another Encounter of which this encounter is a part of (administratively or in time)." - HL7 FHIR, Encounter.partOf
scopingProviderPointer to the Healthcare Provider (organization) under whose auspices the Encounter occurred."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." - HL7 FHIR, Encounter.serviceProvider"Code for the provider who is most responsible for this encounter." - PCORnet Common Data Model, Encounter.ProviderId
serviceType"Broad categorization of the service that is to be provided (e.g. cardiology)." - HL7 FHIR, Encounter.serviceType
statusA value specifying the state of this patient encounter (based on the RIM Act class state machine), for example, active, aborted, completed "planned | arrived | triaged | in-progress | onleave | finished | cancelled +." - HL7 FHIR, Encounter.status
statusHistory"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." - HL7 FHIR, Encounter.statusHistory
subjectGroup"The patient or group present at the encounter." - HL7 FHIR, Encounter.subject. Note that in FHIR, the subject can be a Patient (subjectPatient) or a Group (subjectGroup). In FHIM, these are two separate associations: patient and subjectGroup. If one association is not empty, the other association must be empty. Therefore, this property is marked as zero to one, whereas logically it should be one to one.
