Diagnostic data infrastructure
A result is data.
Access is metadata.
Metaclinic automates the management 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. Nine classes of data by nine parties is 81 separate questions, and the answers are the product — each one decided in advance, on a stated legal basis, enforced in the database rather than in a policy document, and recorded the moment it happens.
| stakeholder → data class ↓ | Patient | Ordering clinician | Consulting specialist | Referring practice | Billing and coding | Attorney of record | Payer and UM | Public health | Research sponsor |
|---|---|---|---|---|---|---|---|---|---|
| Requisition | |||||||||
| Discrete results | |||||||||
| Narrative report | |||||||||
| Images and slides | |||||||||
| Molecular and genomic | |||||||||
| Part 2 substance use | |||||||||
| State-protected | |||||||||
| Charge and lien ledger | |||||||||
| Raw interface message |
Toxicology and treatment-linked results that originated in a federally assisted substance use disorder program, which carry consent obligations that survive every downstream hop.
Part 2 requires patient consent specific to the recipient
How it happensA general medical authorization is not sufficient and will not release it.
This stakeholderNothing moves without a signed authorization naming the categories. Treatment relationship does not create attorney access.
A laboratory result is finished. Its job is not.
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.
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.
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.
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.
One result, released nine ways
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.
Adding one stakeholder adds nine decisions
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.
Every source is a relationship with a spec
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. |
Multi-tenant, and the interesting part is the doors
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.
The patient is not a stakeholder to be managed
A laboratory subject to CLIA has been required to give a patient copies of their completed test reports since 2014, and the HIPAA exception that used to shield laboratories is gone. The engineering question is no longer whether to release. It is how to release something a person can actually use.
Results go to the patient when they are final and identity is verified, with no waiting period built in to give a clinician time to call first. A plain-language summary sits above the report and never replaces it. Reference intervals and flags travel with every value, sourced from the performing laboratory. Corrections are surfaced as corrections with the prior value visible. And the ordering clinician is notified the moment a critical or malignant result is released, so the call happens fast — which is the real answer to the hard case, not a delay.
One record, and nobody wants the same thing from it
Results that land, and proof they did
Outreach practices get their own tenant instead of a shared inbox. Patient requests stop being a project. Send-outs reconcile home. Denials get an evidence trail.
For laboratories Practices and MSOsOne place the diagnostic picture is complete
Results from every laboratory in one worklist, with outstanding orders, unacknowledged criticals, pending send-outs, and unmatched results as visible conditions.
For practices and MSOs Attorneys of recordRecords that arrive complete and dated
Authorization parsed into categories, production run against that scope, and anything outside it withheld and reported by name rather than discovered at deposition.
For attorneys of recordWhat we are, legally, and what follows from it
Metaclinic is a business associate of the laboratories and practices it serves. It is also very likely a health information network under the information blocking rules, because it administers agreements enabling electronic health information to move among more than two unaffiliated organizations. That makes the obligation ours directly, not one inherited from a customer.
Which is why the defaults on this site are written as exceptions
Where a request is not fulfilled, the reason is recorded against a named exception — preventing harm, privacy, security, infeasibility, health IT performance, content and manner, fees, licensing, or the exchange framework. A refusal without a recorded exception is a violation with extra steps.
Which stakeholder is currently asking you for data you cannot easily give them?
That is the useful first conversation, and it is a short one. Bring the laboratories, the practices, and the thing that breaks today.
service@meta.clinic Read the release model first