Encounter

Trial Use 4 Clinical — Care Provision

An interaction between healthcare provider(s), and/or patient(s) for the purpose of providing healthcare service(s) or assessing the health status of patient(s).

Endpoints

devhttps://api.sandbox.ovok.com/fhir/R5/Encounter

Interaction	Method	Path
Read	GET	/fhir/R5/Encounter/[id]
Vread	GET	/fhir/R5/Encounter/[id]/_history/[vid]
Update	PUT	/fhir/R5/Encounter/[id]
Patch	PATCH	/fhir/R5/Encounter/[id]
Delete	DELETE	/fhir/R5/Encounter/[id]
Create	POST	/fhir/R5/Encounter
Search	GET	/fhir/R5/Encounter?...
History	GET	/fhir/R5/Encounter/[id]/_history
Type-history	GET	/fhir/R5/Encounter/_history

Top-level elements

Element	Type(s)	Cardinality	Description
identifier	Identifier	0..*	Identifier(s) by which this encounter is known
status	code	1..1	planned
class	CodeableConcept	0..*	Classification of patient encounter context - e.g. Inpatient, outpatient
priority	CodeableConcept	0..1	Indicates the urgency of the encounter
type	CodeableConcept	0..*	Specific type of encounter (e.g. e-mail consultation, surgical day-care, ...)
serviceType	CodeableReference	0..*	Specific type of service
subject	Reference	0..1	The patient or group related to this encounter
subjectStatus	CodeableConcept	0..1	The current status of the subject in relation to the Encounter
episodeOfCare	Reference	0..*	Episode(s) of care that this encounter should be recorded against
basedOn	Reference	0..*	The request that initiated this encounter
careTeam	Reference	0..*	The group(s) that are allocated to participate in this encounter
partOf	Reference	0..1	Another Encounter this encounter is part of
serviceProvider	Reference	0..1	The organization (facility) responsible for this encounter
participant	BackboneElement	0..*	List of participants involved in the encounter
appointment	Reference	0..*	The appointment that scheduled this encounter
virtualService	VirtualServiceDetail	0..*	Connection details of a virtual service (e.g. conference call)
actualPeriod	Period	0..1	The actual start and end time of the encounter
plannedStartDate	dateTime	0..1	The planned start date/time (or admission date) of the encounter
plannedEndDate	dateTime	0..1	The planned end date/time (or discharge date) of the encounter
length	Duration	0..1	Actual quantity of time the encounter lasted (less time absent)
reason	BackboneElement	0..*	The list of medical reasons that are expected to be addressed during the episode of care
diagnosis	BackboneElement	0..*	The list of diagnosis relevant to this encounter
account	Reference	0..*	The set of accounts that may be used for billing for this Encounter
dietPreference	CodeableConcept	0..*	Diet preferences reported by the patient
specialArrangement	CodeableConcept	0..*	Wheelchair, translator, stretcher, etc
specialCourtesy	CodeableConcept	0..*	Special courtesies (VIP, board member)
admission	BackboneElement	0..1	Details about the admission to a healthcare service
location	BackboneElement	0..*	List of locations where the patient has been

Resource-specific search parameters

Parameter	Type	Description
account	reference	The set of accounts that may be used for billing for this Encounter
appointment	reference	The appointment that scheduled this encounter
based-on	reference	The ServiceRequest that initiated this encounter
careteam	reference	Careteam allocated to participate in the encounter
class	token	Classification of patient encounter
date	date	When the event occurred
date-start	date	The actual start date of the Encounter
diagnosis-code	token	The diagnosis or procedure relevant to the encounter (coded)
diagnosis-reference	reference	The diagnosis or procedure relevant to the encounter (resource reference)
end-date	date	The actual end date of the Encounter
episode-of-care	reference	Episode(s) of care that this encounter should be recorded against
identifier	token	Account number
length	quantity	Length of encounter in days
location	reference	Location the encounter takes place
location-period	composite	Time period during which the patient was present at the location
part-of	reference	Another Encounter this encounter is part of
participant	reference	Persons involved in the encounter other than the patient
participant-type	token	Role of participant in encounter
patient	reference	The entity that caused the expenses
practitioner	reference	Persons involved in the encounter other than the patient
reason-code	token	Reference to a concept (coded)
reason-reference	reference	Reference to a resource (resource reference)
service-provider	reference	The organization (facility) responsible for this encounter
special-arrangement	token	Wheelchair, translator, stretcher, etc.
status	token	planned
subject	reference	The patient or group present at the encounter
subject-status	token	The current status of the subject in relation to the Encounter
type	token	E.g. patient, expense, depreciation

Reference

• Official FHIR R5 spec: Encounter
• Maturity: Trial Use 4 (FMM 4).