Hey Webmasters! New Photo Album Service Launched - Check it out!
|
|
|
Integrated Action Learning Project Plan
Development of a Proposal for the Implementation of a Medical Technology Wireless Data Network for St. Mary Hospital
Ralph W. Beckon
TS4990 Integrated Action Learning Project
Instructor, Dr. Sharon L. Bender
July 31, 2005
My project is a proposal for the installation of a Medical Technology Wireless Data Network to be used by Four Medical Technology Service (MTS) personnel at St. Mary Hospital . The proposal would permit remote and wireless access to vital service documentation, equipment history, communications and service alerts. The system will also allow data updates and implement the use a bar code readers to increase workflow processes, efficiency and improve data accuracy. The basic system will involve the use of our current hospital backbone providing personnel wireless access and the full functionality of their desktops.
The Medical Technology Wireless Data Network Proposal for St Mary Hospital will demonstrate how remote and wireless access to vital service communication, documentation, equipment history and service alerts will benefit our organization. The primary stakeholder will be Keith Miller the lead technologist within the MTS workgroup. Other stakeholders will include Linda, Norm, and me.
In performing a feasibility check I examined the following areas:
Objectives
In producing my project my major objectives are to:
1. Produce a wireless network proposal that will benefit MTS.
2. Produce documentation that may be duplicated at other Trinity Health Sites.
2. Apply the skills that I have learned about during my education at Capella University .
In producing my project my learning objectives are to:
1. Learn about new wireless technologies and standards; something I have avoided so far.
2. Refine my current skills in the development of a project plan and project Management.
3. Learn new research and whole project pricing skills.
Concept Map
The following Concept map is designed to show a very simple Concept for the proposal for a Wireless Data Network project for St Mary's Mercy Hospital .
In producing my IAL Project I will apply the following project schedule:
Tasks |
Duration |
Research Phase |
8/8/05 – 8/14/05 |
Task 1: Research Basic Wireless networking technology Theories. Task 2: Research Security issues and HIPPA Policies. Task 3: Research existing infrastructure and available wireless technologies. |
|
Resources: Literature Bender, S. L. (2003). Producing the Capstone Project. This course book will be used to guide the project. Brelsford, H. (2001). MCSE Windows 2000 Designing. This book will give me specific network design guidance. Savetz, K (2004). How To Install A Wireless Network. Smart Computing. October 2004 • Vol.15 Issue 10 PMBOK (2000). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)—2000 Edition. The PMBOK guide will help me organize my project phases. Internet Cisco (2005). Home Page Probably the best source for up to the minuet information on networking technology, Cisco home page will be a starting point for most of my research. Cisco (2002). Wireless LAN Security White Paper http://www.cisco.com/en/US/products/hw/wireless/ps430/products_white_paper09186a00800b469f.shtml While somewhat dated, this white paper is required reading offering a comprehensive Review of 802.11 Wireless LAN Security ID Automation.com http://www.idautomation.com/scanners/Opticon_LG2.html Offers a full range of Bar Code devices and accessories. Microsoft TechNet http://support.microsoft.com/default.aspx?scid=kb;en-us;314897&sd=tech Microsoft Technical support and Wireless configuration Guide.
People Keith Miller is an expert on wireless telemetry systems. He knows the specialized blocked medical frequencies and can offer advice on how to avoid interference with medical standards and devices.
|
|
Analysis Phase |
8/15/05 – 8/21/05 |
Task 1: Analyze Risk and Security and issues Task 2: Analyze Patient HIPAA Policies. Task 3: Analyze wireless compatibility issues. |
|
Resources: Literature (2005). MTS Policy and procedure guidelines. This is the Policy and procedure manual that is the basis of all Medical Technology services at St Mary Hospital. The manual is produce by Trinity Health corporate office and is followed in over 40 major hospital. (2004). St Mary Hospital policy and procedure manual. This manual covers internal St Mary Hospital policies and procedure and includes a comprehensive communications policy that will be used in part to define the new systems communication plan. Internet AAMI. Association for the Advancement of Medical Instrumentation. http://www.aami.org/publications/BIT/guidelines.html AAMI is the standards organization that defines specific medical device standards. These guidelines will help to reduce the risk of interference between our new mobile wireless system and patient medical devices. Cisco (2002). Wireless LAN Security White Paper http://www.cisco.com/en/US/products/hw/wireless/ps430/products_white_paper09186a00800b469f.shtml Again this Cisco white paper is required reading offering a comprehensive Review of 802.11 Wireless LAN Security FDA. U.S. Food and Drug Administration (2002) http://www.fda.gov/cdrh/EMC/wmt-about.html In partnership with the FCC the FDA monitors specific medical devices for safety. This site give resources and defines the specific frequencies that cannot be used by our wireless network. The Wireless Medical Telemetry Service (WMTS) report sets aside the frequencies of: 608 to 614 MHz, 1395 to 1400 MHz, and 1429 to 1432 MHz for primary or co-primary use by eligible wireless medical telemetry device and equipment. HIPAA. Guidelines for Academic Medical Centers on Security and Privacy http://www.aamc.org/members/gir/gasp/ The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a government mandate document that provides both protection and security of patient information. This website offers a comprehensive source for HIPAA guidelines that must be enforced when using a wireless network that has any connection to personal patient information. People Tom Hargin, IT specialist. Tom will give guidance on the current wireless system, security and accessibility.
|
|
Preproduction Phase |
8/22/05 – 8/28/05 |
Task 1: Obtain Hardware Cost estimates. Task 2: Produce Manpower time estimates. Task 3: Produce Concept map and basic Network Diagram. |
|
Resources: Literature PMBOK (2000). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)—2000 Edition. The PMBOK guide will help me Develop manpower estimations. Bender, S. L. (2003). Producing the Capstone Project. This course book will be used to guide the project. Internet ID Automation.com http://www.idautomation.com/scanners/Opticon_LG2.html Bar Code Devices will be reviewed from this site. Price Watch.com This is a source that provides links for any almost any specific product related to this project. The advantage to this website is it allows you to comparison shop and easily find the products you need. Software (2002) Microsoft Visio 2002 will be used to draw the concept map. This is a resource because it will be required to modify documents to fit specific Trinity Wide sites.
|
|
Documentation Phase |
8/29/05 – 9/4/05 |
Task 1: Amend existing HIPPA Policy to reflect wireless Technologies. Task 2: Produce staff user training and guidelines Documentation. Task 3: Produce rough draft |
|
Resources: Literature (2005). MTS Policy and procedure guidelines. (2004). St Mary Hospital policy and procedure manual. Both of these manuals will be required to follow proper format and ensure policy compatibility. Hacker. D. (2003) A Writers Reference. Fifth edition. Producing documentation requires the used of reference material and Diana book is one of the best I have used. Internet Capstone Learning Center . (2005). http://sharonbender.com/capstone.html I will use this site to compare documentation.
|
|
Proposal Signoff Phase |
9/5/05 – 9/11/05 |
Task 1: Seek feedback from the Stakeholder. Task 2: Obtain Proposal signoff from Keith Miller. Task 3: Review / Lessons learned. |
|
Resources: Literature NNSA. (2001). Lessons learned Assessment Checklist. http://www.eh.doe.gov/ll/proceedings/proceed1001/nvassess1001.pdf This document is extensive but will serve as an example and be used as a basic guideline to assess my projects success and lessons learned. People Keith Miller is the Stakeholder and will be asked to advise and sign off the project After feedback has been received. Linda Reinhart will be asked to review the project and provide feedback. Norm Haro will be asked to review the project and provide feedback.
|
|
In producing my project I performed the following risk assessment:
Risk Factor Checklist |
||||
Risk Considerations
|
Low Risk |
Medium Risk |
High Risk |
|
Equipment Reliability |
|
|
x |
|
Production Quality |
|
|
x |
|
Obstructions to Delivery |
x |
|
|
|
Data Reliability |
|
x |
|
|
|
|
|
|
|
High Risk Analysis |
||||
Risk Considerations |
Risk Significance and Potential Solution |
|||
|
|
|||
Equipment Reliability
|
Problem: Interference with Patient Medical devices.
Equipment reliability and interference has always been an issue in an industrial setting. Reliability is of especially high risk because of the mission critical effects that failures can bring. Solution: As a solution backups and redundancies can be set in place. One Backup could be that the mobile device can be used as a backup to be synchronized in case of network failures. Another solution is that manual data input may be used if a barcode device fails.
|
|||
Production Quality
|
Problem: Security or sensitive patient data hacking.
The risk of production quality is a factor because the IT staff has been overworked and may be lacking in some security skill sets. Solution: To improve the production quality and security the key stakeholder can be brought in and involved at an early stage. Other measures might include a review at each stage by the technical manager at the corporate offices. Allocations of overtime or bringing in third party venders are options that may improve the overall quality of the final implementation of the project. |
|||
Contingency Plan
After completing a risk analysis it has been determined that the high-level risks to the successful completion of my project are:
1. Equipment Reliability
2. Production Quality
Efforts to offset these risks are in place. However, if for some reason my project does not appear to be developing successfully regardless of the efforts made, I would present reasons why I am unable to proceed with the project as planned. Appropriate redirection of the plan would take place upon instructor and/or stakeholder approval and the new direction would be discussed in the final project report. Redirection might be to permit the [analysis, testing, presentation, or other] phase(s) of my project to constitute my project in its entirety. The outstanding phase(s) [e.g., implementation] of my project would in such case be completed outside the scope of the capstone project. Upon approval, such redirection would represent my project in its entirety.
I performed the following literature review concerning the value in producing my project:
1. Balgrosky, J. (2005). Rx for Administrative Overhead — deploying wireless
technology, collaboration tools, and Web services Retrieved July 2005 from:
http://www.microsoft.com/business/executivecircle/content/page.aspx?cID=788&subcatID=4
This article describes how the implementation of wireless technology in the Scripps Health healthcare network lightened the load on workers while promoting and enhancing compliance with the Health Insurance Portability and Accountability Act (HIPAA) regulations. The article reinforces the value of my project and how it might serve as an example to be used in other departments and Trinity health hospitals.
Balgrosky discusses the value of a wireless network by protecting privacy, Electronic Data Interchange (EDI) and securing medical records. Scripps wireless network also had the benefit of providing real-time flow of data that is important in all areas of medical technology. The article continued to discuss the benefits such as reduction in the amount of paperwork and reduction of the physical demands of back-and forth trips to retrieve patient charts and doctor's orders.
The key value of a wireless system is that workers “spend less time finding the data they need and more time concentrating on and caring for the patients who need them.” This time benefit also includes the improvement of auxiliary services like equipment management and internal supply chains. These benefits can be directly experienced by MTS staff at St. Mary Mercy and show the value of my project proposal.
2. Greegard, S. (2004). Cutting the Wires to Enterprise Systems.
Retrieved July 2005 from the Business Finance Magazine archives.
http://www.businessfinancemag.com/magazine/archives/article.html?articleID=14209&Print=Y
This article explored how major companies like Chase-Pitkin, Pitney Bowes and others turned to the benefits of wireless technology to improve their bottom lines. Greegard focuses on the business and finance perspective to explain how wireless technology works for an organization at it deepest roots. The financial benefits of a wireless system are far reaching affected most of an enterprise by increasing productivity and employee flexibility, extending the reach of enterprise systems, and bringing a better value to customers.
The article explains how a wireless network gives companies a competitive advantage by providing faster and cheaper data access and processing. The article builds on this and talks about companies that supply field technicians with wireless technologies that enable them to “place orders, view schedules and databases, and check their e-mail without using a desktop computer.” Other benefits include inventory control and equipment tracking. These benefits show the value of my proposal as they relate directly to the goals established by MTS and St Mary Mercy Hospital.
The article supports the value of my proposal and its affect of improved customer satisfaction and real-time service. By reducing paperwork and manual data entry we can streamline our processes and improve our technicians' visibility; all these add up to increased satisfaction. Customer satisfaction is a core value that MTS, Trinity health and St Mary Mercy share.
3. Williamson, J. (2005). Hospitals scan for new ways to broaden instrument management.
Horizons, retrieved July 2005 from the Healthcare Purchasing News
http://www.findarticles.com/p/articles/mi_m0BPC/is_2_29/ai_n10302415
This article is about Gundersen Lutheran Health System and how it implemented an instrument management solution. This system included a discussion about Bard Code technologies and the software infrastructure that “streamlined instrument processing and assembly”, improved the accuracy of trays or equipment delivered and allowed real time tracking. This article arts out showing Gundersen's success with instrumentation and make further connection to equipment and supplies found throughout a hospital setting.
Going beyond the nuts and bolts of a wireless system, Williamson talks about the far reaching future benefits of such technology. One example might be if someone is looking for a piece of equipment, a technician who has it in front of him can scan the tag which brings up a digital image that helps the remote staff find the unit. A system might also include radio transmitters attached to a piece of equipment allowing for GPS location of the missing unit. Wireless technology could even allow remote access for repairs or updates.
It seems that the possible software applications are limitless in a barcode system; from a single scan you can pull up equipment specific PM sheets, equipment history and asset management details. Williamson also describes the possibility that these programs and processes can become part of an overall strategic initiative by integrating system, track processes, productivity, and in the end making organizations more efficient.
The following appendixes would be added to the Integrated Action Learning Project Final Report to provide a sample of my work and to evidence satisfactory project completion:
Appendix A: Proposal Documentation.
Appendix B: Letter of Project Completion from the Stakeholder, Keith Miller.
bravenet.com