Class: Patient_encounter

Description of: Patient_encounter

Class steward is Patient Administration
Interested committees Orders/Observation
An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.

OpenIssue: This MUST be discussed with Patient Care in the context of Episode and Service Event definitions. Episode and Encounter definitions needs to be discussed.

Attribute definitions for: Patient_encounter

administrative_outcome_txt

Type of further action, if any, planned as part of the care of the patient (e.g., appointment given, appointment to be given, admission arranged, patient admitted, . . .).

cancellation_reason_cd

A code depicting the reason for cancellation of an encounter.

confidentiality_constraint_cd

A code indicating the level of publicity allowed for external release about a patient encounter. Examples are no publicity, family only, no publicity constraint.

|PV2^21^00722^Visit Publicity Code|

desc

A textual description of the patient encounter.

|PV2^12^00713^Visit Description|

encounter_classification_cd

A classification of a patient encounter.

|PV2^7^00187^Visit User Code|

end_dttm

The date and time that the patient encounter ends.

|PV1^45^00175^Discharge Date/Time|

expected_insurance_plan_qty

A count of the number of insurance plans that may provide Healthcare benefit coverage for this patient encounter.

|PV2^20^00721^Expected Number of Insurance Plans|

first_similar_illness_dt

The date the patient first experienced a similar illness. Used to determine pre-existing conditions

|PV2^29^00730^First Similar Illness Date|

follow_up_type_cd

A code indicating the type of follow-up required after completion of the patient encounter.

id

A unique identifier assigned to the patient encounter.

|PV1^19^00149^Visit Number| |PV1^50^00180^Alternate Visit ID|

medical_service_cd

A type of medical management area in which care is scheduled to be delivered.

OpenIssue: This may need to be a repeating field with a type code to differentiate the entries to clarify scheduled, actual, administrative, etc. Clarify how this code is relevant to purpose_cd.

patient_classification_cd

This field contains site-specific values that identify the type of patient, for example, outpatient surgery, inpatient short stay, etc.

OpenIssue: Current x-ref is from Patient Type and Patient Class. Should this be two attributes?

|FT1^18^00148^Patient Type| |PV1^2^00132^Patient Class| |PV1^18^00148^Patient Type|

purpose_cd

A code depicting the purpose of the patient encounter.

record_signing_dttm

The data and time the documentation of the patient encounter is signed.

special_courtesies_cd

A code identifying special courtesies extended to the patient. For example, no courtesies, extended courtesies, VIP courtesies.

|PV1^22^00152^Courtesy Code|

start_dttm

The date and time that the patient encounter begins.

status_cd

A code depicting the status of the patient encounter.

|PV2^24^00725^Patient Status Code|

transport_requirement_cd

A code depicting the type of transportation required or arranged for the transport of the patient (e.g., stretcher, wheelchair, ambulance, taxi, . . .).

triage_classification_cd

The triage classification of the patient during an encounter.

Rationale: This attribute is related to an encounter rather than to the patient in general

urgency_cd

A code depicting the urgency of the patient encounter.

|PV2^25^00726^Visit Priority Code|

Association definitions for: Patient_encounter

is_authorized_by (0,1) :: Preauthorization :: authorizes (1,n)

involves (1,1) :: Patient :: is_involved_in (0,n)

follows (0,n) :: Patient_encounter :: precedes (0,1)

has (0,n) :: Administrative_patient_accident :: is_present_in (1,n)

Rationale: Allows removal of generalization (patient_clinical_item) with single specialization

is_scheduled_by (0,n) :: Appointment :: schedules (1,n)

has_assigned_to_it (0,n) :: Service_event :: is_assigned_to (0,1)

Rationale: Establish independence of service events from encounters.

is_preceded_by (0,1) :: Patient_arrival :: precedes (1,1)

has (0,n) :: Risk_management_incident :: pertains_to (1,1)

precedes (0,1) :: Patient_encounter :: follows (0,n)

has (1,n) :: Location_encounter_role :: pertains_to (1,1)

has_as_participant (1,n) :: Encounter_practitioner :: is_associated_with (1,1)

Whole-part definitions for: Patient_encounter

has_parts (0,n) :: Administrative_birth_event :: is_part_of (1,1)

is_part_of (1,1) :: Episode :: has_parts (1,n)