Class: Patient

Description of: Patient

Class steward is Patient Administration
Interested committees Orders/Observation
A person who is subject to receive, is receiving, or has received Healthcare services.

OpenIssue: This is really the state of the relationship between other stakeholder classes, or other classes not in the stakeholder tree. Context of state is unclear. May have something to do with structural changes in the RIM. May be a throwaway. May also be a methology issue. See minutes for 6/99.

Association definitions for: Patient

is_requested_by (0,n) :: Patient_appointment_request :: requests (1,1)

has_a_primary_provider (0,1) :: Individual_healthcare_practitioner :: is_the_primary_provider_for (0,n)

participates_in (0,n) :: Preferred_provider_participation :: has_as_care_recipient (1,1)

is_scheduled_by (0,n) :: Patient_slot :: is_a_scheduleable_unit_for (1,1)

is_a_role_of (1,1) :: Person :: takes_on_role_of (0,1)

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

has (0,n) :: Healthcare_benefit_coverage_item :: is_for (1,1)

Rationale: This class now contains the attributes of a "master" class and therefore is not associated with an individual patient.

is_insured_by (0,n) :: Master_healthcare_benefit_product :: insures (0,n)

OpenIssue: Is the fully optional many-to-many on both ends correct?

has (0,n) :: Patient_billing_account :: belongs_to (1,1)

has_as_primary_facility (0,1) :: Master_patient_service_location :: is_primary_facility_for (0,n)

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

has (0,n) :: Health_chart :: belongs_to (1,1)

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

has (0,1) :: Administrative_patient_death :: pertains_to (1,1)

is_known_by (1,n) :: Patient_provider_association :: identifies (1,1)

The relationship between a person and a healthcare provider organiztion by which a person establishes a patient relationship to a healthcare provider association.

OpenIssue: Consider merging Patient and Patient_provider_association into a single class, or at least consider changing the name to encompass numbers.

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

Rationale: 2.3 abstract message definition

OpenIssue:

has_as_a_contact (0,n) :: Contact_person :: is_a_contact_for (0,1)

OpenIssue: Review/explain cardinatlity

OpenIssue: The same person can be a contact for more than one patient and a patient can have more than one contact persons.