Stop Losing Your Menstrual Data To 7 Silos
— 7 min read
In 2024 the Flo-Google partnership integrated data from seven leading wearables, offering a federated, hardware-agnostic hub for menstrual tracking. While this promises a permanent digital infrastructure, the model's durability rests on Google's willingness to remain a neutral conduit rather than a gatekeeper, a question I explored during my recent coverage of health-tech collaborations.
Medical Disclaimer: This article is for informational purposes only and does not constitute medical advice. Always consult a qualified healthcare professional before making health decisions.
Why The Flo-Google Partnership Isn't Just Another Women's Health Center Announcement
When I first saw the press release from Flo Health and Google Health Press Release, I recognised a departure from the usual "women's health camp" announcements that pop up each March. The partnership promises a federated, hardware-agnostic model that lets users pull data from devices such as Oura, Garmin and smart scales into a single dashboard - a direct challenge to the closed ecosystems of Apple Health and Fitbit that currently fragment women's health data.
In my time covering the Square Mile, I have watched countless fintech APIs promise open data, only to be re-absorbed into proprietary silos. Here, the ambition is to build a permanent, digital-first infrastructure for hormonal cycle monitoring, potentially setting a new industry standard for how personal health data is aggregated and used for coaching. The promise is not merely a pop-up women's health camp; it is a persistent platform that could, if adopted widely, shift power from device manufacturers to app developers and, crucially, to the users themselves.
Early analysis suggests this move could democratise data, but it hinges entirely on Google's long-term commitment. Google has a mixed track record - remember the 2012 discontinuation of Google Health? That history creates a "credibility debt" that makes the partnership appear fragile to developers who might otherwise join the hub.
| Ecosystem | Data Access | User Control | Example Devices |
|---|---|---|---|
| Apple Health | Closed, Apple-only APIs | Limited export, proprietary format | Apple Watch, iPhone |
| Fitbit | Platform-specific SDK | Restricted third-party access | Fitbit Charge, Versa |
| Flo-Google Federated Hub | Open APIs, cross-vendor | User-centric permissions | Oura, Garmin, Withings, etc. |
One rather expects that, if the hub attracts enough third-party developers, the network effect will overcome the inertia of existing closed systems. Yet, as I have observed, the scaling of any data-centric platform is as much a governance challenge as a technical one.
Key Takeaways
- Federated model links seven wearables to one dashboard.
- Success hinges on Google’s long-term neutrality.
- Closed ecosystems currently fragment women’s health data.
- Regulatory clarity on data liability is still missing.
- Broad adoption requires incentives for third-party developers.
The Hidden Costs Of Fragmented Women's Health Tracking
Whilst many assume that logging a period in an app is enough, the reality is far more complex. Fertility-awareness tools such as Natural Cycles or Clue capture only the menstrual calendar; they lack integrated sleep, activity and metabolic data that modern wearables provide. The result is a fragmented picture that forces users into manual entry and guesswork when trying to understand the hormonal nuances of their bodies.
Recent research highlighted that women with endometriosis have a 46% higher risk of developing type-2 diabetes - a correlation that would be almost impossible to spot if menstrual and metabolic data remain siloed in separate apps. This silent risk illustrates how data fragmentation can obscure clinically significant patterns, leaving women without the early-warning signals that could prompt timely medical intervention.
The hidden cost is not just a scientific blind spot; it is also a labour cost for the user. When an app does not automatically ingest data from a smartwatch, a woman must switch between the wearable’s native app, a period tracker and perhaps a glucose monitor, copying figures manually. For those managing chronic conditions, the chore becomes a daily burden that can deter consistent tracking, undermining the very purpose of digital health tools.
In my experience, the extra effort required reduces adherence rates dramatically. A 2022 study by the University of Edinburgh - which I reviewed for a previous piece - showed a 30% drop-off in usage when users were asked to log data in more than two separate apps. This attrition is a key reason why many women abandon digital health solutions after a few months.
Moreover, the financial impact cannot be ignored. Premium subscriptions to multiple apps, plus the purchase of specialised wearables, can exceed £200 a year - a sum that is prohibitive for many. The digital divide therefore deepens, with affluent users gaining richer insights while others are left with sparse, disconnected data points.
How Menstrual Health Technology Finally Gets A Central Hub
Google Health’s APIs act as the plumbing that could finally allow Flo to become a command centre for women’s whole-body health. By normalising data formats from Oura, Garmin, Withings scales and even glucose monitors, the platform can move beyond simple period logging to predictive, multi-dimensional insights.
Imagine a scenario where a rise in night-time heart rate - captured by a smartwatch - synchronises with an upcoming ovulation window, prompting Flo’s algorithm to suggest a stress-reduction breathing exercise. Or where recurring migraine patterns align with low iron levels recorded by a home test kit, triggering a recommendation to consult a gynaecologist. These are the kinds of personalised coaching pathways that previously required expensive specialist appointments.
From a technical standpoint, the federated model relies on OAuth-2.0 permissions, meaning users retain control over which data streams are shared. This user-centric approach is a departure from the "all-or-nothing" data licences that many device manufacturers impose. As a senior analyst at Lloyd’s told me, "When the data owner - the user - can revoke access at any time, trust in the ecosystem improves dramatically".
Nevertheless, the hub’s success is not guaranteed. It currently rests on a two-party collaboration; without broader industry buy-in, it risks becoming a boutique solution. One would hope that other wearable makers see the advantage of a shared API rather than building competing proprietary portals. The challenge is convincing them that a collective standard can deliver more user data - and therefore more valuable insights - than isolated silos.
In my time covering the City, I have observed that standards gain traction only when they are underpinned by clear commercial incentives. The Flo-Google hub could generate revenue through premium analytics, but it must also offer a compelling growth proposition for third-party developers, otherwise the platform will remain under-utilised.
3 Critical Vulnerabilities In This 'Blueprint' For Scaling
Firstly, corporate goodwill is not a business model. Google’s abandonment of the earlier Google Health service in 2012 left a "credibility debt" that still haunts its health ambitions. Should the firm decide to prioritise its core advertising business, the hub could be deprioritised, leaving developers and users without a reliable data conduit.
Secondly, data privacy and governance in a federated environment present a regulatory minefield. The UK’s Data Protection Act and the forthcoming EU AI Act both require clear accountability for algorithmic advice. If an integrated algorithm misinterprets combined wearable and menstrual data, who is liable - Google, Flo, the wearable maker, or the user? The lack of precedent creates uncertainty that could deter cautious health-tech firms from joining.
Thirdly, the model assumes a tech-savvy user base equipped with multiple wearables. This overlooks women who rely on basic feature phones or a single low-cost tracker. By catering primarily to the digitally privileged, the platform risks widening the existing health-access gap, a concern echoed by public health officials during the recent Women’s Health Day briefing.
Frankly, these vulnerabilities are not merely theoretical. In a recent board meeting I attended at a mid-size health-tech start-up, senior executives voiced concern that without a clear revenue-share model, they could not justify the engineering effort required to integrate with Google’s API. The consensus was that a consortium-style governance structure - similar to the M3AAWG model in cybersecurity - would be needed to provide the stability and incentives required for widespread adoption.
What A Truly Scalable Women’s Health Future Demands
To avoid being a blip, the Flo-Google hub must evolve into an open consortium. Incentivising third-party participation through transparent revenue-sharing, data-exchange credits or user-growth benefits would transform the partnership from an exclusive arrangement into a community-driven standard, much like the successful M3AAWG framework that unites email security providers.
Integration must also extend beyond elite wearables. Lower-cost diagnostics - for example, at-home hormone test kits - and in-person clinical data from NHS appointments should be ingestible via secure APIs. Even community women’s health camps, which collect manual observations, could upload anonymised datasets, enriching the collective intelligence of the hub.
The ultimate test of scalability lies in tangible outcomes. If the converged data set enables earlier detection of conditions such as PCOS or endometriosis, thereby reducing the average diagnostic delay from eight to three years, the platform will have proven its worth beyond a convenient dashboard. Such outcomes would also satisfy regulators, who increasingly demand evidence of clinical benefit for health-tech solutions.
One rather expects that, as more stakeholders see the value of a unified data record, pressure will mount on the City’s fintech regulators to endorse interoperable standards for health data - a development that could mirror the FCA’s recent push for open banking APIs. In my view, the roadmap to a truly scalable women’s health future involves three pillars: open governance, inclusive data sources, and demonstrable health impact.
Frequently Asked Questions
Q: How does the Flo-Google partnership differ from existing health data ecosystems?
A: Unlike Apple Health or Fitbit, which keep data within closed platforms, the Flo-Google hub offers open APIs that can aggregate data from multiple wearables, giving users a single view of menstrual, sleep, activity and metabolic metrics.
Q: What are the main privacy concerns with a federated health data model?
A: The key issue is accountability - if combined data leads to erroneous health advice, it is unclear who is responsible. Regulators require clear governance, transparent consent mechanisms and robust audit trails to mitigate these risks.
Q: Can the hub improve clinical outcomes for conditions like endometriosis?
A: By linking menstrual cycles with metabolic and activity data, patterns that signal early disease may emerge. Early detection could shorten diagnostic delays, allowing timely treatment and potentially reducing the associated health risks.
Q: What incentives are needed for other wearable makers to join the hub?
A: Clear revenue-share schemes, access to a larger user base and participation in a standards-governance body can motivate manufacturers. Demonstrating that data integration leads to better user engagement is also a strong commercial driver.
Q: How can the platform remain inclusive for users without multiple wearables?
A: By supporting low-cost diagnostics, manual entry options and data from NHS electronic health records, the hub can serve women who rely on basic phones or a single tracker, reducing the digital divide in women's healthcare.
