I build the systems my clinic runs on.

Clinical test tracking platform

Functional testing at the practice (PPT, FMS, grip, endurance) lived in three places: CareCloud for scheduling and documentation, the testing hardware for results, and a shared spreadsheet for who ordered and who performed each test. Staff entered every test four times. When a patient missed a test and didn't rebook, it slid to the bottom of the sheet and was gone.

I found the problem, quantified what it was costing the practice for leadership, wrote the build spec, and shipped the replacement.

What it does

• Tracks every test order through a defined lifecycle. A passed date with no completion flips the test to Missed automatically, with a visible countdown to auto-cancel at 30 days.
• Event-driven follow-up. The re-test alert fires when the patient checks in, not on a calendar. Protected visit types like Precert and Re-eval are never interrupted; the test moves to the next visit instead.
• Multi-test visits. Ordering PPT, FMS, and grip together creates three independent records, so a patient can finish one and miss another without breaking either.
• Soft deletes for providers and evaluators. Retiring a staff member hides them from new entries but keeps their full history in every report.
• Provider performance dashboard: arrival rates, visits per plan of care, and productivity by provider, the numbers ownership uses to judge ROI.

Security and compliance

Row-level security scopes every query to the user's site and role. Changes write to an audit trail. PDFs never persist in the browser. The platform runs under the practice's HIPAA controls, and the business associate agreement with the EHR vendor was handled separately from the technical work.

EHR integration

I ran the technical calls with CareCloud and mapped the FHIR R4 and REST endpoints the sync needs: appointments, check-in status, visit type, and next appointment. The design has since moved to a hybrid model with Salesforce as middleware. The app keeps its own tables with CareCloud identifiers, Salesforce polls CareCloud every 30 minutes, and the app calls Salesforce live for appointment data instead of duplicating it. I wrote the developer documentation the Salesforce developer is building the REST APIs from.

Rollout

I led the multi-location rollout: role-based access, staff training, go-live support, and an ongoing support channel for questions and feature requests. Adoption held because it removed work instead of adding it.

This is the practice's application and runs on real patient data, so there is no public demo or source. I'm happy to walk through it on a call.

Protocol and inventory tracker

A nurse practitioner running an independent practice was tracking patients, protocols, stock, and revenue by hand. I built her a tracker that ties all four together.

• Patient profiles with purchase history and discount tiers applied from pricing rules, not typed in.
• Each protocol's cycle length drives the patient's reorder date and bloodwork date automatically.
• Inventory that moves with every sale, and a revenue view by calendar year.
• Hosted on Supabase and Cloudflare with access limited to named users.

I also drafted the software use agreement and HIPAA business associate agreement between developer and practice, so the paperwork matched how the system actually handles data.

Physical capacity testing engine

Different testers running the same assessment get different numbers when the protocol lives in their heads. This engine puts aerobic capacity, maximal strength, and mobility testing under one standardized set of parameters, so any trained tester produces comparable results.

It connects to an intake form and admin console I built, so a client moves from intake to baseline testing to retest without anyone re-entering data. Same principle as the clinical platform: one entry, one source of truth.