Software Requirements(Softeng).docx

7/28/2019 Software Requirements(Softeng).docx

1/32

MEDICAL RECORDS AND BILLING SYSTEM OF MEDCREST MULTIPSPECIALTYDIAGNOSTIC CLINIC

Faculty of Computer Studies DepartmentCavite State University Imus Campus

Imus, Cavite

In Partial FulfillmentOf the Requirements for the subject ITEC55B

System Analysis and Design

Rina E. TabamoJayson Philbert Ted C. Maaol

Ceferino Rio

2013


2/32

Software Requirements Specification of MedicalRecords and Billing System for Medcrest

Multispecialty Diagnostic Clinic

1. Introduction

1.1 Goals and objectives1.2 Statement of scope1.3 Software context1.4 Major constraints

2. Usage scenario

2.1 User profiles2.2 Use-cases

2.2.1 Use-Case Diagram2.2.2 Use-Case Descriptions

2.3 Special usage considerations2.4 Activity Diagrams

3. Data Model Description

3.1 Data objects

3.2 Relationships3.3 Complete data model

4. Functional Model Description

4.1 Class diagrams4.2 Software Interface Description

4.2.1 External machine interfaces4.2.2 External system interfaces4.2.3 Human interface

5. Behavioral Model Description

5.1 Description for software behavior

5.1.1 Events5.1.2 States

5.2 Statechart Diagram

6. Restrictions, Limitations, and Constraints


3/32

7. Validation Criteria

7.1 Classes of tests7.2 Expected software response7.3 Performance Bounds

1. Introduction

1.1 Goals and objectives

The purpose of this document is to describe requirements for the Medical records and Billing software that willserve as a foundation for the final product. It is important that an agreement of these requirements be reached so

that everyones expectations will be met. This document uses written descriptions as well as various types of

modeling diagrams to illustrate the high level structure of the application. Although some of these diagrams mayseem to convey similar information they typically do so from an alternate perspective. This gives differentstakeholders a view of the requirements that is better suited to their area of responsibility.

A Land based solution will be delivered so that even though there is no internet connection the system can still beused. Visual Basic 6 programming language will be use because it is user friendly for the users and easy tomaintain. Microsoft Access will be used to store information and it is the main database container for the medical

records of the patient and their billings.

The Medical Records and Billing System is intended to provide a computer based system that will assist inmanaging a diagnostic clinic. Many of the typical functions involved in operating a Diagnostic clinic will beautomated through software to improve the operational workflow within the facility. The system is expected to helpMedcrest Multispecialty Diagnostic Clinic because of its ability to automatically compute the patient's bills,generates reports and official receipt that surely fasten their transactions with the patients. Laboratory proceduresand other procedures will be updated and presented in precision. With the help of this proposed computerizedsystem the Medcrest Multispecialty Diagnostic Clinic can easily keep track and maintain each patient's information.

1.2 Statement of scope

This section contains a general description of the software functionality followed by detailed requirements that willbe traced throughout the project.

Before gaining access to the Medical Records and Billing system an employee will be required to enter their username and password. An employees access privileges within the system are determined by their job classification.

All the medical staff has the authority to access the system.

After inputting it will track the services that each patient undergoes. This system also includes the billing system ofthe Medcrest Multispecialty Diagnostic Clinic; the automated calculation of patients total payment, change andprinting of receipt.

This system tries to eliminate the manual patient monitoring and billing system that is currently used by MedcrestMultispecialty Diagnostic Clinic. All information from the transaction of a patient will be recorded, even thelaboratory procedures and medicines. With this information, the patient bills will be automatically computed andgenerated.

The system also includes Discounts and other privileges in the billing process. The system does not include thepayroll of employees.


4/32

User Requirements for Medcrest Multispecialty Diagnostic Clinic Software Project

Req. No. Priority Reference Description

Access Privileges

R1 High Customer There shall be log-in for the medical staff

R2 High Customer The medical staff shall only be allowed to enter or

edit medical records.

R3 Med Customer Only the medical staff shall be allowed to view or

print reports.

R4 High Customer All the medical staff shall be allowed to issue printed

billings of patient.

Security

R5 High Customer Each user shall be required to log on with a uniqueuser name and password before using the system. The

password does not need to be unique.

R6 Low CodeWorks The user name shall be their position and theirpassword will be their desire words or characters.

R7 High Customer A password shall be assigned to each user.

R8 High Customer The password shall contain 6 to 8 alphanumeric

characters.

R9 Med Code

Works

After three unsuccessful attempts to enter a password

the user shall be locked out of the system until their

password is reset.

R10 High Customer The administrator can view the username and

password of all the users and if a user forgot its

password only the administrator can view it.

TransactionsR11 High Customer The administrator, cashier and staff of the Clinic can

have the authority to transact to the customer or

patient.

R12 Low CodeWorks

The cashier can print the billing reports of the patientor customer.

R13 Med Code

Works

The cashier, staff and administrator can add

transaction made by the patient or customer.

Billing

R14 High Customer A Billing receipt will be received by the patient orcustomer upon payment.

R15 High Customer Any of the three users can issue a receipt for the

patient or customer.

R16 High Customer There is a discount for the senior, laboratory to

laboratory patients and doctors who will transact to

the clinic.

R17 High Customer All of the billing of the patient will be recorded.


5/32

R18 High Customer Products that have been purchased by the patient or

customer will be printed in the receipt.

R19 High Customer Transactions that have been made by the patients will

be printed in the receipt.

R20 High Customer All the transaction and purchased products will be

listed in the receipt including the discount of thepatients or customer.

Reports

R21 High Customer A Patient List shall view the customers

alphabetically by last name and include their address

and contact number.

R22 High Customer A Medical Test List shall alphabetically list the all

the medical test done by the clinic.

R23 High Customer A Patient Report can view the list of patients that are

include in the clinic and prints its Name, age andaddress.

R24 High Customer A Daily Sales Report can be view to know theincome of the clinic in a specific day.

R25 High Customer A Modified Sales Report can be view to know the

income of the clinic from a date to the specific date.

R26 High Customer The User Account shall list all the users in the system

according to their UserID. It includes adding, editingand deleting of user accounts. Only the administrator

has the authority to view it.

R27 High Customer The Med Techs Accounts can be viewed to know all

the listed medical technician or doctors that are in theclinic.

Account Information

R28 Med Customer When a user edits an account their user ID along withthe password, username and other information shall

be recorded in the database.

R29 High Customer The Patients record shall contain the following

information:

1. Name

2. Gender

3. Contact Number

4. Age

5. Civil Status

6. Address


6/32

R30 High Customer The Users record shall contain the following

information:

1. Name2. Username

3. Password4. LogIn Type

R31 High Customer The software shall support the ability to enter, store,and update patients and billing information.

User Interface

R32 High Customer The system shall have a Land based interface that

works with Visual Basic 6.

R33 High Customer There are different kinds of colors in all windows.

R34 High Customer The system shall respond to all user requests within

10 seconds.

1.3 Software context

Today, computerization is a major advancement in technology that helps in many ways: it makes informationstorage easier and faster thus it can save a lot of time and manpower, and many tasks are done in a certainamount of time.

Great amount of time is being consumed by information retrieval and the billing process of most Diagnostic Clinicswithout computer generated system is slow. To be able to provide the medical needs of the rapidly growingpopulation, Diagnostic Clinics must be versatile to the current trends and innovation in today's changes intechnology.

One of the concerns of Medcrest Multispecialty Diagnostic Clinic is how to lessen the number paper works in havinga transaction with the patient that could fasten the process of admission, discharging and billing of a patient. Thisgreatly affects the profitability of the institution that makes the admission and billing of patients a long process.

Another concern is how to extend the accuracy in computing the patient bills, which is very essential in MedcrestMultispecialty Diagnostic Clinic. Because some patients are so smart that they can find a way that they do not haveto pay the Clinic bills. Some are having a difficulty in paying because of the slow process of computation which cantake less or more than a month depends on the number of laboratory procedures or other cases.

Observing the institution; the researchers decided to propose a computerized medical records and billing systemthat is intended to solve the concerns that they discovered. Efficient medical records and billing managementgreatly affect Medcrest Multispecialty Diagnostic Clinic such as medical services, billing policies and price rates.With the help of this proposed computerized system the Medcrest Multispecialty Diagnostic Clinic can easily keeptrack and maintain each patient's information.

The computerized medical records and billing system is expected to help Medcrest Multispecialty Diagnostic Clinicbecause of its ability to automatically compute the patient's bills, generates reports and official receipt that surelyfasten their transactions with the patients.


7/32

1.4 Major constraints

The Medical records and Billing system will use Microsoft Visual Studio 6 or Visual Basic 6 which is fit toreplaced the current client manual system.

2. Usage scenario

2.1 User profiles

The following definitions describe the actors in the system.

Administrator An administrator has the responsibility for registering new customers and user

accounts. They have unrestricted access to the Medical Records and Billing System

including viewing and changing passwords.

Cashier A Cashier has the responsibility to handle payment of patients and customers and has

the authority to issue a receipt.

Employee An employed is the general name that refers to an administrator, cashier, or med

tech.

Patient The patient is a customer of the Medcrest Multispecialty Diagnostic Clinic. They are

the one who get medical test.System The system refers to the computer hardware and software that controls the

application. It accepts user input, displays user output, and interfaces.

Customer A customer is the one who purchased medicine or other products from the Medcrest

Multispecialty Diagnostic Clinic.

Microsoft

Visual Basic 6

is the third-generation event-driven programming language and integrated

development environment (IDE) from Microsoft. It is known for its COM programming

model. VB is also considered a relatively easy to learn and use programming language,

because of its graphical development features and BASIC heritage.
http://en.wikipedia.org/wiki/Third-generation_programming_languagehttp://en.wikipedia.org/wiki/Event-driven_programminghttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Component_Object_Modelhttp://en.wikipedia.org/wiki/BASIChttp://en.wikipedia.org/wiki/BASIChttp://en.wikipedia.org/wiki/Component_Object_Modelhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Event-driven_programminghttp://en.wikipedia.org/wiki/Third-generation_programming_language


8/32

2.2 Use-cases

The following use-cases are typical interactions between the external environment and the

internal software system. Each use-case is described in section 2.2.2.

1. Log onto system

2. Add patient information.3. View List of Test

4. Billing Reports

5. View List of Patients6. Transaction

7. Add Transaction to the patients

8. Enter Transaction

9. Print Receipt Bill

10. Add or view User Accounts11. Add or view Med Tech Accounts

2.2.1 Use-Case Diagram

The use-case diagram in

Figure 1 shows four actors that were described in section 2.1. In order to minimize the

complexity of this diagram several connections were left out. For instance, every use-case will

typically involve an interaction with the System and Database, but since this is a secondaryactivity it is not shown in the drawing. The Employee could be an administrator, cashier or clinic

staff. Instead of drawing separate connections to each of these actors, the Employee was added to

make the diagram easier to read.


9/32

Figure 1 : Use- Case Diagram of Medical Records and Billing System of Medcrest Multi-specialty

Diagnostic Clinic


10/32

2.2.2 Use-Case Descriptions

Use-case: Log on to System

Primary actor: Employee

Goal in context: To gain access to the System

Preconditions: The employee has a valid user name and passwordTrigger: An Employee needs access to the System to perform their job

Scenario: 1. The System prompts the employee for their user name and password.2. The Employee enters their user name and password.

3. The System sends the user name to the Database.

4. The System verifies the username and password and sets the users

authorization.

6. The Employee is given access to the System to perform their job.

Exceptions: The user name and password cannot be verified

Use-case: Add Patient InformationPrimary actor: Administrator

Goal in context: To add a patient information into the database.

Preconditions: 1. Patients must undergo transaction2. Patients should go directly to the administrator of the Clinic to be added in the

database.

Trigger: Patient undergo test of medical examination to know their health status.

Scenario: 1. A Patient undergoes a medical test.

2. The Administrator logs onto the System.

3. The Administrator selects New Account from the Main menu.

4. The Administrator add information of the patient

6. A new account is created.7. Patient information is entered into the System.

8. The System sends the account information to the Database.

9. The Patient verifies the information added in the system.

Exceptions: The system has reached its capacity of adding patients.

Use-case: View List of Test

Primary actor: Administrator

Goal in context: To retrieve medical test information.

Preconditions: The user has a valid password

Trigger: An admin has an event that they need to be reminded ofScenario: 1. The admin logs onto the System.

2. The admin selects Master Files from the Menu Bar.

3. The admin selects List of Patients.

4. The System will open the list of Medical Test.

5. A printed report will display on the screen.

Exceptions: The medical test records are not there.


11/32

Use-case: Billing Reports


Goal in context: To show the sales report of the Clinic

Preconditions: A income of the Clinic should be recorded

Trigger: The date of a reminder is the current dateScenario: 1. The Administrator logs onto the System.

2. The Administrator selects Reports from the Menu Bar.

3. The Administrator selects Billing Report.

4. The System will open the window of Billing Report.

5. The Administrator will choose daily sales report or modified sales report.

6. The Administrator can print the Billing Report of the Clinic.

Exceptions: The sales report will not display any sales if no income.

Use-case: View List of PatientsPrimary actor: Administrator

Goal in context: To retrieve account information

Preconditions: The account exists

Trigger: An administrator needs information from one of their accounts

Scenario: 1. The admin logs onto the System.2. The admin selects Reports from the Menu Bar.

3. The admin selects List of Patient.

4. The System requests the record from the Database.

5. A report of the record is displayed on the screen.

Exceptions: The account does not exist

Use-case: Transaction

Primary actor: Med tech /employee

Goal in context: To manage the transaction of the Patient

Preconditions: The patient should avail any of the medical test to be added in transaction

Trigger: A patient avails in a medical test.

Scenario: 1. The med tech/employee logs onto the System.2. The med tech/employee selects Transaction from the Menu Bar.

3. The System prompts for the name of the Patient.

4. The System requests the record from the Database.

5. A form for adding transaction is displayed on the screen.6. The med tech/Employee input the appropriate fields.

7. The med tech confirms the selected medical test to the patient.

8. The System sends the updated record to the database for storage.

9. The med tech will be prompt by the system if he/she wants to print a receipt

bill.

10. The med tech/employee receives confirmation that the information was saved.

Exceptions:


12/32

Use-case: Add or View User Accounts


Goal in context: To add user account or to view.

Preconditions: Only a employee of the Clinic can have a user accountTrigger: A new employee is hired by the Clinic.

Scenario: 1. The Administrator logs onto the System.2. The Administrator selects Tools from the Menu Bar.

3. The Administrator selects User Account.

4. The System will display the list of all user accounts.

5. The Administrator shall decide if to add, edit or delete a user account.

6. If the Administrator selects Add, a window will pop up showing information to

be input in the appropriate fields

7. The system will add all the information of the user account created by the

Administrator including the Username and Password.

Exceptions:

Use-case: Add or View Med Tech Account


Goal in context: To add user account or to view.

Preconditions: Only a medical technician of the Clinic can have a Med Tech Account

Trigger: A new med tech is hired by the Clinic.

Scenario: 1. The Administrator logs onto the System.

2. The Administrator selects Tools from the Menu Bar.

3. The Administrator selects Med Techs Account.4. The System will display the list of all Med Tech accounts.

5. The Administrator shall decide if to add, edit or delete a user account.

6. If the Administrator selects Add, a window will pop up showing information to

be input in the appropriate fields

7. The system will add all the information of the Med Tech account created by the

Administrator.

Exceptions:

2.3Special usage considerations

Billing fees cannot be changed.


13/32

2.4 Activity DiagramsThe following activity diagrams show the actions that occur during a particular use-case.

Figure 2 shows the steps taken as an employee logs on to the computer system. Access is onlygranted if the correct user ID / password combination is entered. Once access is granted the

employee can use the system according to their level of authorization.

Figure 2 - Activity diagram for logging on to the system


14/32

In Figure 3 a proponent has contacted a Laboratory staff to register as a patient. The

Laboratory staff will now get the patients information. If the patient is accepted, a new

account will be created and all customer information will be entered into the system.

Figure 3 - Activity diagram for adding a patient

Add a patient

activity diagram


15/32

Figure 4 shows the activity involved in viewing or updating the system users. Only the

administrator could access this feature.

Figure 4 Activity Diagram to view / update account information


16/32

Figure 5 shows the editing of the Test Information whether it will be Laboratory test,

OBGyne test, or X-ray-Ultrasound test.

Figure 5 editing test information activity diagram


17/32

Figure 6 shows the editing and printing of all the Laboratory Test report of a patient.

Figure 6 Editing and Printing of Laboratory Test Report Activity

Editing and

Printing

Laboratory Test

Report Activity


18/32

Figure 7 shows the adding of transaction and Printing of the Bill of Patients.

Figure 7 Adding and Printing Bill Report Activity

Adding

transaction and

printing of bills


19/32

3. Data Model and Description

3.1 Data objects

PatientInfo Data Object

PatientIDa unique identifier assigned to the patient.Lastnamethe surname of the patient

Firstnamethe first name of the patient

MIthe middle name of the patientGenderthe patient gender

Agethe age of the patient

Addressthe address of the patient

ContactNothe contact number of the patientCivil Statusindicates the civil status of the patient

Users Data ObjectUserIDa unique number assigned to the user account.

Firstnamethe first name of the user.

Lastnamethe surname of the user.Usernamea unique character for the user.

Passworda secret word or phrase that must be used to gain admission to the system.

LogInTypeis the type of position a user or employee have. It refers to the authority a user canhave.

MedTechID Data ObjectMedTechIDa unique number assigned to the medical technical.

MedTechNamethe full name of the medical technical.Passwordused by med tech no gain admission to the transaction of the patients.

Tests Data ObjectTestIDa unique number assigned to the kind of test.TestNamethe identifier or name of the tests.

TestPriceit indicates how much the price of the test is.

MedicalFeeindicates how much is the fee of the medical done to the patient.

TestTypeindicates what type category is the test.

KindofTestindicates what kind of test is done to the patient.

RecordTypeindicates what type of record is done.PackageNameindicates if the test is in a package.

TestTypes Data ObjectTestTypeIDunique number assigned to the test type.

TestTypethe name of the category of the test.


20/32

PatientRecords Data ObjectPatientRecordIDa unique number for the patient record.

PatientIDa unique character for the patient.TestIDa unique number for the Test.

DateofRequestthe date of the patient requested the test.

Discountthe discount of the patient in a test.ORnothe unique number for the patient in a type of test.

CheckedHistory Data ObjectCheckedHistoryIDidentifier for the checked history of the patient.PatientIDidentifier for the patient.

Checkedbyidentify the name of the medical technician that checked the patients.

TestTypethe type of test the patient transact.

ChemistryTest Data ObjectChemistryTestIDunique id for the chemistry test.

Testname of the test.

ChemistryResult Data ObjectChemistryResultIDunique id for the chemistry result.

PatientIDidentifier for the patient.

ChemistryTestIDunique id for the chemistry test.Resultthe result of a test done by the med tech.

FecalysisResult Data ObjectFecalysisResultIDunique id for the fecalysis result.

PatientIDidentifier for the patient.TestRequestedrequested test by the patient.Colorrefers to the color of the stool of the patient.

Mucoustest that refers to the number of mucous present in the stool.

Bloodtest that refers to the blood that can be seen in the stool of the patient.AdultHelminthsparasitic worms that can be found in a stool. Test that refers to the number of

parasitic worms.

PusCellstest that refers to white blood cell that can be found in a stool.

RedBloodCellstest that refers to Red blood cell that can be found in a stool.Protozoatest that refers to a intestinal parasite that can be found in stool.

OccultBlood test that refers to a blood that found in stool.

Helminthstest that parasitic worms that can be found in a stool.

Flagellatestest that is an organism or parasite that can be found in a stool.Othersrefers to other result of fecalysis test in a patient.

Remarksthe evaluation of the med tech personel in a fecalysis test.

MedTechthe personnel who conduct the test.DateofReportthe date where the test is reported.

LabNois the unique lab number for the patient.

ORNois the unique or number for the patient given by the med tech or other employee.


21/32

HematologyResult Data ObjectHematologyResultIDunique id for the hermatology result.

PatientIDidentifier for the patient.Hemoglobintest that refers to the iron-containing oxygen-transport metalloprotein in the red

blood cell, it refers to how much hemoglobin a patient has in a hematology test.

Hematocritit refers to blood test that measures the percentage of the volume of whole bloodthat is made up of red blood cells. RBCCountit refers to a blood test that tells how many red blood cells (RBCs) you have.

ReticulocyteCountit refers to a blood test that measures how fast red blood cells called

reticulocytes are made by the bone marrow and released into the blood.CoagulationProfilea test which measures the speed of blood coagulation at different steps of

the coagulation pathway.

PlateletCountis a test to measure how many platelets you have in your blood.

BleedingTimeis a medical test done on someone to assess their platelet function.ClottingTimeis the time required for a sample of blood to coagulate in vitro under standard

conditions.

ESRis a test to rate the red blood cells sediment in a period of one hour.WBCis a blood test to measure the number of white blood cells.

Neutrophilis a blood test to measure of neutrophil oxidation in the blood.

Segmenteris a blood test to measure of segmenter oxidation in the blood.

Othersrefers to other result of hematology test in a patient.Remarksthe evaluation of the med tech personel in a hematology test.

MedTechthe personnel who conduct the test.

DateofReportthe date where the test is reported.LabNois the unique lab number for the patient.


ImmunologyResult Data ObjectImmunologyResultIDunique id for the immunology result.

PatientIDidentifier for the patient.

TestRequestedrequested test by the patient.Specimenit refers to what specimen is to be undergo to a immunology test.

TestMethodit refers to what kind of method is to be done in a immunology test.

Resultthe evaluation of the med tech personel in a immunology test.MedTechthe personnel who conduct the test.

DateofReportthe date where the test is reported.

LabNois the unique lab number for the patient.

http://www.webmd.com/hw-popup/red-blood-cell-erythrocytehttp://www.webmd.com/a-to-z-guides/reticulocyteshttp://www.webmd.com/heart/anatomy-picture-of-bloodhttp://en.wikipedia.org/wiki/Red_blood_cellshttp://en.wikipedia.org/wiki/Red_blood_cellshttp://www.webmd.com/heart/anatomy-picture-of-bloodhttp://www.webmd.com/a-to-z-guides/reticulocyteshttp://www.webmd.com/hw-popup/red-blood-cell-erythrocyte


22/32

3.2 Relationships

In order for a patient to have an account with the Medcrest Multi-Specialty Diagnostic Cinicthey must have a consultation or test in order for them to have their medical record. Since a

patient can have a multiple test to a doctor a one-to-many relationship exists. It is also true that a

patient and med tech cannot exist alone in the MRBC system. In general all patients must havedoctor assigned to them or requested by them and a patient without a laboratory, X-rayultrasound or ObGyn test has no need to register for the Medcrest Multi-Specialty Diagnostic

Cinic.

A patient will receive a new bill on each test so a one-to-many relationship exists. The bill will

issued by the employee and every gathered test will be included in the bill. The discount like

senior citizen, doctor, lab to lab may avail by the patient whos fitted on the said discount.

A patient record can have different test type so one-to-many relationship exists. The patient can

request for their medical record if they want. The employees just need to search for the patient

name and print the medical record.

A Med tech can be assigned to any patient so one-to-many relationship exist. The med tech can

conduct test on every patient and they are the only personnel who can edit the result of the test.

An Administrator can edit patient, test, user information so one-to-many relationship exists.

The admin has the only authority to access all the transaction. The other user has a restricted

access to the system.

A Test like laboratory, X-ray ultrasound or ObGyn test can be avail by one patient so there is a

many-to-one relationship. Every test there will be a med tech assigned so one-to-one relationship

exist.

Each room in the clinic can accommodate one person at a time so a one-to-one relationship

exists between room and patient.


23/32

3.3 Complete data model

The relationships between the data objects describe in section 3.2 are shown in Figure 11.

Figure 11 - Relationship diagram for the ACCM system


24/32

4. Functional Model and Description

4.1 Class diagrams

The associations between the different classes are shown in Figure 12. The access functions to

get and set private data attributes have been removed for clarity.

Figure 12Medical Record and Billing System class diagram


25/32

4.2 Software Interface Description

4.2.1 External machine interfaces

The software will be capable of printing reports on a local printer.

4.2.2 External system interfaces

The MRBC system will be use in a land base environment.

4.2.3 Human interface

The system shall permit complete navigation using the keyboard alone, in addition to usingmouse and keyboard combinations.

5. Behavioral Model and Description

5.1 Description for software behavior

5.1.1 Events

Patient Class Events

Admin registers patient

patients examined by doctor

Patients receives bill

Med tech Class Events

Med tech conduct testMed tech logs onto the system

Med tech fill-up the test information

Med tech issue receipt

Employee Class Events

Employee is hired

Employee logs onto the systemEmployee add transaction

Employee issue bills

Employee logs off of the system


26/32

Employee gets promoted

Employee is no longer employed

Patient List Class Events

Patient added to patient list

Patient removed from Patient list

Test List Class Events

Test added to Test listTest removed from Test list

Bill Class Events

Bill printed

Bill issuedPayment received

5.1.2 States

Patient States Description

Waiting The patient has been placed on a waiting list if there is a patient who arrives

first.

Signed In The Patient has arrived in the Clinic

Signed Out The Patient has left the Medcrest Clinic.

Registering The Patient is the process of being registered.

Withdrawn The Patient will no longer be attending the Medcrest Clinic.

Med tech States Description

Registering The Med tech is setting up a new account.

Active The Med tech has to do test in the medcrest cinic.

Inactive The Med tech has no longer attending to the medcrest clinic.

Terminated The Med tech has been terminated and must be blocked in using the system.


27/32

Employee States Description

Hired An employee has been hired and a new employee account must be set up.

Promoted The employee has been promoted and their access privileges may need to

change.

On Line The employee has logged on to the system.Off Line The employee has logged off the system.

Terminated The employee has been terminated and must be blocked from using the

system.

Patient List States Description

Initializing Information about the patient is being entered.

Altering New information about the patient is being added.

Closed No information has been added.

Test List States Description

Initializing Information about the test is being added.

altering New information about the patient is being added.

Closed No information has been added.

Bill States Description

Updating The accounts are being update according to the tests conducted

Printing The bill was printed and issue to the patient.

Paid Upon receiving the bill the patient will pay for the services rendered.

5.2 Statechart Diagram

A state chart diagram for the entire system is shown in Figure 13. After a user logs on the

system, the user will select a menu option.

Figure14 contains state chart for the outpatient, guardian, and the employee. The guardian of the

outpatient may decide if theyre going to register another outpatient. If an employee is promoted

their access privileges will change so they will need to log out then log on to the system for the

new changes to take effect


28/32

The various states for a room, waiting list and diagnostics are shown in Figure 15. The statechart

for the room is identical to that for the waiting list except for the guard conditions. Either object

can be at capacity or below.

Figure 13 - Overall system state chart diagram


29/32

Outpatient Class State Diagram

Guardian Class State Diagram

Figure 14 - Statechart diagrams


30/32

Figure 15 - Statechart di

Outpatient Class Statechart

Diagram

Waiting List Class Statechart

Diagram

Diagnosis Class StatechartDiagram

Figure 15 - Statechart diagrams


31/32

6. Restrictions, Limitations, and Constraints

The system shall integrate within the existing LAN structure and with the existing systems, such

as the database management systems.

It is made in the visual basic 6 programming language therefore it is not a web based system.

The database is done in Microsoft Access and not appropriate for a web based system.

Visual Basic Studio or Visual Basic 6 should be installed in the computer.

7. Validation Criteria

Software validation will ensure that the system responds according to the users expectations;

therefore it is important that the end users be involved in some phases of the test procedure. Alltests will be traced back to the requirements in section 1.2.

7.1 Classes of tests

Unit testing will be conducted on all of software subsystems including

1. Accessing Transaction

2. Viewing and editing information

3. Viewing and printing reports

4. Logging on to the system

5. Adding Patient Information

6. Viewing Billing Reports

7. Adding, Editing and Deleting User Account.

Test cases for black box testing will be based on equivalence categories. These categories will

include values that lie on and around the boundary values of a function. For example, if a

function can accept values from 0 to 100 then the test cases will include the values -1, 0, 1, 99,

100, and 101.

Acceptance testing will be conducted at the customers site.

7.2 Expected software response

The software should display an appropriate error message when a value outside the accepted

limits is entered.

The software should not be capable of deleting a patient record even if they withdraw from the

Diagnostic Clinic.


32/32

7.3 Performance Bounds

The system shall support up to a thousand information of patient and username.The system will provide access to the database management system with a latency of no more

than 20 seconds.

Appendix A: Glossary

Account A reference for all of the information related to a parent, including child and billing

information.

Administrator A person on the administrative staff of the Medical Records and Billing System.Employee A person that has a position of either cashier or staff of the Diagnostic Clinic.

Patient A Customer of the Medcrest Multispecialty Diagnostic Clinic.

Visual Basic 6 A programming language use to create the Medical Records and Billing System.

Transaction An instance of testing in the Diagnostic Clinic.

Med Tech Can be a Doctor, Nurse or a Medical Technician in the Clinic.

Bill Reports Can be view to see the records income or financial of the Diagnostic Clinic.

MRBS The Medical Record Billing System.

Software Requirements(Softeng).docx

Documents

Transcript of Software Requirements(Softeng).docx