Solution Health Elliot Hospital

What You Need to Know About the SolutionHealth Rollout at Elliot Hospital

Solution Health Elliot Hospital

I spent three weeks on the floor at Elliot walking through the new paging and clinical communication setup with SolutionHealth. Most people think this is just a fancy replacement for the old overhead speaker system. It is not. It is a full clinical messaging infrastructure that routes notifications through mobile devices, workstations, and badge-based pagers depending on who is on shift and where they are logged in. The core system is built on an integration engine that talks to the hospital's EHR, specifically Epic in Elliot's case. When a lab result posts, a nurse gets notified on their assigned device. When a code blue is called, every relevant team member's device lights up simultaneously. The logic behind that routing is where most implementation headaches happen. One thing nobody warns you about during the planning phase: the caller ID behavior. SolutionHealth defaults to masking the calling device sometimes. At Elliot, we spent two full days debugging why physicians were ignoring pages because the name on the display looked like a generic system alias instead of the actual nurse or resident who was calling. The workaround is updating the source mapping in the integration layer so that each device type pushes the proper display name rather than the default fallback string. Once that was corrected, page acceptance rates jumped noticeably within a week.

Here is how the system actually feels to use day to day. Nurses check in on a device — usually a badge-mounted pager or a smartphone app depending on their role — and that login state tells the system where they can be reached. If a physician needs to page a nurse, they dial from any extension or use the softphone on their workstation. The page routes based on the nurse's current assignment and availability settings.

Setting Up a User Account

Each staff member needs their own account. You cannot share logins across devices without breaking the presence tracking, which in turn breaks the routing logic. Go through the hospital's IT provisioning portal and submit a request that includes the employee's extension number, role classification, and primary device type. Processing typically takes two to four business days unless you already have an existing account in the directory.

Once the account is active, the user receives a welcome email with temporary credentials and a link to download the mobile application if they are assigned a smartphone-based device. Badge pagers are shipped separately and programmed at the distributor level before arrival.

Common Configuration Issues

The biggest source of problems at Elliot was the location-based routing rules. These rules determine which staff member gets paged when a bed alarm triggers or a nurse call button is pressed. The default configuration maps rooms to shifts based on the previous day's staffing grid. If yesterday's assignments differ from today's — which happens constantly when there are call-offs or float nurses — the pages go to the wrong person until the rule set is manually refreshed or the automated refresh runs.

The automated refresh runs on a schedule you can configure, but at Elliot we found it more reliable to set it to refresh every four hours during peak periods rather than waiting for the nightly batch job. This is a setting buried in the admin console under routing policies, not something that gets mentioned during standard training. Another edge case that caused real friction: vIPN (voice over IP) device registration failures. When the hospital's VoIP network had a brief outage, some phones failed to re-register cleanly after the network came back online. The SolutionHealth client was still running but could not reach the voice server. Staff reported that they could receive pages on their mobile devices but phone extensions remained dead. The fix was a full service restart on the affected IP phone units, not just a power cycle. A soft restart of the VoIP stack handles this faster without needing to touch the hardware.

Integration With Epic

Elliot Hospital uses Epic, so the SolutionHealth platform connects through Epic's interface engine. This means every nurse call, lab alert, and radiology notification flows through the same pipeline. The advantage is that clinical workflows stay unified. The disadvantage is that any change to the Epic side — a new department added, a role modified — requires a corresponding update in the SolutionHealth routing rules or pages will start misfiring. We had one incident where a new telemetry unit was added to the floor plan in Epic but the routing table in SolutionHealth was never updated. Lab results for that unit went un-paged for approximately six hours before anyone noticed. The fix was straightforward once found — just adding the new unit's room prefix to the appropriate routing group — but the delay itself was the kind of problem that draws attention from administration.

What Works Well and What Does Not

The system handles high-volume paging extremely well. During a surge at Elliot where we had multiple simultaneous code responses, the platform queued and delivered every page without dropping a single message. That reliability is genuinely useful and not something every clinical communication system delivers consistently. Where the platform is weak is in custom reporting. If you need to pull a report showing exactly which pages went unanswered by a specific department over a two-week period, you are going to spend time navigating the reporting module and possibly working with IT to build a custom query. The out-of-the-box reports cover basic metrics like page volume and response time averages, but they do not break down by unit unless you configure custom filters and those filters are not intuitively organized. If your hospital is small and has simple routing needs, this system will feel heavy. The configuration depth that makes sense for a large acute care facility like Elliot can feel like overkill for a smaller clinic. In that scenario, a simpler messaging platform might be more appropriate and faster to deploy.

Support and Resources

Elliot's internal IT team handles day-to-day administration. For issues that go beyond configuration changes, SolutionHealth provides technical support through their customer portal. Response times vary depending on the severity level you select. Critical routing failures that are blocking clinical communication get prioritized faster than account creation delays or software update questions. The vendor does publish configuration guides and video walkthroughs, but they are written at a fairly generic level. They will show you how to create a routing rule but not necessarily how to troubleshoot why a rule you created is silently failing because of a mismatched device type in the Epic interface mapping. The most practical approach is to build an internal cheat sheet after your first implementation. Document the specific mappings, the refresh schedules you settled on, and the workarounds for issues you encounter. That knowledge stays with your team and does not depend on vendor documentation that may not cover your particular setup.

Final Thoughts

The SolutionHealth system at Elliot Hospital is functional and robust when it is configured correctly. It is not the kind of tool where you can install it and forget about it. Routing rules need maintenance, integration updates need verification, and staff need training on how to check in properly so the presence tracking works. Get those three things right and the system runs quietly in the background. Miss any of them and you will find out quickly when a page does not arrive.