1. PROJECT PROGRESS REPORT F.AID TEAM – HIS PROJECT

2. AGENDA  PROJECT BACKGROUND  PROCESS & PLAN  REQUIREMENT  ARCHITECT  DESIGN

3. PROJECT BACKGROUND GOAL HIS HOSPITAL NEED SOFTWARE TO SOLVE SOME CURRENT PROBLEMS AND FUTURE AS: EVERY DAY, HOSPITAL HAVE ABOUT 1000 PATIENT TO EXAMINE WITH 1200 TIME. ACCORDING TO THE PREDICTION OF PATIENT GO TO HEALTH CARE MAY INCREASE 3 TIME IN 5 YEARS CURRENTLY, THE HOSPITAL HAVE 12 CLINICS, 3 UNITS PERFORM PRECLINICAL, 2 UNITS RECEIVING PATIENT AND HAVE EXPANSION NEED IN THE FUTURE THE PURPOSE OF SOFTWARE IS INCREASE PERFORM IN THE HEALTHCARE, IMPROVE PRODUCTIVITY OF DOCTOR, NURSE AND STAFF OF HOSPITAL VISION SCOPE SOFTWARE WILL USING BY 12 CLINICS, THE ROOM PERFORM CLINICAL SERVICES. THE COMPUTER HAVE BEEN INSTALL SOFTWARE CAN USING IN DATABASE VIA LOCAL NETWORK, TO CONNECT AND SYCE DATA BETWEEN DEPARTMENTS

4. PROCESS & PLAN

6. REQUIREMENT – SYSTEM MODULES

7. REQUIREMENT - FUNCTIONAL 1. System’s Managements CodeVersionFeaturesThe Requester/UserUsecasePriority HT- 011.0 User group Management Admin UC.SM.GM.01 UC.SM.GM.02 UC.SM.GM.03 UC.SM.GM.04 High HT-021.0User ManagementAdmin UC.SM.VM.01 UC.SM.VM.02 UC.SM.VM.03 UC.SM.VM.04 High HT-031.0AuthorizationAdminUC.SM.AUHigh HT-041.0System diaryAdmin UC.SM.SD.01 UC.SM.SD.02 Medium

8. REQUIREMENT - FUNCTIONAL 2. Items Management DM-011.0WardManageUC.IM.WM.01 UC.IM.WM.02 UC.IM.WM.03 UC.IM.WM.04 Medium DM-021.0DistrictManageUC.IM.DM.D1 UC.IM.DM.D2 UC.IM.DM.D3 UC.IM.DM.D4 Medium DM-031.0Province/CityManageUC.IM.PM.P1 UC.IM.PM.P2 UC.IM.PM.P3 UC.IM.PM.P4 Medium DM-041.0DepartmentManageUC.IM.FM.01 UC.IM.FM.02 UC.IM.FM.03 UC.IM.FM.04 Medium DM-051.0StaffManageUC.IM.SD.01 UC.IM.SD.02 UC.IM.SD.03 UC.IM.SD.04 High DM-061.0PathologicManageUC.OP.DM.01 UC.OP.DM.02 UC.OP.DM.03 UC.OP.DM.04 High DM-071.0Disease GroupManageUC.IM.DG.01 UC.IM.DG.02 UC.IM.DG.03 UC.IM.DG.05 Medium DM-081.0MedicineManageUC.OP.MM.01 UC.OP.MM.02 UC.OP.MM.03 UC.OP.MM.04 Medium DM-091.0PrescriptionManage Doctor UC.OP.PM.01 UC.OP.PM.02 UC.OP.PM.03 UC.OP.PM.04 Medium

9. REQUIREMENT - FUNCTIONAL 3. Manage patient information and metical register information DM-121.0 Patient Information Reception Staff UC.PI.IM.01 UC.PI.IM.02 UC.PI.IM.03 UC.PI.IM.04 High DM-131.0 Registration medical Reception Staff UC.PI.RI.01 UC.PI.RI.02 UC.PI.RI.03 UC.PI.RI.04 Medium 4. Outpatient’s Examine KB-011.0 Medical Information Doctor Nurse UC.OP.PI.01 UC.OP.PI.02 UC.OP.PI.03 UC.OP.PI.04 High KB-021.0 Information vital sign Nurse UC.OP.BS.01 UC.OP.BS.02 UC.OP.BS.03 UC.OP.BS.04 Medium 5. Statistical/ Report TK-011.0Statistical/ ReportDirectorUC.SR.01 UC.SR.02 UC.SR.03 UC.SR.04 UC.SR.05 UC.SR.06 Medium

10. REQUIREMENT – USE CASE

11. ARCHITECT – SYSTEM CONTENT

12. ARCHITECT – PHYSICAL VIEW

13. ARCHITECT – STATIC VIEW

14. ARCHITECT – DYNAMIC VIEW

15. ARCHITECT – SEQUENCE

16. ARCHITECT – QUALITY ATTRIBUTES IDVersionQuality attributeDescription PE-011.0Performance  System will be quickly show results (2-5s) when perform functions  The software will work on all computers of the PC at hospital as well as the company. For the highest efficiency. No crashes (freezes)... to use.  Low latency, fast operation. Increase work efficiency (not much time). AV-021.0Availability  During time operation of the store from 8 am to 10 pm, the system ensures the availability of data. Make sure the store is always active during downtime (if any). US-031.0Userability  All the interface of each functionality layout reasonable, easy to see, easy to manipulate.  The system has tools to help support, user queries can lookup the catalog in the "User Guide"

17. DESIGN – DATABASE DIAGRAM

18. DESIGN – DATABASE SCHEMAS 1. DMTINHTHANH (MATINHTHANH, TENTINHTHANH, TRANGTHAI) 2. DMQUANHUYEN (MAQUANHUYEN, TENQUANHUYEN, MATINHTHANH, TRANGTHAI) 3. DMPHUONGXA (MAPHUONGXA, TENPHUONGXA, MAQUANHUYEN, TRANGTHAI) 4. DMPHONGBAN (MAPHONGBAN, TENPHONGBAN, TRANGTHAI) 5. DMBANKHAM (MABANKHAM, TENBANKHAM, MAPHONGKHAM, TRANGTHAI) 6. DMNHOMBENH (MANHOMBENH, TENNHOMBENH, TRANGTHAI) 7. DMBENHLY (MABENHLY, TENBENHLY, MANHOMBENH, TRANGTHAI) 8. DMTHUOC (MATHUOC, TENTHUOC, KHOILUONGHOATCHAT, DONVITINH)

19. DESIGN – DATABASE SCHEMAS 9. NHANVIEN (MANHANVIEN, MATKHAU, TENNHANVIEN, GIOITINH, NAMSINH, CHUYENKHOA, SDT, SONHA, DUONG, MAPHUONGXA, MAQUANHUYEN, MATINHTHANH, MANHOM, TRANGTHAI) 10. NHOMNGUOIDUNG (MANHOM, TENNHOM, TRANGTHAI) 11. CHUCNANG (MACHUCNANG, TENCHUCNANG, TRANGTHAI) 12. NHOMNGUOIDUNGCHUCNANG (MANHOM, MACHUCNANG, TIM, THEM, CAPNHAT, TAOBAOCAO, TRANGTHAI) 13. BENHNHAN (MABENHNHAN, HOTEN, GIOITINH, NAMSINH, NGHENGHIEP, SDT, SONHA, DUONG, MAPHUONGXA, MAQUANHUYEN, MATINHTHANH, MANHANVIEN, TRANGTHAI) 14. THONGTINDANGKY (MATTDK, NGAYGIODANGKY, MAPHONGKHAM, MABENHNHAN, MADVTN, MANHANVIEN, TRANGTHAI)

20. DESIGN – DATABASE SCHEMAS 15. THONGTINSINHHIEU (MATTSH, CANNANG, CHIEUCAO, NHIPTIM, NHIPTHO, NHIETDO, NGAYDO, MABENHNHAN, MANHANVIEN) 16. BENHAN (MABENHAN, MABENHLY, TIENSU, MATTSH, MATTDK, MAPHONGKHAM, MABENHNHAN) 17. TOATHUOC (MATOATHUOC, NGAY, MABACSI, MANHOMBENH, MABENHAN, MANHANVIEN) 18. LIEULUONG (MALIEULUONG, MATOATHUOC, MATHUOC, DONVITINH, SOLUONGTHUOC, LANNGAY, LIEULAN, CACHDUNG) 19. NHATKY (STT, NOIDUNG, MANHANVIEN, NGAY, MAPHONG, MABANKHAM)

21. DESIGN – LOGIC DATA MODEL NO.AliasInterpretationDomain valueNote 1MaTinhThanhProvince IDVarchar(10)Not null 2TenTinhThanhProvince nameNvarchar(50)Not null 3TrangThaiStatusBitNull