Transitioning complex executive-health clinic operations from a fragile low-code stack to an offline-first Next.js PWA with zero downtime, live payment processing, and HIPAA + PCI-DSS compliance.
Consultations happen in underground rooms and behind lead radiation shielding where internet drops to zero. When standard cloud apps disconnect, patient charts lock up and uncommitted notes are lost.
Shielded Exam Rooms
Lead-lined walls and underground suites block wireless signal.
Cloud App Failure
Traditional cloud canvas apps freeze and drop patient notes when disconnected.
Offline-First Solution
Next.js PWA saves instantly to the tablet and syncs safely once reconnected.
The clinic ran on 14 tablet screens, 18 automated flows, and 12 database tables in Microsoft Power Platform. When nurses charted in basement suites, long chains of flows timed out and lost patient notes.
Canvas tablet forms that became sluggish and froze during bedside patient visits.
Automated orchestrations that chained together and timed out under clinic load.
Fragmented data tables that blocked leadership from seeing real-time clinic profit margins.
Nurse inputs vitals into cloud-dependent tablet form
Nurse inputs vitals with immediate tactile response
Flow #1 triggers Flow #4 across external servers
Saved in milliseconds to tablet’s local IndexedDB
Weak signal halts the flow chain mid-task
Chart completes seamlessly with zero internet required
Flow aborts after 45s; nurse must re-enter from scratch
Device safely pushes encrypted updates once in range
- FAULT 01
Flows timed out mid-chart
Complex nurse charting and multi-provider billing ran through long chains of Power Platform flows that failed to complete.
Impact: The screen locked up mid-appointment, losing entered notes.
- FAULT 02
Exam suites had no signal
Consultations take place in underground and lead-shielded rooms where cellular and WiFi signals drop to zero.
Impact: Frequent disconnects right where charting happens.
- FAULT 03
Leadership flew on lagging numbers
Inflexible low-code reporting prevented executives from viewing real-time unit economics and clinic margins.
Impact: No live view of profit margin per clinic location.
Try the simulation below: switch to the shielded room, add vitals notes, then reconnect. The tablet saves everything locally to IndexedDB and syncs automatically once in range.
A touch-first Next.js PWA, autonomous local storage on the tablet, hardened Node.js microservices on AWS, and a PostgreSQL database with real-time P&L reporting.
Local Device Storage
Autonomous client database running directly on the tablet hardware.
Patient charting continues uninterrupted even with zero WiFi.
In executive healthcare, a single consultation fee must be split between a booking deposit, attending physician fees, and external lab costs. We built a payment pipeline where card details stay safely with the payment processor, while payments split automatically with zero manual accounting errors.
Single Patient Charge
Patient pays once at the clinic terminal. Card data stays tokenized at the gateway.
Collected in advance at reservation to secure the appointment time.
Distributed automatically to the specific medical providers who saw the patient.
Settled once external diagnostic results and third-party laboratory costs arrive.
Credit card details stay securely with the payment processor. The clinic application only handles secure split tokens—card numbers never touch clinical servers.
All clinical intake, notes, and medical orders remain encrypted at rest and in transit within the BAA application boundary.
How do you replace an operating system while clinics see patients every day? Features were cut over in phases so not a single patient appointment was interrupted.
Both sides carried real appointments throughout. Neither ever went to zero, which is the whole reason there was no downtime.
Eight days from proposal to team deployment. Clinics continued operating on legacy stack without interruption.
Clinics never stopped seeing patients. Both platforms ran side-by-side during cutover with zero operational interruption.
- 8 Days
- Proposal to kickoff
- Rapid technical evaluation to deployed pod of 6 engineers.
- Go-Live
- Phases 1 and 2
- Signed off August 2026 with full clinical acceptance.
- 100% Live
- Payment processing
- Split deposit, physician fee, and lab balance with zero manual reconciliation errors.
- 8 Weeks
- Core sprint
- Delivered by 6 full-stack and DevOps engineers, transitioning to ongoing retainer.
What changed in everyday clinical operations.
Sluggish tablet forms timing out mid-chart
Offline-first PWA with instant local saving
Frequent staff disconnects in basement suites
Uninterrupted charting with automatic background sync
Flow timeouts during multi-provider split billing
Automated 3-rail payment gateway with 0 reconciliation errors
Lagging reports blocking unit economics
Real-time multi-location P&L margin dashboard
This clinic group is described by sector and region rather than by name. All figures are verifiable on Upwork.
A stack that got you live is not automatically the stack that scales. We re-platform operations that cannot afford to stop.
What we ship
- Low-code to production re-platforming
- Offline-first PWAs with IndexedDB reconciliation
- HIPAA-boundary application architecture
- PCI-DSS split-payment gateways
- Zero-downtime phased cutovers
- Multi-location real-time P&L