All work · Healthcare
Merging five acquired healthcare products into one Azure SaaS platform under HIPAA, HITECH, HITRUST and SOC 2, incrementally, with legacy and unified running side by side.
A healthcare company had grown by acquisition and owned separate software assets, each with its own stack and one to five databases of its own. They needed one coherent platform, in a regulated setting, and they could not stop serving customers while they got there.
I own the target architecture: Azure service selection, region and network design, the tenancy model, identity and access on least privilege, and disaster recovery against approved RPO/RTO targets. Plus the data models against SNOMED, LOINC and RxNorm, the API contracts, migration scripts, and deployment pipelines with security and compliance gates built in. Migration is incremental by design: features move one at a time out of legacy, legacy and unified run side by side, and each legacy system is decommissioned only once its replacement is verified in production. Interoperability covers SMART on FHIR, HL7 FHIR and v2, X12 EDI, C-CDA, DICOM, XDS/PIX/PDQ, Kafka and event hubs, webhooks and secure FTP.
The unifying data access layer is built, working and tested. It spans nine programming languages, reaches every acquired product's own stack and databases, and pulls all data-access code into one place, so the refactor happens once rather than in twenty places. It runs over gRPC, against internal pushback that a common gRPC layer would be too slow. Final technical decision authority within approved scope, and the go/no-go on every cutover.
Stack
Tell me what it does, what it is written in, and what breaks when it goes down. I will say plainly whether I can help and how I would approach it.
Tell me what it runs on