What I build, how it works, and what I can prove
The signed-consent module transforms wearable device data from the Google Health API into FHIR R4 Observation resources with LOINC coding. The OAuth 2.0 authorization flow grants scoped, time-limited access tokens; the participant controls which data types are shared and for how long. Seven-day ingestion windows with automatic token refresh. Every grant and revocation is recorded as an independently verifiable consent event.
Authentication and informed consent happen in a single cryptographic event: the person signs a human-readable consent statement with their wallet, and that signature simultaneously proves identity, records consent, and authorizes the session. No username, no password, no email. Permission scopes are explicit and enumerated. Revocation is available at any time, with the revocation itself recorded as a verifiable event. The architecture extends EIP-4361 (Sign-In with Ethereum) so that the signed statement IS the consent text.
A formal security audit identified findings across the deployed infrastructure. Critical and high findings have been remediated; medium findings are tracked with remediation in progress. The architecture operates with a zero-PHI data model: no conventional direct personal identifiers are collected or stored. Wallet addresses are persistent pseudonymous identifiers; the regulatory posture rests on operating as neither a covered entity nor a business associate. All nine contracts are source-verified on the Blockscout explorer.
I own the product end to end: discovery, requirements and acceptance criteria, architecture, roadmap, and release decisions. Delivery runs on AI-assisted, multi-agent pipelines under written scope contracts with build-artifact verification. Every feature ships against stated acceptance criteria. The platform — from the consent architecture to the FHIR mapping to the smart contracts — was designed, built, and deployed under my technical and strategic leadership.