PowerPoint Presentation

Project Progress ReportF.Aid Team HIS project

AgendaProject backgroundProcess & PlanRequirementArchitectDesignProject backgroundGoalHIS 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 yearsCurrently, the hospital have 12 clinics, 3 units perform preclinical, 2 units receiving patient and have expansion need in the futureThe purpose of software is increase perform in the healthcare, improve productivity of doctor, nurse and staff of hospital

Vision

ScopeSoftware 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

Process & Plan

Process & PlanRequirement System modules

Requirement - Functional1. Systems ManagementsCode Version FeaturesThe Requester/UserUsecase PriorityHT- 011.0User group ManagementAdminUC.SM.GM.01UC.SM.GM.02UC.SM.GM.03UC.SM.GM.04HighHT-021.0User ManagementAdminUC.SM.VM.01UC.SM.VM.02UC.SM.VM.03UC.SM.VM.04HighHT-031.0AuthorizationAdminUC.SM.AUHighHT-041.0System diaryAdminUC.SM.SD.01UC.SM.SD.02MediumRequirement - functional2. Items ManagementDM-011.0WardManageUC.IM.WM.01UC.IM.WM.02UC.IM.WM.03UC.IM.WM.04MediumDM-021.0DistrictManageUC.IM.DM.D1UC.IM.DM.D2UC.IM.DM.D3UC.IM.DM.D4MediumDM-031.0Province/CityManageUC.IM.PM.P1UC.IM.PM.P2UC.IM.PM.P3UC.IM.PM.P4MediumDM-041.0DepartmentManageUC.IM.FM.01UC.IM.FM.02UC.IM.FM.03UC.IM.FM.04MediumDM-051.0StaffManageUC.IM.SD.01UC.IM.SD.02UC.IM.SD.03UC.IM.SD.04HighDM-061.0PathologicManageUC.OP.DM.01UC.OP.DM.02UC.OP.DM.03UC.OP.DM.04HighDM-071.0Disease GroupManageUC.IM.DG.01UC.IM.DG.02UC.IM.DG.03UC.IM.DG.05MediumDM-081.0MedicineManageUC.OP.MM.01UC.OP.MM.02UC.OP.MM.03UC.OP.MM.04MediumDM-091.0PrescriptionManage DoctorUC.OP.PM.01UC.OP.PM.02UC.OP.PM.03UC.OP.PM.04MediumRequirement - functional3. Manage patient information and metical register informationDM-121.0Patient InformationReception StaffUC.PI.IM.01UC.PI.IM.02UC.PI.IM.03UC.PI.IM.04HighDM-131.0Registration medical Reception StaffUC.PI.RI.01UC.PI.RI.02UC.PI.RI.03UC.PI.RI.04Medium4. Outpatients Examine KB-011.0Medical Information DoctorNurseUC.OP.PI.01UC.OP.PI.02UC.OP.PI.03UC.OP.PI.04HighKB-021.0Information vital signNurseUC.OP.BS.01UC.OP.BS.02UC.OP.BS.03UC.OP.BS.04Medium5. Statistical/ ReportTK-011.0Statistical/ ReportDirectorUC.SR.01UC.SR.02UC.SR.03UC.SR.04UC.SR.05UC.SR.06MediumRequirement Use case

Architect System content

Architect physical view

Architect static view

Architect dynamic view

Architect sequence

Architect Quality attributesIDVersionQuality attributeDescriptionPE-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"Design database diagram

Design database schemas dmTinhThanh (MaTinhThanh, TenTinhThanh, TrangThai)dmQuanHuyen (MaQuanHuyen, TenQuanHuyen, MaTinhThanh, TrangThai)dmPhuongXa (MaPhuongXa, TenPhuongXa, MaQuanHuyen, TrangThai)dmPhongBan (MaPhongBan, TenPhongBan, TrangThai)dmBanKham (MaBanKham, TenBanKham, MaPhongKham, TrangThai)dmNhomBenh (MaNhomBenh, TenNhomBenh, TrangThai)dmBenhLy (MaBenhLy, TenBenhLy, MaNhomBenh, TrangThai)dmThuoc (MaThuoc, TenThuoc, KhoiLuongHoatChat, DonViTinh)Design database schemas NhanVien (MaNhanVien, MatKhau, TenNhanVien, GioiTinh, NamSinh, ChuyenKhoa, sdt, SoNha, Duong, MaPhuongXa, MaQuanHuyen, MaTinhThanh, MaNhom, TrangThai)NhomNguoiDung (MaNhom, TenNhom, TrangThai)ChucNang (MaChucNang, TenChucNang, TrangThai)NhomNguoiDungChucNang (MaNhom, MaChucNang, Tim, Them, CapNhat, TaoBaoCao, TrangThai)BenhNhan (MaBenhNhan, HoTen, GioiTinh, NamSinh, NgheNghiep, SDT, SoNha, Duong, MaPhuongXa, MaQuanHuyen, MaTinhThanh, MaNhanVien, TrangThai)ThongTinDangKy (MaTTDK, NgayGioDangKy, MaPhongKham, MaBenhNhan, MaDVTN, MaNhanVien, TrangThai)Design database schemas ThongTinSinhHieu (MaTTSH, CanNang, ChieuCao, NhipTim, NhipTho, NhietDo, NgayDo, MaBenhNhan, MaNhanVien) BenhAn (MaBenhAn, MaBenhLy, TienSu, MaTTSH, MaTTDK, MaPhongKham, MaBenhNhan)ToaThuoc (MaToaThuoc, Ngay, MaBacSi, MaNhomBenh, MaBenhAn, MaNhanVien)LieuLuong (MaLieuLuong, MaToaThuoc, MaThuoc, DonViTinh, SoLuongThuoc, LanNgay, LieuLan, CachDung)NhatKy (STT, NoiDung, MaNhanVien, Ngay, MaPhong, MaBanKham)Design logic data model NO.Alias InterpretationDomain valueNote1MaTinhThanhProvince IDVarchar(10)Not null2TenTinhThanhProvince nameNvarchar(50)Not null3TrangThaiStatusBitNull