We build the layer nobody photographs

Metaclinic started as billing infrastructure for practices whose receivables nobody else wanted to touch. Doing that work for years taught the thing this company is now built around: almost every failure downstream of a diagnostic test is a failure to move the result correctly to the people entitled to it.

So the product is not a portal and it is not a billing system, though it contains both. It is a release model with an implementation: nine classes of diagnostic data, nine kinds of stakeholder, and an explicit answer for every pair, enforced at the database and recorded in an audit trail a patient can read.

What Metaclinic actually is

We automate the management decision and report on the clinical outcome.

Everything else is how that gets done. A diagnostic case is a chain of management decisions before it is anything else: where the specimen goes, which bench runs it, who is entitled to the result, what is billed, and what should happen next. Those decisions are mostly made today by people reading documents and asking each other questions. We make them in software, and then report on what followed clinically.

The four things this company does are that one sentence at different depths. The laboratory information system is where the decisions are made — built for anatomic gastrointestinal pathology, extended outward from there, and carrying the logistics, reporting, and billing for more than fifty laboratories. The release model is how the result then reaches everyone entitled to it without handing anyone everything. The marketplace is how a practice reaches an esoteric assay that no single laboratory runs economically on its own. The development work is how a laboratory gets the part that is specific to it rather than the part everyone shares.

Which is why the release model on the rest of this site is not a diagram of something we would like to build one day. It is the layer a working book of laboratory data already moves through, and it is written down rather than improvised per customer because a management decision that cannot be explained afterwards is not automation, it is just speed.

Software people and doctors, in the same room

Metaclinic was built by software developers and physicians who went into business together. That is an ordinary sentence to write and an unusual company to run. The developers had shipped systems that had to be correct; the doctors knew which of those systems were lying to them. Going into the laboratory space is the decision that made the pairing matter, because a laboratory is where the two trades stop being able to avoid each other.

The work started as custom laboratory information systems, built one at a time for laboratories whose requirements did not fit anything sold off the shelf. Each build was specific to its laboratory. What they had in common was the infrastructure underneath, which we own, and which connected them to each other and to everyone downstream of them. That is the thing that turned a set of separate builds into a network rather than a portfolio.

The part nobody planned for was the metadata. Because each laboratory was reached through an interface rather than a file drop, the infrastructure could see the shape of the work: what was ordered and by whom, what came back and how quickly, what was billed, what was denied, and what was still sitting somewhere with nobody accountable for it. That turned out to be essential to every part of a laboratory business rather than only the clinical part, and it is the same material the release model on this site is made of.

It is also why this layer is a reasonable foundation for models. A model is only as good as the structure of what it is handed, and years of interfaced diagnostic data with the decisions still attached is a better starting point than the same years of PDFs. Laboratories and models end up wanting the same thing for the same reason: the data has to mean something before either of them touches it.

Inside Deploy Holdings

Metaclinic is part of Deploy Holdings, a New Orleans healthcare infrastructure company. The laboratory information system above reports roughly 250,000 cases a year across deployed laboratories. The portfolio also includes remote monitoring, teleneurology, and a set of clinical measurement tools. The thesis across all of it is that perception is the missing layer in medical technology: the instruments exist, and what is missing is the infrastructure that carries what they see to the person who needs it.

How we work

• Deny by default, and make the refusal legible.
• Say what we will not do on the same page where we say what we will.
• Retain everything and overwrite nothing, because disputes are about what was known when.
• Treat the patient's right of access as an obligation with a clock, not a feature with a roadmap.

Talk to us

The useful first conversation is short and specific: which laboratories, which practices, which stakeholders are currently asking for data you cannot easily give them, and what breaks today.