Name	Flags	Card.	Type	Description & Constraints
Encounter	TU		DomainResource	An interaction during which services are provided to the patient Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
identifier	Σ	0..*	Identifier	Identifier(s) by which this encounter is known
status	?! Σ	1..1	code	planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown Binding: Encounter Status ( Required)
class	Σ	0..*	CodeableConcept	Classification of patient encounter context - e.g. Inpatient, outpatient Binding: Encounter class ( Preferred)
priority		0..1	CodeableConcept	Indicates the urgency of the encounter Binding: ActPriority ( Example)
type	Σ	0..*	CodeableConcept	Specific type of encounter (e.g. e-mail consultation, surgical day-care, ...) Binding: Encounter Type ( Example)
serviceType	Σ	0..*	CodeableReference( HealthcareService)	Specific type of service Binding: Service Type ( Example)
subject	Σ	0..1	Reference( Patient | Group)	The patient or group related to this encounter
subjectStatus		0..1	CodeableConcept	The current status of the subject in relation to the Encounter Binding: Encounter Subject Status ( Example)
episodeOfCare	Σ	0..*	Reference( EpisodeOfCare)	Episode(s) of care that this encounter should be recorded against
basedOn		0..*	Reference( CarePlan | DeviceRequest | MedicationRequest | ServiceRequest)	The request that initiated this encounter
careTeam		0..*	Reference( CareTeam)	The group(s) that are allocated to participate in this encounter
partOf		0..1	Reference( Encounter)	Another Encounter this encounter is part of
serviceProvider		0..1	Reference( Organization)	The organization (facility) responsible for this encounter
participant	Σ C	0..*	BackboneElement	List of participants involved in the encounter + Rule: A type must be provided when no explicit actor is specified + Rule: A type cannot be provided for a patient or group participant
type	Σ C	0..*	CodeableConcept	Role of participant in encounter Binding: Participant Type ( Extensible)
period		0..1	Period	Period of time during the encounter that the participant participated
actor	Σ C	0..1	Reference( Patient | Group | RelatedPerson | Practitioner | PractitionerRole | Device | HealthcareService)	The individual, device, or service participating in the encounter
appointment	Σ	0..*	Reference( Appointment)	The appointment that scheduled this encounter
virtualService		0..*	VirtualServiceDetail	Connection details of a virtual service (e.g. conference call)
actualPeriod		0..1	Period	The actual start and end time of the encounter
plannedStartDate		0..1	dateTime	The planned start date/time (or admission date) of the encounter
plannedEndDate		0..1	dateTime	The planned end date/time (or discharge date) of the encounter
length		0..1	Duration	Actual quantity of time the encounter lasted (less time absent)
reason	Σ	0..*	BackboneElement	The list of medical reasons that are expected to be addressed during the episode of care
use	Σ	0..*	CodeableConcept	What the reason value should be used for/as Binding: Encounter Reason Use ( Example)
value	Σ	0..*	CodeableReference( Condition | DiagnosticReport | Observation | ImmunizationRecommendation | Procedure)	Reason the encounter takes place (core or reference) Binding: Encounter Reason Codes ( Preferred)
diagnosis	Σ	0..*	BackboneElement	The list of diagnosis relevant to this encounter
condition	Σ	0..*	CodeableReference( Condition)	The diagnosis relevant to the encounter Binding: Condition/Problem/Diagnosis Codes ( Example)
use		0..*	CodeableConcept	Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) Binding: Encounter Diagnosis Use ( Preferred)
account		0..*	Reference( Account)	The set of accounts that may be used for billing for this Encounter
dietPreference		0..*	CodeableConcept	Diet preferences reported by the patient Binding: Diet ( Example)
specialArrangement		0..*	CodeableConcept	Wheelchair, translator, stretcher, etc Binding: Special Arrangements ( Preferred)
specialCourtesy		0..*	CodeableConcept	Special courtesies (VIP, board member) Binding: Special Courtesy ( Preferred)
admission		0..1	BackboneElement	Details about the admission to a healthcare service
preAdmissionIdentifier		0..1	Identifier	Pre-admission identifier
origin		0..1	Reference( Location | Organization)	The location/organization from which the patient came before admission
admitSource		0..1	CodeableConcept	From where patient was admitted (physician referral, transfer) Binding: Admit Source ( Preferred)
reAdmission		0..1	CodeableConcept	Indicates that the patient is being re-admitted Binding: hl7VS-re-admissionIndicator ( Example)
destination		0..1	Reference( Location | Organization)	Location/organization to which the patient is discharged
dischargeDisposition		0..1	CodeableConcept	Category or kind of location after discharge Binding: Discharge Disposition ( Example)
location		0..*	BackboneElement	List of locations where the patient has been
location		1..1	Reference( Location)	Location the encounter takes place
status		0..1	code	planned | active | reserved | completed Binding: Encounter Location Status ( Required)
form		0..1	CodeableConcept	The physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.) Binding: Location Form ( Example)
period		0..1	Period	Time period during which the patient was present at the location
Documentation for this format