UMUC Student Health Service Clinic
Table of Contents
2.0 UMUC Student Health Service Clinic. 4
2.6 The Hardware or rather Server Specs. 7
2.7.1 Development and Testing Phase. 9
2.7.2 Implementation Phase. 10
1.0 ABSTRACT
This report includes identifying and documenting a full information system for a small company, that will apply the basic steps of the SDLC (Systems Development Life Cycle) to design and implement the IT infrastructure for an electronic health care data system for an urgent care facility* for a (mythical) UMUC Student Health Service clinic by addressing what actions are taken and what decisions are made in each phase. The key technical issues and specific key elements and components of a computer system, include: CPU type, speed, Memory type, size, speed, etc., Desktop or mobile, In house or cloud based system, Networking, Operating system, Other required software, I/O devices (i.e., peripherals), Shared resources, Storage; backup; disaster planning, Physical and electronic Security, Privacy. During this report assessment the main objective included Identify and document a full information system for a small company (UMUC Student Health Service Clinic), Apply basic steps of the SDLC (Systems Development Life Cycle) to design and implement the IT infrastructure for an electronic health care data system for an urgent care facility, Detail each step in the SDLC, with an emphasis on the technology outcome and how it flows from the functional requirements, Outlining how one could test the system and gain user acceptance (Easy communication between patients and doctors.).
Key Words: Systems Development Life Cycle (SDLC), communication, services delivery system, hardware, networking, network, patients, doctors…
2.0 UMUC Student Health Service Clinic
2.1 Introduction
The need for an efficient and effective electronic health care data system for UMUC Student Health Service clinic would enhance the way in which service delivery for patients (Stair, 2009). For instance the appointment system would facilitate better ways of boosting appointments and reduce the waiting time of patients. Patients seek faster response to medical conditions they are suffering.
The Systems Development Life Cycle (SDLC) methodology is used to develop new system that would ensure efficient service delivery for this clientele. In addition, patients need to have privacy convenience and higher levels of flexibility to meet the doctor or their physicians.
This report is about applying the basic steps of the SDLC (Systems Development Life Cycle) to design and implement the IT infrastructure for an electronic health care data system for an urgent care facility (i.e. UMUC Student Health Service clinic ).
The main objectives of this paper are to:
- Identify and document a full information system for a small company (UMUC Student Health Service Clinic)
- Apply basic steps of the SDLC (Systems Development Life Cycle) to design and implement the IT infrastructure for an electronic health care data system for an urgent care facility
- Detail each step in the SDLC, with an emphasis on the technology outcome and how it flows from the functional requirements.
- Outline how one could test the system and gain user acceptance (Easy communication between patients and doctors.).
2.2 Project Methodology
After examining all existing methodologies it has been decided to use the SDLC for the following reasons:
- All requirements of the system are well known and note likely to be changed or at least it will change gradually over time
- Easy to use in developing such systems
- The strength of its documentation
- To be more certain about final delivery time and cost
The process of this methodology includes the following significant steps: Planning; Systems Analysis; Systems Design; Development; Testing; Implementation; and (Support or Maintenance)
2.3 SDLC Methodology
SDLC methodology may be described as solution delivery model which uses various methodologies for managing project all through the development life cycle (Alexander). The SDLC’s framework or model uses phases; deliverables, sign offs as well as gates to ensure that a project is completed successful and has a strong element of sustainability in its development and completion.
SDLC is used by various system engineering, information systems and software engineering professional to develop: the process of setting up, forming, and testing and setting out an information system within an organizational system (Alexander). Consequently during its use, the cycle within SDLC, has been found to be ideal in the application of software configuration, hard ware configurations. Similarly to any manufacturing process the SDLC seeks to produce a high quality system that are tailored to meet the clienteles need, which including cost estimates project deadlines and functionality.
On the other hand in order to bring a project to completion an engineer has to ensure that each step of the SDLC phases is trailed to completion. These phases include: Planning; Systems Analysis; Systems Design; Development; Testing; Implementation; and (Support or Maintenance (Stair, 2009). Initiation phase- in this stage the owner or sponsor aptly identifies a need or an opportunity for an intended purpose, planning phase- this phase entails establishing what the goal is and the preeminent way to accomplish it, system analysis involves soliciting for the exact problem of that is to solved, and flow diagrams are developed to ensure that there is a solution in regard to information systems (Stair, 2009). The system design phase entails designing a system that would solve the identified problems in the information system, the testing phase entails ensuring that there is proper operation of the whole system’s subsystems hence ensuring that they are all working together to achieve a common goal when used efficiently. Implementation phase involves the putting into operation every aspect of the new system and running it from its initial stage process to its completion or cycle stages. Support or maintenance- in this phase constant monitoring is applied at various sections and maintenance of the business solution.
2.3.1 Project Planning
During this stage the project seeks to establish the high-level view of the proposed project and determine the project goals. Therefore, the importance of this stage is to determine what technologies best solve problem within the existing system (Schneidewind, 2012). In addition, an economic feasibility study will be undertaken to determine if the organization can afford the proposed system and if it will provide a return on the investment. Furthermore, operationally feasibility determines the human aspects of the project to determine how willing and able the staffs able to change with its implementation. Lastly, a schedule feasibility analysis is performed to determine if the proposed system schedule is practical.
The project planning project established that the project goals were design and implement the IT infrastructure for an electronic health care data system for an urgent care facility. Second, the proposed project was economically feasible and provides a high return on investment. Third, employee resistance to change will be countered by making sure that they are involved through every stage of its development (Alexander, 2005). In addition, training of the employee such is undertaken after the project is complete in order to familiarize them with the system. Use of various planning tools indicated that schedule is practical. Therefore, the entire project was feasible.
2.4 Requirements Analysis
This stage defines the project goals and defines the operations and functions of HIPAA compatible EMR software. It also undertakes the end-user information needs. It uses many tools to gather information through computer-aided systems engineering tools. Therefore, requirement analysis is used to gain a deep understanding of the UMUC Student Health Service Clinic problems and how best to solve them. In this stage we will review various documents, interview employees and observe the daily business patterns in order to gain a better understanding of the business. Consequently, data, flow charts and other associated tools will be used during this stage.
The following were established as the system requirement UMUC Student Health Service Clinic
The System Requirements include:
HIPAA compatible EMR software*
Hardware that supports the EMR:
- CPU type, speed, etc.
- Memory type, size, speed, etc.
- Desktop or mobile
- In house or cloud based system
- Networking
- Operating system
- Other required software
- I/O devices (i.e., peripherals)
- Shared resources
- Storage; backup; disaster planning
- Physical and electronic Security
- Privacy
2.5 System Features:
In order to ensure that the EMR logic software system is fully operational, it is vital to employ hardware technology that would maximize the speed as well as performance of the EMR software (Alexander, 2005). The EMR offers three specific hardware services for clientele, hence its use:
The Turn key option– the EMR logic software is able to give a command to the hardware, the networking software which then configures and sets up hardware at the clinic site (Schneidewind, 2012). Any software engineer would be able to ensure that all the network software and the hardware is set up at the suggested point of performance.
The hostage server option– the EMR logic software is able to give a command to the hardware, the networking software hence making it ready for use (Alexander, 2005). The server as well as the hardware can be easily installed by an IT or software engineer, this will make certain that all hardware and network software are well configure and fully operational to meet a high level of performance
Order and ship option– EMR logic software can be shipped to the specific locality or area of the clinic where it would be ideal for software or IT personnel to install it hardware and software with precision.
2.6 The Hardware or rather Server Specs
The Hardware that supports the EMR has a minimum of eight (8 GB) RAM, a minimum of 500 GB free space minimal, and a minimum of 50 GB for creating an operation system partition.
2.6.1 Server Software:
The server that is recommended for EMR is 2008R2. The server will need all service pack and updates for its software compatibility, Microsoft SQL 2008, License for loading MS Word 2010,
2.6.2 Printer Specs
Network tailored printers highly recommended. Local PC and Terminal servers will be used to load print drivers for local printing
2.6.3 Scanner Specs
- The EMR Logic Software recommends Kyocera Scanners
- Scanner workstations must have 5gb RAM and USB 2.0 ports
- Scanner workstation must have 2008 Windows Operation System /Windows XP
- Assess the scanner to ensure it’s compatible to develop a PDF document or image.
2.6.4 Other Requirements
- Digital and analog fax line that is linked to a modem on server for clientele faxing
- Static IP addresses are ideal for computer internet installations
- Business class routers for the clinic would be ideal for use
- Site VPN are recommended for satellite office that deal with scanning large amounts of documents for organizational use.
- Physical and electronic Security would be needed to ensure that there is enough security for the internal as well as external stakeholders’, therefore metal detectors and scanner will be install at every entry point to the clinic and would be linked by a security server.
- Client must have a DSL, Cable Modem or rather a T1 line Internet Connection
- Cloud computing would be needed to store vast medical data
2.7 System Design
During this stage of the project is to describe the desired features and operations in fine detail. It includes the specific functions and the various sections that it should contain. There two main components of system design. First, is the logical system design document that shows the actual components of the proposed system to be used in order to achieve the desired functionality? Second, it the physical system design specifics of the proposed system that will use to implement the logic design. It is important to note that once the system design has been agreed by the client no changes can be later. This is to avoid scope creep and feature creep this could lead budget and schedule over runs
The EMR system design supports data exchanges between various platforms clinical setting, government and external laboratory. The main purpose of this approach is to accommodate various external sources of data in the clinic setting (Alexander, 2005). These multi data streams are interoperable via standards and technical links within the EMR systems. The entire network infrastructure is designed to provide secure encrypted data during transportation and storage through encryption and multiple firewalls. So that data can be easily audited and tracked (Stair, 2009). This design model allows the data to reside at the source to ensure efficient workflow, while at the same time the network infrastructure allows for data to be transported and integrated without any changes to the existing uses. Therefore, the user views can limit the privileges of the data requirements for only specific uses based on the needs of the user. This requirement within the network infrastructure covers the rights and responsibility of the users in order to reduce the cases of abuse of data and information.
The system is based on standards set for EMR and meets all requirements of the Health Insurance Portability and Accountability Act (HIPAA) that details patient privacy and regulation in the healthcare sector. In addition, the EMR system uses replaceable modules that could be replaced by another superior technology that performs the same task. The system represents a distributed and decentralized approach but can easily be changed into monolithic network. The systems design combines data from various known health related agencies but can also be extended to other heterogeneous sources. The system is robust. It offers the user access control and privacy features that enforce non-repudiation of data.
The server chosen, EMR 2008R2, offers more for less staff and addition organization of operation. It is recommended that when choosing the client computers, it has to complement the practice while interesting to use. The wireless Tablet PC’s is recommended. It is connected to the server using the wireless network. The network topography used is the local area network considering the small functional space required to undertake operations. The tablets offers one ability to roam one room to another while taking records of the patients electronically. This is quite popular as it offers functionality and is affordable as one only needs a tablet PC for every provider one saves hardware costs as opposed to a workstation. The most appropriate peripherals would be scanner and printer as well as a UPS. The software installed in the hardware will be protected from external threats using a Kaspersky Antivirus taking into consideration that the network would be easy to access from a patient’s mobile device while placing appointments or making enquires.
2.7.1 Development and Testing Phase
During this phase all the necessary equipment and software will be installed (Schneidewind, 2012). Software will be installed and tested. The entire network will be set-up in the entire organization to guarantee connectivity and communication between various devices. Testing the network will be tested to ensure that all the equipment and software are working correctly as planned. This will involve verification and validation process. Verification is done through various simulations testing process to guarantee everything is working properly. This will be with the help of the staff and users who would use the equipment and software and offer their opinion and recommendation. A weekly status meeting will be held at this stage so as to offer a communication process to inform the team of the status, test plans and action items from the past week.
2.7.2 Implementation Phase
This phase involves a series of steps. First of all a review of phase prerequisite is done to ensure that all of the prior phases is complete. This includes the testing, implementation plan, training plans for end users, system documentation is done and system has completed C&A in reference to DoIT guidelines. This is followed by monitoring of project performance that comprises:
- Getting details on changes to base line
- Alteration on management data,
- Progress of status details and level of completion.
- Quality assurance
- Resource utilization
Additionally, the project manager manages and overlooks the systematic quality. The project is measured by setting timelines and metrics for success of the project.
The PMP of the project is updated constantly so as to ensure that it matches the project performance accurately. This adds to the project manager’s duty of distributing the PMP and risk control data in regard to the updated Communication Management Plan.
Risk management follows and comprises of identification of risks, its analysis using qualitative risk management methods and response plan that tracks, monitors, identifies, executes response plans and assesses the risks control appropriately in addition to monitoring and control.
The implementation starts by choosing the standards, methods and tools for using, undertaking the implementation phase and a review is done for change management process to make sure the test phase has been recorded. The system is then deployed in production setting while maintaining the configuration details. Later, the project manager distributes the change implementation to end users and companies that are connected to the clinic.
The security of the system is similarly taken into consideration by undertaking a review of the security plan for vital security policies and process in the process of implementation phase. Conformation is done for the customers and staff to receive training on DoIT security policies and process. The security plan is executed and a standard operating process is created.
With confirmation of the documentation, a post-implementation review is undertaken as well as the project performance.
2.7.3 Maintenance Phase
During this phase, employees will ensure that all the resources perform at the optimal. Support staff will be on call to troubleshoot errors in the system (Schneidewind, 2012). Regular backups will be done to ensure that data can easily be recovered in case of system failure.
3.0 Conclusion
The primary purpose of this project is to assess the SDLC (The Systems Development Life Cycle) methodology that is used in developing a new system that would ensure efficient service delivery for this clientele. It is important to note as an engineer that apt knowledge of the SDLC (The Systems Development Life Cycle) is vital in improving the care of patients, business’ among many others timely delivery of a demand.
This report illustrated all phases in the life cycle of the produced application including gathering the requirements and analyzing them. Moreover, design and implementation phases have been covered. To make sure that the application has achieved all its objectives, testing and evaluating the system functionalities and usability has been carried out in the final stage.
Therefore, it’s imperative to note that: testing the system in the most vital part in the SDLC and gaining user acceptance or rather being user friendly ensures that the system could be developed to produce better system to help other sector apart from the health sectors (Stair, 2009). For instance they can be used in improving the curriculum for nursing, teacher, and engineers among others in higher institutes of learning, hence the society ends up having competent person who are able to solve problems through using of creative aspects of technology within their environment.
4.0 References
Alexander, I and Maiden, N. (2005). Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle. Hoboken. New Jersey: NJ. John Wiley & Son. Chap. 1 p.10 -20
Stair, R. & Reynolds, G. (2009). Principles of information systems. Stamford, CT: Cengage Learning.
Schneidewind F. N. (2012). Computer, Network, Software, and Hardware Engineering with Applications. Hoboken: New Jersey.NJ. John Wiley & Son. Chap. 7 p.233 -230
