Case study
Patient-support software
I translated nurse protocols and medication-program requirements into full-stack workflows.
Context
The product
Resilix was a digital patient-support product used for medication programs. Each program had its own protocols, treatment stages, tasks, prompts, and information requirements, so my work involved translating those differences into configurable interface and backend behavior without creating a separate implementation for every client.
What I owned
My role
- Implemented features supporting patient onboarding, communication, medication management, and treatment-stage-dependent behavior
- Translated nurse protocols and program requirements into application rules and interface states
- Connected Vue interfaces, MongoDB configuration, persisted workflow data, and third-party services
Project example
Web calls for nurses
One feature connected nurses to patients' mobile phones directly from Resilix. From the existing text-chat workspace, a nurse could open a web-call modal that combined the live call with standardized, medication-specific prompts and a space for notes, keeping the call, required questions, and patient context in one place instead of asking the nurse to coordinate across separate tools.
I implemented the feature across the stack: integrating a third-party API for web calling, configuring prompts in MongoDB, persisting the nurse's notes, and managing Vue component states. The main technical work was keeping the interface and stored state in sync as the call moved from initiation to disconnection.
- Chat workspaceExisting patient context
- Call initiatedThird-party calling service
- Guided conversationMedication-specific prompts
- Notes persistedWorkflow record retained
Reuse
Using the same parts across programs
- Scope
- 4+ client programs
- Ownership
- Full-stack workflows
- Domain
- Patient adherence
Modular UI components, database-driven configuration, and shared services such as web calling let us reuse the work across client programs, which reduced the amount of client-specific implementation required when similar workflows appeared in more than one medication program.
Reflection
How healthcare constraints shaped the work
Before this role, I had not fully appreciated how deeply privacy and policy shape the engineering process in healthcare. Protecting personal health information affected how we developed and tested every feature, from masking data and creating synthetic test fixtures to separating development, staging, and production environments with different access controls; I carried that awareness into my later work with laboratory and clinical teams at Broad.