ROOK's EHR/EMR API delivers each user's health data as FHIR R4, with LOINC codes and UCUM units, ready to integrate into clinical systems.
How it works
Clinical systems record what happens during a visit. ROOK adds what happens between visits: continuous activity, sleep, and vital sign data, delivered in the format those systems already understand.
Users connect their wearables and health apps through ROOK Connect.
With every new or updated summary, ROOK turns the available metrics into standardized clinical observations.
The FHIR document reaches the backend through the same Data Webhook the integration already uses, ready to be sent to the clinical system.
Continuous data, in clinical language
Every metric with an available LOINC code is delivered as an individual FHIR observation, ready to be read by any compatible system.
Weight, height, BMI, blood pressure, resting heart rate, oxygen saturation, and caloric intake.
Steps, distance, average heart rate, VO₂max, and oxygen saturation.
Sleep duration and stages, breathing rate, oxygen saturation, and time to fall asleep.
{ "resourceType": "Observation", "status": "final", "code": { "coding": [{ "system": "http://loinc.org", "code": "8867-4", "display": "Heart rate" }] }, "valueQuantity": { "value": 94, "unit": "beats/min", "system": "http://unitsofmeasure.org" }}Benefits
FHIR R4, LOINC, and UCUM documents that update with every new summary, on the ROOK Connect integration and webhook you already run.
Activity, sleep, and vital signs measured every day, not just on the day of the visit.
FHIR R4, LOINC, and UCUM, with no proprietary formats to translate.
It runs on top of the ROOK Connect integration and arrives through the same webhook.
The document updates with every new summary and only creates a new version when the clinical content changes.
Use cases
Digital health, remote monitoring, insurance, and research teams send wearable data to clinical systems in the format those systems read.
01Telehealth and care programs that bring patients' continuous data to clinical teams, in the format of their system.
02Follow-up between visits, with vital signs and sleep and activity habits ready to be added to the clinical record.
03Health and wellness programs that share standardized data with clinical provider networks.
04Studies that need continuous wearable data in a standard, comparable clinical format.
Coming soon
Today the EHR/EMR API delivers wearable data to clinical systems. Soon, ROOK Connect will also bring data from EHR and EMR systems into ROOK, alongside each user's continuous data.
Data from EHR and EMR systems, brought into ROOK Connect through the same integration.
Clinical records linked to the same user as their wearable and lab data.
Wearable data flows out to clinical systems, and clinical data flows into ROOK.
EHR/EMR API
The EHR/EMR API turns the data already flowing through ROOK Connect into standardized clinical information, ready for health systems.
Read more in our technical documentationFAQ
What the EHR/EMR API delivers today and what comes next.
The EHR/EMR API delivers the wearable data already flowing through ROOK Connect to clinical systems as FHIR R4, through the Clinical Ready capability. Bringing data from EHRs, EMRs, patient portals, and health networks into ROOK is coming soon.
For wearable data sent to clinical systems, ROOK delivers a FHIR R4 Bundle through the Data Webhook for metrics that can be mapped. For records that will come from EHR and EMR systems, ROOK anticipates structured clinical information with FHIR R4 interoperability, and resources may vary by provider.
Availability will depend on the source and authorized access. The intended scope includes information useful for longitudinal records, intake automation, care coordination, and personalized experiences.
ROOK will publish supported EHR, EMR, and health-network sources when the capability launches. Teams that need a specific source can share it with the ROOK team today.
Talk to the ROOK teamThe flow will depend on the clinical provider and applicable requirements. In general, users will authenticate and authorize the relevant access. ROOK and the customer may only use data permitted by that flow and the applicable contractual relationship.
Medical-record retrieval can vary by provider, portal availability, user identity, permissions, historical coverage, and source quality. Customers should not assume that every record or provider will deliver the same resources.
No questions match that yet. Try another word or topic.
ROOK structures and standardizes available health data. Clinical interpretation and care decisions remain with qualified healthcare professionals.