The wearable technology market has exploded over the past decade, with smartwatches, fitness trackers, and medical-grade health monitors becoming ubiquitous. These devices promise to revolutionize personal health management, fitness tracking, and even chronic disease monitoring. Yet, despite this remarkable growth, the ecosystem remains fragmented. Users often find that a device from one manufacturer cannot easily exchange data with another, and developers must navigate a maze of proprietary APIs and inconsistent data formats. The root cause is a persistent lack of standardization and interoperability across the industry. Without addressing these fundamental challenges, the full potential of wearables—especially in critical fields like healthcare—remains out of reach.

Defining the Core Concepts: Standardization and Interoperability

Standardization refers to the development and adoption of common technical specifications that all devices, platforms, and services adhere to. These standards can cover everything from communication protocols (e.g., how a device transmits heart rate data) to data formats (e.g., the structure of a step count record). Interoperability, on the other hand, is the practical outcome of standardization: the ability of two or more systems or components to exchange information and to use that information without special effort on the part of the user.

In the wearable context, interoperability spans multiple levels. At the hardware level, it means a smartwatch can pair with any smartphone regardless of brand. At the data level, it means a fitness tracker’s sleep data can be ingested by any health app, analyzed, and combined with data from other devices. At the system level, it means a hospital’s electronic health record (EHR) can receive and interpret patient-generated wearable data seamlessly. Achieving all these levels requires robust, agreed-upon standards—something the wearable industry has struggled to deliver.

The Major Challenges Facing Wearable Standardization

Fragmentation of Communication Protocols

Wearable devices predominantly use Bluetooth Low Energy (BLE) for short-range communication, but the implementation of BLE varies widely. While the Bluetooth Special Interest Group (SIG) has defined generic attribute profiles (GATT), each manufacturer often layers proprietary services and characteristics on top. For example, a Garmin watch may use custom BLE services to transmit workout data, while an Apple Watch uses its own HealthKit framework. This fragmentation means that a third-party app cannot easily read raw data from multiple devices without writing device-specific code. Moreover, some devices also use Wi-Fi, NFC, or even cellular radios, each with its own set of interoperability challenges. The result is a patchwork of point-to-point integrations that stifle plug-and-play compatibility.

Proprietary Ecosystems and Vendor Lock-In

The most successful wearable companies—Apple, Google (Fitbit), Samsung, Garmin—have built powerful, curated ecosystems that offer a smooth experience when using only their own hardware and software. However, these ecosystems are largely closed by design. Apple Health is notoriously restrictive about exporting raw data to non-Apple platforms; Fitbit was only reluctantly opened up after regulatory pressure. This vendor lock-in benefits the companies’ bottom lines by keeping users within their walled gardens, but it severely limits consumer choice. A user who prefers a Garmin for running and an Oura ring for sleep tracking may find it impossible to merge both data streams into a single dashboard without manual workarounds. Developers are also forced to choose which ecosystem to support, often prioritizing the largest player and ignoring others.

Inconsistent Data Formats and Semantics

Even when two devices can communicate, the data they exchange may be formatted differently. One device might report steps as an integer count over a 24-hour period; another might report them as a timestamped event stream. Heart rate data can be expressed in beats per minute (bpm), as a rolling average, or as raw inter-beat intervals (RR intervals). Sleep stages (deep, light, REM) are notoriously inconsistent—definitions vary by manufacturer and even by firmware version. These semantic differences make it extremely difficult to build comparative analytics or clinical decision support tools. Without standardized data dictionaries and ontologies, any integration requires extensive mapping logic that must be updated with each device revision.

Regulatory and Privacy Hurdles

Wearables intended for medical purposes must comply with regulations such as the FDA’s digital health framework in the US or the EU’s Medical Device Regulation (MDR). However, these regulations focus on safety and efficacy, not interoperability. The absence of mandated data exchange standards creates a regulatory gray area: a device may be cleared for use, but there is no requirement that it share its data in a way that other certified systems can use. Furthermore, privacy laws like GDPR and HIPAA impose restrictions on data sharing, and the lack of standardized consent and data-use frameworks complicates cross-platform data flow. Manufacturers are understandably cautious, but excessive caution leads to siloed data that cannot be used for population health research or integrated care models.

Real-World Consequences of Interoperability Gaps

For Consumers: Silos and Frustration

The average health-conscious consumer now owns more than one wearable device. Yet, they typically must use multiple apps to see their data. Want to combine your Apple Watch activity rings with your Withings scale weight readings and your Dexcom continuous glucose monitor readings? You’ll need three separate apps, and any attempt to aggregate them in a single service like Apple Health requires you to trust Apple’s data mapping, which is not always accurate. This fragmentation reduces the value of owning multiple devices and can discourage users from adopting wearable health monitoring altogether. Moreover, when users switch brands or platforms (e.g., from Fitbit to Samsung), they often lose years of historical data because export formats are incompatible or nonexistent.

For Developers: Increased Cost and Complexity

Developers of health and fitness apps face a daunting landscape. Each device manufacturer provides its own software development kit (SDK) and API, often with different authentication methods, data schemas, and rate limits. Supporting just three major platforms (Apple, Google, Samsung) can triple engineering effort. Smaller developers may be forced to focus on a single ecosystem, limiting their potential user base. The lack of a universal data standard also makes it nearly impossible to build a single analytical model that works across devices; researchers using wearables in clinical trials must often buy the same device model for all participants to ensure data consistency, which inflates study costs and limits scalability.

For Healthcare Providers: Integration with Electronic Health Records

Perhaps the most critical impact is in healthcare. Providers see the potential of patient-generated health data (PGHD) from wearables to improve chronic disease management, remote monitoring, and early intervention. However, integrating this data into electronic health record systems (EHRs) like Epic, Cerner, or Allscripts is extremely difficult. Each device outputs data in its own format, and EHRs cannot easily ingest or normalize it. Even when data can be imported, clinicians often distrust its accuracy because the measurement methods and calibration differ across devices. The lack of standardized quality indicators (e.g., “this step count is from a wrist-worn accelerometer, validated against double-labeled water”) means that PGHD is seldom used in clinical decision-making. As a result, the promised revolution of continuous, real-world health data remains largely unrealized in clinical practice.

Current Efforts and Emerging Standards

Despite these challenges, significant work is underway to create the standards that the industry needs. Both industry consortia and formal standards bodies have recognized the urgency of interoperability.

IEEE 2413: A Framework for IoT Interoperability

The IEEE 2413 standard provides an architectural framework for the Internet of Things (IoT), including wearables. It defines a common reference architecture that includes layers for devices, communication, services, and applications. By following this framework, manufacturers can design wearables that are inherently more interoperable with other IoT systems. While still abstract, IEEE 2413 has influenced several national and regional IoT roadmaps. You can learn more about the standard on the IEEE 2413 page.

Bluetooth SIG Health Thermometer Profile and Beyond

The Bluetooth Special Interest Group has introduced several standard profiles for health and fitness devices, such as the Health Thermometer Profile (HTP), the Heart Rate Profile (HRP), and the more recent Continuous Glucose Monitor Profile (CGM). These profiles define precisely how a device should broadcast data so that any compliant receiver can interpret it correctly. Adoption of these profiles is growing, especially in certified medical devices. The Bluetooth SIG also maintains the Bluetooth Core Specification which includes the Generic Attribute Profile (GATT) that underpins all health profiles. Wider adoption of these standardized profiles would dramatically reduce fragmentation.

HL7 FHIR for Wearable Data in Healthcare

In the healthcare IT world, the HL7 Fast Healthcare Interoperability Resources (FHIR) standard has become the leading framework for exchanging health data. FHIR defines resources (data models) for observations, devices, patients, and more. Recently, the HL7 community has worked on extensions specifically for wearable and sensor data, such as the Physical Activity and Sleep observation profiles. When a wearable can output data in FHIR format (or a middleware service can transform it), it becomes much easier to integrate into EHRs. The HL7 FHIR specification is freely available and has been adopted by major EHR vendors. The challenge now is to encourage device manufacturers to natively support FHIR, or at least ensure their SDKs produce FHIR-compatible outputs.

Open Source and Grassroots Initiatives

Several open-source projects aim to fill the interoperability gap from the ground up. Open Wearables (openwearables.org) is a community effort to create open-source firmware and hardware designs that adhere to common protocols. Open mHealth (openmhealth.org) provides data models and APIs for aggregating health data from multiple sensors. While these initiatives are not yet mainstream, they demonstrate that interoperability is technically achievable and offer blueprints for the industry. The IHE (Integrating the Healthcare Enterprise) also publishes profiles for device-to-EHR communication, such as the Patient Care Device (PCD) domain, which includes wearables.

The Path Forward: Collaborative Solutions

Achieving true standardization and interoperability will require coordinated action across multiple stakeholders:

  • Industry consortia must agree on a minimal set of mandatory data formats and communication profiles. The Continua Design Guidelines (now part of the Personal Connected Health Alliance) is a good starting point, but it needs broader adoption beyond the medical device sector.
  • Regulatory bodies should consider mandating data export in standardized, non-proprietary formats as a condition for market access. The FDA’s recent guidance on Software as a Medical Device (SaMD) and the EU’s European Health Data Space (EHDS) both hint at future requirements for interoperability.
  • Large platform owners (Apple, Google, Samsung) must open their data export APIs and adopt standard profiles. While Apple’s HealthKit has made strides, its exporting capabilities remain limited. Google’s acquisition of Fitbit could be an opportunity to push for Android-wide wearable data standards.
  • Healthcare providers and payers should demand interoperable devices from vendors. Large health systems have purchasing power to influence manufacturers. Initiatives like the Digital Medicine Society (DiMe) are working to set best practices for digital health measurement.
  • Developers and data scientists can advocate for open standards by refusing to build on proprietary, single-vendor APIs when viable alternatives exist. Open-source tools and libraries that translate proprietary formats into common standards (e.g., converting raw accelerometer data to standardized physical activity metrics) can accelerate adoption.

Conclusion

Wearable devices have already transformed how individuals monitor their health and fitness, but their potential is severely constrained by a fragmented, non-interoperable ecosystem. Standardization is not just a technical nicety—it is essential for enabling meaningful data analysis, empowering consumer choice, and integrating wearables into clinical care. Progress is being made: organizations like the IEEE, Bluetooth SIG, and HL7 have laid the groundwork with robust standards. However, widespread adoption requires sustained pressure from regulators, healthcare providers, and users. The industry must move away from proprietary walled gardens and toward an open, standards-based future. Only then will wearables deliver on their promise of a truly connected, health-aware world.