Avanceret UML-klassediagram for hospitalstyringssystemer

Dette omfattende UML-klassediagram modellerer kerne-aktører, enheder og relationer for et moderne hospitalstyringssystem (HMS), der understøtter kliniske, administrative og finansielle arbejdsprocesser.

Aktør-klasser

Patient

+----------------+ 
| Actor: Patient | 
+----------------+ 
* Attributes: 
- PatientID: String 
- Name: String 
- DateOfBirth: Date 
- Gender: Enum 
- Address: Address 
- Phone: String 
- Email: String 
- Insurance: InsurancePolicy 
- EmergencyContact: ContactInfo 
* Operations: 
+ Register() 
+ UpdateProfile() 
+ RequestAppointment() 
+ ViewMedicalRecords() 
+ ViewBillingHistory() 
+ PayBill() 
+ ProvideConsent() 

Læge

+-------------------+ 
| Actor: Doctor | 
+-------------------+ 
* Attributes: 
- DoctorID: String 
- Name: String 
- Specialty: SpecialtyEnum 
- Department: Department 
- LicenseNumber: String 
- YearsExperience: Integer 
- Schedule: Schedule 
* Operations: 
+ DiagnosePatient() 
+ PrescribeTreatment() 
+ PerformProcedure() 
+ ViewPatientRecords() 
+ ManageAppointments() 
+ SignDocumentation() 
+ OrderTests() 

Yderligere aktører

  • Sygeplejerske – Patientpleje, medicingivning, vitaltegn-overvågning, plejeplan-udførelse
  • Administrator – Brugerhåndtering, systemkonfiguration, rapportering, overholdelse
  • Laboratorie-tekniker – Prøvebehandling, resultat-indtastning, kvalitetskontrol-håndtering
  • Farmaceut – Medicin-verificering, udlevering, interaktionskontrol, compounding
  • Faktureringsspecialist – Krav-generering, kodning, afvisningshåndtering, betalingsbogføring

Kerne-enhedsklasser

Afstemning

+----------------------+ 
| Class: Appointment | 
+----------------------+ 
* Attributes: 
- AppointmentID: String 
- PatientID: String 
- ProviderID: String 
- DateTime: DateTime 
- Duration: Integer 
- Type: AppointmentType 
- Status: AppointmentStatus 
- Location: Location 
- Reason: String 
* Operations: 
+ Schedule() 
+ Reschedule() 
+ Cancel() 
+ CheckIn() 
+ Complete() 
+ GetDetails() 

Medicinsk journal

+--------------------------+ 
| Class: MedicalRecord | 
+--------------------------+ 
* Attributes: 
- RecordID: String 
- PatientID: String 
- Encounters: List<Encounter> 
- Diagnoses: List<Diagnosis> (ICD-10) 
- Allergies: List<Allergy> 
- Medications: List<Medication> 
- Immunizations: List<Immunization> 
- ProblemList: List<Problem> 
* Operations: 
+ AddEncounter() 
+ AddDiagnosis() 
+ UpdateProblemList() 
+ GenerateSummary() 
+ ExportCCD() 

Behandling / Plejeplan

+------------------+ 
| Class: Treatment | 
+------------------+ 
* Attributes: 
- TreatmentID: String 
- PatientID: String 
- ProviderID: String 
- Diagnosis: Diagnosis 
- Plan: CarePlan 
- Medications: List<Prescription> 
- Orders: List<Order> 
- Status: TreatmentStatus 
* Operations: 
+ CreatePlan() 
+ UpdatePlan() 
+ AddPrescription() 
+ AddOrder() 
+ GetHistory() 

Fakturering & Økonomi

+----------------+ 
| Class: Bill | 
+----------------+ 
* Attributes: 
- BillID: String 
- PatientID: String 
- EncounterID: String 
- LineItems: List<BillLineItem> 
- TotalCharges: Decimal 
- InsurancePayments: Decimal 
- PatientResponsibility: Decimal 
- Status: BillingStatus 
* Operations: 
+ Generate() 
+ SubmitClaim() 
+ PostPayment() 
+ Adjust() 
+ GenerateStatement() 

Hospital / Organisation

+---------------------------+ 
| Class: Hospital | 
+---------------------------+ 
* Attributes: 
- HospitalID: String 
- Name: String 
- Address: Address 
- Phone: String 
- LicenseNumber: String 
- BedCount: Integer 
- Departments: List<Department> 
- Providers: List<Provider> 
* Operations: 
+ ManageResources() 
+ GenerateReports() 
+ ConfigureWorkflows() 
+ AuditCompliance() 

Nøgle-relationer

  • Patient 1..* — * Afstemning (Patient har mange aftaler)
  • Læge 1..* — * Afstemning (Læge har mange aftaler)
  • Patient 1 — 1 MedicinskJournal (En journal per patient)
  • Kontakt 1..* — * Ordre (Kontakt genererer ordrer)
  • Ordre 1 — 1..* Resultat (Lab/billeddiagnostik-ordrer producerer resultater)
  • Kontakt 1 — 1 Faktura (Hver kontakt genererer fakturering)
  • Hospital 1 — * Afdeling (Hospital indeholder afdelinger)
  • Afdeling 1 — * Udbyder (Afdeling har udbydere)

Anvendte designmønstre

  • Facade: HospitalManagement forenkler subsystems-interaktioner
  • Observer: Afstemnings-notifikationer, kritiske resultat-alarmer
  • Strategy: Faktureringsregler per betaler, planlægnings-algoritmer
  • State: AppointmentStatus, TreatmentStatus, BillingStatus
  • Composite: CarePlan sammensat af Ordre, Mediciner, Mål

Implementeringsnote: Denne model justeres med HL7 FHIR-ressourcer (Patient, Practitioner, Encounter, CarePlan, MedicationRequest, Claim) for interoperabilitet.

Hospitaler