I lead development teams on healthcare applications — translating business and clinical requirements into technical specifications, setting up the codebase, and coordinating delivery across product, clinical, and compliance teams. This is high-stakes work: prescriptions have to be correct, secure, and standards-compliant, every time.
Electronic prescribing connects clinical workflows to pharmacies — prescriptions, including controlled substances under EPCS, are created in the EHR and routed electronically across the e-prescribing network. I work hands-on in this domain and the standards and integrations it depends on.
Hands-on with the public standards that govern US e-prescribing:
NCPDP SCRIPTThe messaging standard for e-prescription transactions (NewRx, EPCS).
E-prescribing networksRouting prescriptions to pharmacies across the US e-prescribing network.
EPCS & identity verificationControlled-substance workflows with identity / two-factor verification services.
Drug databasesIntegrating drug-database providers to keep medication data accurate within charts.
Interoperability certificationFamiliar with third-party EHR interoperability certification (ONC-ACB audits).
This kind of system ships against hard deadlines and external certification gates — there's no room for "close enough." I'm comfortable owning technical direction in that environment: making the architectural calls, keeping data integrity and format compliance airtight, and leading a team through to a certified, production-ready release.
A note on confidentiality.
Specific client and project details are held in confidence. This page describes my role and domain expertise — not any client's confidential information. That discretion is part of how I work with enterprise clients.