readabl.ai auto-categorization across 50+ document types
the readabl.ai engine in production at a multi-hospital system, renewed
Matching and filing for Epic, MEDITECH, and Oracle Health
Epic integrations built, shipped, and supported for software vendors. Epic Vendor Services member.
Built for the places the EHR leaves open.
Each platform solves a data problem the EHR does not: documents that arrive unstructured, codes that do not mean the same thing across systems, and trial protocols written without the patient data to test them.
readabl.ai, becoming Waypoint
readabl.ai reads, classifies, and files inbound faxes, scans, and payer letters into Epic today, across 50+ tuned document types. In 2027 it becomes Waypoint, the agent platform that carries each document to its next step with the evidence recorded, adding MEDITECH Expanse and Oracle Health.
readabl.ai and Waypoint →Rosetta
Local codes resolved to SNOMED, LOINC, and RxNorm with a confidence score on every map and audit-grade lineage on every transformation. The rails under regulatory reporting, data platform migrations, and AI model inputs.
Rosetta →Senza ARC
Protocol feasibility, site selection, and enrollment monitoring modeled against real patient populations before the protocol is locked, for sponsors, health systems, and CROs.
Senza ARC →FHIR and HL7 integration, built and run by people who operate interface engines every day.
Interfaces are where implementations stall and where AI inputs go wrong. We build, migrate, and operate them as part of the same managed services contract that runs the EHR.
Interface development
HL7 v2, FHIR R4, CDA, X12, and flat-file interfaces on your engine: Epic Bridges, MEDITECH interfaces, Rhapsody, Cloverleaf, and Mirth.
Interface migrations
Engine consolidations and EHR transitions with interface inventories, parallel testing, and cutover runbooks.
FHIR API enablement
Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization APIs on normalized data, ahead of CMS-0057-F.
Interface operations
Monitoring, error queue management, and break-fix under the same L1 to L3 SLA as the EHR.
Device and ancillary integration
PACS, lab, pharmacy, OnBase, and medical device data into Epic and MEDITECH as discrete, mapped, clinically actionable values.
Data platform feeds
Warehouse and lakehouse pipelines on AWS and Google Cloud, with Rosetta normalization so downstream analytics and models read data that means what it says.
Agent orchestration
Epic Agent Factory where licensed, or an external orchestrator via FHIR and web services where not, for the four governed agents and your own.
Whatever your platform needs from the EHR, we can build it.
Software vendors need their platforms to read from and write to Epic and MEDITECH without a custom integration at every hospital. We partner with vendors to design, build, certify, and support the middleware that makes EHR integration a product feature rather than a customer project. We have done it for multiple vendors, across identity governance and access management platforms, and those integrations are in production on Epic today. On Epic, we now also build Connectors, so Epic's own AI can work inside your app.
Put your app where Epic's AI can use it.
Epic announced Connectors on October 21, 2026. A Connector lets Art, Emmie, Penny, and the agents health systems build in Agent Factory find information and complete tasks in your app, within the read and change permissions each hospital approves. Health systems will find developer-built Connectors on Epic Showroom starting in March 2027.
We help software vendors build and list one: deciding which facts and tasks your app should offer Epic's agents, mapping permissions to your data model, building and testing, preparing the Showroom submission, and keeping the Connector current as Epic's program changes. We are planning one for Waypoint, our own agent platform, in 2027.
Use-case scoping: the questions and tasks Epic's agents should be able to bring to your app
Permission design that matches the read and change approvals each hospital grants
Build, sandbox testing, and Showroom submission, run by an Epic Vendor Services member
Support after listing, as Epic's agents, APIs, and program terms change
Epic integration middleware for an identity governance platform built on ServiceNow.
The vendor's health-system customers needed Epic user access governed from the same identity platform as every other system, inside the ServiceNow workflows their IT teams already used. We designed and built the middleware that connects the two: ServiceNow identity and access workflows on one side, Epic's FHIR and web service APIs on the other. Account requests, approvals, security template assignments, and removals flow into Epic user records under the customer's own governance policy, and communication runs through the ServiceNow MID Server so data stays inside the customer's network.
We took the integration live, transitioned operation and hosting to the vendor, and hold an annual engineering and application support agreement: solution knowledge, Epic API revalidation as endpoints, versions, and certificates change, and break-fix maintenance, delivered by the US-based engineers who built it.
Epic Vendor Services member, with the sandbox enrollment and Epic support channels an integration depends on
Epic API integration layer owned as a product surface: authentication, endpoint versioning, certificate rotation, error handling
Vendor-owned and vendor-hosted after handoff, with documentation, release notes, and test evidence at every change
Named engineering support under a fixed annual availability model, reported monthly and reviewed quarterly
Roadmap-ready: additional Epic record types scoped as follow-on releases rather than bolted into the shipped version
Identity governance and access management
User provisioning, security template or role assignment, access reviews, and deprovisioning from IGA and access management platforms into the EHR. Built on Epic for more than one vendor in this category.
Service management and workflow platforms
EHR access requests, approvals, and fulfillment surfaced inside the ITSM portal your customers already run, with status and audit written back.
Whatever your product needs from the EHR
Clinical, operational, or administrative data in either direction: FHIR resources, web services, and HL7 interfaces on Epic or MEDITECH, or an Epic Connector. Scoped in a working session.
Discovery & API mapping
Your data model against the EHR's APIs: which FHIR resources, web services, or Connector tasks, which build objects, which security model.
EHR developer program enrollment
Epic Vendor Services membership, sandbox, and review, or MEDITECH's developer program, handled as part of the build rather than discovered at the end.
Build & certify
Middleware development, EHR sandbox testing, customer pilot, and the documentation health systems ask for before enabling a vendor integration.
Operate & sustain
Handoff to you with runbooks, then annual engineering support so the integration survives EHR upgrades.
Software built on Epic and MEDITECH.
When the EHR does not do it and no vendor does it well, we build it: scoped, governed, documented, and handed over with an owner's manual.
Epic extensions
SMART on FHIR apps, Agent Factory use cases, and vendor connector middleware, built by certified Epic developers.
MEDITECH extensions
Expanse integrations, reporting extensions, and workflow tools sequenced to your release calendar.
Patient and staff applications
Portals, intake, and operational tools on the access build beneath them, with HITRUST-certified hosting.
Phase-gated delivery with a go/no-go at every gate
Governance under AIGaaS for any component that uses AI
Documentation as legacy: build catalogs, runbooks, and sustainment guides are core scope
Optional managed operations after handoff
Bring the integration that will not close.
Thirty minutes with the software and integration leads. We map it against the engine, the data, and the SLA.
Epic, MyChart, Agent Factory, Art, Emmie, and Penny are trademarks of Epic Systems Corporation. MEDITECH and Expanse are trademarks of Medical Information Technology, Inc.