Mike brought the clinical expertise.The 1health platform broughteverything else.
A physician with a proven clinical model should not have to become a software company in order to use it. That is the part the 1health platform solved.
The hard thing about ExpertDx was never the diagnosis. It was everything wrapped around it. A HIPAA-compliant way to move a case between two organizations that have no relationship. Identity and consent. Licensure routing. An audit trail a hospital compliance office will accept. Billing. A corporate structure that survives a regulatory read. Every one of those is a year of work and a budget, and none of them is medicine.
The 1health platform had already built that layer and was already running real clinical traffic on it. So ExpertDx did not start from an empty repository. It started from working infrastructure, and the only new work was the part that is specific to expert diagnostic consultation.
The platform side of this build, including the specific services and protocols each piece runs on, is written up in 1health case studies.
What this normally costs
- About 12 months from decision to a product a physician can actually use.
- $500,000 to $1,000,000 is the going quote for a HIPAA-compliant clinical application built from scratch.
- A CTO, an engineering team, a compliance consultant, and a security review before a single case moves.
- A funding round raised to pay for the build, before there is any evidence anyone wants it.
What actually happened
- Live in one month, on rails that were already carrying clinical traffic.
- A fraction of the cost, because the expensive layer already existed and did not have to be rebuilt.
- No engineering team to hire. The 1health platform team built it.
- Real cases moving before the raise, which changed what the raise was for.
What the 1health platform provided
ExpertDx was the first venture built this way, so the team went all in on everything. In practice it is two layers. One is the platform. The other is the company building work around it.
Standard with every build. This is what running on the 1health platform means.
HIPAA-compliant healthcare rails
The infrastructure that moves a case between organizations, with identity, consent, encryption, and an audit trail already in place and already in production.
Product and engineering
The case workflow, the AI drafting step, the expert review and signing interface, and the delivery back to the ordering physician, all designed and built on the 1health platform.
Ongoing platform operations
Security, uptime, compliance, and support, run by the platform rather than by a clinical team that should be reading cases.
ExpertDx took all of it. The next expert takes what they need. Some want the full build the way Mike did. Some bring their own people and just want the rails.
Regulatory and corporate architecture
Corporate form, state licensure routing, the consultation posture, and the clinical risk structure, worked out before the first case rather than after the first problem.
Business model and economics
Pricing, unit economics, the expert payout structure, and the operating model that has to hold as case volume grows.
Go to market
Positioning, the physician outreach program, the site you are reading, and the commercial motion behind it.
Dr. Laposata did not hire a CTO, spend a year in specification meetings, or raise money to fund a build. He kept doing the thing only he can do, which is read a hard case and sign the answer. The 1health platform did the rest.
Have a model that works and no way to ship it?
If you are an expert with a proven clinical model and no interest in becoming a software company, this is the path Mike took. We can walk you through it.
The 1health platform is built and operated by Tachin.ai.