QICoreEncounter

This is basic constraint on Encounter for use in US Core resources.

= Must Support, = Is Modifier, = QiCore defined extension

Field	Card.	Type	Description
statusReason	0..1	Extension	Captures the reason for the current state of the resource.
procedure	0..*	List<Extension>	Procedures performed during the encounter, or as the primary reason for the encounter.
identifier	0..*	List<Identifier>	Identifier(s) by which this encounter is known.
status	1..1	String	planned | arrived | triaged | in-progress | onleave | finished | cancelled +. Binding: Current state of the encounter. (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.
class	1..1	Code	Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. Binding: Classification of the encounter. (extensible)
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 transitions 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 kind of discharge from emergency to inpatient.
type	1..*	List<Concept>	Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Binding: Valueset to describe the Encounter Type (extensible)
serviceType	0..1	Concept	Broad categorization of the service that is to be provided (e.g. cardiology). Binding: Broad categorization of the service that is to be provided. (example)
priority	0..1	Concept	Indicates the urgency of the encounter. Binding: The priority of the encounter (e.g., Urgent, Normal, etc.) (preferred)
subject	1..1	QICorePatient	The patient or group present at the encounter.
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).
basedOn	0..*	List<QICoreServiceRequest>	The request this encounter satisfies (e.g. incoming referral or procedure request).
participant	0..*	List<participant>	The list of people responsible for providing the service.
appointment	0..*	List<Appointment>	The appointment that scheduled this encounter.
period	0..1	Interval<DateTime>	The start and end time of the encounter.
length	0..1	Duration	Quantity of time the encounter lasted. This excludes the time during leaves of absence.
reasonCode	0..*	List<Concept>	Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. Binding: Reason why the encounter takes place. (preferred)
reasonReference	0..*	List<QICoreCondition | QICoreProcedure | QICoreObservation | QICoreImmunizationRecommendation>	Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
diagnosis	0..*	List<diagnosis>	The list of diagnosis relevant to this encounter.
diagnosisPresentOnAdmission	1..1	Extension	Indicator of whether the Encounter diagnosis was present at the time of admission.
account	0..*	List<Account>	The set of accounts that may be used for billing for this Encounter.
hospitalization	0..1	hospitalization	Details about the admission to a healthcare service.
location	0..*	List<location>	List of locations where the patient has been during this encounter.
serviceProvider	0..1	QICoreOrganization	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.
partOf	0..1	QICoreEncounter	Another Encounter of which this encounter is a part of (administratively or in time).