Diagnostic data infrastructure

A result is data.
Access is metadata.

Metaclinic automates the administrative decision and reports on the clinical outcome. One signed report, and nine parties with a claim on part of it: the ordering clinician, the referring practice, the consulting specialist, the coder, the payer, counsel, the registry, the research sponsor, and the patient.

Every result, to everyone entitled to it — decided in advance, on a stated legal basis, and recorded the moment it happens.

A single beam of white light entering one face of a milled steel block and leaving the other separated into many distinct ribbons of blue, each a different width, fanning apart and running off the frame. — One result in. Every release out, already scoped to whoever is entitled to it.

23 released by default 39 conditional on something specific 19 withheld, with the reason stated all 81 decisions →

A laboratory result is finished. Its job is not.

the premise

The test was performed correctly and the report is right. Everything after that is a delivery problem, a scoping problem, and an evidence problem — handled by whatever happens to sit in the seam between the laboratory information system, the practice's EHR, the billing vendor, and a fax machine. Almost every expensive failure in diagnostics happens in that second half, and it is nobody's product.

Failure one

The result is a document

Filed as a PDF, it cannot be trended, thresholded, coded from reliably, or split so one party sees part of it and another does not. That choice is made at intake and everything downstream inherits it.

Failure two

Access is a role, not a relationship

Give a consulting specialist a role and they keep it after the consult, across every patient in the tenant. The relationship was one case for three weeks. The permission should have been too.

Failure three

The patient is treated as a request queue

Direct patient access has been required of laboratories since 2014 and delay without a defined exception has been information blocking since 2021. Most systems still model it as a favor with a turnaround time.

A broad sheet of cool blue light meeting one face of a milled aluminium plate and emerging from the other as a single narrow ribbon with hard edges. — The same light on both sides. The geometry decides how much of it leaves.

One result, released nine ways

the shape of the thing

The same issued report becomes nine different disclosures, because nine parties are entitled to different parts of it on different authority. That is not a workflow with nine steps. It is one object, scoped nine ways, at the moment it is asked for.

Scoped per class, per stakeholder, and per state. Every number here is read from the release matrix: each slot opens in proportion to what that stakeholder receives by default, line weight carries the same count, and a dashed line means nothing is released until a condition is met.

Adding one stakeholder adds nine decisions

the network effect, stated honestly

This is the part that compounds. A tenth stakeholder does not add one relationship to the model, it adds nine — one per class of data, each needing an answer that is defensible on its own. That is why the rules are written down and generated from one file rather than decided per integration, and it is why the answer to “can they see it” is never a shrug.

23 connections released by default, 39 conditional on something specific. The 19 withheld are the lines that are not drawn.

Every source is a relationship with a spec

hl7 v2 · fhir r4 · tefca

Diagnostic data crosses organizations that share no identity system, no code set, and no incentive to make it easy. The integration surface is a graph, and the posture toward each edge is different.

Connection	Direction	How	What to know
Laboratory information systems	Source	HL7 v2.5.1 ORU^R01 over TLS or SFTP, plus a FHIR R4 read where the LIS supports it. Orders return as ORM or OML.	GPS LIS is a first-class source. Every other LIS is treated as a stranger with a spec, which is the correct posture.
Electronic health records	Source and destination	SMART on FHIR app launch for in-workflow access, US Core profiles for read, and Bulk FHIR export for panel-level pulls.	Certified EHRs must expose a standards-based API. When one does not, that is a finding, not an integration problem.
Reference and send-out laboratories	Source	Result-only interfaces reconciled back to the originating accession, so a send-out returns to the case it left.	The failure mode is an orphaned molecular result nobody bills and nobody reads. Reconciliation is the whole job.
National networks	Source and destination	Query and retrieve through a designated QHIN under TEFCA, including individual access services for patient-initiated requests.	Useful for prior results and outside history. Not a substitute for a direct interface where volume is predictable.
Health data aggregators	Source	Normalized clinical and lab feeds from a network aggregator, used to fill in outside results in weeks rather than quarters.	Fastest path to coverage, thinnest control over data quality. Use it to start, replace it where the volume justifies a direct build.
Direct secure messaging	Destination	Direct addresses for practices with no interface and no API, because a surprising number of destinations are still an inbox.	Lowest common denominator, and the one that keeps a rollout on schedule.
Patient endpoints	Destination	Portal, patient-facing FHIR API with a registered third-party app, and a full electronic export on request.	Patient-directed transmission to a third party is a distinct path with its own record, not a shortcut around authorization.
Payers and clearinghouses	Destination	Claims and attachments out, remittance and adjudication back, reconciled against the charge that produced them.	This is where Metaclinic already lives. Diagnostic data access makes the claim defensible instead of merely submitted.

How a connection goes live

Multi-tenant, and the interesting part is the doors

org · suborg · role · grant

Multi-tenant usually means isolation: every customer in a sealed box. Diagnostic data does not work that way. A laboratory reports to a practice, the practice consults a specialist at another organization, a delegated biller codes the case, a firm holds a lien, and the patient stands outside all of them holding a legal right to the whole thing.

So the model has four layers — organization, sub-organization, role, and grant — and only the last one crosses a boundary. A grant is an edge attached to a case or a matter with an expiry on it. There is no standing permission to look at another tenant's data, enforcement has a floor in the database rather than only in application code, and support access is a break-glass event that notifies the affected tenant when it happens.

one specimen, nine release events