Cross-brand wearable interoperability: standards, APIs, and the remaining gaps
Cross-brand wearable interoperability: standards, APIs, and the remaining gaps
Wearable interoperability means being able to move data from different brands into a shared format that apps, researchers, or health systems can interpret. The main distinction is that shared schemas and healthcare standards describe how data should be represented, while unified API services connect to device providers and normalize their outputs; neither guarantees that brands measure the same thing in the same way.[1][2][3]
What the initiatives contribute
- Open mHealth: shared meaning for health measures. Open mHealth provides open JSON schemas for patient-generated data from wearables, apps, and other sources. Schemas describe not only a value’s format but also its clinical context, such as whether a glucose reading was fasting or a heart-rate measurement was taken at rest or during exercise. They can include metadata about the measurement, its source, and how it was collected, and can support mapping into FHIR implementations.[4][5][6][7][8]
- IEEE P360, now IEEE Std 360-2022: an architecture framework. The published standard provides terminology, categories, and an architecture for wearable consumer-electronics standards and specifications. It is not a unified wearable API or a device-to-device protocol, and the available source does not show it mandating a common data format, interface, or radio protocol. It was approved on February 9, 2022, and published on April 25, 2022.[9][10][11]
- FHIR and HL7: a route into healthcare systems. FHIR, developed by HL7, can provide a structure for representing wearable observations so they can be integrated with electronic health records and other health systems. A reported Garmin integration case used a data dictionary and FHIR resources to map wearable data, illustrating the translation work involved rather than proving universal plug-and-play compatibility.[12][13][14]
- Platform and API layers: practical bridges, not necessarily standards. Google Health Connect is described as an Android platform route for apps to access health data across devices and services. Commercial providers such as Terra and Thryve offer APIs that normalize data from multiple brands; Open Wearables offers a self-hosted REST API that maps provider data into a unified schema. These can reduce the number of integrations developers build, but they are products rather than shared industry standards.[15][16][17][18]
Participation and industry activity
Participation spans standards organizations, developer communities, researchers, device vendors, and API providers, but the available sources do not provide a complete membership roster. IEEE’s Consumer Technology Society and its Emerging Technology Standards Committee are associated with IEEE 360-2022; the Wearables Working Group is chaired by Yu Zhu. HL7 is identified as the organization behind FHIR.[19][20]
Open mHealth says its community includes more than 6,000 developers and health organizations working on patient-generated data interoperability, though the cited material does not name individual member organizations. A healthcare integration study used Garmin Vívoactive 4 watches, the Fitrockr API and data dictionary, the MORE research platform, and a Kodjin FHIR server and resource mapper. This is evidence of collaboration across device, API, research, and health-data infrastructure, not evidence that those companies formally participate in IEEE’s working group or Open mHealth.[21][22][23]
API providers also connect multiple commercial platforms: the sources name Terra and Spike, and list brands and services including Apple Health, Fitbit, Garmin, Oura, Samsung Health, and WHOOP among integrations. Their role is to broker access and normalize data; the sources do not establish that the named device makers jointly govern a single cross-brand standard.[24][25]
Hurdles to genuinely unified data
- Different technical interfaces. Device brands may expose data through separate SDKs, with differing data structures, quirks, and rate limits. A developer account describes integrating multiple SDKs and transforming inconsistent JSON; a 2025 study also reports interoperability gaps between wearables and healthcare standards such as FHIR.[26][27]
- Different definitions and data quality. A value is not self-explanatory: systems may need to align its code, unit, time, subject, collection context, and source. The cited integration work describes using a data dictionary to align wearable data with FHIR resources, and flags data quality as an issue requiring further work.[28][29][30]
- Privacy, consent, and governance. Wearable data may be shared with cloud services or third-party apps, creating concerns about user awareness, unauthorized access, breaches, and misuse. One research prototype used participant-controlled sharing, pseudonymization, and anonymization; regulatory coverage can also be fragmented, with consumer wearable companies often outside HIPAA’s covered-entity framework while other rules may apply.[31][32][33]
- Commercial incentives are a concern, but causation is not established. Sources describe business uses and potential risks involving wearable data, but they do not show that manufacturers deliberately keep systems incompatible to protect revenue or market share. That possible incentive should therefore be treated as an open question, not a demonstrated explanation for interoperability gaps.[34][35]
Bottom line
The emerging approach is layered: Open mHealth schemas help give measurements consistent meaning; FHIR can carry those data into healthcare systems; IEEE 360-2022 supplies a broader wearable-standards framework; and platform or commercial APIs handle connections to device ecosystems. The unresolved work is aligning definitions and data quality while addressing technical access, privacy, and governance. A unified API can simplify integration, but it cannot by itself make unlike measurements equivalent, and the available evidence does not support treating IEEE 360 as an API standard or claiming that all named companies formally participate in the standards efforts.[36][37][38][39][40]
Veiem alternatives:
- Modifica la consulta.
- Inicia un nou fil.
- Elimina les fonts (si s'han afegit manualment).