What is an "Earn the Right" Location-based Services Strategy?


Hey Reader,

Location-based services (LBS) are fundamental to healthcare's digital transformation, yet many implementations fall short of expectations. While some systems even exceed expectations, the lack of consistent patterns creates an atmosphere of mistrust. It's is usually not the fault of the technology, the integrators or the customers. Usually bad outcomes are because the implementation strategy doesn't fit the organization. Too aggressive or too lean and expectations are not met. A key part of that strategy should be "gated" where each project "earns the right" to proceed to the next. Done correctly, the entire program pays for itself with the data to prove it.

TLDR:

Successful LBS implementation requires focusing on outcomes before ROI, understanding uncertainty in location systems, and building a strategic roadmap with proper governance structures.

Key Concepts:

  • Location-based Services (LBS): Technologies and systems that enable tracking and managing assets, people, and workflows based on location data
  • Location Fidelity: The accuracy and precision of location data provided by the system
  • Planning Horizon: The timeframe over which decisions need to be made and data needs to be available

Details

Understanding Uncertainty

All sensor systems have inherent uncertainty that should be factored into how they are used. Location fidelity varies based on environmental factors like building materials and architecture. Demos often show best-case scenarios, not real-world performance so it is not about eliminating uncertainty it is about understanding it.

Matching Solutions to Outcomes

To match the levels of uncertainty to the desired outcome you should focus on specific workflow requirements. Clinical engineering needs a specific IV Pump for preventive maintenance versus nursing that needs one that is clean and ready for use. These might both fall under the use case category of Asset Management but they each have different location requirements. Also, these are real-time "capable" systems but data gathered over longer "planning horizons" is full of valuable insights. These are only valuable if there is a goverance structure that is set up to consume them and is empowered to react.

Strategic Implementation Approach

Strategic alignment is found by starting with a review of all the organization's improvement initiatives. Most organizations don't realize where LBS can be the most effective so skipping this step is a missed opportunity. For example, maybe a top priority improvement initiative is Capacity Management. This should trigger a deeper look at patient location tracking as an opportunity for RTLS.

Governance is Critical

By establishing proper governance through LBS steering committee access to the operational strategy can be established. This means the composition of the committee should be mostly operational people with a few technical experts to guide the roadmap. The roadmap that is created has an "earn the right" theme to it. This means it has gates where the success criteria are evaluated. Economics are a determining factor if the next project starts.

  • Create a roadmap that "earns the right"
  • Have good ROM estimates for each project
  • Tie outcomes to economic returns
  • Ensure the outcome has enough time to be measured
  • Focus on outcomes before ROI calculations
  • Show the networking effect of each technology implementation
  • Give process changes the consideration they deserve

Example projects that focus on outcomes.

  • "Implement PAR Stocking for IV pumps" or "Implement a Comprehensive Loss Prevention Program" versus "Implement an RTLS Asset Management Solution"
  • "Implement Capacity Management for Reduced LOS" or "Implement Patient Wandering Detection and Response" versus "Implement Patient Tracking"
  • "Implement Staff Safety Incident Detection and Response" versus "implement Employee Duress System".
  • "Reduce HAIs and Leapfrog Scores from Better Hand Hygiene" versus "implement Hand Hygiene Tracking"

Common Pitfalls

  • Implementing tools without good process adaptation and departmental engagement.
  • Focusing on how to use the technology instead of how to solve the business problems.
  • Lack of governance, committment and oversight
  • Failure to collect the data that can show evidence of improvement or lack of improvement.

Key Takeaways:

  • Success requires focusing on outcomes and processes before selecting tools
  • A strong governance structure through an LBS steering committee is essential
  • Implementation should follow a strategic roadmap that demonstrates value at each stage
  • Understanding system limitations and matching them to use cases is crucial

Conclusion:

Location-based services can transform healthcare operations, but success requires a strategic approach focused on outcomes, proper governance, and careful attention to workflow integration. Start by establishing an LBS steering committee and creating a roadmap that builds on demonstrated success.

Ready to develop your LBS strategy? Book a consultation to discuss creating a roadmap for your organization.

Until next week,

Paul E Zieske
Location Based Services Consulting

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
Unsubscribe · Preferences

Why Where Matters

Our weekly newsletter that tackles the complex world of location based services using concepts from Care Traffic Control. Taping into IoT, digital twins, geolocation and mobile devices we provide insight to an industry that is primed for new ideas.

Read more from Why Where Matters

Hey Reader, The Missing Layer Between AI Hype and AI Success How Precursor’s Digital Shadow Prevents the 95% Failure Rate Let that sink in. Ninety-five percent. Billions invested. Almost nothing to show for it. But here's what the research reveals: The AI itself usually works fine. The technology isn't the problem. The problem is that AI is deployed to processes that are more complex than they appear. They contain hidden dependencies, informal workarounds, and tribal knowledge outside formal...

The Flight Simulator for Your Supply Chain by Bryan Small. Visual comparing traditional supply chain management (stressed) versus semantic intelligence approach (confident). Tagline: Crash in the simulator, succeed in reality.

Hey Reader, The Flight Simulator for Your Supply Chain What if you could predict the impact of your IV pump preventive maintenance schedule on clinical availability before taking units offline? What if you knew how changing restocking schedules would affect OR efficiency before disrupting anyone's workflow? What if you knew which PAR reductions were safe and which ones would compromise patient care before making any cuts? This isn't science fiction. It's what happens when you apply the same...

Hey Reader, When RTLS Meets AI-Native Design: Beyond Asset Tracking to Revenue Generation Two Emerging Use Cases with referenced Case Studies: Predictive Patient Flow and OR Optimization Last time I talked about AI-Native Consulting - how adding AI to traditional RTLS use cases like equipment tracking transforms them from "where's my IV pump" to "predict when we'll run short and automatically redistribute before it happens." That was about making existing use cases smarter. But here's what...