You adopted AI but the delivery timeline didn’t change. Our paper explains why →

US HEALTH TECH

AI MODERNIZATION

Beyond FHIR: Reaching the EHR data the standard doesn't expose

Letting clinicians reach the parts of their EHR that the industry data standard leaves out, without waiting for a new integration from the EHR vendor

INDUSTRY

US health tech

SERVICE

AI Modernization

ENGAGEMENT

2+ years, ongoing

TEAM

Entire tech org, ~21 people

ON THIS PAGE

    The Outcome – Potential Impact

    What this could reach once it ships

    180K+

    physicians and nurse practitioners would gain personalized, automated workflows beyond a standard EHR

    110K+

    facilities could run this with zero new integration work, using the EHR's own APIs directly

    1000s

    of endpoints unlocked, typically everything an EHR has to offer, instead of just the 200 to 300 exposed via FHIR

    From the client

    “It’s great that we have built this browser extension. I am very excited that we can now use it with any web application to expand agentic automations for their use cases”

    • THE CHALLENGE

    It was challenging for clinicians to reach parts of the EHR that FHIR doesn't cover

    The full provider directory, messaging a provider, an insurance eligibility file, and writing back to a progress note. FHIR, healthcare’s standard for sharing clinical data, exposes only a thin, fixed slice of what’s inside an EHR: enough for basic use cases, but well short of the full picture.
    Everything FHIR leaves out sits behind the EHR vendor’s own internal interfaces, which have no standardized integration path. That leaves two options: don’t reach that data, or wait, often indefinitely, for the vendor to build a custom API for each data need.
    The enterprise AI platform’s founder summed up the problem clearly:

    “The endpoints that are there today are not adequate to build the richness of the applications that users are asking for.”

    • THE APPROACH

    Two phases

    Incubyte worked as the platform’s cross-functional team across product management, infrastructure, DevOps, development, QA, and design, and solved this in two phases:

    01

    Standard data, the standard way.

    We built a FHIR connector for the platform: a FHIR MCP server paired with a matching MCP client. This lets the platform plug into any FHIR-compliant healthcare system and pull standardized patient and clinical data immediately and safely.

    02

    The data FHIR can't reach.

    For everything outside FHIR’s scope, we built a way to call an EHR’s internal APIs directly via a browser extension running within the clinician’s already authenticated session. This reaches data FHIR doesn’t expose, such as looking up every provider and their ID, messaging that provider, reading an eligibility file, and more.

    Together, the two phases mean the clinicians can reach the complete clinical picture with zero dependency on the EHR vendor shipping a new API or engaging tech teams to integrate those APIs.

    INSIDE THE LEGACY SCREEN

    • THE OUTCOME

    What we delivered might be better

    We’ve built the capability and are targeting release alongside the EHR vendor’s next product update. It isn’t live with end users yet.
    This becomes important for the platform’s customers in healthcare because it builds AI capability directly into a clinician’s existing EHR and workflows, extending what practices can do with the systems and data they already run on.
    Once released, that capability reaches the vendor’s entire installed base.
    On watching the system pull lab results, have them interpreted by AI, and write them back into a progress note, the platform’s founder said:

    “Brilliant! Brilliant. This is fantastic work, everybody. Thank you all.”

    And on the security model behind both phases:
    “It takes care of our concern regarding isolation… both sides is isolated very well… and yet it gives us the power to continue to move forward really fast.”
    • STACK AND TEAM

    Tech

    Spec-Driven Development

    TDD

    CI/CD

    Browser Extension 

    FHIR MCP

    HIPAA

    Team

    Akshay Vadher

    Software Craftsperson – Tech Advisor

    Sanket Dhokte

    Technical Product Craftsperson

    Yogendra Jaiswal

    Software Craftsperson

    Weighing a rewrite?

    There’s a third path. Most of our work begins with a thirty-minute conversation.
    Contact Us
    • READ NEXT
    • US Health Tech
    • AI Product

    FHIR ran out. The roadmap didn’t.

    Rolai, 0 new vendor APIs to reach the full record.

    Read next
    • US Health Tech
    • AI Enablement

    Built by people who don’t code.

    Rolai, 1 weekend from prompt to a shipped interface.
    Read next