Selected professional work
myoncare
A Class IIa medical device under EU MDR that lets patients share treatment plans, medication and activity data with their healthcare teams.
Employer-owned system. The source is not public.
Overview
myoncare connects patients and care teams around a shared treatment plan: medication schedules, care tasks and activity data flow in one direction, clinical guidance flows back, and both sides see the same up-to-date picture. As a regulated Class IIa medical device, every workflow change has to hold up to EU MDR traceability requirements, not just work correctly.
Architecture
A NestJS backend fronts a React web app and a React Native and Capacitor mobile app from one shared TypeScript codebase. MySQL holds structured clinical and care-task records; MongoDB holds higher-volume, less structured activity and wearable data. RabbitMQ carries background work — wearable sync jobs, notification fan-out — off the request path, with Redis in front of the read-heavy endpoints. FHIR gives the platform a standard shape for exchanging data with external health systems instead of a bespoke integration per partner.
Engineering
Built and maintained care task management, patient monitoring dashboards and the wearable integration pipelines that keep activity data current. Containerised every service with Docker so the same image runs identically in staging and production, which matters more than usual under EU MDR change control.
- Role
- Backend and full-stack engineer since 2022, working across care task management, patient monitoring and wearable integrations.
- Category
- Healthcare
- Stack
- Node.jsNestJSTypeScriptReactReact NativeCapacitorMySQLMongoDBRedisRabbitMQFHIRDocker