Everything it does
The whole list.
53 capabilities, grouped by what you would be doing when you need them. Nothing here is a roadmap item — if it is on this page it is in the product today, and a test ties each group to the code that keeps it that way.
Documentation that writes itself
Speak once. The document that comes out is the one that specialty actually writes — not a transcript with headings pasted on.
- Dictate the consultationThe note structures itself, the vitals fill their own boxes, every computable score is computed and the reasoning starts — before you reach for a keyboard.
- Dictate the operationThe operative note is assembled from a vetted template: position, anaesthesia, incision, the steps in order, haemostasis, counts, closure, drains, post-op orders.
- Dictate the ward roundLands as structured SOAP against the right admission — subjective, objective, assessment, plan.
- Summarise the day's roundsEvery SOAP entry from today synthesised into a progress note, per patient.
- Nineteen document typesOPD and admission notes, SOAP, discharge summary, referral letter, prescription, operation and procedure notes, post-op orders, consent, patient advice, fitness and medical certificates, investigation requests, follow-up plans, handouts, billing documentation, progress and consult notes.
- Speak into any fieldThe microphone is on every free-text field in the app, not only the main dictation box.
- Type instead, if you preferThe same background preparation runs for doctors who write rather than speak. Nothing is gated behind a microphone.
- Rewrite any draftTell it what to change, or edit the text yourself. Nothing is final until you approve it.
- Default-complete, not blankTemplates arrive filled with what is canonically true for that operation. You subtract what did not happen instead of typing what did.
Decisions you accept, one tap at a time
SkyScribe proposes; a clinician decides. Nothing reaches the record without a person accepting it.
- Differential diagnosesRanked with reasoning. Tap the one you agree with and it becomes a coded entry on the problem list.
- InvestigationsTap to order. It reaches the laboratory or radiology queue by itself and the result comes back into the record.
- MedicationsTap to prescribe and the prescription is ready to print.
- Follow-upTap to schedule; it appears in your due queue on the day it matters.
- Ask a clinical questionAnswered against authoritative sources with the sources named, so you can check it rather than trust it.
- Discuss the caseA conversation about this patient, with the record already in context.
- Reasoning you can auditEvery recommendation carries what it was drawn from. Results persist, so they survive a reload.
Safety that is computed, not guessed
The parts that must never be wrong are tested code, not a language model.
- Clinical scores, calculated not estimatedTested code checked against published worked examples — never a language-model guess. Prefilled from the record where the values already exist, and covering what each specialty uses day to day.
- A contraindicated drug is refusedAllergy cross-reactivity, drug interactions and renal-dose limits are checked deterministically. Prescribing anyway requires an explicit, recorded override.
- A panic value finds youA critical result raises an alert even when the sending lab did not flag it. The thresholds are ours and deterministic.
- AI output is a draftApproval needs the permission for it and writes a physician-approval event to the record. There is no path where a machine signs anything.
- Reasoning runs de-identifiedClinical reasoning calls have identifiers stripped and restored around them.
Depth, past the specialty
A stroke neurologist and an epilepsy neurologist are both "neurology" to every other system. Not here.
- 31 specialties and superspecialtiesFrom general medicine to surgical gastroenterology, each with its own documentation surface.
- Subspecialty profiles underneathEach specialty carries profiles that change the sections, the examination, the recommended scores and the note itself.
- Structured examination templatesThe examination for that specialty, as fields — not a paragraph you retype.
- Diagnosis and procedure cataloguesPer specialty, so entry is a pick rather than free text, and the problem list stays coded.
- Guided operative and procedure notesVetted templates spanning open surgery, endoscopy and bedside procedures — each with the fields that procedure actually has, rather than a blank page.
- Consent off the same templateThe procedure you picked produces its own consent form.
- Chemotherapy by regimenPick FOLFOX or R-CHOP; the cycle prefills with the drugs and the orders it implies.
- Pre-op board that builds itselfConsent, fitness, investigations and clearances assemble from the record. You see what is missing, not a blank checklist.
The whole hospital, one system
Fourteen role-scoped staff workspaces. Each sees only its own queue; work routes itself and results flow back.
- Orders route themselvesInvestigations reach the lab, drugs reach pharmacy, admissions reach the ward — without anyone carrying paper.
- Queues update liveStaff screens push new work as it arrives rather than polling.
- Results flow backLab values and reports land on the patient timeline the moment they are entered.
- Photograph a reportStaff upload the printed report; the values are read out of it and stored as data, not an image.
- Nursing administrationDoses given, or held with a reason, charted back against the prescription.
- Refer inside the hospitalA consult reaches the other specialty's queue; their answer comes back to the referring doctor.
- Reception and walk-insAppointments, walk-in registration, and a collision-proof hospital number per patient.
- Admission, ward and dischargeBed board, progress notes, lab trends, and a discharge summary that synthesises the whole admission rather than the last visit.
- Modules are opt-inA clinic with no laboratory is not given a laboratory queue. Switch on what you run.
It talks to what you already own
Your engineers integrate against a documented surface, with credentials you issue yourself.
- HL7 v2 in and outADT and ORU accepted with proper acknowledgements; orders sent out to the LIS or RIS.
- MLLP listenerThe transport your existing interface engine already speaks.
- DICOM modality worklistThe scanner picks the patient off a list instead of a radiographer typing the name — so the study comes back matched to the order.
- FHIR R4Export any record as a Bundle, or let a machine read it by the MRN your own system issued.
- Self-serve credentialsRegister an interface, issue and rotate its secret, and read the message log yourself when something goes wrong.
- Never acknowledges unfiled dataA result for an unknown patient is refused, not quietly accepted — so nobody deletes a real result believing it landed.
The record, and the practice around it
What has to outlive every feature above.
- An append-only timelineThe clinical record is added to, never rewritten. There is no update or delete.
- A managed problem listActive and resolved, coded, carried across visits.
- Give the patient their recordA secure link to what was found, what to take and when to return.
- Printed on your letterheadEvery document carries the hospital's own identity, not ours.
- Sign it onceSave your signature; it goes on the documents you approve.
- Multi-clinic identityOne login for a doctor who works at more than one place, with the records kept strictly apart.
- Billing and insuranceAssemble the bill from what was captured; Indian insurers, TPAs and schemes with coverage split and claim lifecycle.
- Audited accessWho saw what, and when.
- Your data stays yoursBring your own storage bucket. Deletion is owner-only and deliberate — there are no cascades and nothing expires on its own.
Easier to watch than to read
One complicated surgical case travels through all of it — registration to discharge, with a panic lab value and a refused prescription on the way.