OCR Blood Result Upload

OCR blood result upload lets you submit existing blood result documents, such as lab PDFs, scans, screenshots, or photos of printed reports, through Blood Result Upload. InsideTracker processes those files asynchronously and converts extracted biomarker values into structured data that can support downstream outputs.

Use the Blood Result Upload guide for the file upload, process submission, status, and webhook mechanics. Use this page for OCR-specific input expectations and User-experience guidance.

Accept documents

Let Users provide existing blood result PDFs or images.

Process by OCR

InsideTracker extracts biomarker data from the submitted documents.

Update status

Use BRU status or terminal webhook events to update the User's experience.

Where This Fits

Use OCR when a User has existing blood result documents and your integration wants InsideTracker to extract the biomarker values from those documents.

You already have	You do here	This helps support
A customer-level token, a document upload experience, and one or more supported blood result files	Submit the files through BRU and present clear processing status to the User	Structured biomarker data that can feed recommendations, scores, Inner Age, and other biomarker-based outputs

Supported Files

OCR accepts PDF and image documents through BRU.

Rule	Value
Supported MIME types	`application/pdf`, `image/jpeg`, `image/png`
Maximum file size	Smaller than 50 MB
Upload style	Upload each file separately
Rate limit	14 files per customer per 300 seconds
File retention before process submission	Uploaded files expire after 24 hours if they are not submitted in a BRU process

Give Users guidance before upload. Clear, complete, readable documents are more likely to process successfully than blurry, cropped, or partial images.

OCR Processing Flow

The User selects one or more blood result documents.
Your application uploads each file separately through BRU.
Your application submits a BRU process with the returned uploadedFileIds.
InsideTracker processes the documents asynchronously.
Your application uses POST /webhooks/bru-terminal or GET /bru/customer/v1/processes/{processId} to track completion.
When the process reaches PUBLISHED, published blood result identifiers are available in the process status or webhook payload.

User Experience Guidance

Set clear expectations that OCR processing is not instant and may require review if the document is unclear, incomplete, or cannot be interpreted.

Recommended states:

State	Meaning
Not started	User has not uploaded documents.
Uploading	One or more files are being submitted.
Processing	Files were accepted and are being converted into structured data.
Results available	OCR processing published blood results successfully.
Action needed	Upload failed, the file was unreadable, or no published result was produced.

Avoid telling Users that OCR extraction is guaranteed. A better framing is that InsideTracker is processing the document and converting it into structured health data when possible.

Handling Completion

Treat PUBLISHED as the success path. The BRU process status response or terminal webhook payload may include bloodResults with published blood result legacy IDs.

If a process reaches COMPLETE without published results, do not show new blood result data to the User. Route the submission through your support or exception-handling workflow.

Testing Checklist

Upload succeeds for a PDF lab report.
Upload succeeds for a JPEG document.
Upload succeeds for a PNG document.
Multiple files can be submitted through one BRU process, with each file uploaded separately.
Oversized or unsupported files produce a clear User-facing error.
Completion status updates the correct User.
Duplicate or repeated uploads do not create confusing User-facing results.
Support can trace a User issue back to the uploaded file and BRU processId.