From your spreadsheet to the bedside

Every hospital already has an antimicrobial policy and a committee that maintains it. What most do not have is a way to get a change from that committee to the person prescribing, quickly enough to matter. This is that path, end to end.

  1. It starts as the spreadsheet you already keep

    Your antimicrobial committee maintains these files today. There is no new authoring tool to learn, no template to migrate into, and nothing to retype. The columns you already use are the columns we read.

  2. Someone changes one dose

    Tier 1 pyelonephritis moves from 1 g to 2 g of ceftriaxone. That is the whole edit: one cell, in the file, by the person who owns it.

  3. Upload the file

    Drag it into the studio. Nothing is published yet, and nothing about the live guideline has changed — this is a proposal, not a deployment.

  4. The studio shows what changed, and only what changed

    The studio lists the fields that differ, with the old value beside the new one. Here that is one field. The other 209 rows of the corpus are not re-presented for you to re-read — a reviewer checks a change rather than a document, which is the difference between a review that happens and one that is signed off unread.

  5. A committee member approves it, with a reason

    The note is kept with the version. Six months later, when somebody asks why the dose went up, the answer is attached to the change rather than in a meeting minute nobody can find.

  6. Clinicians have the new dose

    On the ward, on a phone, at the bedside — the same minute it was approved. No reprint, no PDF version to circulate, and no pocket card that is a year old.

The other half

A guideline tells you what your hospital decided.
It cannot tell you what changed last week.

Both are true at the same time, and a doctor at three in the morning needs both. The protocol is a committee decision, revised when the committee meets. Everything outside it moves continuously. So we put them one click apart, in one signed-in session, and left the clinician in charge of the join.

  1. Global medical knowledgeInternational evidence, national guidelines, and a literature that does not wait for anyone
  2. AtlasThe evidence copilot. Every answer carries a citation you can open, and it says so when it cannot find one
  3. EvidenceoThe contextual intelligence layer
  4. Your institutionThe committee’s own protocols, their own resistance data, their own decisions — rendered, never rewritten
  5. The doctorAction, at the bedside, on a phone

Global awareness and local actionability

  • Your columns, not our template. The files your committee already keeps, read as they are. There is no authoring tool to learn and nothing to retype.
  • A review of the change, not of the document. The fields that differ, old value beside new, with the approval note kept against the version. Which is the difference between a review that happens and one that is signed off unread.
  • The same evidence can mean different things in different hospitals. A first-line antibiotic that is right almost everywhere in the world can be the wrong first choice against the organisms growing in one particular building. That is not in any global reference. It is in your own laboratory data.

See it with real content

The demonstration hospital is a full deployment: empiric therapy, an antibiogram, a susceptibility grid, durations, surgical prophylaxis and a risk calculator. Sign in with any Google account — it enrols you to read the demonstration, and to nothing else.

Open the live demoAbout Evidence Atlas

⚠ The hospital, the resistance data and the doses shown here and in the demonstration are invented. Meridian General Hospital does not exist. Nothing on either site is clinical advice.