Healthcare data API·Private beta
rail.to/

Complete health record.
Just one API call.

Patient consents once. We reconcile every source into a single FHIR record — and keep the receipts on every fact.

Sourced, merged,
signed.

Rail Connect handles consent: one sign-in to the provider, payer, or wearable and a single call to our API.

What comes back is FHIR R4, deduplicated, reconciled, and with every fact carrying its source.

Disparate data sources totally normalized into FHIR R4
Customizable Rail Connect component (React + vanilla)
Deduplication and provenance built in
HIPAA · SOC 2 Type II · audit-logged
app.tstypescript
// Patient authorizes via drop-in UI component.
const link = RailConnect.create({
  onSuccess: (token) => sendToBackend(token),
  scopes: ['claims', 'clinical', 'medications', 'labs'],
});

// Fetch the complete longitudinal record.
const record = await health.patients.get(token);
recordFHIR R4 · 200 OK · 184ms
.conditionsCondition[]merged · 7 sources
.medicationsMedicationRequest[]active + historical
.labsObservation[]with reference ranges
.claimsExplanationOfBenefit[]across every payer
.encountersEncounter[]full timeline

Data reconciliation engine

Messy in.
Clinical out.

Clinical data can be oddly un-clinical. Insurance claims speak ICD-10. Labs send loose text and numbers. Notes are freeform prose in idiosyncratic shorthand.

Rail reconciles them, pulling clinical concepts out of the text, coding every fact to SNOMED, LOINC, and RxNorm, collapsing the duplicates and flagging any inconsistencies. The original source stays attached to each element.

17 1 address for every patient's complete health record.

Request access