-
-
Key: = Must support, = QICore-defined extension, = Is-Modifier
Field Card. Type and Description 
account 0..*List<Account>The set of accounts that may be used for billing for this Encounter.appointment 0..1AppointmentThe appointment that scheduled this encounter.class 0..1Codeinpatient | outpatient | ambulatory | emergency +.(Extensible)
condition 0..1ExtensionThe reference to conditions related to this encounter, aside from the primary condition.episodeOfCare 0..*List<EpisodeOfCare>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<ReferralRequest>The referral request this encounter satisfies (incoming referral).indication 0..*List<Condition | Procedure>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.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..1EncounterAnother 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.patient 0..1PatientThe patient present at the encounter.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: value set (Preferred)
reasonCancelled 0..1ConceptIf the encountered was cancelled after it was planned, why? Applies only if the status is cancelled.Binding: value set (Example)
relatedCondition 0..*List<RelatedCondition>The conditions considered and cared for within this encounter. This includes items such as reason for visit, admission diagnosis, discharge diagnosis, chief complaint. Do not use reason or indication in the Action class to specify encounter-related diagnoses.role 0..1ExtensionThe role of the condition within this encounter, e.g. chief complaint, admission diagnosis, discharge diagnosis, comorbidity.serviceProvider 0..1OrganizationAn 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..1codeplanned | arrived | in-progress | onleave | finished | cancelled | entered-in-error.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.type 0..*List<Concept>Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).Binding: value set (Preferred)
Key: = Must support, = QICore-defined extension, = Is-Modifier
-