Doc Halo debuts Pronto, mobile enterprise-wide scheduling and messaging system

Caregivers using Pronto can access up-to-the-minute schedules, find and message on-call providers, activate critical-care teams, and enable care coordination, the vendor unveiled at HIMSS16.
By Bill Siwicki
01:30 PM

LAS VEGAS – Doc Halo has introduced Pronto, an enterprise-wide scheduling and messaging system that is part of the vendor’s Halo Mobile Health Platform for clinical communication. The system is designed to replace paper schedules and pagers. The vendor made the announcement at HIMSS16 in its exhibit hall booth (#661), where it is demonstrating the new technology for conference attendees.

[Also: See photos from Day 2 of HIMSS16]

Using the new Pronto module, caregivers can access enterprise-wide schedules with up-to-the-minute accuracy, find on-call providers anywhere in a health system and message them immediately, activate critical-care teams within seconds, and create custom clinical teams for care coordination, Doc Halo said.

Clinicians access Pronto teams and schedules from their smartphones. Administrators can input and update schedules through a web console.

Healthcare providers often serve several functions at once, making it nearly impossible to automate healthcare scheduling using a tool designed for another industry, Doc Halo said.

“This technology will coordinate care by connecting healthcare providers in ways never before possible,” said Jose Barreau, MD, the CEO of Doc Halo. “Pronto saves time in a setting where time is critical.”

Twitter: @SiwickiHealthIT


This story is part of our ongoing coverage of the HIMSS16 conference. Follow our live blog for real-time updates, and visit Destination HIMSS16 for a full rundown of our reporting from the show. For a selection of some of the best social media posts of the show, visit our Trending at #HIMSS16 hub.

Topics: 
Mobile
Want to get more stories like this one? Get daily news updates from Healthcare IT News.
Your subscription has been saved.
Something went wrong. Please try again.