Intake · care · claims
Less time on forms,more time with patients.
Registration, scheduling, documentation, claims and stock run by systems that read the record and write back to it, with consent recorded and every clinical decision left to the clinician.
The record should follow the patient, not the paperwork.
THE PROBLEM
A patient fills in a form that is typed into the hospital system. The front desk spends the morning on the phone booking and rebooking. Clinicians write notes after hours. A claim is a folder of documents assembled by hand, keyed into an insurer's portal and chased for weeks. Protocols live in PDFs nobody can find at two in the morning, and a consumable runs out at the bedside because the count was on paper.
HOW SOLONOMOUS DOES IT
We automate the administration around care and leave care alone. Forms and identity documents are read into the record. An assistant books, reschedules and reminds by phone and message. With consent, a consultation is transcribed into a draft note in the clinician's own template, which the clinician reviews and signs. Claims are assembled from the record, submitted and tracked. Protocol questions are answered from your own documents with the source attached. Consumption posts from the record so stock reorders itself.
WHAT YOU GET
The front desk answers fewer calls and makes fewer errors. Notes are finished in the room, not at home. Claims go out complete and come back faster, and a rejection arrives with its reason. Every automated action is logged against the record, and nothing leaves your region.
Workflows
What we automate here.
7 workflows
- 01
Patient intake and registration
TODAY
Patients fill in paper forms and hand over identity and insurance documents. The desk types the forms in, photocopies the documents and creates a duplicate record when the name is spelt differently.
AUTOMATED
Forms, identity and insurance documents are read into the record, matched against existing patients and flagged where a duplicate is likely. The desk confirms, and the patient is registered once.
- 02
Scheduling and reminders
TODAY
Appointments are booked by phone during working hours. Rescheduling means another call, and missed appointments are discovered when the patient does not arrive.
AUTOMATED
An assistant books, reschedules and confirms by phone, message and web against each clinician's rules, and reminds patients before the day. Anything unusual is handed to the desk with the conversation attached.
Done with
- 03
Clinical documentation support
TODAY
Clinicians write consultation notes after the clinic closes, from memory and shorthand. Discharge summaries and referral letters are typed from the same notes a second time.
AUTOMATED
With the patient's consent, the consultation is transcribed and drafted into the clinician's own note template, with a discharge summary or referral letter drafted from it. The clinician edits and signs; nothing enters the record unsigned.
- 04
Claims and pre-authorisation
TODAY
Staff assemble a claim from the record, print or scan the supporting documents, key the claim into the insurer's or TPA's portal and chase it by phone.
AUTOMATED
The claim pack is assembled from the record and the tariff, submitted through the portal, and tracked. A query or rejection is routed to the billing desk with the insurer's reason and the documents it refers to.
- 05
Protocol and policy questions
TODAY
Clinical protocols, formularies and hospital policies are PDFs on a shared drive. A nurse on the night shift asks a senior or guesses.
AUTOMATED
An assistant answers from your own protocols and policies, with the source paragraph attached, on the ward and on a phone. It does not answer from anything outside your documents.
Done with
- 06
Pharmacy and consumables stock
TODAY
Ward stock is counted on paper and reordered when someone notices it is low. Expiries are found on the shelf.
AUTOMATED
Consumption posts from the record as items are used, stock is reordered at the threshold you set, and items nearing expiry are listed before they do. Purchase orders wait for approval where the value requires it.
- 07
Rostering and payroll
TODAY
Rosters are built in spreadsheets, leave is approved by email, and payroll inputs are collected from all of it at the end of the month.
AUTOMATED
Rosters, attendance and leave live on one employee record, and the payroll run reads them without re-entry. Statutory filings are prepared from the same record.
Engagement
How it starts in a hospital or clinic
We begin with the administration around care, and with your privacy officer in the room.
- 01
Map the patient's path
We follow a patient from the first call to the settled claim and list every form, call and re-keying, with the staff who do them.
- 02
Agree the boundaries
With your clinical and privacy leads we set what the systems may do, what needs a signature, where consent is taken and where the data lives.
- 03
Run one department in shadow
The automation runs beside one desk or one ward for an agreed period. Outputs are reviewed against what staff did, and the rules are tuned.
- 04
Hand over, or keep running
Your IT and operations teams take it on with the runbooks and code, or we run it inside your region under your keys and your access rules.
Details
On the spec sheet.
- Systems integrated
- Hospital and practice management systems, electronic medical records, laboratory and radiology systems, insurer and TPA portals, pharmacy stock systems, telephony and messaging
- Data handled
- Registration forms, identity and insurance documents, appointments, consultation audio and notes, claims, protocols, stock movements, rosters
- Compliance considerations
- HIPAA where patients in the United States are involved, India's DPDP Act and ABDM guidance where they apply, consent recorded before any recording, protected health information kept in your region, every access logged
- Clinical boundary
- No diagnosis, prescribing or triage decision is made by a system; drafts are signed by a clinician before they enter the record
- Deployment
- In your cloud region or on-premise; models can run inside your network so records never leave it; run by us under your keys where you prefer
- Languages
- Scheduling assistants and transcription in the languages your patients and clinicians speak; notes in the language of the record
- Hand-over
- Runbooks, source code, integrations and model weights, with your IT team trained to operate and retrain them
Proof
Case studies
Questions
Asked before we start.
Does patient data leave our hospital?
Only if you choose that. The whole stack, including the language and speech models, can run inside your own network or your own cloud region. Where we operate it, it runs under your keys and your access rules, and every access is logged.
Is a recording of a consultation always made?
No. Transcription runs only where the patient has consented and the consent is recorded against the visit. A clinician can switch it off for any consultation, and the audio is retained only as long as your policy says.
Can the system make clinical decisions?
No. It drafts notes, letters and claims and answers from your own protocols with the source shown. Diagnosis, prescribing and triage stay with the clinician, and nothing enters the record without a signature.
How are claim rejections handled?
A rejection or query comes back to the billing desk with the insurer's reason and the documents it refers to. Where the fix is a missing document, the pack is completed and resubmitted; where it needs judgement, a person decides.
We use a hospital information system from another vendor. Does that matter?
Most systems expose an interface, and we connect to it. Where one does not, a bot works through its screens under a staff account until an interface is available, with every action logged.
Start
Tell us what your teamstill does by hand.
We map the workflow with you and say plainly what can run on its own, what should not, and what it takes.