Skip to main content

Introduction

ROOK is a service that simplifies the collection and delivery of Users' Health Data from various sources. We offer a set of technology components to help developers easily integrate our services into their applications. By integrating, clients can save time and effort by avoiding the need to integrate and maintain multiple Health Data Sources. ROOK automates the collection of data by polling the Health Data Sources or via SDKs directly on mobile devices. The collected data is then processed to make sense of it and this processed data is delivered to clients through notification and consultation mechanisms like APIs and webhooks.

What does ROOK do?

The data stages are broken down the following steps:

  1. Data Extraction Stage:
    • The data must first be extracted from the data source using the extraction mechanism provided by the data source. This can be done through API polling or by listening to the data coming from the data source. Health data sources with APIs only require the end user to authorize ROOK to access their health data. Data sources have authorization pages that can be accessed through the connections page or API endpoints to generate data source authorization page URLs. Once authorized, we automate the data collection process in accordance with available health data technologies. Some technologies offer Webhooks in which ROOK is notified of newly available User data, providing a faster experience for data collection. Other data sources require polls to request new data For health data sources without APIs, data must be pulled directly from mobile using our SDKs.
  2. Processing Stage:
    • Our servers process health data, storing it standardized, harmonized, and cleaned up.
    • The ROOK Extraction SDKs perform some data processing such as standardization and harmonization.
  3. Data Consumption Stage:
    • From ROOK Server:
      • Clients can consult the summaries and events of their Users using our API endpoints.
      • Clients can receive the summaries and events by subscribing to ROOK Webhook for notifications.
    • From the mobile:
      • Clients can extract the data directly from the mobile without necessarily transmitting that data to our servers. This could be useful for customers who have their own cloud processing backend.

What are the advantages of using ROOK?

Responsibilities

  • Data Sources:
    • We support Data Sources with over 300 wearable Health Data Sources, and is constantly adding more Data Sources. Please contact us if you need a provider that is not listed.
  • Technical:
    • We connect to all Health Data Sources, whether they use endpoints, notifications, or mobile SDKs to get the data you need. We also take care of any updates and changes that health data sources make to their protocols.
  • Legal:
    • ROOK's legal and security team understands the responsibilities of managing your and your Users' Health Data from different sources and conveys them in simple terms for you and your Users - shown to them in the authorization web embedded into your application.
  • Payments:
    • For some Health Data Sources, their APIs or connections to the data are behind a paywall which would make integrations very expensive or even unaffordable for a single company. However, ROOK covers all the costs related to those Health Data Providers, and you only have to pay ROOK the fee for actual usage.

What is the technology behind ROOK?

ROOK offers a suite of technology components including SDKs, APIs, and webhooks to help developers easily integrate our services into their applications. Please read each component specific section to learn more

What are the ROOK technology rules?

When designing ROOK technology, there are three key rules to follow: modularity, generality, and ease of integration.

Modularity

  • Components are modularized with delimited responsibilities, allowing clients to integrate each component of the solution separately.
  • For example
    • Clients can use ROOK's Bluetooth extraction SDK to create their own app for training without using ROOK's Training SDK.
    • ROOK's Health Data Extraction SDK can be used directly on mobile without requiring data to be pushed to ROOK servers.
    • ROOK's Transmission SDK can be used to transmit health data generated by themselves on mobile.

Generality

ROOK technology is flexible and can be used in different verticals, with flexible data structures that work for different business models.

Ease of Integration

Integration with ROOK technology is intended to be fast and easy, providing modularized components for different levels, time and resources available for the development.