Upload
ehtisham-ulhaq-ghouri
View
243
Download
4
Embed Size (px)
DESCRIPTION
A system developed for hospital.
Citation preview
Hospital management system
Software Engineering
Submitted by :
Ehtisham Ulhaq 10-arid-93
Jamal Ahmed 10-arid-121
section :
BS(cs) 5-A
Submitted to :
Sir Nasir Minhas
Use cases and fully dressed use cases
Use case Schedule Appointment
Actors Receptionist
Type Primary
Description: when an out-patient comes to receptionist or calls from phone and asks to receptionist for appointment. Then see the schedule of specific doctor and fix a time for appointment of patient.
Schedule Appoinment
(from use case)
Receptionist
(f rom Actors)
Fully Dressed Use Case1 Use case name Schedule Appointment2 Scope fix checkup time with doctor3 Level User goal4 Primary actor Receptionist5 Stakeholder Patient, doctor6 Precondition Login to system7 Post condition Allocate appointment slip to patient 8 Success scenario Login to system
View schedule of specific doctorFix appointmentPrint out appointment slip.
9 Extensions View scheduleRegister patient
10 Special Req Receptionist could search all doctor schedule by their name or id.
Use case Admit patient
Actors Receptionist
Type Primary
Description: when a patient comes to hospital then the receptionist admit him. Patient may be in-door or out-door. In case of in-door patient would allocated a bed. In case of out-door patient the patient would get treatment according to schedule
Admit patient
(from use case)
Receptionist
(f rom Actors)
Fully Dressed Use Case1 Use case name Admit patient 2 Scope Admit in-door and out-door patient3 Level User goal4 Primary actor Receptionist5 Stakeholder Patient 6 Precondition Login to system7 Post condition Allocate admit slip to patient8 Success scenario Login to system
Select admitSelect indoor/outdoorRegister patientAllocate badGive admit slip to patient
9 Extensions Register patientSearch bedAllocate bed
10 Special Req Receptionist could search bed by specific ward.Use case Discharge patient
Actors Receptionist
Type Primary
Description: when a patient get treatment in the hospital then he will discharge from hospital. Receptionist will discharge him. Receptionist will create bill for patient according to his services that he used in hospital.
Receptionist
(f rom Actors)
Discharge patient
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Discharge patient 2 Scope Generate bill for patient3 Level User goal4 Primary actor Receptionist5 Stakeholder Patient , accountant6 Precondition Login to system7 Post condition Allocate bill patient8 Success scenario Login
Select dischargeSelect indoor/outdoor dischargeVie servicesGenerate billPrint out bill
9 Extensions View servicesRecord services
10 Special Req Bill contains details of all services and next visit dateUse case Give prescription
Actors Doctor
Type Primary
Description: After getting registration patient would get treatment from doctor. Doctor would give prescription to the patient and record in the patient’s record.
Give prescription
(from use case)
Doctor
(f rom Actors)
Fully Dressed Use Case1 Use case name Give prescription 2 Scope Record prescription given to patient 3 Level User goal4 Primary actor doctor5 Stakeholder Patient, nurse6 Precondition Login to system7 Post condition Give prescription slip to patient 8 Success scenario Login
Select prescriptionEntre patient idRecord prescriptionSee massage prompt
9 Extensions Wrong patient id10 Special Req Doctor could record drug prescription and food
prescription seperately
Use case Give suggestion
Actors Doctor
Type Primary
Description: when doctor give treatment to the patient he could suggest suggestion may be for tests, operations and to admit.
Doctor
(f rom Actors)
Give suggestion
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Give suggestion2 Scope Suggest tests, operation or to admit in hospital3 Level primary4 Primary actor doctor5 Stakeholder patient6 Precondition Login to system7 Post condition Give suggestion slip to patient8 Success scenario Login
Select specific suggestionEnter patient idRecord suggestionPrint out suggestion slip
9 Extensions Wrong patient id
10 Special Req There are separate suggestion slip for admit, surgery or to admit in hospital.
Use case view patient record
Actors Doctor , Nurse
Type Primary
Description: when doctor give treatment to patient he could see pervious record of the patient. He could see the reports of different test of the patient. He could see operations details, previous prescription etc
Doctor
(f rom Actors)
view patient record
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name view patient record 2 Scope Doctor could view treatment history3 Level Primary4 Primary actor Doctor5 Stakeholder Patient6 Precondition Login7 Post condition Get patient record8 Success scenario Login
Select view recordSelect specific recordEnter patient idView record
9 Extensions Wrong patient id
10 Special Req Doctor have different option to view record.Eg Last visit, specific visit
Use case File reports
Actors Nurse
Type Primary
Description: when reports of test are generated these reports would given to the nurse who record these reports. These reports would become the permanent part of the patient record.
Nurse
(f rom Actors)
File reports
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name File reports 2 Scope Record test reports, daily reports and operation
details3 Level primary4 Primary actor Nurse 5 Stakeholder patient6 Precondition Login to system7 Post condition Record report8 Success scenario Login
Select file reportSelect specific reportFile report detailsPrompt message
9 Extensions Wrong patient id
10 Special Req Report should be detail, Date of report mentionUse case Manage User
Actors Admin
Type Primary
Description: Admit control system. He could create users, update user and delete users. Update include different tasks like change user name, change password etc. when ever he create a user he allocate him a user name and password to user.
Admin
(f rom Actors)
Manage Users
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Manage User2 Scope Admin manage accounts of different users of system3 Level primary4 Primary actor Admin5 Stakeholder staff6 Precondition Login to system7 Post condition Update user accounts8 Success scenario Login
Select manage accountsSelect create/delete/updateEnter account idEnter admin passwordEnter dataPrompt message
9 Extensions Wrong patient id , wrong admin passward
Use case Manage Inventory
Actors Storekeeper
Type Primary
Description: storekeeper manage inventory. he could issue inventory on request of employee. He could see current status of inventory. He could also purchase inventory. He see add item in request list. He will see request list when he will going to the purchase inventory.
Storekeeper
(f rom Actors)
Manage Inventory
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Manage Inventory2 Scope Manage inflow and out floe of inventory3 Level Primary4 Primary actor Storekeeper 5 Stakeholder Employers6 Precondition Login7 Post condition Record transaction8 Success scenario Login
Select issue/purchase/request /add itemEnter inventory id Enter quanity Prompt message
9 Extensions Wrong inventory idInventory not in stock
10 Special Req After transaction prompt message give last quanity of inventory item.
Use case Manage schedule
Actors Shift In-charge
Type Primary
Description: shift in-charge handle schedule of staff. He allocate duties according to the rank of doctor , nurses . Doctors and doctor have to follow this schedule.
Shift In-charge
(f rom Actors)
Manage schedule
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name schedule duties2 Scope Allocate duties of doctors and nurses3 Level User goal 4 Primary actor Shift In-charge5 Stakeholder Doctor, nurses patient6 Precondition Login7 Post condition Assign duties
Print out schedule8 Success scenario Login in
Select nurse/doctor dutiesEnter id Enter select indoor/outdoor dutiyEnter ward idEnter time /datePrompt message
9 Extensions Wrong employee id, wrong ward id10 Special Req Date and time should mention clearlyUse case view schedule
Actors doctor/nurses / shift in-charge
Type Primary
Description: doctor and nurses can view there are schedule in order to perform their duties. This schedule is maintained by shift in-charge
doctor / nurses
(f rom Actors)
Record Attendance
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name view schedule 2 Scope View schedule of duties 3 Level User goal 4 Primary actor Nurse /doctor 5 Stakeholder Doctor, nurses6 Precondition Login7 Post condition Get schedule
Success scenario Login inSelect view scheduleEnter date / week/monthView schedule
9 Extensions Wrong date
10 Special Req Employee should different to view schedule.
Use case Manage employee record
Actors Admin
Type Primary
Description: when an employee get hire in the hospital. Then admin will record his all details. Details include bio data, joining date, rank and thumb impression etc. admin could update record of the employee.
Admin
(f rom Actors)
Manage employee
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Manage employee record 2 Scope Manage all details of employee 3 Level User goal 4 Primary actor Admin5 Stakeholder Employees 6 Precondition Login
Authority letter from higher management 7 Post condition Record employee information8 Success scenario Login in
Select hire employee/fire employee/update employeeEnter id (not in first case)Enter datePrint out information
9 Extensions Wrong employee id10 Special Req Print out paper include all information Use case Record Attendance
Actors scanner
Type Primary
Description: when a employee get enter in the hospital he record his attendance of the employee. Sensor will get thumb impression and records it to attendance sheet.
Scanner
(f rom Actors)
Record Attendance
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Record Attendance 2 Scope Daily get attendance of all employees 3 Level Primary4 Primary actor Scanner 5 Stakeholder employee6 Precondition Scan thumb impression7 Post condition Alarm indicating attendance has record8 Success scenario Scanner switch on
Give thumb impressionListen alarm voice
9 Extensions Failure of scannerDo not match thumb impression
10 Special Req There should be signal indicating failure of record attendance
Use case Issue funds
Actors Treasure Officer
Type Primary
Description: treasure officer control flow cash in the organization. He deals with salaries and funding for other matters. He will issue funds for salaries and for inventory in the hospital.
Treasure Officer
(f rom Actors)
Issue funds
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Issue funds 2 Scope Issue funds for all activities 3 Level primary4 Primary actor Treasure Officer 5 Stakeholder employee6 Precondition Login7 Post condition Print out slip of issued fund8 Success scenario Login
Select salary/ maintainace / inventoryEnter amountPrint out slip
9 Extensions 10 Special Req Slip contains details of the issued fund
Date should be mentioned in the slip.
Use case Handle transaction
Actors Accountant
Type Primary
Description: Accountant would handle all transaction. He could collect bills for patient. He also give salary to the employees and give funds for purchasing for inventory.
Accountant
(f rom Actors)
Handle transaction
(from <Use Case Name>)
Fully Dressed Use Case1 Use case name Handle transaction 2 Scope Handle inflow and outflow of cash 3 Level primary4 Primary actor Accountant 5 Stakeholder Employee / patient 6 Precondition Enter issue slip number /bill number7 Post condition Collect bill / pay cash8 Success scenario Login
Select inflow/outflowSelect salary/inventory/maintaince (outflow case)Enter bill/ issue slip numberVerify bill/ fund slipCollect bill / pay cash
9 Extensions Verify issue fund slipWrong issue fund/bill numberCash not available
Extended use case
Diagrams
Schedule Appointment
Receptionist
(f rom HMS)
view schedule
(from included use cases)
Schedule Appointment
(from HMS)
<<extend>>
Admit patient
Admit outdoot patient
(from HMS)
Verify appoinment
(from extended use cases)
<<extend>>
Allotment of bed
(from included use cases)Admit indoor patient
(from HMS)
<<include>>
check doctor reference
(from extended use cases)
<<extend>>
Register patient
(from included use cases)
Admit patient
(from HMS)
<<include>>
Receptionist
(f rom HMS)
Discharge patient
Discharge in-patient
(from classes )
Discharge out-patient
(from classes )
Receptionist
(f rom HMS)
Discharge patient
(from HMS)
view patient services
(from extended use cases)
Generate bill
(from included use cases)
<<include>>
<<extend>>
Give prescription & suggestion
suggest test
(from classes )
Give drug food prescription
(from classes )
Give food prescription
(from classes )
Give suggestion
(from HMS)
Doctor
(f rom HMS)
Give prescription
(from HMS)
view patient record
(from HMS)
<<extend>>
suggest admit
(from classes )
Refer to Opreate
(from included use cases)
suggerst surgery
(from classes )
<<include>>
Refer to Admit
(from included use cases)
<<include>>
<<extend>>
view patient record
view old prescription
(from classes )
view report
(from classes )
view opreation report
(from classes )
view daily report
(from classes )
view test reports
(from classes )
Doctor
(f rom HMS)
view patient record
(from HMS)
Nurse
(f rom HMS)
File reports
File opreation reports
(from classes )
File daily reports
(from classes )
File test reports
(from classes )
File reports
(from HMS)
Nurse
(f rom HMS)
Manage User
Admin
(f rom HMS)
Manage User
(from HMS)
suspent user
(from classes )
delete user
(from classes )
update user
(from classes )
create user
(from classes )
Manage Inventory
Add inventory
(from classes )
Manage Inventory
(from HMS)
stockeeper
(f rom HMS)
issue inventory
(from classes )
check avalibility
(from extended use cases)
<<extend>>
Issue funds
Issue inventory fund
(from classes )
Issue maintaince fund
(from classes )
Issue salary fund
(from classes )
Treasure officer
(f rom HMS)
Issue fund
(from HMS)
check funds avability
(from extended use cases)
<<extend>>
Handle transaction
Handle inventory transaction
(from classes )
Handle maintaince transaction
(from classes )
Handle salary transaction
(from classes )
verify fund
(from included use cases)
Handle funds
(from classes )
<<include>>
Handla bill
(from classes )
Handle transaction
(from HMS)
Accountant
(f rom HMS)
Issue fund
(from HMS)
Schedule Appointment
(from HMS)
Admit patient
(from HMS)Discharge patient
(from HMS)
Receptionist
(f rom HMS)
Give suggestion
(from HMS)
File reports
(from HMS)
Give prescription
(from HMS)
Doctor
(f rom HMS)
Handle transaction
(from HMS)
Accountant
(f rom HMS)Manage User
(from HMS)
Admin
(f rom HMS)
Manage Inventory
(from HMS)
stockeeper
(f rom HMS)
Treasure officer
(f rom HMS)
Nurse
(f rom HMS)view patient record
(from HMS)
System sequence diagram
Schedule Appointment
Receptionist
(f rom HMS)
new-appointment( )
{}{}
Fix apoinment(name ,time, date, doc-id)
Appointment receipt
Admit patient
Enter-doctor-id(doc-id)
Doctor schedule
[*more search]
Hospital management
system
Receptionist
(f rom HMS)
newAdmit( )
Enter-admit type(admit type)
Enter-reference(r-id)
Appointment details, reference details
Register- patient(name,nic,sex)
Registration receipt
Discharge patient
Hospital management
system
Receptionist
(f rom HMS)
Discharge( )
Enter-id(patient-id)
Clear-patient()
Total services bill, services details
Make-payment(amount)
Returns, receipt
Give prescription
Hospital management
system
Enter-services(services-id, quanity)
Services description ,charges
[*more services]
Doctor
(f rom HMS)
New- prescription ()
End- prescription ()
Prescription receipt
Give suggestion
Hospital management
system
Enter-id(prescription-id)
Enter- prescription (prescription)
[*more prescription]
Doctor
(f rom HMS)
New- suggestion ()
End- suggestion ()
suggestion receipt
view patient record
Hospital management
system
Enter-id(-id)
Enter- suggestion (suggestion)
[*more search]
Doctor
(f rom HMS)
Review ()
Enter-Id(pat-id)
End-review()
File report
Hospital management
system
Enter-date(date)
Suggestion, prescription, reports
[*more review]
Nurse
(f rom HMS)
New-report()
Enter-Id(pat-id)
End-report()
Receipt
Issue funds
Hospital management
system
Enter-report-id(r-id)
Enter-report-details( r-details )
[*more reports]
Treasure officer
(f rom HMS)
New-fund()
Enter-fund-type(funf-type)
End-fund()
Receipt
Handle transaction
Hospital management
system
Enter-ammount(ammout)
Verification issue fund
[*more fund]
Accountant
(f rom HMS)
New-transaction()
Enter- transaction-type(t-id)
Enter-slip-id(s-id)
Fund details
Make-payment(amount)
Receipt
End-tranctiont()
Issue Inventory
Hospital management
system
stockeeper
(f rom HMS)
Issue-inventory()
End-issue()
Receipt
Add Inventory
Hospital management
system
Entre inventory (inv-id)
Quanity
Enter-quanity(quanity)
[*more inventory]
stockeeper
(f rom HMS)
Add-inventory()
End-inventory()
Receipt
Hospital management
system
Entre inventory (inv-id)
Enter-quanity(quanity)
[*more inventory]
System contracts
Fix appoiment
Operation : Fix appointment (doc-id :string , date and time: date, patient-name: string)
Cross reference : use case : schedule appoinment
Pre conditions : Receptionist has been authorized by system
Post conditions : new instance of appointment was created. After new instance was
created The attributes were modify . Appointment.date=date ,
appointment.time=time , appointment.docid=docid was settled.
Register patient
Operation : Register patient(name:string ,age:integer, mobileno:double, sex: string )
Cross reference : use case : Admit patient
Pre conditions : Receptionist has been authorized by system
Post conditions : Instance of new patient was created. Attribute of patent like
patient.name=name, patient.age =age, patient.mob=mobile no
patient.sex=sex was seted.When patient was registered then new class of
the admit was initated.
New admit
Operation : New admit ( reference-id : string , date : date, patient-id ,type : string )
Cross reference : use case : Admit patient
Pre conditions : patient has been registered.
Post conditions : After patient was register he would eligible to admit. On calling new admit
new instance of admit class was created. After creation of instances
attributes of this class was modify. admit.reference=reference-id ,
admit.date=date admit.patient=pat-id , admit.type=type.
New discharge
Operation : New discharge(p-id: string , date : date )
Cross reference : use case : discharge patient
Pre conditions : patient was admit in hospital
Post conditions : calling this method cause new instance of Discharge . when instance
“discharge” of discharge was created attribute of discharge was settled.
discharge.patiet=p-id , discharge.date=date.
Enter patient services
Operation : Enter patient services
( services-id:string, duration:integer)
Cross reference : use case : discharge patient
Pre conditions : admitted patient was complete his treatment.
Post conditions : when patient treatment was completed then patient was discarged. Calling
this method cause new instances of bill was created. Instance of billing list
was created. Bill list object get all services used by patient. When services
completed then get total from list object. Bill.patinet=p-id , bill.date=date ,
bill.total=total.
Enter- prescription
Operation : Enter prescription(p-id:string, d-id:string ,date:date type:string, pres:string)
Cross reference : use case : Give prescription
Pre conditions : doctor was authorized and patient was registered
Post conditions : by calling this method new instance of prescription was created. After this
Attributes of prescription was setteed. Prescription.pid=p-id,
prescription.doc=doc-id, Prescription.date=date, prescription.pres=pres,
prescription.type=type
Enter suggestion
Operation : Enter suggestion(p-id:string, d-id:string ,date:date type:string, sug:string)
Cross reference : use case : Give suggestion
Pre conditions : doctor was authorized and patient was registered
Post conditions : when doctor gave suggestion. Instance of suggestion class was created.
After created this instance set arrtbutes. Suggestion.patient=p-id,
suggestion.doctor=d-id, suggestion.date=date, suggestion.type=type,
suggestion.sug=sug.
Enter report
Operation : Enter report(p-id:string, nur-id:string ,date:date type:string, rep:string)
Cross reference : use case :File report
Pre conditions : Nurse was authorized and patient was registered
Post conditions : when report was created nurse would file report in patient record. When
Filing a report new object of report was created. After object created its
attributes was settled. Report.patient=p-id, report.date=date,
report.type.type , report.rep=report
Enter transaction
Operation : Enter transaction(slip-id:string, amout:double ,date:date type:string)
Cross reference : use case :Handle transaction
Pre conditions : account was authorized
Post conditions : when new transaction was done then instance of transaction was created.
After creating instance of Transaction class attributes of transaction was
set. Transaction.slip=slip-id, Transaction.ammount=amout ,
Transaction.date=date , Transaction.type=type.
Sequence Diagrams
Schedule Appointment
: Receptionist : schedule : appoiment
view schedule
doctor schedule
enter appoiment
conformation of appoinment
Admit patient
: Receptionist : admit : patient : outdoorAdmit : indoorAdmit
req.admit
admit conform
conform admitpatient id
register (for indoor admit)
(for outdoor admit)
details
details
Discharge patient
: Receptionist : discharge : patient
enter pat-id
verify patient
conform patient
Allow discharge
enter discharge detail
conform discharge
Give prescription
: Doctor : prescription : patient
req prescriptionverify patient
conform patient
Allow prescription
enter prescription
confrom prescription
File reports
: Report : patient : Nurse
enter patient_idverift patient
enter report details
confrom report
conform patient
allow report
Give suggestion
: Doctor : suggestion : patient
req suggestion
Allow suggestion
enter suggestion
complete suggestion
verify patient
conform patient
Handle transaction
: Accountant : tranction : Funds : Bill : patient
req tnanc (for in tranctions)
(for out tranction)
verfy patient
conform
conform
allow tranction
enter tranction
complete tranction
Issue funds
: Treasure officer : Funds : staff
req fund verift employerconform
Allow funds
enter fund
complete fund
Collaboration Diagrams
Schedule Appointment
: Receptionist
: schedule {destroyed}
:oppoiment {new}
1: getschedule(doc-id)
3: destroyed()
2: fix oppoinment (doc-id, time,date)
Admit patient
:Admit new( )
: Receptionist
: patient new( )
2: register ( name,sex,age )
1: req.admit( )
Discharge patient
:discharge {new}
:patient {destroyed}
: Receptionist
1: enterpatient(p)
3:
2: discharge(pat-id,date,total bill,next visit)
Give prescription
:prescription {new}
:patient {destroyed}
: Doctor
2: enterprec(prec-type,presc deatail,prec-date, doc-id)
1: enterpatient(pat-it)
3: destroyed()
File reports
:report {new}
:patient {destroyed}
: Nurse
2: enterReport(r-date, rep-type, rep-result, nur-id)
1: verify patient(pat-it)
3: destroyed()
Give suggestion
:suggestion {new}
:patient {destroyed}
: Doctor
2: enterSuggestion(sug-type , sug-date , sug-detail , doc-id)
1: enterpatient(pat-it)
3: destroyed()
Issue funds
: Treasure officer
:fund {new}
:emp {destroyed}
1: verifyemployee(e-id)
2: enterFund(f-date, f-amount, f-type,treasure-id)
3: destroyed()
Class diagram
outdoorAdmit
ward-id : int
(f rom Use-Case Model)
appoiment
appit-id : stringtime : timedate : Datedoc-id : string
appoinmentstatus() : void
(f rom Use-Case Model)
Discharge
dic-id : stringpat-id : stringdis-date : Dateadmit-id : String
generatebill(servces) : Amount
(f rom Use-Case Model) Bill
bill-id : stringdis-id : stringtotla : Amount
(f rom Use-Case Model)
11 1
+have a
1
admit
admit-id : stringpat-id : stringdate : dateadmit-type : stringamit-detail : string
admitstatus() : voidalloctebed() : Bedno
(f rom Use-Case Model)
Receptionist
rres-id : stringname : stringshitt : string
fixappoinment(doc-id, date) : Appoinmenynoviewschedule(doc-id) : voidadmitpatient(pat-id, date, diseases, type) : voidregisterpatient(name, nic, mob, sex) : pat-iddischarge(admit-id, services) : void
(f rom Use-Case Model)
+Fix appoiment
1..*
1
+perform
1..*
1
0..*
1..*
0..*
1..*
indoorAdmit
oppoint-id : string
(f rom Use-Case Model)
Bed
bed-no : intward-id : stringdept-id : int
(f rom Use-Case Model)
1
1
1
+allocate1
suggestion
seg-id : stringpat-id : stringdoc-id : StringSeg-date : Dateseg-deteil : string
(f rom Use-Case Model) prescription
prec-id : stringprec-deaail : stringprec-date : Datepat-idStringdoc-id : string
(f rom Use-Case Model)
patient
pat-idtypedetails
paybill(amount) : void
(f rom Use-Case Model)
11..*
+Admit
11..*
register patianm
1
1..*
1
+/belong to
1..*
0..*
1
+/belong to0..*
1
1..*
1
+paybill
1..*
1
Report
r-id : Srtingp-id : Stringreport detail : Stringr-date : Date
(f rom Use-Case Model)
+/belongto
Nures
n-id : string
filereport(pat-id, report) : voidviewreport(pat-id, r-id) : voidviewsuggestion(p-id, date) : suggestiom
(f rom Use-Case Model)
0..*
1..*
0..*
+file
1..*
doctor
doc-id : stringspeclization : Stringdept : StringShift : string
giveprescription(pres, pat-id) : voidgivesuggestion(sug, pat-id)viewpres(pat-id) : Presscriptionviewsuggestion(pat-id) : Sugestionviewreport(pat-id) : Report
(f rom Use-Case Model)
0..*
1..*
0..*
+suggest to patient
1..*
0..*
1..*
+prescribe to patient
0..*
1..*
Department
dept-id : intdept-nam : srtingdept-loc : string
(f rom Use-Case Model)
ward
ward-id : stringdept : stringward-type : string
wardstatus() : status
(f rom Use-Case Model)
1 1..*
+belong
1 1..*
1
1..*
1
1..*
Component diagram
receptionistinterface
resisterpatientResistration<<Database>>
outdoor
indoor
admitstatus
doctorinterface
registered
nursrinterface
reportrecorder
tesreport
HosptlDB<<Database>>
report
doctorinterface
testreportstatus
prescriptionrecorder
Foodpresscption
drugprescption
doctorinterface
prescptionDB<<Database>>
prescribed
prescription
nursrinterface
tranctionDb<<Database>>
accountant interface
treasureofficerinterface
tranctionrecorder
bill
funds
tranction
fundDB<<Database>>
fundstatus
isssuefunds
Deployment diagram
Receptionist computer
register
Admit
discharge
Dataserver
mysql
Doctor computre
givetreatment
viewtreatment
nursecomputre
filereport
viewtreatment