Faster integration
No months spent building and maintaining document processing.
Lab results, in the same shape as everything else
The ROOK Connect Lab Data API turns PDF and image lab reports into structured biomarkers with LOINC codes and FHIR R4 output, linked to each user's wearable data.
How it works
From a lab report to structured biomarkers in three steps
Users already have valuable information in their lab results, but it stays locked in PDFs, scans, and images. ROOK's Lab Data API turns it into structured data and combines it with continuous health data, so teams don't have to build their own pipeline.
Users upload a lab report
Users share their report within the app's existing workflow.
ROOK extracts the biomarkers
ROOK extracts the results and turns them into standardized biomarkers.
Your product uses the results
The data arrives ready for profiles, dashboards, analytics, or personalized experiences.
Benefits
Structured lab data adds value to every result
More personalization
Combines laboratory results with biomarker and wearable data.
Tracking over time
Isolated reports turned into a longitudinal biomarker history.
Focused teams
The roadmap stays on the user experience, not on formats and parsers.
Coverage
Biomarkers, formats and standards covered
Biomarkers
+45 biomarkers across five panels: Complete Blood Count (CBC), Comprehensive Metabolic Panel (CMP), Lipid Panel, Thyroid Panel, and HbA1c.
File formats
Digital PDF, scanned PDF, JPG, JPEG, and PNG. Users don't need to change how they receive their results.
Clinical standards
Biomarkers standardized with LOINC, with FHIR R4 output available.
Explore the technical docs →
ROOK structures and standardizes existing lab information. It does not diagnose conditions or prescribe treatments.
Use cases
Products teams build with Lab Data
Teams that treat a lab report as data, not as a document someone has to read.
01Personalized experiences
Biomarkers inside experiences that already use activity, sleep, or glucose data.
02Biomarker tracking
How results change over time, not just the latest report.
03Metabolic health
HbA1c, glucose, lipids, and other supported markers.
04Longevity & wellness
Bloodwork combined with lifestyle data.
05Health analytics & AI
Structured results sent straight to dashboards, analytics, and models.
06Research & real-world data
Lab observations alongside other longitudinal signals.
Lab data + continuous data
A lab result is a snapshot. Continuous data tells the story.
A lab test captures a single moment. Wearable and device data show what happened before and after. Lab Data connects with the rest of ROOK Connect through the same user identity.
One
user_idArticles on Lab Data API from the ROOK blog
- How are wearables and AI changing chronic disease management?How digital biomarkers from wearables, combined with AI, support continuous tracking, earlier care conversations and more personalized chronic disease programs.Read more
- How Does AI Turn Wearable Data into Evidence for Pharma?How AI cleans, standardizes and interprets noisy wearable data so pharma teams can use it in clinical trials, digital biomarkers and real-world evidence.Read more
- How can ACCESS programs make multiple health data sources useful?ACCESS programs can connect wearables, medical devices, lab results, and clinical data. Standardization, context, and interoperability are what make that data useful.Read more
Nothing matches that search.
Lab Data API
Users already have the lab data. ROOK makes it usable.
The tests have already been done. The Lab Data API turns them into a useful part of every digital product.
Read more in our technical documentationFAQ
Frequently asked questions about the Lab Data API
How lab reports become structured data, and where the limits are.
What is the ROOK Connect Lab Data API?
The Lab Data API converts laboratory documents into structured data. The application submits a file, ROOK extracts and normalizes the results, and then delivers them to the configured Data Webhook.
How does a user submit laboratory results?
The customer defines the upload experience within its own product. The file is submitted to the Lab Data endpoint and processed asynchronously. Once processing is complete, the structured result is delivered to the webhook.
Which file formats does the Lab Data API accept?
The Lab Data API accepts PDF documents and compatible images. Current file limits are listed in the technical documentation.
Read the Lab Data docsDoes it work with results from any laboratory, country, or language?
Coverage is not universal. Results depend on document legibility, structure, language, units, biomarkers, and overall quality. For new formats or markets, the ROOK team can validate representative samples.
How is lab information standardized?
ROOK extracts biomarkers and panels, normalizes names, units, and values, attempts to map biomarkers to LOINC codes when available, and performs consistency checks. Depending on the available configuration, the response may be delivered in ROOK JSON or FHIR R4.
How can I trust that the data is extracted correctly?
ROOK includes extraction, normalization, and validation steps, but no document processing is infallible. Products built on the Lab Data API should retain the original document, show data provenance, and define human review for critical, ambiguous, or low-confidence results.
How long does it take to process a result?
The Lab Data API works asynchronously, and processing time varies with the document and service load. The structured result is delivered to the Data Webhook as soon as processing finishes.
No questions match that yet. Try another word or topic.
Still have questions?Our team can review your sources and use case with you.
Schedule a demo