Você está na página 1de 32

MEDICAL RECORDS AND BILLING SYSTEM OF MEDCREST MULTIPSPECIALTY DIAGNOSTIC CLINIC

Faculty of Computer Studies Department Cavite State University Imus Campus Imus, Cavite

In Partial Fulfillment Of the Requirements for the subject ITEC55B System Analysis and Design

Rina E. Tabamo Jayson Philbert Ted C. Maaol Ceferino Rio

2013

Software Requirements Specification of Medical Records and Billing System for Medcrest Multispecialty Diagnostic Clinic

1. Introduction 1.1 1.2 1.3 1.4 Goals and objectives Statement of scope Software context Major constraints

2. Usage scenario

2.1 User profiles 2.2 Use-cases 2.2.1 Use-Case Diagram 2.2.2 Use-Case Descriptions 2.3 Special usage considerations 2.4 Activity Diagrams 3. Data Model Description 3.1 Data objects 3.2 Relationships 3.3 Complete data model 4. Functional Model Description 4.1 Class diagrams 4.2 Software Interface Description 4.2.1 External machine interfaces 4.2.2 External system interfaces 4.2.3 Human interface 5. Behavioral Model Description 5.1 Description for software behavior 5.1.1 Events 5.1.2 States 5.2 Statechart Diagram 6. Restrictions, Limitations, and Constraints

7. Validation Criteria 7.1 Classes of tests 7.2 Expected software response 7.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 will serve 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 may seem to convey similar information they typically do so from an alternate perspective. This gives different stakeholders 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 be used. Visual Basic 6 programming language will be use because it is user friendly for the users and easy to maintain. 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 in managing a diagnostic clinic. Many of the typical functions involved in operating a Diagnostic clinic will be automated through software to improve the operational workflow within the facility. The system is expected to help Medcrest 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 procedures and other procedures will be updated and presented in precision. With the help of this proposed computerized system 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 will be traced throughout the project. Before gaining access to the Medical Records and Billing system an employee will be required to enter their user name 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 of the Medcrest Multispecialty Diagnostic Clinic; the automated calculation of patients total payment, change and printing of receipt. This system tries to eliminate the manual patient monitoring and billing system that is currently used by Medcrest Multispecialty Diagnostic Clinic. All information from the transaction of a patient will be recorded, even the laboratory procedures and medicines. With this information, the patient bills will be automatically computed and generated. The system also includes Discounts and other privileges in the billing process. The system does not include the payroll of employees.

User Requirements for Medcrest Multispecialty Diagnostic Clinic Software Project

Req. No. Priority Reference Access Privileges R1 High Customer R2 High Customer R3 R4 Security R5 Med High Customer Customer

Description There shall be log-in for the medical staff The medical staff shall only be allowed to enter or edit medical records. Only the medical staff shall be allowed to view or print reports. All the medical staff shall be allowed to issue printed billings of patient. Each user shall be required to log on with a unique user name and password before using the system. The password does not need to be unique. The user name shall be their position and their password will be their desire words or characters. A password shall be assigned to each user. The password shall contain 6 to 8 alphanumeric characters. After three unsuccessful attempts to enter a password the user shall be locked out of the system until their password is reset. 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. The administrator, cashier and staff of the Clinic can have the authority to transact to the customer or patient. The cashier can print the billing reports of the patient or customer. The cashier, staff and administrator can add transaction made by the patient or customer. A Billing receipt will be received by the patient or customer upon payment. Any of the three users can issue a receipt for the patient or customer. There is a discount for the senior, laboratory to laboratory patients and doctors who will transact to the clinic. All of the billing of the patient will be recorded.

High

Customer

R6 R7 R8 R9

Low High High Med

Code Works Customer Customer Code Works Customer

R10

High

Transactions R11

High

Customer

R12 R13 Billing R14 R15 R16

Low Med

Code Works Code Works Customer Customer Customer

High High High

R17

High

Customer

R18 R19 R20

High High High

Customer Customer Customer

Products that have been purchased by the patient or customer will be printed in the receipt. Transactions that have been made by the patients will be printed in the receipt. All the transaction and purchased products will be listed in the receipt including the discount of the patients or customer. A Patient List shall view the customers alphabetically by last name and include their address and contact number. A Medical Test List shall alphabetically list the all the medical test done by the clinic. A Patient Report can view the list of patients that are include in the clinic and prints its Name, age and address. A Daily Sales Report can be view to know the income of the clinic in a specific day. A Modified Sales Report can be view to know the income of the clinic from a date to the specific date. The User Account shall list all the users in the system according to their UserID. It includes adding, editing and deleting of user accounts. Only the administrator has the authority to view it. The Med Techs Accounts can be viewed to know all the listed medical technician or doctors that are in the clinic. When a user edits an account their user ID along with the password, username and other information shall be recorded in the database. The Patients record shall contain the following information: 1. Name 2. Gender 3. Contact Number 4. Age 5. Civil Status 6. Address

Reports R21

High

Customer

R22 R23

High High

Customer Customer

R24 R25 R26

High High High

Customer Customer Customer

R27

High

Customer

Account Information R28 Med

Customer

R29

High

Customer

R30

High

Customer

The Users record shall contain the following information: 1. 2. 3. 4. Name Username Password Log In Type

R31 User Interface R32 R33 R34

High

Customer

The software shall support the ability to enter, store, and update patients and billing information. The system shall have a Land based interface that works with Visual Basic 6. There are different kinds of colors in all windows. The system shall respond to all user requests within 10 seconds.

High High High

Customer Customer Customer

1.3 Software context Today, computerization is a major advancement in technology that helps in many ways: it makes information storage easier and faster thus it can save a lot of time and manpower, and many tasks are done in a certain amount of time. Great amount of time is being consumed by information retrieval and the billing process of most Diagnostic Clinics without computer generated system is slow. To be able to provide the medical needs of the rapidly growing population, Diagnostic Clinics must be versatile to the current trends and innovation in today's changes in technology.

One of the concerns of Medcrest Multispecialty Diagnostic Clinic is how to lessen the number paper works in having a transaction with the patient that could fasten the process of admission, discharging and billing of a patient. This greatly 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 Medcrest Multispecialty Diagnostic Clinic. Because some patients are so smart that they can find a way that they do not have to pay the Clinic bills. Some are having a difficulty in paying because of the slow process of computation which can take 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 system that is intended to solve the concerns that they discovered. Efficient medical records and billing management greatly 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 keep track and maintain each patient's information.

The computerized medical records and billing system is expected to help Medcrest 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.

1.4 Major constraints

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

2. Usage scenario
2.1 User profiles

The following definitions describe the actors in the system.

Administrator

Cashier Employee Patient System Customer Microsoft Visual Basic 6

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. A Cashier has the responsibility to handle payment of patients and customers and has the authority to issue a receipt. An employed is the general name that refers to an administrator, cashier, or med tech. The patient is a customer of the Medcrest Multispecialty Diagnostic Clinic. They are the one who get medical test. The system refers to the computer hardware and software that controls the application. It accepts user input, displays user output, and interfaces. A customer is the one who purchased medicine or other products from the Medcrest Multispecialty Diagnostic Clinic. 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.

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 Patients 6. Transaction 7. Add Transaction to the patients 8. Enter Transaction 9. Print Receipt Bill 10. Add or view User Accounts 11. 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 secondary activity 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.

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

2.2.2 Use-Case Descriptions Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario: Log on to System Employee To gain access to the System The employee has a valid user name and password An Employee needs access to the System to perform their job 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. The user name and password cannot be verified

Exceptions:

Use-case: Primary actor: Goal in context: Preconditions:

Trigger: Scenario:

Exceptions:

Add Patient Information Administrator To add a patient information into the database. 1. Patients must undergo transaction 2. Patients should go directly to the administrator of the Clinic to be added in the database. Patient undergo test of medical examination to know their health status. 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. The system has reached its capacity of adding patients.

Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

View List of Test Administrator To retrieve medical test information. The user has a valid password An admin has an event that they need to be reminded of 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. The medical test records are not there.

Exceptions:

Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

Billing Reports Administrator To show the sales report of the Clinic A income of the Clinic should be recorded The date of a reminder is the current date 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. The sales report will not display any sales if no income.

Exceptions:

Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

Exceptions:

View List of Patients Administrator To retrieve account information The account exists An administrator needs information from one of their accounts 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. The account does not exist

Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

Transaction Med tech /employee To manage the transaction of the Patient The patient should avail any of the medical test to be added in transaction A patient avails in a medical test. 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:

Use-case: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

Add or View User Accounts Administrator To add user account or to view. Only a employee of the Clinic can have a user account A new employee is hired by the Clinic. 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: Primary actor: Goal in context: Preconditions: Trigger: Scenario:

Add or View Med Tech Account Administrator To add user account or to view. Only a medical technician of the Clinic can have a Med Tech Account A new med tech is hired by the Clinic. 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.3 Special usage considerations

Billing fees cannot be changed.

2.4 Activity Diagrams The 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 only granted 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

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.
Add a patient activity diagram

Figure 3 - Activity diagram for adding a patient

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

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

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

Editing and Printing Laboratory Test Report Activity Diagram

Figure 6 Editing and Printing of Laboratory Test Report Activity

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

Figure 7 Adding and Printing Bill Report Activity

3. Data Model and Description


3.1 Data objects PatientInfo Data Object PatientID a unique identifier assigned to the patient. Lastname the surname of the patient Firstname the first name of the patient MI the middle name of the patient Gender the patient gender Age the age of the patient Address the address of the patient ContactNo the contact number of the patient Civil Status indicates the civil status of the patient

Users Data Object UserID a unique number assigned to the user account. Firstname the first name of the user. Lastname the surname of the user. Username a unique character for the user. Password a secret word or phrase that must be used to gain admission to the system. LogInType is the type of position a user or employee have. It refers to the authority a user can have. MedTechID Data Object MedTechID a unique number assigned to the medical technical. MedTechName the full name of the medical technical. Password used by med tech no gain admission to the transaction of the patients. Tests Data Object TestID a unique number assigned to the kind of test. TestName the identifier or name of the tests. TestPrice it indicates how much the price of the test is. MedicalFee indicates how much is the fee of the medical done to the patient. TestType indicates what type category is the test. KindofTest indicates what kind of test is done to the patient. RecordType indicates what type of record is done. PackageName indicates if the test is in a package. TestTypes Data Object TestTypeID unique number assigned to the test type. TestType the name of the category of the test.

PatientRecords Data Object PatientRecordID a unique number for the patient record. PatientID a unique character for the patient. TestID a unique number for the Test. DateofRequest the date of the patient requested the test. Discount the discount of the patient in a test. ORno the unique number for the patient in a type of test. CheckedHistory Data Object CheckedHistoryID identifier for the checked history of the patient. PatientID identifier for the patient. Checkedby identify the name of the medical technician that checked the patients. TestType the type of test the patient transact. ChemistryTest Data Object ChemistryTestID unique id for the chemistry test. Test name of the test.

ChemistryResult Data Object ChemistryResultID unique id for the chemistry result. PatientID identifier for the patient. ChemistryTestID unique id for the chemistry test. Result the result of a test done by the med tech. FecalysisResult Data Object FecalysisResultID unique id for the fecalysis result. PatientID identifier for the patient. TestRequested requested test by the patient. Color refers to the color of the stool of the patient. Mucous test that refers to the number of mucous present in the stool. Blood test that refers to the blood that can be seen in the stool of the patient. AdultHelminths parasitic worms that can be found in a stool. Test that refers to the number of parasitic worms. PusCells test that refers to white blood cell that can be found in a stool. RedBloodCells test that refers to Red blood cell that can be found in a stool. Protozoa test that refers to a intestinal parasite that can be found in stool. OccultBlood test that refers to a blood that found in stool. Helminths test that parasitic worms that can be found in a stool. Flagellates test that is an organism or parasite that can be found in a stool. Others refers to other result of fecalysis test in a patient. Remarks the evaluation of the med tech personel in a fecalysis test. MedTech the personnel who conduct the test. DateofReport the date where the test is reported. LabNo is the unique lab number for the patient. ORNo is the unique or number for the patient given by the med tech or other employee.

HematologyResult Data Object HematologyResultID unique id for the hermatology result. PatientID identifier for the patient. Hemoglobin test 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. Hematocrit it refers to blood test that measures the percentage of the volume of whole blood that is made up of red blood cells. RBCCount it refers to a blood test that tells how many red blood cells (RBCs) you have. ReticulocyteCount it 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. CoagulationProfile a test which measures the speed of blood coagulation at different steps of the coagulation pathway. PlateletCount is a test to measure how many platelets you have in your blood. BleedingTime is a medical test done on someone to assess their platelet function. ClottingTime is the time required for a sample of blood to coagulate in vitro under standard conditions. ESR is a test to rate the red blood cells sediment in a period of one hour. WBC is a blood test to measure the number of white blood cells. Neutrophil is a blood test to measure of neutrophil oxidation in the blood. Segmenter is a blood test to measure of segmenter oxidation in the blood. Others refers to other result of hematology test in a patient. Remarks the evaluation of the med tech personel in a hematology test. MedTech the personnel who conduct the test. DateofReport the date where the test is reported. LabNo is the unique lab number for the patient. ORNo is the unique or number for the patient given by the med tech or other employee. ImmunologyResult Data Object ImmunologyResultID unique id for the immunology result. PatientID identifier for the patient. TestRequested requested test by the patient. Specimen it refers to what specimen is to be undergo to a immunology test. TestMethod it refers to what kind of method is to be done in a immunology test. Result the evaluation of the med tech personel in a immunology test. MedTech the personnel who conduct the test. DateofReport the date where the test is reported. LabNo is the unique lab number for the patient. ORNo is the unique or number for the patient given by the med tech or other employee.

3.2 Relationships In order for a patient to have an account with the Medcrest Multi-Specialty Diagnostic Cinic they 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 have doctor assigned to them or requested by them and a patient without a laboratory, X-ray ultrasound 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.

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

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 12 Medical Record and Billing System class diagram

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 using mouse 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 test Med 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 system Employee add transaction Employee issue bills Employee logs off of the system

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 list Test removed from Test list

Bill Class Events Bill printed Bill issued Payment received

5.1.2 States

Patient States Waiting Signed In Signed Out Registering Withdrawn Med tech States Registering Active Inactive Terminated

Description The patient has been placed on a waiting list if there is a patient who arrives first. The Patient has arrived in the Clinic The Patient has left the Medcrest Clinic. The Patient is the process of being registered. The Patient will no longer be attending the Medcrest Clinic. Description The Med tech is setting up a new account. The Med tech has to do test in the medcrest cinic. The Med tech has no longer attending to the medcrest clinic. The Med tech has been terminated and must be blocked in using the system.

Employee States Hired Promoted On Line Off Line Terminated

Description An employee has been hired and a new employee account must be set up. The employee has been promoted and their access privileges may need to change. The employee has logged on to the system. The employee has logged off the system. The employee has been terminated and must be blocked from using the system. Description Information about the patient is being entered. New information about the patient is being added. No information has been added. Description Information about the test is being added. New information about the patient is being added. No information has been added. Description The accounts are being update according to the tests conducted The bill was printed and issue to the patient. Upon receiving the bill the patient will pay for the services rendered.

Patient List States Initializing Altering Closed Test List States Initializing altering Closed Bill States Updating Printing Paid

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

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

Outpatient Class State Diagram

Guardian Class State Diagram

Figure 14 - Statechart diagrams

Outpatient Class Statechart Diagram

Waiting List Class Statechart Diagram

Diagnosis Class Statechart Diagram

15 - Statechart FigureFigure 15 - Statechart di diagrams

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. All tests 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.

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 Administrator Employee Patient Visual Basic 6 Transaction Med Tech Bill Reports MRBS A reference for all of the information related to a parent, including child and billing information. A person on the administrative staff of the Medical Records and Billing System. A person that has a position of either cashier or staff of the Diagnostic Clinic. A Customer of the Medcrest Multispecialty Diagnostic Clinic. A programming language use to create the Medical Records and Billing System. An instance of testing in the Diagnostic Clinic. Can be a Doctor, Nurse or a Medical Technician in the Clinic. Can be view to see the records income or financial of the Diagnostic Clinic. The Medical Record Billing System.