Skip to content

Latest commit

 

History

History
114 lines (113 loc) · 5.67 KB

File metadata and controls

114 lines (113 loc) · 5.67 KB

RegMed

Medical Registration Application, wrote in javaFX

System specification:

  1. Application should have few modules:
  2. Patient have access to Patient module
  3. Doctor have access to Doctor module
  4. Administrator have access to All modules
  5. Possibility to generate raports

User administration module:

  • Managing accounts (patient, doctor, administrator): Adding, Removing, Editing
  • Adding new doctor specializations

Report module:

This module is responsible for creating a pdf files.

  • Generating prescriptions -> P
  • Generating referral -> P
  • Generating patient documentation -> P
  • Generating list of patients -> D
  • Generating schedule -> D
  • Generating logs report -> A
P-patient, D-doctor, A-administrator

Configuration module:

This module simplifying database configuration.

  • DB localization
  • Username
  • Password
  • DB name

Target and scope of system:

System will be used to register patient and keeping his medical documentation like history of health state, diseases and health benefits. During creating account patient must choose his first contact doctor. After create account and log in patient have possibility to choose day and hour of visit to the doctor.
During the visit doctor filling in the patient file in system, after diagnosis can write and print a prescription or make a referral in a different manner unlock in patient panel possibility to register to Specialist Doctor. Also the doctor can set days and hours of admission. Additionally doctor will have possibility to create list of patients and weekly schedule.
Only administrator of system have access to add, edit or remove doctors, and create a new specialization.

Stakeholders: medical clinics, hospitals and private medical practices.

Types of reports:

  • Patient:
    • Perscriptions (An instruction written by a medical practitioner that authorizes a patient to be provided a medicine or treatment.)
    • Refferals (Referring for consultation, review, or further action.)
    • Documentation (Provides official information or evidence or that serves as a record.)
  • Doctor:
    • List of patients (List of people assigned to visit a selected doctor.)
    • Schedule (Plan for carrying out a process or procedure, giving lists of intended visit and events.
  • Administrator:
    • Logs report (It's raport with chronological record containing information about events and activities concerning the computer system.

Information in this system will be transmitted and processing only local or using intranet.
Users permissions:

  • Patient: Patients using the program can register themselves for an appointment with a selected doctor, have access to the history of their visits to the hospital.
  • Doctor: Has the ability to administer visits in his office. The doctor has access to the history of treatment of the patient connected with him.
  • Administrator: The administrator has access to the entire database, has full control over the patient's records and data. He can freely change and control visits in the doctor's office. Due to access to sensitive data, the system administrator should be covered by the confidentiality clause.

Hardware requirements:

System for propertly working need:

  • Kiosks - will be used by patients for register to doctor, specialist, or for create their account
  • PC/laptops - for doctors and administrators, which they will be use for handle their system functionalities
  • Printers - will print generated pdf-s.
  • Local (internal) network - for proper communication between computers, printers, and different medical clinics if they will be using our system

Unfunctional requirements:

  • System must be adapted to the provisions of Polish law
  • System must be fully configured and thusready to implementall the required functionalities.
  • System must meet the security requirements for user access to system resources through the use of user authentication mechanisms
  • System must provide resources protection against unauthorized access from outside and inside the system
  • System should be scalable
  • System must provide mechanisms for granting access rights, enabling selected users to selectively access information
  • System must have a Polish language interface of the user
  • System must function in accordance with the teleinformatic network of the clinic
  • System must be comprehensive, it must perform all the functions and activities required by the Employer

UML

Use Case Diagram:

Sequence Diagram:

Class Diagram:

State Diagram UML:

Database ERD Diagram: