Southern New Hampshire University - IT 650Final Project Submission - 9-2 - Law Ethics and Security Plan and Database Management System. 9-2 Final Project Submission: Law, Ethics, and Security Plan and Database Management System Westlake Research Hospital IT-650 Principles of Database Design 1 July 2020.

Document Content and Description Below

9-2 Final Project Submission: Law, Ethics, and Security Plan and Database Management System Westlake Research Hospital IT-650 Principles of Database Design 1 July 2020 INTRODUCTION Westlake Re... search Hospital is a traditional medical hospital as well as an investigative drug research facility. The hospitals’ research organization has recently undertaken a new double-blind study for a new antidepressant drug. The organization will utilize over 400 participants for this study, including doctors, researchers, pharmacists and patients. Study patients will either receive the new drug or Prozac during this study and depending on the results of the follow-up appointments they may continue treatment. The study is expected to last for 18 months and patients will have regularly scheduled follow-up interviews with their doctor twice a month. At the start of the study, each doctor will be given 20 patients to examine and interview. Over the course of the study, it is expected that some patients may and will drop out of the program. The pharmaceutical company sponsoring this study will distribute the study drugs in generic bottles with only the two testing supervisors knowing who is receiving the new drug. This will be done to, one, prevent any trade secrets for this drug to be compromised and leaked to their competition and secondly, to prevent any of the participants in knowing what they are receiving. This will help in preventing the patients from generating false results while taking the study medication. PROBLEM Currently, Westlake is maintaining their patient data with the utilization of traditional methods of storing data, that is through paper forms and note pads. Information is typically transferred through email between the doctor and their secretaries. The doctors will maintain the patient data in file cabinets within their office and reference it for each appointment. The patient’s files are growing making it harder and more time consuming for the doctor to track changes with each patient. In order to improve business operations and patient tracking while complying with current regulation the hospital will need to effectively streamline their patient data into a database. This will allow the doctor to input more pertinent information into the patient’s file and prevent access to the data by unauthorized groups and individuals. Limitations 1. Information is stored manually on paper which consumes much time and effort by the doctors and their staff. 2. Due to cost restraints, the hospital is reluctant to organize the patient’s data from their current systems and methods because it will require additional funding. 3. The system currently used by the hospital cannot properly track their patient’s health records. 4. The existing system lacks any real data retrieval system. 5. The existing system results in extra overhead costs for the storage and retrieval of patient records, such as paper and extra personnel costs. 6. Using paper forms is not a secure method of data storage; paper can be lost, destroyed or altered. 7. Backing up a manual system can increase departmental budgets for items such as storage space, consumables and personnel resources. 8. The current system limits functional communications between researchers, pharmacists and doctors. 9. Currently patients manually record their appointment times and wait in queue to see the doctor. 10. The current system cannot flag patients whose medications may cause potentially hazardous situations when interacted. 11. The current system is not capable of generating meaningful analytics. Business Requirements 1. The hospital requires an information system that is quick. 2. An online patient scheduler. 3. The system should allow patients to view their medical history online. 4. The system should securely store patient data. 5. Prevent external entities from compromising testing data. 6. Able to assign hospital staff the appropriate roles and permissions for data access. 7. Allows doctors to input patient’s vitals, test results and notes. 8. Restrict doctors in being able to only view their patients’ data. 9. Prevent the duplication of stored patient data. 10. Robust enough to be able to store all of the patient’s data from their first intake screening to follow-up visits and capable of analyzing their medical condition. 11. The system should allow for 24x7 availability to patient records by hospital personnel and patients. 12. Allow for the effective tracking of hospital financial data. In order to achieve the above business requirement, the hospital will need to implement a modern database system. The implementation of a database system can aid in enhancing internal and business processes and procedures. The system being proposed is capable of effectively tracking hospital revenues and expenditures. In addition to generating meaningful data analytics that can be used by operations for tracking costs and in the case of this study, tracking patient results. DEPARTMENTS / OPERATIONS All departments within the hospital function differently while working towards the overall goals of the hospital. However, being able to streamline departmental operations and procedures will help in solving many of the organizations issues. At Westlake, the potential for multiple departments having overlapping dependencies exists and by thoroughly analyzing and breaking the processes down will allow for efficiencies to be made. Some of the departments impacted by the above would be: Pharmacy: The challenges faced by this department can result in significant harm to the hospital. Patient data provided to the pharmacy should be detailed to help the pharmacist in administering the proper medications to patients. Additionally, security is a concern, in that the appropriate people should have access to this information while restricting access to those not authorized. The pharmacy department is facing the following challenges: • Being able to identify the difference between a medical symptom and a medication side-effect the patient is having can be a challenge. If critical information is not available to the pharmacy team the patient could be at risk of harm. • The ability to analyzing a patient’s health record in order to provide input into the patient’s medication and treatment process prescribed by the doctor. • Information maintained by the hospital regarding the new antidepressant drug study needs to be secured. Finance: The ability to be able to track the hospital’s financials is critical to the success of the organization. This group should have an understanding of the expenses generated by other departments, including such costs as employee wages, drug costs and vendor expenses. Failing to capture all of the expenses incurred by the hospital could lead to financial hardships by the hospital. Additionally, access to this group’s data should be secured and only authorized user should be able to access the data. Finally, financial data should be maintained in a separate environment apart from patient data. Lab: The challenges faced by this group is related to the misunderstandings that arise from their message. Users should be utilizing the proper communications channels when communicating with other groups; similar to the utilization of notes, depression scales and which patient test they are examining. Administration: This assumes that the users here are the doctors who are examining and interviewing patients when they come in for their appointments. Doctors should have the ability input a patient’s vitals and any issues they are having. The failure to be able to do these routine tasks could result in misleading patient data being used by other departments, skewing the study’s results. DATABASE ANALYSIS AND DESIGN Conceptual Design The Conceptual Data Model is a schema that provides an in-depth look at business concepts, that is developed for a business audience. The model is not meant to be a solutions model and as a general rule it is technology and application neutral (Techopedia, 2018a). When creating this model, it is not recommended to draw all of the entities, this is a conceptual model and adding any unnecessary relationships and entities should be avoided. This model provides users a good means for viewing entity relationships. The model is designed to be independent of any data storage technologies or database management systems (DBMS) (Techopedia, 2018). Conceptual Data Model for Westlake Research Hospital. REFERENCES Conger, S. (2014). Hands-On Database: An Introduction to Database Design and Development, Second Edition. Upper Saddle River: Pearson Education, Inc. Techopedia. (2018a). Conceptual Data Model. Techopedia Inc. Referenced from https://www.techopedia.com/definition/28026/conceptual-data-model Techopedia. (2018b). Logical Data Model (LDM). Techopedia Inc. Referenced from https://www.techopedia.com/definition/30599/logical-data-model-ldm Techopedia. (2018c). Physical Data Model. Techopedia Inc. Referenced from https://www.techopedia.com/definition/30600/physical-data-model WhoIsHostingThis. (2018). SQL ANSI Standards: How to Build Industry-standard Databases. WhoIsHostingThis.com. Referenced from https://www.whoishostingthis.com/resources/ansi-sql-standards/ DB Engines. (2018). DB-Engines Ranking. Solid IT GMBH. Referenced from https://db-engines.com/en/ranking Microsoft. (2018a). Features Supported by the Editions of SQL Server 2014. Microsoft Corporation. Referenced from https://msdn.microsoft.com/en-us/library/cc645993(v=sql.120).aspx Microsoft. (2014). Comparison of Microsoft Access SQL and ANSI SQL. Microsoft Corporation. Referenced from https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb208890(v=office.12) Chan, A. (2014). Microsoft Access vs. Microsoft SQL Server. LinkedIn. Referenced from https://www.linkedin.com/pulse/20141204231202-292713093-microsoft-access-vs-microsoft-sql-server Kelley, KB. (2018). Filtering SQL Server Columns Using Column Level Permissions. Referenced from https://www.mssqltips.com/sqlservertip/2124/filtering-sql-server-columns-using-column-level-permissions/ Mack, J. (2014). Five Advantages & Disadvantages of MySQL. Datarealm. Referenced from https://www.datarealm.com/blog/five-advantages-disadvantages-of-mysql/ Microsoft. (2018b). Access. Microsoft Corporation. Referenced from https://products.office.com/en-us/access Microsoft. (2018c). SQL Server 2017 Standard Edition. Microsoft Corporation. Referenced from https://www.microsoft.com/en-us/p/sql-server-2017-standard-edition/dg7gmgf0dwp2 Oracle. (2018). Introduction to the Oracle Database. Oracle Corporation. Referenced from https://docs.oracle.com/cd/B19306_01/server.102/b14220/intro.htm MySQL. (2018). MySQL 8.0 Reference Manual. Oracle Corporation. Referenced from https://dev.mysql.com/doc/refman/8.0/en/preface.html Bergandy, J. (2018). Guidelines: Data Model. University of Massachusetts Dartmouth. Referenced from http://www.cis.umassd.edu/~jbergandy/process/modguide/md_datmd.htm Kendle, N. (2005). The Enterprise Data Model. The Data Administration Newsletter, LLC. Referenced from http://tdan.com/the-enterprise-data-model/5205 Silva, N. (2017). Basics of Database Modeling with Creately. Cinergix Pty. Ltd. Referenced from https://creately.com/blog/diagrams/database-modeling-basics/ Blaha, M. (2017). Enterprise Data Modeling. DATAVERSITY Education, LLC. Referenced from www.dataversity.net/enterprise-data-modeling/ Hernandez, M. (2013). Database Design for Mere Mortals, 3rd Edition. Addison-Wesley Professional. Boston, MA. Rouse, M. (2018). HIPAA (Health Insurance Portability and Accountability Act). TechTarget. Referenced from https://searchhealthit.techtarget.com/definition/HIPAA TechTarget. (2018). HITECH FAQ: What is the impact of the HITECH Act on IT operations?. TechTarget. Referenced from https://searchcompliance.techtarget.com/feature/HITECH-FAQ-What-is-the-impact-of-the-HITECH-Act-on-IT-operations Hus, G. (2016). Why Healthcare Providers Need a HIPAA-Compliant Database. Data Center Journal. Referenced from http://www.datacenterjournal.com/healthcare-providers-need-hipaa-compliant-database/ Durbin, S. (2016). Insiders are today’s biggest security threat. Vox Media, Inc. Referenced from https://www.recode.net/2016/5/24/11756584/cyber-attack-data-breach-insider-threat-steve-durbin Lynch, M. (1994). Ethical Issues in Electronic Information Systems. University of Texas at Austin. Referenced from https://www.colorado.edu/geography/gcraft/notes/ethics/ethics.html Presson, M. (2012). Building a database security program. LinkedIn Corporation. Referenced from https://www.slideshare.net/matt_presson/building-a-database-security-program-14348280 [Show More]

Last updated: 1 year ago

Preview 1 out of 31 pages