Connections
Connects to what you already run.
HL7 from laboratories, FHIR from EHRs, TEFCA across networks, Direct where nothing else exists.
Every kind of connection
| 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. |
Four gates
Signed scope, synthetic test messages, a parallel period, then production with monitored volumes.
Silence is caught
Volume baselines per source and message type, so an interface that quietly stops is noticed the same day.
One patient, four identifiers
Deterministic matching first. Anything ambiguous waits for a human, because a false link is a disclosure to the wrong person.
Bring the thing that breaks today.
Thirty minutes. Your laboratories, your practices, and the one stakeholder you cannot easily give data to.
Book a 30-minute call service@meta.clinic