-
-
Key: = Must support, = QICore-defined extension, = Is-Modifier
Field Card. Type and Description 
account 0..*List<Reference>The set of accounts that may be used for billing for this Encounter.appointment 0..1ReferenceThe appointment that scheduled this encounter.class 0..1Codeinpatient | outpatient | ambulatory | emergency +.Binding: value set (Preferred)
classHistory 0..*List<ClassHistory>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 transisions 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 kindof discharge from emergency to inpatient.diagnosis 0..*List<Diagnosis>The list of diagnosis relevant to this encounter.episodeOfCare 0..*List<Reference>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).hospitalization 0..1HospitalizationDetails about the admission to a healthcare service.identifier 0..*List<Identifier>Identifier(s) by which this encounter is known.incomingReferral 0..*List<Reference>The referral request this encounter satisfies (incoming referral).length 0..1DurationQuantity of time the encounter lasted. This excludes the time during leaves of absence.location 0..*List<Location>List of locations where the patient has been during this encounter.partOf 0..1ReferenceAnother Encounter of which this encounter is a part of (administratively or in time).participant 0..*List<Participant>The list of people responsible for providing the service.period 0..1Interval<DateTime>The start and end time of the encounter.priority 0..1ConceptIndicates the urgency of the encounter.Binding: value set (Preferred)
reason 0..*List<Concept>Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.Binding: Encounter Reason Codes (Preferred)
reasonCancelled 0..1ExtensionIf the encountered was cancelled after it was planned, why? Applies only if the status is cancelled.serviceProvider 0..1ReferenceAn organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization.status 1..1Stringplanned | arrived | triaged | in-progress | onleave | finished | cancelled +.Binding: EncounterStatus (Required)
statusHistory 0..*List<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.subject 0..1ReferenceThe patient ro group present at the encounter.type 0..*List<Concept>Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).Binding: EncounterType (Example)
Key: = Must support, = QICore-defined extension, = Is-Modifier
-