Interoperability

A unified data model

Each wearable manufacturer has its own format, units, and API. Without a layer to standardize this diversity, analysis is inconsistent or impossible.

UbitelCare It solves this with a transformation module that adapts the data from any source—regardless of the manufacturer or format— to a unified internal model. The analysis engine always works on a consistent basis: it works with Fitbit today, with Withings tomorrow, and with any future manufacturer, without changing anything in the analysis or the interfaces.

This makes the platform truly device agnosticIt is not built for a specific hardware and then adapted, but designed from the ground up to be hardware independent.

What this architecture brings

An integration designed to be hardware-independent and reliable over time.

  • Manufacturer independence

    The analysis and results are consistent regardless of the wearable device used by the user or patient.

  • Gradual incorporation of devices

    Integrating a new manufacturer only requires their adapter, without touching the analysis engine or interfaces.

  • Data quality control

    The system evaluates the reliability of each source and discards or marks data that does not meet the minimum criteria.

  • Transparency

    Consumer wearables provide approximate signals, not certified clinical measurements. The system consistently takes this into account.

HOW INTEGRATION WORKS

From wearable to internal data model

Four phases that turn data from any wearable into information ready for analysis: authorization, synchronization, normalization, and quality control.

01

User authorization

From the app, the user authorizes access to their wearable data via OAuth 2.0, without the platform storing their credentials. They retain control and can revoke access at any time.

02

Data synchronization

The system synchronizes data periodically or based on events, according to the manufacturer's API. It supports both models and automatically handles errors such as token expiration or temporary failures.

03

Transformation and normalization

The transformation module adapts each provider's format to the internal model: it unifies units and time structures. This ensures the analysis engine always works with data in the same format.

04

Data quality control

Before analysis, the system evaluates the signal's continuity, coverage, and consistency. Data that fails this check is discarded or marked as unreliable.

DEVICES AND STANDARDS

What does the platform support today?

UbitelCare's interoperability is based on open industry standards. The architecture allows new manufacturers to be incorporated by developing only their adapter, without modifying the rest of the system.

Integrated devices

Built on Fitbit's APIs, this integration is compatible with Withings, Corsano, Apple, Samsung, and Huawei. New manufacturers are added via their adapter, without affecting the rest of the system.

OAuth 2.0

Access to wearable data is done via OAuth 2.0: the user grants permission without sharing credentials, accesses only what is authorized, and can revoke access at any time.

HL7 FHIR

Standard for exchanging clinical information with electronic health record systems, implemented in production. Enables interoperability with the institutional healthcare ecosystem.

SYSTEM LIMITS

What wearable data is and what it isn't

A principle of honesty Define the system design: consumer wearable data are approximate signals of physiological behavior, not certified clinical measurements. A smartwatch heart rate is not equivalent to an ECG.

UbitelCare takes this into account by design. This data is used as an indicator of physiological evolution over time, not as absolute clinical values: the analysis is based on deviations from the user's own historical pattern, not on comparing values with clinical thresholds. This decision is consistent with the actual use of these devices and the purpose of each solution.

CONTACT

Do you work with healthcare systems or devices that need to be integrated?

If you represent a healthcare institution, a device manufacturer, or an operator with your own technology ecosystem, let's explore together the possibilities of integration with the platform.

TECHNOLOGY

Other pillars of technology

Platform

The analytics engine that processes the integrated data from the devices.

Artificial intelligence

The analytics engine that processes the integrated data from the devices.

Security and privacy

How is the data that the system analyzes protected?.