The product
QuickTake Health brings a self-service health-measurement experience into physical spaces. Its public offering serves settings such as medical clinics, senior living communities, fitness facilities, sports programs, and workplaces. A person interacts with a kiosk, completes a guided session, and receives results through a connected digital experience. The wider product connects that encounter with member-facing and administrative software.
For a visitor, the experience needs to feel straightforward: approach the kiosk, follow the prompts, complete the measurement steps, and understand what happens next. For the teams delivering the product, that simple journey depends on several disciplines working together. Physical devices, Windows software, backend services, web interfaces, and release processes all need to support the same experience. That relationship between software and the real world is what makes the engineering work distinctive.
- Approach
A self-service kiosk
- Follow prompts
A guided session
- Receive results
Complete the session
The challenge
The 2.0 delivery effort had to support both clinical and wellness application experiences while keeping shared development practical. It also needed a repeatable way to install and update kiosk applications as work progressed through development and UAT. A release is more than a web deployment when it must arrive on a physical device and continue behaving correctly alongside hardware and the rest of the application.
I focused on separating application delivery channels, preserving a workable update lifecycle, and requiring evidence from builds, application checks, and real-device validation before promoting changes.
My contribution
As technical lead and backend developer at PureLogics, I combined implementation work with technical direction, review, planning, and cross-functional coordination. I worked across the API and kiosk delivery effort, coordinated with frontend, kiosk, QA, and DevOps colleagues, and translated product requirements into bounded engineering work.
I owned key decisions around the kiosk release and update approach. I directed the evolution from a single application release setup to distinct clinical and wellness delivery channels, each with development and UAT tracks. The shared-code restructure was implemented by a colleague; my contribution centered on release engineering, review, validation requirements, and rollout coordination.
Technical decisions
I established a clear distinction between initial installation and ongoing application updates. That gave the team a more coherent lifecycle to test and maintain. I also worked on automated delivery for the .NET API and coordinated promotions across the connected applications, with verification tied to each environment.
My workflow combined Claude Code and OpenAI Codex with explicit engineering ownership. AI tools assisted with implementation, testing, review, and documentation. I set scope, evaluated the results, corrected assumptions, and retained responsibility for merge and release decisions. Real-device checks and collaboration with QA remained important parts of that process.
Four delivery tracks
- Clinical DEV
- Clinical UAT
- Wellness DEV
- Wellness UAT
Outcome & delivery scope
The work established four functioning development/UAT release channels across the clinical and wellness kiosk applications, supported ongoing application updates, and contributed to onboarding a client kiosk into UAT. It also created a clearer delivery path across the backend and connected applications. These outcomes describe the 2.0 development and acceptance-testing effort as of October 2026.
Relevant stack
C# / .NET 10, PostgreSQL, WinUI 3, AWS ECS Fargate, GitHub Actions, MSIX / App Installer, and Microsoft Intune.
Connected web portals use React and TypeScript, with frontend implementation owned by a teammate.