Assignment 2: The Presentation
Running head: ABC PHARMACEUTICALS 1
ABC PHARMACEUTICALS 2
To: Charles Thompson, Cyber Security Manager
From: Janella Lawton, Cyber Analyst
Date: August 1, 2018
Subject: Combating Shadow IT Proposal
Introduction
ABC Pharmaceuticals is a local pharmacy that serves the residential area around it. The company has an information system that has been identified as being inadequate in realizing the needs of the organization. This has led to the rise of shadow IT projects to help bridge the gap posed by the system. However, the surest way to improve the functionality of the organization as a whole is to have a robust information system that can improve the functionality of the pharmacy.
Stylistic Choices of Information Systems
HelpSystems is an IT company that provides management software and services to organizations to help them solve IT issues. Our organization can benefit from their Robot, Halcyon, and InterMapper services to monitor our IT infrastructure which will provide us with the insight we need to secure our network.
Proposed Information System
The new system will have the functionality to facilitate the seamless sharing of data and information in the organization. This means that it has the functionality of communicating within the organization so that the information available in one department is also available in another department in an easy way. This will reduce the cases of having un-updated data in other departments.
Main Functions of the System
The system will also be able to diagnose and recommend medication based on the available information about the medication. There is new information every day in the medical field, and there is the need for a system that can recommend patient prescriptions based on the patient history as well as the developments in the medical field.
This means that the system should be able to hold data such as patient and client information. Client information is vital to be able to better diagnose and recommend medication. More data that will be held include the inventory information of the drugs in the pharmacy; employee information will also be collected. There will be data gathered about previous prescriptions given to the clients that will also help decision making in the future. Finance and billing information including insurance information will also be held.
Data Quality
Data and information integrity will be ensured in three main ways. First, the system will be password protected where each employee will get a user account. Encryption will also be used to protect any data that needs to be shared. The system will keep user logs of the activities of each user to track system use. There will also be access levels where each user will be allowed to view data and information based on their level of clearance in the system. Finally, data integrity will be ensured by reducing redundancy and ensuring the data is always up to date.
Improved System Functions
The old system was not able to seamlessly communicate and update information all through the system. This is so since it was desktop based and thus, the data and information needs to be updated on each desktop which makes it cumbersome. The system was also not able to support decision making in the pharmacy since it was not able to capture and store patient information.
Feasibility
Pharmacy support systems have been implemented as part of Electronic Health Records systems in many hospitals in the United States. The technology required to build these systems is readily available making it easy to acquire at a relatively reasonable price. The organization is also in need of newer technology that is more seamless and helpful in decision making. Also, the staffs have basic knowledge of using technology, and it is possible to train them to get better performance from both the staff and the system. This shows that the system is indeed a feasible venture since the technology is available at an affordable price and the staffs either have the knowledge or can acquire it easily from training.
References
Bassil, Y. (2012). A simulation model for the waterfall software development life cycle. arXiv preprint arXiv:1205.6904.