About ITAS
Independent primary care is worth keeping.
Small practices are being bought, absorbed, and closed — not because the medicine is worse, but because the economics stopped working. We think the money to fix that is already on the table, and what's missing is the machinery to collect it.

What a practice keeps when it works with us
Why this exists
The work is already happening. The payment isn't.
Between visits, a primary care team is already fielding calls, adjusting medications, chasing specialists, and worrying about the patients most likely to end up in an emergency department. Medicare pays for that work through two standing programs.
Almost no independent practice runs them. Not because the rules are secret — they are published — but because collecting on them requires an operational discipline that costs more than a two-provider practice can hire for. Someone has to enrol patients, document consent in a specific way, count transmission days, log clinical minutes, place a live call every month, and hold back any month that doesn't qualify.
Miss one of those and you have not just lost the revenue. You have created an audit exposure. That asymmetry is why the programs stay unclaimed, and it is exactly the kind of problem software is good at.
We run the operational machinery for the care a practice is already delivering, so a small clinic can be paid like a large one without becoming one.
The alternative on offer to most practices is to sell — to a hospital system, a payer-owned group, or a private equity roll-up — and accept that someone else will decide how much time a patient gets. We would rather make the independent version profitable.
That is a narrower ambition than most health-tech companies advertise, and we think that is the point. This is infrastructure work: unglamorous, rule-bound, and valuable precisely because nobody wants to do it carefully.
How we operate
Four constraints we designed the company around.
Each of these costs us money or growth. They are here because the alternative creates risk that lands on the practice rather than on us.
We employ no clinicians
Your staff furnishes the care under your supervision, billed under your NPI. We are a software vendor, not a staffing agency wearing one — which is also why proposed federal rules on who may furnish monitoring don't unsettle the arrangement.
We never touch the claim
We prepare, you submit. We do not bill Medicare, do not take reassignment of benefits, and never sit between a practice and its money.
We hold the claim rather than file it
A month that misses a requirement does not become a claim, even when a practice would rather send it anyway. Filing optimistically is how ordinary exposure turns into a repayment demand two years later.
AI drafts; a human signs
The engine reads, ranks, and drafts. It cannot sign an order or a note, change a plan, enrol a patient, or send a claim. That line is enforced in code rather than promised in a policy document.
The reasoning behind each, with citations, is on the compliance page.
Who builds it
A small team, deliberately.
Three founders. Two who have spent their careers making regulated systems behave, and one who practises the medicine we are writing software for.
Sid Chauhan
Cofounder
Twelve years building systems where failure has consequences, at Cisco, Samsara, and AWS. Georgia Tech. He owns how the platform behaves under audit, and he is the person you will talk to first.
sid@itas.healthOur engineering cofounder
Cofounder
Built the clinical engine here, including the parts that stop it from acting on its own. Comes from shipping AI inside primary care, not from wrapping a model in a dashboard.
Introduced by name on a call, at his discretion.
Our physician cofounder
Cofounder, practising primary care
A practising primary care physician in Honolulu, and the reason this product resembles a clinic rather than a dashboard. He signs the orders, takes the calls, and tells us when a workflow we are proud of would waste his afternoon.
Introduced by name on a call, at his discretion.
Software for a clinic that has never been used in one is a guess with a login screen.
Where we are
Early, and specific about it.
We are building this inside a working primary care practice rather than in front of a whiteboard, and we are talking to independent practices about being among the first outside it.
What that means concretely: the platform runs today on synthetic records with its compliance controls enabled, our physician cofounder's practice is the proving ground, and no real patient data has entered the system. When it does, it will be under a signed business associate agreement, in a configuration reviewed with the practice first.
We say that here because you will find it out anyway, and because a vendor that oversells its stage at the first meeting will oversell everything after it. Our security page lists what is built, what is committed, and what we simply don't have.
Working between California and Honolulu, founded in 2026.
Come argue with our numbers
Bring your panel and your scepticism. Thirty minutes tells you whether these programs are worth anything on your patients, and we would rather hear a fast no than manage a slow maybe.
No EHR change. No commitment.