While you slept, Rounds saw every patient.It's the night shift. Rounds is already on it.
Not another records system. An agent on permanent rounds — reading every chart, filing every order, coding every claim, and waking a human only when a human is worth waking.
- FHIR R4 native
- On-prem or cloud
- Humans sign everything
Last night, at one 400-bed hospital
1,847 ACTIONS · 9 NEEDED A HUMAN- 01:42Bed 7B-04 — potassium 6.1 flagged → nephrology paged, repeat ECG ordered · escalated
- 02:15Pharmacy — 14 overnight orders interaction-checked, one substitution proposed for the 06:00 round
- 03:12Ward 3A — discharge summaries drafted for all six morning departures, awaiting signature
- 04:20Claims — 212 invoices coded and queued, zero manual entries, zero retypes
- 05:37OT — today's list re-sequenced around a delayed implant delivery; surgeons notified
- 06:00Morning report compiled — nine decisions on your desk, everything else already done
Every action is logged, attributed and reversible. Rounds drafts; your clinicians decide and sign.
Other systems store the hospital. Rounds runs it.
Every chart, every hour
A continuous pass over every open episode — vitals trends, pending results, stalled orders — the way a chief resident would, if there were forty of them.
Paperwork, finished by morning
Notes drafted from the encounter, codes from the diagnosis, claims from the care itself. Your clinicians read and sign — they stop typing.
Only what deserves you
A thousand routine things handled silently; the nine that need judgment surfaced with full context. The pager gets quieter and smarter at once.
The world's best HIMS is a bold claim. So we itemised it.
Best isn't a banner we hang — it's a comparison we're happy to stand behind, line by line, against the system you're running today. Read it the way you'd read a chart: quickly, and looking for what's abnormal.
The HIMS you have —Waits for someone to type into it.
Rounds —Reads itself every hour — trends, pending results, stalled orders — and acts.
The HIMS you have —Written at midnight, after the shift, by the doctor.
Rounds —Drafted from the encounter by the agent; the doctor reads and signs.
The HIMS you have —Coded by hand, denied in weeks, retyped in months.
Rounds —Coded from the care itself — 98.4% clean on first pass.
The HIMS you have —A dark screen and a pager that cries wolf.
Rounds —1,847 actions handled quietly; the nine worth waking for, escalated.
The HIMS you have —Eighteen months, a consulting army, a training season.
Rounds —First ward live in six weeks — on your servers or ours.
“Best” is a title you re-earn nightly. Rounds files its evidence every morning at six.
Slide to your bed count. Meet tonight's workload.
Directional estimates, scaled from pilot averages at a 400-bed hospital. The demo runs the real thing — computed from your own wards, not an average.
Estimates only — every hospital rounds differently. Illustrative figures pending audited pilot data.
Designed like it matters — because at 3 a.m., it does.
Hospital software is where good design went to die: beige grids, twelve open tabs, a manual thicker than a chart. Rounds was drawn the other way up — an interface calm enough for the night desk, fast enough for a code blue, and honest about who did what on every screen.
Blue is you. The trace is the agent.
Every colour is a signature. Cobalt marks what a human clicks and signs; trace green — the colour of the monitor line that watches all night — marks what the agent drafted, flagged or filed. Accountability at a glance, no audit menu required.
Porcelain by day, Obsidian by night
A light theme for morning rounds, a dark theme tuned for the 3 a.m. nursing station — same layout, same muscle memory, switched before the screen even paints.
Reads like a handover, not a menu
The morning report runs top to bottom the way a good handover does. New staff find their footing inside one shift — no training season, no laminated cheat sheet taped to the monitor.
Motion that earns its place
Every animation explains something — a count settling, a feed still writing — and every one of them stands down for reduced-motion users. Tired eyes are a design constraint here, not an afterthought.
- WCAG-contrast palettes
- Keyboard-first
- Zero layout shift
- Sub-second screens
From 60 beds to 600, the mornings sound the same.
“I used to reach at six to finish yesterday's notes. Now the notes are waiting for me. My duty doctors round on patients again, not on paperwork.”
“Cashless files used to take my TPA desk three follow-ups and a week of calls. Now the claim is coded the night of discharge — complete, attached, first-pass. The desk chases approvals now, not paperwork.”
“Every hospital in a tier-2 town says the same thing: we cannot hire more doctors. Rounds didn't add staff — it gave the staff I have their evenings back. That is the only recruitment I could afford this year.”
“NABH audit used to mean three weeks of hunting files across departments. Every action in Rounds is logged and attributed, so when the assessors asked for our records, we gave them a login.”
Pilot-cohort voices, attributions illustrative — named, consented references replace these at launch.
Built by people who've lived inside hospital systems.
Rounds isn't a general-purpose AI wearing scrubs. Behind it are HIMS business analysts who have mapped a thousand ward workflows, product owners who have carried hospital software through real go-lives, and clinicians who know exactly what 6 a.m. feels like. That fluency is baked into every screen — and it walks in the door with every deployment.
Every deployment ships with a named team
- HIMS business analyst
Maps your wards, OPD flows, forms and edge cases before a single screen changes. Your processes lead; the software follows.
- Product owner
Owns the rollout backlog and answers to your CMO and nursing head — not to our feature roadmap.
- Clinical lead
A physician on our side of the table, so nothing ships that wouldn't survive a real morning round.
- Integration engineer
FHIR, HL7, PACS, lab analysers, payer feeds — connected in weeks, documented forever.
Named on day one. On WhatsApp by day two.
You should be skeptical. Here are the real answers.
Q1What if the AI makes something up?
Rounds drafts; it never commits. Every note, code and order is a proposal pinned to its evidence — the lab value, the medication line, the vital trend it read. The clinician sees the source beside the suggestion, then signs, edits or discards. An unsigned draft touches nothing.
Q2Who is liable when it's wrong?
The same person who has always been: the clinician who signs — which is exactly why nothing enters the record unsigned. What changes is what they're signing. A draft with its evidence attached beats a blank screen at midnight, and the full action log means any decision can be reconstructed, minute by minute.
Q3Where does our data live?
Wherever you decide. Rounds runs fully on-premise, in your private cloud, or in ours — same product, same speed. Your patients never train anyone else's model, and nothing crosses a boundary you didn't draw. Air-gapped deployments exist, and they are boring — which is the point.
Q4What happens when it makes a mistake?
Every action is logged, attributed and reversible — one click returns any draft, code or schedule to its prior state. Escalation thresholds are tuned to over-call rather than under-call, and the weekly review with your named team walks through every miss, in both directions.
Q5Is this here to replace our staff?
It replaces the eleven-p.m. paperwork, not the people. Hospitals don't have a surplus of clinicians; they have a deficit of clinician hours lost to typing. Rounds returns the hours. The only head-count it threatens is the backlog's.
Your hospital already has the patients. Give it the Rounds.
A 30-minute demo on your own workflow — one ward, one night, your data model. See the morning report it would have written for you today.