Hubble

Product Introduction

1. Definition: Hubble is a healthcare technology platform that functions as a universal records layer and MCP (Model Context Protocol) server. It is a HIPAA-compliant API and agent orchestration platform designed to retrieve and normalize patient data from disparate electronic health record (EHR) systems, payer portals, and health information exchanges (HIEs).
2. Core Value Proposition: Hubble exists to solve healthcare's pervasive data fragmentation problem. It enables developers and AI agents to access a complete, unified patient record by leveraging the patient's right of access, reaching data that traditional, network-based FHIR APIs and health data APIs cannot. Its primary value is providing a single, governed connection to the entire healthcare system.

Main Features

1. Patient-Mediated Access: This is Hubble's core feature, enabling retrieval of patient records using the patient's own legal right to access their data. How it works: After a patient provides one-time identity verification and consent, Hubble's platform uses a combination of direct EHR APIs, automated browser agents (RPA), and voice interfaces to navigate individual provider and payer portals. It assembles data from every source a patient has touched into a single, normalized JSON payload via one unified API.
2. Provider-Mediated Access (Beta): This feature allows authorized read and write operations directly into the EHRs and portals that provider organizations already use. It operates on the same platform as patient-mediated access, offering functionalities like real-time eligibility and benefits checks, prior authorization, scheduling, and claims management through a single, consistent API, eliminating the need for multiple point-to-point integrations.
3. Governance & Audit-Ready Compliance: Every data retrieval action is fully permissioned, scoped, and logged. The platform is built HIPAA-compliant from the ground up, providing a complete audit trail that details which agent or user accessed which data point and from which source. This built-in governance is essential for compliance in healthcare applications and AI agent deployments.
4. Structured Output with Provenance: Hubble doesn't just return raw data; it normalizes and structures information from dozens of sources. A key technical differentiator is that every data field in the returned record is tagged with its source system (e.g., Epic, UnitedHealthcare), ensuring full traceability and allowing developers to understand data lineage and reliability.

Problems Solved

1. Pain Point: Healthcare data is trapped in thousands of incompatible systems—behind fax lines, phone trees, and forgotten portal logins. Traditional integration methods (like building custom FHIR connections) are slow, expensive, and only reach a fraction of the data, leaving a "long tail" of critical patient information inaccessible.
2. Target Audience: The primary users are healthtech developers and engineering teams building patient-facing applications, AI-powered care navigation tools, prior authorization automation, and revenue cycle management software. Secondary users include compliance officers who need built-in audit trails and product leaders at digital health companies who need to accelerate development.
3. Use Cases:
   • AI Agent Context: Providing AI health agents with a complete, real-time patient history via an MCP server interface.
   • Prior Authorization & Benefits Verification: Automatically pulling patient records and insurance details to populate forms.
   • Care Coordination & Transitions: Assembling a full patient record from multiple previous providers for a new care team.
   • Patient Data Empowerment: Powering applications that give patients a unified, portable view of their own health history.

Unique Advantages

1. Differentiation: Unlike FHIR API aggregators or health data networks that are limited by pre-negotiated contracts and what each health system chooses to expose, Hubble uses patient-mediated access as a legal and technical wedge to reach any provider or payer a patient has visited. It complements APIs with browser and voice automation to achieve near-universal coverage, where others stop.
2. Key Innovation: Hubble's approach combines the legal framework of the patient right of access with advanced, multi-modal data retrieval technology (APIs, browser agents, voice). This allows it to function as a true "records layer"—a standardized abstraction over the entire chaotic healthcare data landscape—and present it as a single, composable API or MCP server for developers.

Frequently Asked Questions (FAQ)

1. How is Hubble different from a standard FHIR API? FHIR APIs are limited to data that a specific health system has enabled and formatted, often resulting in incomplete records. Hubble uses FHIR where available, then deploys browser and voice agents to retrieve the remaining data from patient portals and legacy systems, delivering a truly comprehensive record that API-only tools miss.
2. Is Hubble HIPAA-compliant? Yes, Hubble is a HIPAA-compliant platform by design. It incorporates Business Associate Agreement (BAA) capabilities, enforces role-based access control, and maintains a full, immutable audit trail for every data access event, providing the necessary safeguards for handling protected health information (PHI).
3. Which EHR systems and payers does Hubble connect to? Hubble is live across major systems including Epic, Oracle Health (Cerner), athenahealth, UnitedHealthcare, and Aetna, utilizing over 40 specialized tools. Its patient-mediated method means it can technically reach any provider or payer with an online patient portal, constantly expanding its de facto coverage.
4. What is an MCP server for healthcare, and how does Hubble act as one? An MCP (Model Context Protocol) server provides a standardized way for AI agents to access external tools and data. Hubble acts as a healthcare-specific MCP server, allowing AI agents to securely request and receive normalized patient records from across the healthcare ecosystem through a single, governed interface, complete with audit trails.
5. How long does integration with Hubble take? For patient-mediated access, developers can begin retrieving records immediately via the API after integration. The platform's existing connections are pre-built, so engineering effort shifts from building "plumbing" to defining data permissions and workflows, enabling go-live in weeks rather than the months or years required for traditional health data integrations.