Class TEncounter
Unit
bsFhir_r4b
Declaration
type TEncounter = class(TDomainResource)
Description
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. If the element is present, it must have either a @value, an @id, or extensions
Hierarchy
Overview
Methods
Properties
Description
Methods
 |
constructor Create; override; |
|
|
Properties
|
property identifier : TIdentifierArray read GetidentifierArray; |
|
Identifier(s) by which this encounter is known.
|
|
property status : string read Getstatus write Setstatus; |
|
planned | arrived | triaged | in-progress | onleave | finished | cancelled +.
|
|
property statusElement : TEncounterStatus read GetstatusElement write SetstatusElement; |
|
|
|
property statusHistory : TEncounterStatusHistoryArray read GetstatusHistoryArray; |
|
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.
|
|
property class_ : TCoding read Getclass_ write Setclass_; |
|
Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.
|
|
property classHistory : TEncounterClassHistoryArray read GetclassHistoryArray; |
|
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.
|
|
property type_ : TCodeableConceptArray read Gettype_Array; |
|
Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).
|
|
property serviceType : TCodeableConcept read GetserviceType write SetserviceType; |
|
Broad categorization of the service that is to be provided (e.g. cardiology).
|
|
property priority : TCodeableConcept read Getpriority write Setpriority; |
|
Indicates the urgency of the encounter.
|
|
property subject : TReference read Getsubject write Setsubject; |
|
The patient or group present at the encounter.
|
|
property episodeOfCare : TReferenceArray read GetepisodeOfCareArray; |
|
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).
|
|
property basedOn : TReferenceArray read GetbasedOnArray; |
|
The request this encounter satisfies (e.g. incoming referral or procedure request).
|
|
property participant : TEncounterParticipantArray read GetparticipantArray; |
|
The list of people responsible for providing the service.
|
|
property appointment : TReferenceArray read GetappointmentArray; |
|
The appointment that scheduled this encounter.
|
|
property period : TPeriod read Getperiod write Setperiod; |
|
The start and end time of the encounter.
|
|
property length : TDuration read Getlength write Setlength; |
|
Quantity of time the encounter lasted. This excludes the time during leaves of absence.
|
|
property reasonCode : TCodeableConceptArray read GetreasonCodeArray; |
|
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
|
|
property reasonReference : TReferenceArray read GetreasonReferenceArray; |
|
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
|
|
property account : TReferenceArray read GetaccountArray; |
|
The set of accounts that may be used for billing for this Encounter.
|
|
property hospitalization : TEncounterHospitalization read Gethospitalization write Sethospitalization; |
|
Details about the admission to a healthcare service.
|
|
property location : TEncounterLocationArray read GetlocationArray; |
|
List of locations where the patient has been during this encounter.
|
|
property serviceProvider : TReference read GetserviceProvider write SetserviceProvider; |
|
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.
|
|
property partOf : TReference read GetpartOf write SetpartOf; |
|
Another Encounter of which this encounter is a part of (administratively or in time).
|
Generated by PasDoc 0.15.0.
|