For surgical practices
Patients carry their prep, medications, health data and a line to your team in their pocket. Surgeons carry an inbox of drafts to approve and a surgery-day timeline the family can follow. One download — the app knows who you are.
Every AI reply is read and approved by a human before a patient sees it. Nothing auto-sends.
Why not just the EMR?
The hospital’s portal is the system of record — billing, results, the chart that follows a patient for life. It was never built to carry one surgeon’s instructions through one operation. That is the whole job here.
“The portal is the hospital. Surgery Care is your surgeon.”
The one line patients need.
The full case for a surgeon-owned channel →Two apps, one binary
There is no separate provider portal to roll out and no web login for patients to forget. Your surgeon and your patient install the same thing; signing in decides what it is.
2 family contacts notified at each milestone.
1 patient has no working digital channel — the office must call.
Same build · iPhone and Android · Screens illustrative
A bounded course of care, not an inbox
Ninety days by default — the length is your practice’s setting — with a real beginning and a real end. Your team is not signing up for an open-ended message thread that lives forever — each surgery is a finite course of care that finishes with a satisfaction survey and stops. It closes softly, and your staff can extend it: a complication is always a human conversation, never a silent close.
Context-aware surfaces
Pre-op prep is open only while the patient is pre-op, and closes the moment surgery starts. Post-op instructions appear only once surgery actually happened. Cancel the surgery and both close. Patients are never reading the wrong instructions for the day they are in.
Diagram: the pre-op prep window runs up to the moment surgery starts, and the post-op instruction window begins after it. The two never overlap.
Surgery day
Each milestone fans out immediately to the family contacts the patient consented to — by text and email, with a private link to a live timeline that needs no login and no app. The link is served from your practice’s own domain, so what arrives on a relative’s phone comes from your practice rather than from software they have never heard of.
The second tap is an outcome, not a checkbox: completed successfully, completed with issues, or cancelled. Only a good outcome sends the family the reassuring note by itself. Anything else waits for the surgeon, because a machine should never be the one to deliver hard news.
Tapped once, on the phone already in the surgeon’s pocket.
Maria’s surgery has started. We’ll send an update at each step.
Elena R. · SMS · David R. · email
The procedure is complete. The surgeon will come out to speak with you shortly.
Elena R. · SMS · David R. · email
Maria is in the recovery room and waking up comfortably.
Elena R. · SMS · David R. · email
Maria has been discharged. Her recovery instructions are already in her app.
Elena R. · SMS · David R. · email
Nothing sends until the surgeon taps.
Families are informed without a single call to the front desk — and the desk is not the bottleneck on the busiest day of the patient’s year.
The product principle
This is not a safety setting someone can switch off. There is no path through Surgery Care where an AI-written message reaches a patient without a person on your team approving it first.
01 · Drafted
From your practice’s own knowledge base — your prep sheets, your post-op instructions, your FAQs. Not the open internet.
“Some swelling at the incision on day 3 is expected. Keep the dressing dry and…”
02 · Reviewed
It lands in the provider inbox. Approve, edit, or discard. Until somebody acts, the patient sees nothing at all.
03 · Delivered
In the app, attributed and timestamped — so the patient knows a person at your practice stood behind the answer.
“Some swelling at the incision on day 3 is expected…”
✓ Reviewed & approved · 8:41 AMWhat’s in the apps
Answers from your practice’s own knowledge base — your prep sheets and post-op instructions, not the open internet. Drafts only; a clinician releases.
Ticks are one-way and confirmed. They are statements of fact, so the office can read them as a clinical-readiness signal rather than a toggle someone flipped.
Steps, sleep, resting heart rate and heart-rate range from Apple Health and Health Connect — so recovery is observed, not self-reported.
What the surgeon prescribed, plus the over-the-counter things the patient adds themselves, with dose reminders on the device.
One thread to the practice for the whole of their care. Every reply is on the record and every reply cleared a human.
The provider home screen is a queue of drafts waiting on a person. Approve, edit, or discard. Nothing leaves on its own.
In surgery → outcome → In recovery → Discharged, tapped by the operating surgeon. A good outcome notifies the family by itself; anything else waits for a person.
The recent arc of a patient in one scroll, so whoever picks up the thread is not starting cold.
An honest read on who genuinely cannot be reached digitally and must be phoned — instead of assuming a delivered message was received.
Face ID, Touch ID or fingerprint on both apps as an automatic-logoff safeguard — with a device-passcode fallback so no patient is locked out of their own instructions.
Consent is per contact and per channel — text and email are separate, and both start off until the patient turns them on. Contacts get milestone updates and a timeline link on your own domain, and nothing more. Withdrawing consent kills the link.
Requested and confirmed in the app, before the operation and after it.
Built for protected health data
Your patients are walled off from every other practice’s patients. That separation isn’t a rule our software has to remember to follow — it sits underneath the application and applies to every single request, so a mistake in one feature cannot spill across the wall. The system has worked this way since the first record it ever stored, and there is no setting that turns it off.
Every look at a patient’s information is recorded: who saw what, and when. Information is encrypted on its way to us and while it sits with us. Both apps lock behind a face or fingerprint and sign themselves out when left alone. And we hold signed business-associate agreements with the companies that host our systems and provide our AI.
What we don’t claim: there is no such thing as a HIPAA certification, so we don’t advertise one. We describe the controls we actually run and the agreements we have actually signed — and Surgery Care is the software behind your practice, never a provider in the room between you and your patient.
Getting started
No hospital IT. No committee. No EMR project. A practice can be live with its next patient. Most tools in this space open with an integration conversation; this one opens with a conversation about your instructions.
Your name, your branding, and accounts for your surgeons, PAs, admins and office staff — in your own isolated space on the platform.
Your prep instructions, post-op sheets and FAQs become Atlas’s knowledge base and the content in the patient app. One source, one consistent answer.
Staff enrol a patient in a click. The patient downloads Surgery Care on iPhone or Android, unlocks with Face ID, and their care opens.
If you are a patient
Your practice enrols you; there is no public sign-up, and nobody can add themselves. Your care comes from your surgeon and their team — Surgery Care is the software they use to prepare you, keep your family updated on the day, and stay with you through recovery. Questions about your operation always go to your practice.
Surgery Care