Advertisements
jump to navigation

Server Migration July 19, 2013

Posted by Russ Arnett in Projects and Risks.
add a comment

What is required to move 90+ servers from a “old” server room to a newly constructed one? Primary points:
1. Hospital envrionment
2. Patient Safety is absolute
3. Downtime must be kept at a minimum
4. Will consist of End Of Life Servers
5. Applications might require upgrades – new releases or simply to be replaced.
6. Integration engines for transactions may have an impact
7. Technical and Business Application Owners must be identified.

This is a 10 Billion dollar hospital group – with diverse locations and configurations, so you can see
that the need to be very specific and to require documentation and verifiable proof of what is required
is of ut most importance.

Advertisements

Real Time Location System – Continues March 18, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application.
add a comment

image

Wow! It has now become a very different type of process and continuing implementation then what was expected.

The executive sponsor has always wanted and expected to have the future requirements of the hospital to be based on the RTLS infrastructure that has now been installed and verified.

One issue is that he and his group really did not make his thinking available to the other groups that he will really need support for future implementation.

The future use of the RTLS structure will have a major impact on patient safety, staff productivity, cost and profit.

Patient Safety
Tracking where the patient is at all times will work for assuring a smoother flow and use of critical services – X ray and other services that are in high demand can be scheduled to assure maximum use and less down time.  If a patient were to fall or need immediate assistance a call could be generated for the nurses.

RTLS = Real Time Location system March 13, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application, Universal Risks.
Tags: , , ,
add a comment

So we are now in the final process of training,  validation, documentation and clean up.

The project is about a month ahead of schedule so this will help us to do additional and more importantly detailed training for all levels of staff both end-users and technical support.

In April we will discuss what will be next there is a joint development contract with TeleTracking that will incorporate the installed RTLS infrastructure.

This should ultimately be the decision of the Executive and Business Sponsors but information systems will have a lot to say how much and how it influences the decision will be interesting.

I feel that care must be taken to assure that the best for the future of the enterprise is a part of the decision! ☆

Thanks for the comments March 3, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application, Unsusal Risks.
add a comment

I am currently working on the contents from all of you! We have been waiting for the vendor to respond about the “new” technology LDAP they are, I guess researching if it realky works – hmm I guess 20 years of use a world wide use just does not meet muster for them!
RTLS does work really great and has been readily available and accepted by all of the clinical staff.  From 500 to 700 hits a day during the initial pilot we are now at 700+ hits against the database every hour and uptime is 100%.  Full roll out by end of June is expected.   We will start planning and reviews of patient tracking in mid March if the vendor will cooperate.

RTLS Implementation – Issues February 27, 2013

Posted by Russ Arnett in Basic Risks, Projects and Risks, RTLS - Hospital Application.
Tags: , ,
add a comment

As I write this I will be as always asking for your help and advice!
This RTLS Hospital system was implemented with the idea that all employees would have access – this capabilty is easily provided because access is provided via the employee portal.  But it is important to know that this vendor does not have LDAP capabilty – and questionable capability to provide.
They do provide the service to load the initial group of users (6, 000) but when asked for the script that would allow the hospital to use this script for continuing user maintenance.  Why? Because by adding – modification of users could in some way cause a major data
base failure.

RTLS Hospital Implementation February 15, 2013

Posted by Russ Arnett in Basic Risks, Projects and Risks, RTLS - Hospital Application, Universal Risks.
Tags: , , ,
add a comment

Well we have provided the complete infrastructure to support the specific RTLS equipment for full coverage of the clinical areas.  We have two slelected Pilot areas that have been completed and have proved that the system does work as needed and expected.  The critical department is the Emergency Department. They need to know exactly where critical equipment is located. The RTLS system provides the location instantly and its specific location.

Along with the Pilot areas we also had to
be sure that the service (help desk) was fully in tune and trained on what this system did and it’s basic functions. We don’t expect many if any calls from end-users because the system is very intuitive.
We will be asking the Pilot areas to approve their implementation formally early next week.

We are committed to finishing the public training this weekend to allow the weekend clinical workers access and knowledge.

Overall the project is under budget and on schedule.

Training and technical turnover February 12, 2013

Posted by Russ Arnett in RTLS - Hospital Application, Universal Risks.
Tags: , ,
add a comment

image

Well it will be at leasr 11° for the first training sesson that starts at 4 AM tomorrow – we are covering all 3 shifts for the clinical staff.
The announcement was on the employee portal and that is also where they wll gain access

Review of RTLS Implementation Goals February 3, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application.
Tags: , , ,
add a comment

Due to unparalleled accuracy, TeleTracking provided and supported RTLS can reliably  deliver a hard ROI in less than a year in hospital environments:

  • PAR Level Tracking: Set the system to automatically alert staff if the last pump is removed from a supply room, or better yet, when the next-to-last pump is removed so that your staff will never have to search for equipment. PAR level tracking requires 100% room level accuracy.
  • Rental Management: Have the confidence to reduce excessive spares by knowing the minimum number of spares during the past month.
  • Utilization Rates: Generate alerts whenever used equipment is placed into a soiled utility room, and become aware of equipment shortages before they become critical.
  • Egress/Shrinkage Prevention: Generate an alert if expensive equipment approaches a building exit, or if it comes too close to the incinerator.
  • Reducing Equipment Search Times: Never worry about missing a piece of equipment during an equipment or software recalls, and make it easy to find all equipment before the preventative maintenance interval has expired. Gone are the days of exhaustively searching every room for that one missing pump!
  • Advanced Workflow Optimization: TeleTracking RTLS solution is one that integrates to its own patented XT System that supports workflow analysis or process optimization, such as patient flow, capacity management, bed management, infection and more.

RTLS -production risks January 25, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application.
Tags: ,
add a comment

We know from the excitement of the clinical staff that the ability to quickly find a critical device is a major patient safety issue. The risks will identified as critical if the infrastructure has a failure.
We are developing some mitigation processes that I will share in future posts also sample documentation will be available for those who ask.
The failed devices will need to be isolated and reviewed locally as quickly as possible and if possible resolved by the local technical team. A major issue to be addressed is spares – should there be any kept locally or not? Configuration of these devices is complicated.
By the way this hospital in northern Arizona needs 2 PMP poject managers employees not consultant’s.
Contact me if interested

RTLS Pilot documentation January 25, 2013

Posted by Russ Arnett in Projects and Risks, RTLS - Hospital Application.
Tags: ,
add a comment

The push is on to have viable documentation that will be used to cover the full and final roll out. RTLS Vendor has a method to monitor the information provided by the infrastructure – we will want to have the hospital technical team to also have this capability to be the first and primary group to validate any infrastructure problems and insure that internal issues and faults are corrected as soon as possible.

%d bloggers like this: