For health tech
Medical record retrieval as an API
The patient signs once. Imaging, pathology slides and charts are requested from each provider they have seen; a webhook fires on every status change.
- provider requests
- 100,000+
- provider organizations in Tavrn’s directory
- 425,000
- follow-up with each open provider
- Every 48 hours
The outside chart
What comes back from every provider
Tavrn requests each record type from the provider that holds it, whether or not that provider is on a network.
Network connectors return what a site publishes: C-CDA, FHIR, some PDFs. They rarely carry DICOM and do not carry slides, infusion flowsheets or bills.
Clinical and consult notes
DICOM images with the report
Pathology reports, slides and blocks
Labs from every lab and hospital
Infusion and medication records
Operative notes
Itemized bills
Scanned and legacy charts
Request lifecycle
One request per provider, status by webhook
Create a request per provider under the patient’s case, by API or spreadsheet, with the signed authorization attached. One authorization covers every US provider the patient has seen.
One request per provider
Each request carries its own status, contact dates and any provider fee, passed through at cost under the approval threshold you set.
Networks, then direct
Networks, records vendors and portals return about 63% of a patient’s visits; Tavrn requests the rest from each provider by fax, mail, email and phone.
Follow-up until answered
Every open provider is contacted every 48 hours until it answers. A webhook fires on every status change, or poll the request.
Delivery as providers respond
Records arrive as each provider responds. Download them with the same key, or take delivery by SFTP or in the Tavrn app.
POST /v2/cases/{case_id}/retrieval-requests
{
"patient": {
"name": "Nora Bellamy"
},
"facility": {
"name": "Cedars-Sinai"
},
"requested_records": [
{
"type": "medical_records"
},
{
"type": "billings"
}
],
"auth_form": {
"upload_id": "upl_8f2…"
}
}One request on the patient’s authorization, every provider they have seen.
Trials and RWD
Research on the patient’s authorization
Eligibility and long-term follow-up turn on outside documents: prior regimens and stop dates, pathology and biomarkers, baseline scans.
- Authorization
- Research is not a named network purpose, so your requests run on the patient’s HIPAA research authorization, valid to the study’s end.
- Cohort orders
- One request per cohort, one row per patient per provider.
- Source documents
- Each record is the provider’s own chart, delivered as the provider produced it.
FAQ
Questions before you integrate
What a request returns, who may receive it, what it costs, and how it reaches your product.
SOC 2 Type 1 and Type 2 reports, a HIPAA attestation, and Tavrn’s security policies are on the trust center, shared once a request is approved. More on the security page.