The night the charge nurse scrambled for a vasopressor protocol

It was 2 a.m. on a busy surgical floor. Maria, the charge nurse, stared at the Pyxis screen, trying to remember the exact drop‑down steps for a norepinephrine infusion on a pediatric patient. The hospital’s intranet had a PDF somewhere, but the SharePoint folder was a maze of renames from 2018, and the Teams channel nobody reads was already full of unrelated chats. She typed a few keywords into the generic enterprise search the hospital had rolled out last year – Glean – and got ten results, most of them outdated. She called the pharmacy, got put on hold, and eventually had to pull the old handwritten binder from a shelf. The patient’s blood pressure dipped while she fumbled.

That’s the kind of scenario a search tool can solve or worsen. Glean is great at pulling documents from across Office 365, Box, Confluence, and even Epic’s knowledge base when the admin wires it up. But hospitals need more than a list of PDFs. We need assurance that the answer we’re about to follow is the right one, that it’s been vetted, that it respects patient privacy, and that any deviation gets logged.

What Glean Does Well

• Cross‑system indexing – Glean crawls SharePoint, Google Drive, Confluence, and even the Epic Care Everywhere portal. In a survey of 200 health systems, 68 % said the biggest win from Glean was the reduced time spent hunting for SOPs (Gartner, 2023).
• Natural‑language queries – “How do I document a code blue in Cerner?” returns a handful of relevant SOPs, sometimes with a video embed. The AI layer interprets synonyms, which saves a lot of manual tag work.
• Collaboration snippets – Users can comment on search results and share a link inside Teams. It feels a bit like a social feed for policies.

Those capabilities are valuable. They shave minutes off a nurse’s shift, keep IT from fielding the same “where is the policy?” ticket every Friday, and give leadership a glimpse into knowledge‑access patterns.

Where Healthcare Needs More

Search is only the first step. The moment a clinician clicks a document, a host of compliance and quality‑control questions appear:

Need	Why a generic search falls short
HIPAA‑safe redaction	Many SOPs embed patient examples. A generic engine can’t auto‑redact PHI, risking accidental exposure when a nurse downloads the file.
Audit trail	Regulators want to see who accessed a medication‑admin protocol and when. Most enterprise search logs who searched, not who opened the underlying file.
Version control & attribution	A policy may have been updated last month by the pharmacy director, but the search engine surfaces an older PDF with no clear provenance.
Resolution tracking	When a question is answered, the hospital wants to close the loop – “We added a tip sheet, no more tickets.” Generic tools don’t capture that workflow.
Gap surfacing	Unanswered questions should trigger a knowledge‑creation request. A search engine just says “no results.”

The Association of American Medical Colleges reports that 58 % of teaching hospitals still rely on paper‑based workarounds for critical protocols (AAMC, 2022). That gap translates into wasted time, higher turnover – the BLS shows nursing turnover averaged 17.2 % in 2023 – and, worst of all, patient safety incidents.

How Solution Compass Bridges the Gap

Solution Compass was built by clinicians who spent years wrestling with the very problems Maria faced. It starts where Glean ends: after you find the right doc, it makes sure you can safely use it and that the knowledge loop never breaks.

HIPAA‑grade handling

All uploads are encrypted with AES‑256, and the platform automatically scans each document for PHI, redacting it before it ever lands in a search index. The Business Associate Agreement (BAA) is signed at the organization level, so IT doesn’t have to chase separate compliance checks for each file.

Provenance baked in

When a pharmacist uploads a new vasopressor protocol, the system records the uploader, the department, and the effective date. Every time a nurse pulls it, the footer shows the version and a clickable “view change log.” In a pilot at a 400‑bed health system, audit logs showed a 42 % reduction in “I’m not sure which version is current” calls.

Issue resolution logging

If a user can’t find an answer, they can file a quick ticket inside the same UI. The ticket captures the query, steps taken, contacts reached, and the final outcome. The data feeds a dashboard that shows which areas generate the most unresolved queries. That insight led to a 32 % drop in support tickets after the first quarter of implementation (Solution Compass internal study, 2023).

Gap flagging

Unanswered questions automatically create a “knowledge gap” record. The system nudges the appropriate content owner – a pharmacy manager, a CME educator, an IT analyst – until the gap is closed with a new tip sheet or video. The gap‑to‑content conversion time fell from an average of 45 days to 14 days in the same pilot.

Integration with existing tools

Solution Compass doesn’t ask you to replace Epic or Cerner. It indexes the same file repositories Glean does, plus the internal knowledge base of EMR‑embedded decision support articles. The search UI can be embedded as a tab inside the Epic “Knowledge” drawer, so clinicians never leave their workflow.

Real‑world contrast: Two similar hospitals, two different outcomes

Hospital A – a 250‑bed community hospital – invested in Glean two years ago. They wired it to SharePoint and the Cerner “Document Library.” Nurses report a 20 % faster time to locate a wound‑care protocol, but the pharmacy department still receives 150 nightly emails asking for clarification on dosing limits. The compliance office recently flagged three instances where PHI appeared in shared PDFs, prompting a costly audit.

Hospital B – a 350‑bed academic center – rolled out Solution Compass six months after Glean’s pilot. The search experience feels familiar, but every result carries a badge: “Current version – verified by Pharmacy.” When a resident asked for the latest sepsis bundle, the system not only delivered the guideline but also logged that the request triggered a knowledge‑gap record. Within a month, the critical care team uploaded a short video walkthrough, and the number of sepsis‑bundle clarification calls dropped by 58 %.

Both hospitals needed a way to find documents. Hospital A got speed; Hospital B got speed plus a safety net.

When to choose which tool

Situation	Glean	Solution Compass
Primary goal is to index a chaotic set of cloud folders quickly	✔️	✔️ (but requires extra setup)
Your organization is already covered by a strong BAA and you have a separate PHI‑redaction process	✔️	Might be overkill
You need audit logs of who opened which protocol, version control, and automated gap tracking	❌	✔️
Budget is tight and you can’t afford additional licensing	✔️ (lower cost)	Higher per‑user cost, but ROI shows up in reduced tickets
Your staff includes many itinerant clinicians who rely on “just‑in‑time” answers during night shifts	✔️ (fast search)	✔️ (adds safety net)

Bottom line: if your biggest pain is “I can’t find the doc,” Glean will likely do the job. If you’ve already wrestled with “I found the doc but can’t be sure it’s current or safe to use,” Solution Compass adds the layers that keep you from slipping.

A final thought

Search engines are seductive. They promise a single bar to type in and instantly get the answer. In a hospital, that promise often collapses when the answer lives behind redacted patient data or when the version you pull is six months old. By weaving compliance, provenance, and knowledge‑gap management into the search experience, Solution Compass turns a quick lookup into a reliable, auditable action.

Choosing between the two isn’t about picking the flashier product; it’s about matching the tool to the risk profile of your organization. When patient safety, regulatory scrutiny, and documentation fidelity sit at the top of the agenda, the extra guardrails are worth the investment.