HomeFor surgeonsFor patients Security & privacyAbout us Request demo
For surgeons

The platform does nothingyou didn't tell it to.

Everything a patient reads and everything a nurse reviews against comes from content you authored and signed. Here is what that actually involves.

Onboarding

It's real work. We won't pretend otherwise.

Six content modules per procedure family. We populate every one with defaults so you're editing rather than authoring — but you read all of it, and you sign it. How long that takes depends on how much you want to change. We'll give you a straight answer on the demo call rather than a number that sounds good in a brochure.

Procedure expectation libraryWhat you consider within range at each stage — drainage, swelling, warmth, activity. This is the content that prevents unnecessary calls. A replaced knee is warm for months; an arthroscopy portal leaks for two days. Without your stated expectation, a careful nurse escalates both.
Check-in question setsWhich questions the patient answers, on which days, for which family.
Patient education libraryThe answers your patients read in the app, with your name attached to the ones you rewrite.
Photo instructionsHow you want the incision framed, from what angle, in what light.
Medications and dressingsYour standing regimen and dressing schedule per family, with per-case overrides.
Escalation and call guideWhat you want your office told, by whom, and how fast — the criteria a nurse escalates by, whether the submission was scheduled or sent because something didn't feel right.

Nothing goes live for a procedure family until you have signed that family. Families you haven't signed simply aren't offered at enrollment.

What your patients see

Thirty days of your practice paying attention.

Patients don't judge you on the hour in the operating room. They judge you on the weeks afterward — and right now the ones who feel looked after are the ones who happened to call and get through.

This makes it even. Every patient hears from your office on a schedule instead of only when something goes wrong, and the guidance they're reading has your name on it rather than a photocopied sheet from a binder.

They know what you expect at day three, day ten, day twenty-one.
A question at nine at night has somewhere to go that isn't your cell phone.
What they send gets read by a person, and they're told that up front.
Every patient gets the same attention, not just the persistent ones.

We won't tell you it makes patients less anxious — that's theirs to report, not ours to claim. What we'll say is that showing up for thirty days is visible, and patients notice who does it.

The review layer

The nurse layer is the whole product.

Software does not look at your patient's wound. A licensed nurse does — one licensed in the state your patient is in, reviewing what came in against what you said to expect, and making a judgment about whether your office needs to know.

Licensure verified and enforced by the platform, not by policy alone.
Review during defined daytime windows, with different hours on weekends and holidays.
Every review attributed to a named nurse. No shared logins anywhere in the system.
Two missed check-ins trigger an outbound call rather than silence.
Documentation

When someone asks what happened in week two.

Not a lawyer — a partner covering your weekend, a nurse picking up a chart, a patient who wants to know what they sent you on day nine. Most practices answer that question from memory and a callback note, because there was never anywhere else for it to go.

The same thirty days, recorded two ways
Day of discharge

The patient goes home with a paper sheet and a phone number.

TodayNothing starts. The window opens and no one is counting days.
HereTheir check-in schedule starts, built from the family you signed.
Day 6 to 12

They have a question about the incision and send a photo.

TodayA text to a personal cell, or a portal message read the next morning. No log, no time, no consistent reviewer.
HereA submission with a date on it, reviewed by a named nurse against the expectation you wrote for that procedure and that day.
Day 14 to 21

Something falls outside what you said to expect.

TodayWhether your office hears about it depends on who was at the desk and how the message was worded.
HereYour office is contacted, with the photo, the date, and the patient's own words attached.
Any time after

Someone needs to know what happened across those thirty days.

TodayIt gets reconstructed — from memory, a callback note, and whatever survived in the inbox.
HereIt's a list. Every submission, every review, every contact, with names and times, and it exports.

What the record holds

Every submission, every nurse review, every escalation and every contact with your office — each timestamped and attributed to a named person. No shared logins, so nothing is signed by "the practice."

One list, in date order.

It stays yours

The record belongs to your practice, not to us. We hold it as a business associate under a signed agreement, and it exports in a readable format whenever you want it — including on your way out the door.

Yours to take with you.

What we won't tell you

That it protects you. We don't know whether a complete record changes how a claim goes, and neither does anyone else selling you software. What it's worth is a conversation for you and your counsel.

We'd rather say so.
Commercial terms

What it costs, and how we'll tell you.

Pricing is set per practice — your surgical volume, and which procedure families you turn on. We'd rather give you a real number on a call than publish a table that doesn't fit how you operate.

Bring your case volume to the demo and you'll leave with a figure, not a follow-up.

The platform does not currently integrate with electronic health records.

Bring your hardest follow-up question

The demo is more useful when you're trying to break it.