This report provides a description of the case for the Family First Medical Centre and the development of a medical information system for them. It includes business requirements, feasibility analysis, system design, data flow diagrams, and data models.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: SYSTEM DESIGN System Design Name of the Student: Name of the University: Author Note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1 SYSTEM DESIGN Executive Summary This report has been prepared here for the description of the case for the Family First Medical Centre. The organizationwas started by Dr. Robert Slate. However, the current manual procedures and the paper works have been hampering the business of the organization for a long time and hence the organization would be helped greatly if a medical information system is developed for them. The description of the system is also included in this report aided by models and illustrations.
2 SYSTEM DESIGN Table of Contents System Request................................................................................................................................4 Business Requirements................................................................................................................4 Business Values...........................................................................................................................4 Constraints...................................................................................................................................4 Work Plan........................................................................................................................................4 Feasibility Analysis.........................................................................................................................6 Technical......................................................................................................................................6 Organizational..............................................................................................................................6 Economic.....................................................................................................................................7 Requirements Definition..................................................................................................................8 Functional Requirements.............................................................................................................8 Non-functional Requirements......................................................................................................8 Use Cases.........................................................................................................................................9 Process Model................................................................................................................................10 Context Diagram........................................................................................................................10 Level 0 Data Flow Diagram......................................................................................................11 Level 2 Data Flow Diagram......................................................................................................12 Data Model....................................................................................................................................13 Data Dictionary..........................................................................................................................13
3 SYSTEM DESIGN ER Diagram...............................................................................................................................17 Bibliography..................................................................................................................................18
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
4 SYSTEM DESIGN System Request A medical information system is to be developed for the organization as the current business procedure have been manual and this very unconvincing for Dr. Slate. Hence, the need for an information system has come up that would be managing all the information and procedures of the system. Business Requirements The business requirements of the organization are provided below: The patients’ details are to store in the system. The treatment and the prescription associated with it should be handled properly. The prescription is required to be filed. Finally, the patient should receive the receipt for the prescriptions. Business Values The organization is looking to improve the medical facilities for their customers so that the cost of treatment is reduced and process is accelerated to a great extent. Constraints The company policy does not allow the refills of the Family First prescriptions. Work Plan The work plan for the development of the medical information system of the Family First Medical Center is provided below: Task NameDuratioStartFinishPredecessors
5 SYSTEM DESIGN n Medical Information System Development80 daysMon 9/2/19Fri 12/20/19 Project initiation7 daysMon 9/2/19Tue 9/10/19 Client Meeting3 daysMon 9/2/19Wed 9/4/19 Requirements Gathering2 daysThu 9/5/19Fri 9/6/192 Budget allocation2 daysMon 9/9/19Tue 9/10/193 Project design15 daysWed 9/11/19Tue 10/1/19 Project team allocation4 daysWed 9/11/19Mon 9/16/194 functional Requirements2 daysTue 9/17/19Wed 9/18/196 Non-Functional Requirements1 dayThu 9/19/19Thu 9/19/197 Hardware Requirements2 daysFri 9/20/19Mon 9/23/198 System Design3 daysTue 9/24/19Thu 9/26/199 System Modelling3 daysFri 9/27/19Tue 10/1/1910 Project Implementation43 daysWed 10/2/19Fri 11/29/19 Procurement of Hardware2 daysWed 10/2/19Thu 10/3/1911 Software Installation4 daysFri 10/4/19Wed 10/9/1913 Front End Development11 daysThu 10/10/19Thu 10/24/1914 Data base development14 daysFri 10/25/19Wed 11/13/1915
6 SYSTEM DESIGN Backend integration12 daysThu 11/14/19Fri 11/29/1916 System Testing13 daysMon 12/2/19Wed 12/18/19 Error Detection5 daysMon 12/2/19Fri 12/6/1917 Updating current project6 daysMon 12/9/19Mon 12/16/1919 System Documentation2 daysTue 12/17/19Wed 12/18/1920 Project Closure2 daysThu 12/19/19Fri 12/20/19 Handing over Documentation1 dayThu 12/19/19Thu 12/19/1921 Project Team Sign Off1 dayFri 12/20/19Fri 12/20/1923 Feasibility Analysis Technical The currently manual procedures of the organization would be developed and improved to a great extent. The procedures would be accelerated and the overall cost of treatment would be reduced and the hence, the project would be technically feasible. Organizational Theorganizationalfeasibilitydependsonbusinessefficiencyofthesystem.The development of the system would increase the overall efficiency of the business by reducing the
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
7 SYSTEM DESIGN responsetimeandincreasingtheprofit.Hence,thesystemwouldbefeasibleforthe organization. Economic It is very important that the economic aspect of the project is also considered for the feasibility of the project. The cost benefit analysis provided below is used here for the feasibility study. Analysis Variables: Discount Rate Used6.00% Annual Benefits $ 35,000.00 AnnualOperational Costs $ 8,700.00 One-Time Development Cost $ 38,000.00 Yearof Project 012345TOTALS Economic Benefit$0.00 $ 35,000.00 $ 35,000.00 $ 35,000.00 $ 35,000.00 $ 35,000.00 Discount Rate1.00000.94340.89000.83960.79210.7473 PV of Benefits$0.00 $33,018.8 7$31,149.88$29,386.67 $27,723.2 8$26,154.04 NPVofall BENEFITS$0.00 $ 33,018.87 $ 64,168.74 $ 93,555.42 $ 121,278.7 0 $ 147,432.73 $ 147,432.73 One-Time COSTS $(38,000 .00) Recurring Costs$0.00 $ (8,700.00) $ (8,700.00) $ (8,700.00) $ (8,700.00) $ (8,700.00) Discount Rate1.00000.94340.89000.83960.79210.7473 PVofRecurring Costs$0.00 $ (8,207.55) $ (7,742.97) $ (7,304.69) $ (6,891.21) $ (6,501.15)
8 SYSTEM DESIGN NPV of all COSTS $(38,000 .00) $ (46,207.55 ) $ (53,950.52 ) $ (61,255.20) $ (68,146.42 ) $ (74,647.56) $ (74,647.56) Overall NPV $ 72,785.17 Overall ROI 0.9751 Break-even Analysis YearlyNPVCash FLOW $(38,000 .00) $ 24,811.32 $ 23,406.91 $ 22,081.99 $ 20,832.06 $ 19,652.89 OverallNPVCash FLOW $(38,000 .00) $ (13,188.68 ) $ 10,218.23 $ 32,300.21 $ 53,132.28 $ 72,785.17 From the analysis made above it can be easily seen that both the ROI and NPV obtained on the analysis variables are positive. Hence, it can be derived that the system development would be economically feasible for the organization. Requirements Definition Functional Requirements The main functional requirements of the system are: ï‚·Patient name verification ï‚·Patient Diagnosis process ï‚·Storing drug log ï‚·Generation of the receipt of the prescription for the patients Non-functional Requirements The non-functional requirements of the system are:
9 SYSTEM DESIGN ï‚·The system should be available 24x7 as the patients might need emergency attention at any time. ï‚·The data for the system should be secure as the system would be containing a large amount of data about the health of the patients. ï‚·The system should be scalable as in longer run the system would be required to store an extensive amount of data. Use Cases The main use cases of the system developed for the Family First organization are: ï‚·Registration ï‚·Appointment ï‚·Record details ï‚·Treatment ï‚·Prescription ï‚·Generate Receipt ï‚·Make Payment ï‚·Drug Log
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
11 SYSTEM DESIGN Level 0 Data Flow Diagram Level 1 Data Flow Diagram The treatment and prescription process has been described in this Level 1 Data Flow diagram provided below:
12 SYSTEM DESIGN Level 2 Data Flow Diagram The treatment and prescription process has been described in this Level 2 Data Flow diagram provided below:
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
13 SYSTEM DESIGN Data Model Data Dictionary Category AttributeDatatypeSizeNULL/NOT NULL Key Category_Nam e String50NOT NULLPrimary Key Drug AttributeDatatypeSizeNULL/NOT NULL Key Drug_IDintNOT NULLPrimary Key CompositionString100NOT NULL Category_Nam e String50NOT NULLForeign Key PriceCurrencyNOT NULL Drug Log AttributeDatatypeSizeNULL/NOT NULL Key Log_IDint10NOT NULLPrimary Key
18 SYSTEM DESIGN Bibliography Azaria, A., Ekblaw, A., Vieira, T. and Lippman, A., 2016, August. Medrec: Using blockchain for medical data access and permission management. In 2016 2nd International Conference on Open and Big Data (OBD) (pp. 25-30). IEEE. Burrough,P.A.,McDonnell,R.,McDonnell,R.A.andLloyd,C.D.,2015.Principlesof geographical information systems. Oxford university press. Cassidy, A., 2016.A practical guide to information systems strategic planning. Auerbach Publications. Fuller, M.A., Valacich, J.S., George, J.F. and Schneider, C., 2017.Information Systems Project Management: A Process and Team Approach, Edition 1.1. Prospect Press. Wager, K.A., Lee, F.W. and Glaser, J.P., 2017.Health care information systems: a practical approach for health care management. John Wiley & Sons. Walsham, G., 2015. Interpreting information systems in organizations.