Billing module The Patient Billing module handles all types of billing for long-term care. This module facilitates cashier and billing operations for different categories of patients like Outpatient, Inpatient and Referral. Therefore in this module: The system should provide automatic posting of charges related to different services like bed charges, lab tests conducted, medicines issued, consultant’s fee, food, beverage and telephone charges etc. ;The system should be flexible to allow billing plans to be configured to automatically accept or deny. be tuned to enable this module to capture room and bed charges along with ancillary harass based on the sponsorship category. ; The system should record the charges for various services rendered. ; The system should display payment details. The system should display reports and have a printing option. C )Payroll Module The system should calculate total employee salary including reductions and allow the employer to, print salary slips and salary certificates ; The system should produce IF statements, Gratuity Statements and also provide a monthly analysis. Since the module deals with the maintenance of employee bio-data, the system should keep employee bio data including Attendance / Overtime details. It should also report on absenteeism or leave encasements of an employee. ;The system should permit the department to conduct Employee Related Activities like appointing the staff, maintaining the employee database, Fixing allowances and deductions, Maintenance of Hospital documents, etc. D. Outpatient Management module The outpatient module serves as an entry point to schedule an appointment with the hospital resident doctor or consultant doctor for medical consultations and diagnosis. In this module: The system should provide instant access to comprehensive patient information to and record the appropriate details if any. The system should handle the modules requests and results of laboratory tests and other examinations. ; The system should define external doctor’s visit to in patients as “call on”. ; store patient’s diagnosis details.
The system should provide a record of patient’s appointments. ; The system should store outpatient medical observation details. ; The system should provide a report on outpatient Treatment History. ; The system should store the out patients clinical service details and common billing clinical services of the patient ; The system should support online prescription, online request for Investigations and so n. ; The system should calculate the cost for the services rendered to the patient and reflect it in the billing module appropriately resulting in smooth billing process.
E) Inpatient Management module The inpatient module is designed to take care of all the activities and functions pertaining to Inpatient Management. Therefore: The system should allow this module to automate the day-to-day administrative actives and provides instant access to other modules, which leads to a better patient The system should provide comprehensive data pertaining to Admission of care. ; Patients & Ward Management: Availability of beds, Estimation, Agreement preparation, Collection of advance, planned admission, Emergency admission and so on. The system should enable this module to support Ward Management involving the system recording details off patient being shifted from one ward to the other. ; The system should display and be able to keep a record of the number of available beds ; The system should monitor the administration of drugs. The system should display the details of when a doctor is to be or transferred. ; The system should display requests regarding admission, drugs and also display pending requests. The system should keep and display record of patients that are to be or have been discharged; the details should include the expected or the Date and Time of Discharge. ; The system should allow the module (department) to track every visit made by a patient. F) Pharmacy module Pharmacy module deals with the automation of general workflow and administration management process off pharmacy. ; The system should allow purchasing of orders. The system should store supplier’s information The system should allow online request for stock from various sub-stores and online stock transfer. The system should maintain the drug inventory. The system should record and allow users to view the expiring date of items. ; The system should produce a goods receipt. 4. Nonfunctional requirements. Non-functional requirements define the overall qualities or attributes of the resulting system. Performance Requirements Performance requirements define acceptable response times for system functionality. ; The load time for user interface screens shall take no longer than two seconds. ; The log in information shall be verified within five seconds.
Security Through permitting the changing access permissions for the system data to only be one by the system’s data administrator ;All system data must be backed up every 24 hours and the backup copies stored in a secure location which is not in the same building as the system Reliability The system should perform its required functions under stated conditions if any. ; The system should have a low rate of failure to deliver the services required by end users. Maintainability: The system should be able to cope with the changing of technology.
Size The system should not occupy a large amount of memory disk space. Robustness. After a failure the system should have a backup to assist in immediately functioning as required. 5. Usability requirements Some of the systems usability requirements should include: Informative error messages for example when a record is missing and should be inputted or when incorrect data ; The system should offer help facilities for users who require further assistance or understanding when using the system. ; The system should have well-formed graphical user interfaces. The time needed to be taken for users to learn the facilities of the system. ; How satisfied are the users with the system can be measured by taking a survey. 6. Domain requirements Domain requirements are the requirement that comes from the application domain f the system that reflects the characteristics of that domain. Therefore, as this System is a hospital management System, the domain requirement of this system should concern about the requirements that reflect characteristic of hospital management system.
Our hospital management System should contain the characteristics below: ; The hospital management system must have basic functions: storing, tracking, updating and must be able to generate and display reports also records or details of patients, doctors, medical alerts, doctor’s schedules lists and so Every operation that occurs in the hospital management system must concern f Data Integrity.