09/02/2026
CMS interoperability requirements don't leave much room for interpretation, but the architecture decisions underneath them do and that's where most of the pain lives.
Bulk export at scale, event-driven sync instead of nightly batch jobs, auth that satisfies both security and compliance teams: these aren't edge cases anymore, they're baseline requirements for anyone touching clinical data. Whatever stack you're on, the questions are the same — where does your event bus fit, what's actually going through your API layer versus a private path, how do you keep bulk export from becoming a scheduled outage.
On AWS specifically, HealthLake gives teams a real anchor for FHIR instead of hand-rolling a server from scratch, paired with EventBridge for the event-driven pieces. We've built this pattern for clients who needed it to hold up under audit, not just look clean in a diagram.
Working through your own interoperability or healthcare data architecture challenges?
Talk to our team about building a solution designed for the realities of clinical data.