Omari HealthAbout
The records exist.Someone has to go get them.
Omari is the automation layer for the people who coordinate specialty care.
Why
Why we’re building this
A patient waits months for a first visit with a surgeon. They drive in, sit down, and the surgeon can’t make a decision, because the nerve study, the MRI report or the outside notes never arrived. The visit turns into a conversation about what’s missing, and the patient goes home to wait again.
Behind that visit is a coordinator who spent the morning combing a 150-page referral, calling the patient, and faxing a records request to a clinic that will answer in a week. We spent hundreds of hours shadowing surgeons and coordinators and interviewed about thirty coordinators, nurses, clinic managers and surgeons at academic medical centers in North Carolina and Georgia. Nobody had a written list of what each surgeon needs before a first visit. Everyone carried it in their head, learned over years, one incomplete visit at a time.
The software built for this problem stops short. Scheduling tools book the slot. Chart search finds what’s already in the record. Nothing goes and gets what isn’t there. That’s the work, and that’s what Omari does.
Principles
What we believe
Finding is solved. Getting is the gap.
Health systems can already search a chart. The hours go to retrieving what the chart doesn’t have: records at another practice, imaging on a disc, answers only the patient knows. That’s where we work.
The checklist should be written down.
Each surgeon’s requirements live in the clinic’s own history. Omari learns them from past visits, shows the cases behind each rule, and the surgeon approves, edits or rejects. The rules are the clinic’s, not ours.
Coordinators stay in control.
Every records request, patient message and call waits in the coordinator’s queue until they approve it. Omari proposes; your team decides.
Evidence on everything.
Every fact Omari states points to the page it came from. If a referral doesn’t mention a prior surgery, that’s unknown, not no. Omari asks.
Patients shouldn’t be the courier.
No one should have to drive a CD across town or repeat their history for the third time because a fax didn’t arrive.
Team
Who we are
Three founders, friends since elementary school, who have built clinical machine learning projects together for years.
Shivank Kancharla CEO
Clinical side and customer work. Hundreds of hours shadowing surgeons; nerve regeneration research; EHR charting on a hospital floor.
Rohan Nair Co-CTO
Healthcare data and product engineering. Previously worked on patient payments and clinical data flow at a healthcare payments company.
Adesh Srivastava Co-CTO
Data infrastructure and security. Previously built data-protection and large-scale data pipeline systems in industry and open source.
Now
Where we are
We’re building the first version of Omari now, with coordinators and clinic managers as design partners. If you run or coordinate a specialty clinic and recognize the problem above, we’d like to hear how it looks where you are.
Data
How we handle data
Omari is built for HIPAA from the first line of code. No patient data touches our systems until a Business Associate Agreement is in place; until then we build and test on synthetic and sandbox data. Every action is logged, every fact is traceable to its source, and nothing is sent to a patient or an outside clinic without a coordinator’s approval.
Contact