The runtime every connector reports to.
Core is the orchestration runtime: it receives events from every connected system, routes them through normalization and consent, and guarantees delivery to the destinations a network has contracted with.
- Typed, versioned event bus with replay for every lifecycle event
- Retry, backoff, and dead-letter handling per destination
- SLA tracking per route, visible to both sides of the exchange
- Immutable audit log: every transformation is reproducible
Wrap a legacy LIMS without touching it.
A connector is a bi-directional adapter around a system that was never designed to be integrated. It reads what the lab already produces and writes back in the shape the lab already expects, so the daily workflow at the bench does not change.
- HL7 v2.x, FHIR, DICOM, JDBC, CSV over SFTP, and screen-level fallbacks
- Deployed alongside the LIMS or hosted, depending on the network
- Schema drift detection with alerts before a feed silently breaks
- New connector for an unlisted system typically ships in two weeks
Find, contract, and book across the network.
The discovery layer turns the contracting graph into an API. A payer or aggregator can see which centers run a test, at what price, with what turnaround, and can contract and book without a phone call.
- Searchable catalog of tests, panels, and capacity across partner centers
- Rate cards and turnaround commitments held per contract
- Real-time slot availability and appointment booking
- Contracting reduced from roughly 30 days to 2
One patient record across many labs.
The same patient shows up at three centers under three identifiers. Healjour stitches those records into a consented longitudinal history, so results can be read in sequence rather than as isolated PDFs.
- Deterministic and probabilistic identity matching with review queues
- Consent receipt attached to every record access
- Trend views across time, lab, and analyte
- Export as FHIR bundles for downstream analytics