Final Analysis

Running head: MEDICAL FACILITY ANALYSIS 1

Table of Contents

Project Outline………………………………………………………………………...3

System Requirements …………………………………………………………………3

Final Analysis and Recommendations………………………………………………….15

References……………………………………………………………………………….17

Project Outline

Health care delivery systems are complex sociotechnical systems, characterized by dynamic interchanges with their environments (e.g., markets, payers, regulators, and consumers) and interactions among internal system components. These components include people, physical settings, technologies, care processes, and organization (e.g., rules, structure, information systems, communication, rewards, work flow, culture). ("Agency for Healthcare Research and Quality,", 2012) A local medical facility has requested an analysis to determine what will be required to update the current system and include video consults for the patients. This company has locations in 7 states of the southeastern part of the US. The process will be implemented at 21 locations. Over the next few weeks I will research the details which will include software, hardware, cost for equipment upgrades, and other extra cost that may be involved according to system requirements listed below. Network configuration will be discussed in the functions of the system. The need for the time frame for the project will also be considered. The main concern is to deliver a quality system. The final product will include a system where patients will be able to have face to face consultations with the doctor or PA through video capability.

System Requirements

The Functions of the System

The functions of this system will be to perform the basic functions of any medical offices. The system will be able to book appointments, retain patient records, update system to reflect appointments, billing, transfer information from one location to another location across the country and should be able to handle the load for all the facilities across the country. The main addition to the system will be to allow video transmission for consultations between doctor and patient.

This system will use a client-server, using a 100 Mbps Network Interface Card able to support full-duplex operation. All workstations absolutely need Full Control NTFS permissions and Full Control share permissions to the AMS data folder. Administrators should only user routers that have WPA2 encryption capabilities. WPA2 has the necessary security to ensure PHI will not be compromised (i.e. 256-bit AES encryption, SHA-1 hashing, password/key authentication). We will be using Windows 7 32-bit Client Engine Server. Telemedicine software is needed for this project also, the technical infrastructure consists of access to broadband internet, imaging technology or peripherals since these devices are the backbone of telehealth, access to technical support staff for any questions and staff training to teach staff how to use telehealth technology.

Architecture Selection

Service-Oriented Architecture is well-defined and self-contained, independent and is a client-server design. It provides, reusability, interoperability, composability is a distributed deployment. This is an example of SOA (" Distributed Architecture", 2017)

N-Tier / 3-Tier Architectural

Client-Server

Resources and Timeline

Resources required

Software requirement for implementation of client-server architecture include .Net Framework, windows PowerShell, internet explorer software, and windows 2012 R2 server software. Other software required are windows seven, SQL server, SharePoint server, and print server (Stanek, 2013) The Virtumedix software will be incorporated after the all major software is installed since it depends on the other software to perform the critical functions it was designed to perform.

Before implementing client-server architecture, it is very important to consider hardware requirements. The table below lists hardware requirement for deployment of client-server architecture

Table 1: Hardware requirement

Table 2: Software requirements

To deploy client server architecture, the project manager needs to organize his deployment team and assign a specific role to every team member. Table three below lists deployment team for client-server architecture with their respective responsibilities.

Table 3: Personnel requirements

Other requirements and their roles include

Cost

To go by the budget for this health care facility, I would recommend standard server and data center edition. This is featured by two virtual OSE. The licensing model is processor+. The server pricing for this edition goes for $890. Data center edition goes for $1000. Hardware requirement as listed above will account up to $1000 while software requirement will go up to $500. High cost will be experienced in the personnel needed for the implementation will likely increase to $2000. The $900 a year for the telehealth software will also be allotted in the cost. This will keep us well within the $125,000 for the budget listed in the contract.

Project Timeline

Project timeline communicates the important milestones for a certain project. For this project, the important milestones are installation of client computers with windows seven, server 2012 R2 installation and installation of all health care application services. I believe with this time schedule we are sure to meet the requested two-week time frame stated as the major agreement.

Major project deliverable

The primary goals for this project is to deliver a system that captures organization goals. Deploying client/server architecture can be an overwhelming task. The primary deliverable for this project is to deliver a quality client-server system. The client system must support some services are billing transfer of information from one location to another, allow video transmission, and be able to book appointments. Additionally, all the workstations must be connected to the central computer.

Duration to complete each task

The table shows project plan for full implementation of client-server architecture

Chart to display timelines

The following diagram is Gantt chart for the health project

Security

IT Security risks/threats

Distributed systems are more vulnerable than before to external risks and threats which include phishing attacks, threats, and viruses. The table below shows some of the common security threats and security risks that may be faced by a distributed system.

Common security risks and threats

Risk identification ought to be an ongoing process within an organization. For this reason, organizations should know the order in which security risks are addressed. They should also prepare an action plan. The following table shows the order in which security risks identified in table one is addressed. High risks are on top of the lists while the low risks are below the table:

An action plan outlines organizational strategies to prevent or minimize security risks. Some organization refers to it as a roadmap for risk reduction. The following is a risk plan.

We will assure all The HIPAA Security Rules meet national standards that will protect individuals’ electronic personal health information created, received and used by a covered entity. The Security Rule requires proper administrative, physical and technical safeguards to guarantee the confidentiality, integrity, and security of electronic protected health information. ("The Security Rule", 2017)

References

Agency for Healthcare Research and Quality, (2012). Ahrq.Gov, System Design: AHRQ Resources. Retrieved from System Design: AHRQ Resources. Content last reviewed January 2015. Agency for Healthcare Research and Quality, Rockville, MD.

Architectural Patterns and Styles. (2016). msdn.microsoft.com. Retrieved 23 February 2018, from https://https://msdn.microsoft.com/en-us/library/ee658117.aspx#ClientServerStyle Architectural Patterns and Styles

client/server (client/server model, client/server architecture). (2008). techtarget.com. Retrieved 12 February 2018, from http://searchnetworking.techtarget.com/definition/client-server

Distributed Architecture. (2017). tutorialspoint.com. Retrieved 15 February 2018, from http://www.tutorialspoint.com/software_architecture_design/distributed_architecture.htm

Hardware Specifications - American Medical Software. (2018). American Medical Software. Retrieved 20 February 2018, from http://americanmedical.com/hardware-specifications

McDunnigan, M. Advantages & Disadvantages of Distributed Systems. techwalla. Retrieved 3 February 2018, from https://www.techwalla.com/articles/advantages-disadvantages-of-distributed-systems

Minasi, M. (2014). Mastering Windows Server 2012 R2. Indianapolis: Sybex.

Stanek, W. R. (2013). Microsoft Windows server 2012 inside out. Redmond, Wash: Microsoft Press.

What are the technical infrastructure requirements of telehealth. (2014). healthit.gov. Retrieved 22 February 2018, from http://www.healthit.gov/providers-professionals/faqs/what-are-technical-infrastructure-requirements-telehealth