AONE 2013 Patient Need Based Acuity

My husband ran a distribution center  for 13 years.  When we met had around 150+ employees and through automation, software, and workflow modification was able to reduce the employee count to less than 10% of that number.  His guiding principal was to break tasks down and manage the individuals according to the time it took an average person to accomplish the task.   He and his team could watch a process and identify skills sets and aptitudes that allowed them to manage the team to accomplish the goal in a timely way with a low error rate.

As I have researched acuity it seems to be a similar structure.  The DRG defines a grouping of tasks and the tasks have an associated average time of completion (geeks call this a weight) and the assignment is made based on how many “tasks” can be completed within a shift.  Then the patients are assigned to the caregivers based on the workload associated.  That’s when I started to ask questions….are we treating nurses like assembly line workers?   How does this affect how we assign them to a patient – does our technology really support the mindset?

I have watched this process at a number of hospitals, interviewed a number of managers and I do believe that it’s much more of an art than a science.    In the last few years I have also observed several production facilities - from a Milk Farm to a Coffee Roasterie to Electronics manufacture.  The thing that jumped out at me……the product or coffee bean or electronic doesn’t drive any additional demand or strain on an assembly workers day.  There are outliers where a piece of material is bad but for the most part it’s pick up the widget, put it in a box, etc.   The point is – the widget doesn’t ask for ice chips when you are trying to complete other assigned tasks....the widget dosen't code.   

I get it – there has to be a way to balance the workload of the caregiver and acuity (aka task management) seems to be the best method.  I am not trying to disregard the years of research and work done in creating the tasks associated with diagnosis, etc  but there is more here than just a task list.  We at Sphere3 believe there is a way to capture additional information to make assignment of patients easier and managing the workload more effective.  Stop by and check it out.

I am eager to see at AONE this week how many vendors try to tout their technology as a way to reduce staff….be careful with those statements…..technology should be an enabling tool the data should give the ability to manage the workload more effectively.  Patients aren't Widgets – Caregivers aren’t assembly line workers.   

If you would like to see how Aperum® can help your facility better manage workload of your caregivers stop by BOOTH 727 this week at AONE.

How to Define "Help"?

When you order BBQ in Kansas City – you don’t just order burnt ends – you can order chopped burnt end sandwiches which can be sauced or dry – you can order a platter which can be sauced or dry – you can order it as a combo. Then there are the side dish selections…cheesy corn, beans, slaw, pickles….

Question #4 “During this hospital stay, after you pressed the call button, how often did you get help as soon as you wanted it?”

The interesting thing about the next section of the question is its tie to “help”.   What defines help?  In most hospitals if you press the “call button” there is one “button” it’s big and it’s red. You can figure out it’s for “help” even when you are groggy or sick. The newest fad is to add more buttons – which is great for me would work. I am used to self selecting. I self-check at the airport, I order meals and movies on my Iphone, and think nothing of the lack of real “service” that is providing.

My mom (who is 62) would think the extra buttons were a novelty. She would laugh as she tried to find her glasses to read the small words on the extra buttons “water, pain, or toilet” then ask me if she pressed toilet does that mean she has to go or that she went. She would never press the pain button because she rarely admits when she is in pain.  She would always press the red button.  (Please no hate mail here, I am generalized a generation based on my experience with my parents)

My grandma would press no buttons….even with her glasses she probably couldn’t read those little words, and she would look at the crazy “paddle” and say why are there so many buttons. Then she would look at me and say “Bo, go get my nurse” I would either press her big red button or I would just walk out of the room to find the nurse.

The point is defining “help” is challenging in a healthcare environment especially in a patient self-directed self-selection process. Evaluating “help” is even more challenging. There are numerous options and building the paddle would be a challenge. Ironically, in an industry move to be more efficient and direct patients needs to a caregiver using a decentralized design method – we lost a great deal of the data modeling. There is no way to track the request specifics in an automated fashion in a decentralized design without additional manual steps (which frankly defeats the purpose). There is no way to get specifics but there are request patterns.

There are ways to collect this request data – get a good understanding – then design you call processes. Just to take it a step further – we can tell you how many of each type of request hit when, how many were answered in your desired time frame (or what your average time frame), and even how the caregiver interacted with the request. If there is a hospital interested in knowing how to create a real patient centric care model – call us – we are looking for partners in a study to make life better.

The current analysis structure (at least what we have found published) looks at qualitative information – how many focus groups does it take to get to water, pain, and toilet? What’s crazy is all the information you could want to design the paddle or better the process is locked inside the nurse call system….if the hospital has a reporting package because most nurse call systems are built like archaic life safety tools with proprietary databases.

What’s more – I am the patient – I want to know how quickly you responded to my need – I know the information is there and frankly I know how to get to it. Stop and think how valuable that could be though - if I am going to do a survey (qualitative) to evaluate my care would it be better if I knew on average you answered my call light within 30 seconds every time PRIOR to me filling out the survey. Sometimes it feels like longer – but when you KNOW what the time is aren’t you more patient….Do you think that would influence my decision on whether or not I had good care?

But what do I know…. I am just a mom who had a sick baby and instead of blasting a hospital for a bad experience – I dug down to figure out how to solve for a pain I felt during a hospital stay.  It really is that simple….by the way so is the data.

"The Immediacy Conundrum"

Question #4 “During this hospital stay, after you pressed the call button, how often did you get help as soon as you wanted it?” Answers: Never, Sometimes, Usually, Always, and I never pressed the call button.


“after you pressed the call button”

Patience is not in abundant supply at Gate’s BBQ. When you walk in the door they shout at you - “Hi May I help you?” you must know to yell back very quickly – there is no patience for Umm or questions – by either the counter staff or the patrons behind you. You must shout back – quickly with full confidence - “Yes, I want a burnt end sandwich, fries, and a Ice Tea.” The food arrives to the counter very quickly – you can watch the man through the cook window constantly chopping and slicing meat to serve – you know it will be good, hot, and fresh.

The Gates atmosphere creates an expectation for an immediate response to questions, there must be no hesitation. I have reviewed reams of data from nurse call systems and 4 years ago when we started – the average wait time before exit of the bed for a patient was about 1:13. Now we see a majority falling under the 30 second threshold. Are people getting more impatient? Maybe…

We live in a world where as soon as I want to be connected my expectation is to have connection. The problem with “after you pressed the call button” is many patients expectation is immediate. Geeky techy stuff – if you have a nurse call system older than 2 years and you are functioning in decentralized – there is a lag time. Depending on the specific system – it can be an “eternity” in terms of immediacy. This is not a reflection on caregivers, it may actually be a reflection on the implementation of technology. Yet, caregivers are under pressure. Just like Gates, the health system and government is creating an atmosphere around hospitals that require immediacy. By its ever- more acute care criteria for entry, there is an equal expectation for immediate response?

Let’s talk solutions to the immediacy conundrum. The Decentralized Nurse Call craze of a few years ago is beginning to subside as hospitals realize the limitations of moving the patient call to an individual who is mobile and has variable task responsibilities on the unit. Decentralizing or sending the “Normal” patient call to a wireless device does not solve for immediacy – it’s actually the most difficult methodology for nursing to utilize because there is no immediate feedback on volume of requests or the “queue”. Immediacy requires the “queue” to be low and the person answering the call to interact and disconnect quickly. Think Economics - Basic Supply and Demand Theory – if you have too many nurses and not enough calls then you are fine. However, what is generally the case at documentable specific periods of shifts, if you have too many calls and not enough staff then you are going to get low scores on question 4.

The trick is the patient has a need and since they are not in their home environment and have very little control of their surroundings – many “wants” become needs. Not to mention the variation in expectation. The patient requires an immediate interaction – not an immediate solution. This is a really important point – so don’t miss it – the patient needs an immediate interaction and a sense that their need has been identified and help is on the way. The second key to this is you must deliver on the promise. So, if you have pushed your button and someone has quickly told you “help is on the way” then help must really be on the way. The only way to manage that is to develop a methodology to alert the needed caregiver with a specific request – data rich. Then Mobilize AND Monitor their action towards delivery. What does this mean – the person interacting with the patients request should be air traffic control – they should be able to monitor the total quantity of requests and estimate a delivery time. If there is a change in delivery time – maybe the patient should even be notified…..

The Recipe Matters

I love a challenge, and recently I have taken to making cakes. I am not Duff or Carlos, but I am determined to conquer the cake. My weakness is I don’t like recipes – ok, so I don’t like being told what to do, and I feel a recipe is just Betty Crocker’s way of bossing me around. When cooking, her recipes are general suggestions, but unfortunately in baking, it’s an order.

The thing with a recipe in Betty’s book is someone experienced has documented it – it has been verified – and it has made it to the general public. A recipe is successful because the common language used in each step. We are taught in grade school the standard terms of measure – cup, teaspoon, tablespoon, etc. We are also taught time – minutes, seconds, or hours. We are taught by our moms how to “preheat”, and we are taught by the Food Network how to “fold” in an ingredient.

Documentation of anything requires standard terms and common language. In a recent revelation in speaking with others about my professional passion for clinical alarm data and the picture of patient needs hidden within it, I found that there is not a current standard terminology in the arena of clinical alarm design. Therefore, I am proposing one. Just to set the minds of my readers at ease – Patient Communications Platforms are in my blood. You could say my youth encoded a understanding of clinical alarms into my DNA. I went to my first “nurse call” training before I could drive a car, and had a doll house with RTLS. I am not a novice, however, I am not so proud to think that what I’m proposing can’t be improved upon. Actually, I’d be thrilled if this proposal sparked a debate. So,I challenge all of my readers (all 700 of you) to comment. Collaboration can only occur if we are not so prideful to think we are perfect – if we can agree that little companies have as good of ideas as big companies – if we can solidly stand by saying we must create things for the betterment of healthcare because it’s really about patients – not all about profits.

This is Sphere3’s proposal for common language for documentation of Clinical Alarms. Below is a cascade of action – reaction that can either be generated by a person or the configuration of the clinical alarm system.

Initiating Action:

This is the beginning of the call. It can be manual, such as a patient pressing a button or physiological, such as a telemetry alert. The initiating action can also be a system trigger such as an occlusion or a system creating an alert based on a malfunction or necessary service request. The easy way to remember an Initiating Action is “it’s gotta start somewhere”.

Example:

Patient Press a “Normal Call” button on their Nurse Call System

Patient’s heart beat indicates a “V-Tach”
Notification Action:

How do people know that a clinical alarm has occurred? A Notification Action is the ring, ding, buzz, text, etc. This is the way in which a caregiver knows that an initiating action has occurred – they way they know the patient is in need. There are generally multiple Notification Actions for every Initiating Action. Every Notification Action is an invitation for the Caregiver to interact with the patient or their device.
Example:

Initiating Action = Patient Presses the “Normal Call Button”

Notification Action 1 = The Dome Light is White

Notification Action 2 = The PCT’s Wireless Device buzzes

Notification Action 3 = The PCT receives a Text Message “Normal Call Room #” with the option to “dial back” to the patient room.

Acceptance OR Rejection Actions:
If the Notification Action is the caregivers invitation to interact with the patients need it forces an acceptance of that request or a rejection. Accepting the alert requires an interaction with the patient or their technology. A rejection is a “delay of response” while it could indicate that the call is being ignored, mostly it indicates that the capacity of the caregiver to interact with the workload is challenged.
Example:

Notification Action3: The PCT receives a Text Message “Normal Call Room #” with the option to “dial back” to the patient room.

Acceptance Action 1: The PCT presses “Accept” it “dials back” into the patient’s room, they communicate with the patient.

Rejection Action 1: The PCT is unable to answer the call due to being engaged with another patient.

Escalation Action:

A Patient Communication Platform (aka Nurse Call) has a feature called “always an answer” where it will bounce a call if it’s not handled within a set time frame. Anytime a call is rejected, it bounces either automatically based on timeframe or physically based on a button push. That being said anytime a call is “rejected” technology should be programmed to create an automatic escalation action. Similar to an Initiating Action the escalation action is the technologies methodology of moving the call to the next person or place in line.

Example:

Rejection Action 1: The PCT is unable to answer the call due to being engaged with another patient.

Escalation Action1: Since the call has been “ignored” the technologies internal timer has allowed for a wait time of 2 minutes after which the call is sent to the RN’s wireless device with a message “Normal Call Rm 320”.
Escalations drives additional Acceptance and Rejection Actions, based on time frame. Again, a Rejection Action will create an additional Escalation. The hospital has to decide when the patient request (physiological or physical) has gone on too long, and at what point a failure to respond will generate the final Mandatory Action.
Mandatory Action:

The hospital’s determination of the final phase of the escalation process is the mandatory action. This designation is generally linked to Overtime calls. When a mandatory action occurs, the technology should force a physical face-to-face interaction with the patient. Mandatory Action is a new Initiating Action with a required interaction from staff.

Example:
Normal Call has not been answered in 4 minutes.

Mandatory Action: Due to escalation past allotted time frame the technology changes the alert verbiage to “Overtime Room 320” and tones at the main console and duty stations in all caregiver work areas on the unit. Additionally, the PCT and RN’s wireless phone receives a text message “Overtime Room 320” with no capability to call into the patient’s room. The call can only be cancelled at the patient’s bedside.

Now, let’s get back to baking cakes. Here is what I’ve learned in my most recent experience. There is a certain amount of discipline that comes with baking. To try to get creative on the basics is the best way to really ruin a dessert. Getting the basics of a cake right makes for a great foundation. But, the real fun and creativity begins once you have solid knowledge of the basic fundamentals of a cake. You see, I’ve now learned how to take a basic recipe and make an exciting dessert for my family—its about the secret additives, the substitutes that have just a little more interest in flavor, the interesting style of presentation, and complimentary chemistries of toppings, sides and coffees.

Clinical Alarms is the same thing. You have to know the basics and assure the foundational strategies in clinical alarm design were applied. BUT, once that is accomplished, there is so much more that can be done to enrich the patient and caregiver experience with request and response.

The documentation above associated with each phase is laid out similar to a process chart used in lean, however Sphere3 has created a methodology that is easy to understand and see at a glance. I will create a blog series on each phase of the process if there is feedback on this, but if there is not then we will just leave it as one persons attempt to create some normalcy to the market.

Comment Back – Ask Question - Email me kgovro@sphere3consulting.com if you don't want to post a comment – join this conversation.

It’s not “IP” it’s about creating something we can all use. This shouldn’t be an uneven playing field - this is Sphere3 stepping up and saying it's about the patient - not about the technology.  If alerts are designed incorrectly in the extreme case someone could die – in the most likely case a patient is dissatisfied with their care.

The New Economy

During my visit to San Diego for the NSCA leadership conference Economist Lee McPheters spoke about the economic changes and challenges facing our nation. While the economy seems a daunting – I think that the needed productivity changes are also a huge opportunities for those of us in process redesign and we just need to find ways monetize the work associated. The American worker has been asked to increase their productivity – put in the extra hours – in hopes to help their company make it through the rough waters. The challenge is we can only work so many hours – we can only work at high capacity for so long before it requires an innovation change.

The interesting change is that while businesses have pushed their employees to be “lean” and move faster and do more with less – the American consumer has become more demanding. They expect more, because they are spending less. The American consumer is adopting the Ramsean principals of if you don’t need it don’t buy it - if you don't have the cash then don't buy it.   They are also spending their capital in a more focused manner with a thought process of  you should be treated like a customer instead of a consumer and the idea of disposable society should go by the wayside.

So what does all of this mean for healthcare? It means that the patients – who are customers – should be treated as such and that their demands will become more and more extensive.

Let’s Dream Weave?

If my grandma eats breakfast every morning at 6:30am when she is at home, then when she is in the hospital for hip replacement shouldn’t the hospital know when Grandma would like to eat breakfast? Tools like A-Frame Digital and Parental Health’s Misty can feed into her “record” and begin to create a model of how she chooses to be cared for when she is not in her home. The more data we can drive from the home to the health record the more we can allow our parents to age in place. 
The scenarios of how we function in the home should model how we are cared for in the hospital. The concept of a Patient Communications Platform should encompass more than just request from point A to point B – it should encompass consumer data modeling that preemptively leads to care.

If I document my life in Facebook and am comfortable sharing it with 400+ of my closest friends wouldn’t I be comfortable with sharing my comfort models with the hospital? If I document my food and exercise in My Fitness Pal (ap on the iphone) then why wouldn’t I share my nureotic eating habits with the place that is supposed to heal my ailments? (What if my ailments are caused by my addiction to Latte’s?)

These models allow us to improve patient care. At Sphere3 we use Performance IndiCares™ which are items relating to the behavior and performance of Caregivers and Patient IndiCares™ which are items relating to the behaviors of the patient. We tie the information together to create Risk Models or Risk IndiCares™ clearly finding paths to reduce risk and improve performance. All of these things lead to our three core values Patient Satisfaction, Caregiver Satisfaction, and Safety.

Health IT companies should feel challenged. If the farthest horizon you are looking at is within the walls of the hospital, then you are going to miss the boat.

Workflow and Growth

I have found with a start up there are several rules – I think of them like the If / Then statements we use in developing our software.


The three that I have found to be critical are:

1. IF you don’t have enough Capital THEN you are hosed.

2. IF you don’t make the right relationships THEN you are hosed.

3. IF you don’t create replicatable processes where every move isn’t hinged on you THEN you are hosed.

The third item I noted is one of my favorites – hence the reason for writing the Sphere3 Workflow Tool aka our software program. I don’t like to do the same thing twice, and it kind of drives me nuts to watch someone else do repetitive processes. (Once I have figured out the puzzle you might as well garage sale it because it’s not like revisiting an old friend for me, it’s just dull.)   I think that’s why I like to look at workflow – while there are patterns there are also variables around those patterns keep things interesting.

I recently found a kindred spirit in this vein, Tony Marsico, CEO of PCTS. Tony stopped by our office on a recent trip to Kansas City to get the “Grand” tour. Tony has a graduate degree in documentation of complex processes and corporate training. (No, I didn’t make that up, and yes I did laugh when he told me.) Which makes him perfectly suited to run PCTS, a analytic software firm that provides business intelligence for hospitals via an RTLS system.   He is an investors dream with his ability to clearly document and communicate process back out to his team.

PCTS provides real time business intelligence for Operating Rooms and Emergency Departments with “air traffic control” like screens, mobile buttons, and integration to systems and medical records. The really interesting thing about their product is its ability to run workflow rules and associate them with other rules. (That’s an over simplified way of describing that) Breaking down processes to physical movements, allowing for interaction levels and not only the “time association stand point” such as “IF the RN is in the room for X period of Time THEN do XYZ” obtaining information from other systems to validate the entry and interaction with patient specific information. All of which I have seen in “Demo” mode.

As I have said before I usually don’t believe it until I see it and PCTS was gracious enough to take me on a site visit and let me watch their team in action at Cook’s Children’s Hospital. This was an asset tracking project, so not nearly as complex as the workflow in an Emergency Department or OR, but interesting and exciting. The team was incredible, and the processes appeared to provide real time value to staff.  Including the ability to better locate, identify, and collect recalled pumps and modules.

It’s important to note – while PCTS is dependent on RTLS they are NOT an RTLS company. However, they do provide RTLS products. Tony’s explanation made a lot of sense.   Analytics based on workflow using RTLS is not simple and the validity of the information is a direct correlation to the installation of the RTLS product.    His challenges, similar to many companies I have talked to, is who to hitch his wagon to. He is in need of companies who understand analytics, understand workflow, and understand the relationship to hardware. (That last point may sound “easy” but take it from the voice of experience it’s not)

My assessment – Tony Marsico is an Investors dream - he could "McDonalize" processes within a company.  He has also surrounded himself with good people - which I have found to be the key to building a successful people.  (Yes, that's my secret - I hire people smarter than me.)  He is driven, intelligent, and has an eye for creating better workflow inside his firm and outside.

Tony’s Most Recent Read: Inside the Tornado – which I read the following week and it was a really interesting read. (Note to audience: Just read the first couple of chapters and you will get the gist of the entire book)

Sphere3 celebrated our first birthday in May. Though there was no noted celebration there was a strange, we have arrived moment – meaning that the phone has been ringing a lot and business is definitely starting to move. That momentum has really increased my travel - which has noteably decreased the blog posts. Stay tuned there are good posts to come later this month: Chad West, CEO of Ascom Wireless and Todd Plesko, CEO of Extension

The Patient Within the Code

HIMSS made me have one of those “Wow” moments where the world was once flat and now is in full Spherical shape. I was amazed at the bright colorful booths, the well dressed executives, and the hustle and bustle of it all. As I had a complete geek out moment – playing with widgets, talking tech with providers and hospitals – I began to get lost in the forest of tech and saw how it would be easy to lose the patient amongst the code.


Technology is enabling – Technology is empowering – Technology can become overwhelming and overused.

I had the luxury at HIMSS to tour Grady Hospital with Hakan Ilikan, Director of Process Improvement. Ilikan’s passion is to see technology make life better for the caregivers, patients, and families.  I will tell you the full story in a later post, but one moment stood out.  As I walked through the waiting room of the OR my gaze carried past the screen of information about the patients progression through surgery and I made eye contact with a woman – for a brief moment I was reminded why we are all doing this – for her and her loved one.

How many times a day does the patient enter your conversation?
How about their family?
How many times a day do you visualize how your technology helps them?
Does your technology really help them at all?

Maybe I am the only techy geek that sometimes forgets what it’s all about – maybe I am not. I keep a picture on our website which serves as a reminder for myself and my team of why we do this – why we focus on making life better. 

Technologists – Manufactures – Service Providers is it possible that we are so consumed with the competition, development, deployments, that the patient becomes de-emphasized in our equation?


Don’t misplace the patient among the code – Don’t forget why we are all in this game.


We as a company have not shared our Vision but I think it is important – it’s not long – we didn’t hire a large consulting firm to help us –it’s pretty simple “To Make Life Better” followed by our Mission “To Empower Organizations with integration of people, process, and technology.”

Product Life, Technology Life, Workflow Ability - Part 3

Technology Life Decisions are more readily linked to the exciting features that differentiate the products one from another. Some might call them frivolities, some might see them as necessities. Either way they are items that enhance the base goal of the product.

Technology Life Decisions are difficult to make due to the ever changing nature of technology. The “lifespan” for many technology decisions for medical devices is shortened to 5-6 years (sometimes more or less depending on the flexibility of the platform that is being purchased). Hospitals may delay purchase to wait for the next model to be released. Road Mapped items become decision points and actual realities become less critical. Not to say that a product, software, or service that has a vision for the future is unimportant but reality is more critical than vaporware.

Interestingly, the technology life decision points – things that a manufacture or developer creates to differentiate their product - often become base product decisions. Think of power windows. 20 or fewer years ago wasn’t it suitable to have a crank and before that wasn’t it a luxury to have a crank? Power Windows are an enhancement, but because of the end users interest they have become the standard. The point is often the technological enhancements won’t be enhancements for long .

Early Nurse Call Light Systems consisted of one light and one tone. Now we have systems that have unlimited light and sequence capability through LED and unlimited tones by allowing for wave files to be uploaded. Eventually, this will not be a technological enhancement – it too will become the standard.

So how do we bridge the gap between the technological enhancements of the new products and the apparent short comings of previous products. We believe the answer lies in Unifying Technologies coupled with proper workflow design.

For example, in a car, Micosoft SYNC integration allows the information from your mobile phone to download into the car and allows for voice command and hands-free calling through voice command. While all base capability of making a phone call while mobile is available using just your mobile phone, SYNC increases the value of the vehicle by enhancing your experience with the phone.

SYNC’s value is enhanced because of a unifying technology called BlueTooth.
Similarly, all nurse call systems can notify a caregiver of a patient’s need with a light and a tone. However, some can integrate to wireless phones allowing the caregiver to be mobile while speaking to the patient. There is intrinsic value to the time savings that a hospital will find by integrating their nurse call system to the nurses wireless phones. According to our research, over 30 minutes per day per RN or more depending on the style in which the integration is made. However, prior to today all of that is only possible with a unifying technology called Middleware. Interestingly, this "feature" and ability developed by a vendor outside of nurse call is becoming part of nurse call systems. Eliminating the need for a "unifying technology" all together.

Stay Tuned for
Workflow Ability and how you can transition from one platform to the next more easily and over a longer term investment.

Patient Satisfaction and Value

Patient Safety initiatives can readily be linked directly to value for the hospital. If a hospital reduces one fall there are savings of litigation, and non-reimbursable care. Patient Satisfaction can be a little more abstract when measuring results – not that you can’t get a score very readily from a Press Ganey Survey. What does that mean for dollars? How can we measure our effectiveness in these initiative? Adding new dimension to this is the HCAPS Surveys and how they will affect reimbursement for care.

Every business uses some sort of performance metrics. Often quantity of incoming requests (similar to incoming patients) and quantity of “credits” given for mistaken work (similar to non-reimbursable care) – not that these are exactly the same in all instances but they are similar and make the point that tracking specific information can be helpful when improving business practices.

Sphere3 believes that a stand-alone metric, while valuable information, is less effective as one that is cross-referenced with another. For example, if a hospital were to look at average response time balanced with the staff to patient ratio and correlated with total average call volume – you could use the information together and create a multi-faceted metric. Then take that metric and see if there is safety improvement and if there is also an improvement in patient satisfaction score.

Most importantly, what is the link it to dollars? Will the hospitals elective surgeries increase? Will the hospital have a consistently higher census? I understand there are some large assumptions when loosely linking these two data points but the point is if you had the power to easily look at information such as (1) your response times, (2) quantity of direct interactions with patients, (3) average wait time before exit, and (4) total call volume, would you be able to make specific linkages to improvement in patient satisfaction? Would you be able to take that information and link it to increase in electives and increase in revenues based on increase of paying heads in beds?

Our new Sphere3 Scorecard™ will make it easier for hospitals to get specific information on clinician response and interaction which can be compared to patient satisfaction.

Call us for a full presentation.