Based on the mini-world below, a Class Diagram was modeled on the Astah Community (free version with less features than the professional for non-commercial use: link - Formerly this program had the name of JUDE)
Mini World / Scenery :
Managing patient information and appointment marking is essential for the organization of clinic and office processes. Many of these do not yet have the automation required to make appointment marking and access to medical records efficient, which creates problems for attendants, physicians, and those who need care. This makes it necessary to have a system that is capable of streamlining and managing query schedules, as well as access to medical records.
Goal: Develop a generic consultation scheduling system for clinics and clinics that share attendants, with the primary focus being the scheduling of appointments and a secondary focus of patient access to medical records online.
Features that the system should have:
- Registry of Attendants, Physicians, Specialties, Patients and Covenants.
- Scheduling queries.
- Dissemination of results of exams and medical records online.
- Available to the attendant: Query enrollment and scheduling functions.
- Available to the doctor: Access to the appointments marked for your own and your patients' medical records.
- Available to patient: Access to your medical records / test results online.
(thanks to @Jeferson Almeida and @Randrade for the idea of including the mini-world to facilitate understanding of the proposed modeling system)
Class Diagram
From this diagram, I would like to see if the following readings can be deduced:
In the X Query relationship:
-
1 attendant schedules 0 or more queries.
-
1 query is scheduled by 1 attendant.
In the Patient X Patient relationship:
-
1 covenant has 0 or more related clients.
-
1 patient has 1 or more covenants. (thanks to the comment from @Jeferson Almeida)
In relation Agreement X Consultation (Patient vs. Consultation x Agreement):
-
1 Agreement covers an indeterminate number of Queries
-
1 Consultation is covered by 0 (private consultation) or 1 Agreement (thank the remark of @ Bonifazio and @Washington of the coast)
In relation Patient X Consultation (Patient vs. Consultation x Agreement):
-
1 patient has scheduled none (if it has just been included) or multiple queries.
-
1 query is scheduled for 1 patient.
In the Consultation X Record :
-
1 query will have at its end 1 medical record (and none while it has not been performed).
-
1 medical record comes from 1 query.
In the Medical X Inquiry relationship:
-
1 Consultation will be performed by 1 Doctor.
-
1 Doctor may have performed none (if just logged in to the system) or multiple queries.
In relation Medical X Medical :
-
1 Medical record is prepared by 1 Physician.
-
1 Doctor may have compiled several Medical Records.
In the Specialty X Doctor relationship:
-
1 Physician has 1 or more Specialties. (thanks to @leonardopessoa's remark)
-
Many doctors can have the same specialty.
Is this Class Diagram correct? Is everything okay?
If the modeling is appropriate, it is set as an example for future users who have questions about modeling UML Class Diagrams. If not, please show the problems!
Any input is welcome. Thank you.