Twelve years of engineering. Pharmacy, data, and enterprise systems.

The feeds pharma manufacturers run their patient-affordability programs on, plus clinical program and pharmacy-services partner feeds. DUA-governed and operational rather than analytical — sold and held to latency, coverage, and reliability commitments, where a missed delivery is a commercial problem, not a backlog item.

De-identified, patient-level tokenized claims feeds for RWE aggregators, running on AWS Fargate + ECS + Snowflake. Identified PHI into customer-controlled AWS or Azure environments for buyers running their own tokenization engines. Cross-source combined feeds joining multiple pharmacy systems — the newest motion, unlocking expansion at existing accounts. Growth comes from expansion, not new logos.

Delivery runs across AWS and Azure and multiple Snowflake accounts. I am migrating customer feeds onto a shared combined-feed pipeline to cut per-customer tokenization and processing cost, retiring redundant legacy pipelines while holding delivery continuity for every account on the platform.

Pharmacy transaction data is not claims data, and customer engineering teams usually find that out mid-integration. I set the technical standard for how customers consume it — join-key design, cross-source reconciliation, and file-format decisions across every customer integration — and provide the same framing on business development calls and contract reviews so commercial commitments match delivery reality.

HIPAA compliance, Expert Determination coordination with third-party evaluators, proof-of-delivery audit trails, and provenance documentation for customer legal reviews. Building the engineering function to remove single-person dependencies from customer delivery.