Engagements we've shipped, anonymized by client identity.
Long-running engagement, ten-plus years. National remote patient monitoring and chronic care management company, since acquired.
A national RPM and CCM company brought Diridium in when they had no integration capability at all. The opportunity was to build one platform that could serve every health system, physician group, and provider customer through configuration rather than custom code, before the customer pipeline arrived.
Diridium was principal architect and principal developer of the integration platform. One codebase routing enrollment, clinical, and billing data across the major EHRs (Epic, Cerner, athenahealth) and the long tail of ambulatory systems, with new customers onboarded by configuration rather than engineering work. Diridium also owned the AWS infrastructure, from network topology to deployment automation.
Diridium remained principal architect through more than a decade of growth, then stepped away voluntarily. The platform today serves more than 500 healthcare organizations on the same codebase, now operated by its new owner.
Long-running engagement, ten-plus years. National advance care planning platform.
Diridium first engaged with MyDirectives over a decade ago to build out HIE connectivity, getting advance directive data flowing between the platform and the health information exchanges providers depend on.
That initial integration project opened into a long-running technical relationship. Diridium owns the AWS architecture today (network topology, security posture, environment separation) and works alongside MyDirectives' compliance partner on the technical infrastructure side of their HiTrust program. As the platform has evolved, Diridium has remained the in-house technical hand the team turns to for architecture questions that cross integration, cloud, and security.
Ten-plus years in, MyDirectives is the established platform in advance care planning, a category that's seen multiple waves of entrants and pivots. Diridium's infrastructure work has scaled with the platform through all of it.
Past engagement. Revenue cycle management vendor with an LLM-driven product for automated coding and billing.
A revenue cycle management vendor was building an LLM-powered product to automate coding and billing decisions. The model needed historical clinical and encounter documents from each customer's EHR to do its work, at scale, across the variety of EHR systems an RCM customer base spans.
Diridium built the integration layer that harvested those documents. The hard problem wasn't the AI itself, which was the client's domain. It was getting the data: pulling structured and unstructured documents out of multiple EHR systems consistently, navigating the consent and security model around historical PHI, and delivering it in a form the model could ingest at training and inference time.
This is the shape of work most AI healthcare vendors eventually need. The product team builds the model. Getting it the right data, at scale, across whichever EHRs each customer happens to use, with healthcare-grade security underneath, is a different problem with different expertise. That's the work.
Ongoing multi-year engagement. Multi-state physician group providing tele-neurology, tele-EEG, and related tele-specialty services.
A multi-state physician group provides remote specialty coverage to hospital emergency departments and inpatient units across the country. Their anchor customer is one of the largest hospital systems in the country. Each referring hospital sends consult orders, the group's clinicians document directly back into the originating chart, and the same data feed drives the revenue cycle.
Diridium designed the integration platform that runs the whole loop: orders in, results and signed documentation back, and a clinical feed into the billing system. One platform, configuration-driven, handling every referring hospital and every receiving clinician through the same code path. Spans multiple major EHRs on the hospital side, including Epic and Meditech.
The work extended beyond the integration code itself. Diridium also designed the AWS topology the integration runs on, sized and secured for the platform's throughput and HIPAA posture, and drove development of native configuration controls in the client's product UI. The client's operations team can stand up a new referring hospital end to end without engineering involvement.
Live across more than twenty hospitals within one of the largest US hospital operators. New facilities onboard on the client's own schedule.
2025–present. Remote patient monitoring vendor aggregating implantable cardiac device data for healthcare provider customers.
An RPM vendor in the implantable cardiac device space had grown into hundreds of customer-specific integrations. Each provider customer had its own dedicated integration for each device platform it cared about: Medtronic, Abbott, Boston Scientific. None of them were large individually, but the architecture had no reuse. A change to how any device's data was handled meant touching every customer's copy of that code. New customers added more of the same.
Diridium redesigned the architecture around the device platforms instead of around the customers. Today there is one integration per device platform (Medtronic, Abbott, Boston Scientific, with Biotronik in flight). Customer routing happens inside each one through configuration. The infrastructure consolidated alongside the code: six integration engines collapsed to one. The redesign drew as much on Diridium's network and systems background as on the integration code itself.
The engagement extended into EHR-side integrations, including Epic and Athena, so patient context and orders flow into the same consolidated platform rather than another set of forks.
Onboarding a new customer is now configuration, not engineering. The client's team runs it end to end. Diridium's involvement, if any, is a JSON snippet to register the new tenant. No new code.
Not every engagement is a platform build. Diridium is also called in for shorter, more targeted work: AWS network design, vendor diligence, integration troubleshooting, security architecture reviews. Most of these come from prior clients or referrals who have seen the longer engagements and need a specific problem solved without standing up a new program.
Knowing the limits of our own depth is part of the job. For projects that need deep EHR-specific workflow knowledge, the kind that comes from working inside Epic or Meditech as an employee, we bring in subject matter experts. For projects that aren't ours to take, we say so.
The same senior hand, scoped to the problem.