HealthSync Care

An NDIS disability service provider managing 340+ participants across 3 regions was drowning in compliance paperwork and manual coordination. The entire operation ran on a mix of spreadsheets, shared drives, and a legacy system that hadn't been updated since 2018. Audits were a scramble, and care coordinators spent more time on admin than on actual participant support.

Participant plan management lived in individual spreadsheets. Each coordinator maintained their own files with no standardized format. When a coordinator went on leave, nobody could pick up their caseload without 2+ days of context gathering

Service booking and scheduling was done via phone and email. Coordinators manually matched participants with available support workers based on memory and a shared Google Calendar that was perpetually out of date

NDIS compliance reporting required pulling data from 6 different sources, cross-referencing participant plans, and manually calculating budget utilization. Each quarterly audit prep took 3 weeks of dedicated admin work

Budget tracking was reactive. Coordinators discovered participants had exceeded their plan budgets only when NDIS rejected claims. Average over-budget discovery lag: 4-6 weeks

Incident reporting was paper-based. Forms were filled on-site, physically delivered to the office, and manually entered into a spreadsheet. Critical incidents sometimes took 48+ hours to reach management

Staff credential tracking (Working with Children checks, first aid certifications, NDIS Worker Screening) was managed in a master spreadsheet. Expired credentials were caught during audits, not before they expired

The provider wasn't cutting corners. They were buried under a compliance framework that demanded precision from systems built for approximation.

I built a care management platform purpose-built for NDIS providers, handling participant plans, service coordination, compliance reporting, and staff management in a single system. Every feature designed around the question: "Will this survive an audit?"

Every participant's plan, budget, goals, and service history in one place.

✅ Structured plan records with NDIS line items, budget allocations, goal tracking, and review dates with automatic renewal reminders

✅ Real-time budget utilization tracking showing spend against each line item with projected exhaustion dates

✅ Plan transition workflows handling the handoff between expiring and new plans without service gaps

📊 Outcome: Over-budget discoveries dropped from 4-6 week lag to real-time alerts. Coordinators managing 40% more participants per caseload with structured plan views replacing spreadsheet hunting

Match the right support worker to the right participant, automatically.

✅ Availability-based scheduling matching participant needs (service type, location, language, gender preference) with qualified available support workers

✅ Shift management with automatic conflict detection, overtime tracking, and travel time calculations between participant locations

✅ Participant-worker relationship continuity tracking, prioritizing familiar workers for recurring services

📊 Outcome: Service booking time dropped from 25 minutes per appointment to 3 minutes. Participant-worker continuity improved 58%, directly impacting care quality scores

Audit-ready every day, not just during audit prep.

✅ NDIS claim generation with automatic line item matching, rate validation, and submission-ready export in NDIS bulk upload format

✅ Continuous compliance monitoring checking service delivery records against plan authorizations, worker qualifications, and NDIS Practice Standards

✅ Audit trail on every action: who changed what, when, and why. Immutable logs that satisfy NDIS Quality and Safeguards Commission requirements

📊 Outcome: Quarterly audit prep dropped from 3 weeks to 2 days. NDIS claim rejection rate reduced from 12% to under 2%. Zero compliance findings in the first post-launch audit

Critical incidents reach management in minutes, not days.

✅ Mobile incident reporting with structured forms, photo capture, and severity classification submitted from the field in real time

✅ Automatic escalation routing: critical incidents notify management immediately, standard incidents queue for review within 24 hours

✅ Incident trend analytics showing patterns by participant, location, service type, and time period for proactive risk management

📊 Outcome: Incident reporting lag dropped from 48+ hours to under 15 minutes. Management response time to critical incidents improved from next-day to under 1 hour

Never send an unqualified worker to a participant.

✅ Centralized credential registry tracking expiry dates for all mandatory certifications (WWCC, first aid, NDIS Worker Screening, driver's license)

✅ Automatic alerts at 90, 60, and 30 days before expiry with renewal workflow tracking

✅ Scheduling system blocks assignment of workers with expired or missing credentials, preventing compliance violations before they happen

📊 Outcome: Expired credential incidents dropped to zero. 100% credential compliance maintained continuously. Scheduling blocks prevented 23 potential compliance violations in the first quarter

Why I chose this stack and what tradeoffs I made.

PostgreSQL with row-level security for participant data — NDIS participant data requires strict access controls. Row-level security policies ensure coordinators only see their assigned participants, while managers see regional views. Audit logging captures every data access, not just modifications

Docker for deployment consistency — Healthcare compliance requires reproducible environments. Containerized deployment ensures staging and production are identical, and rollbacks are instant if a release introduces issues during business hours

AWS with Sydney region data residency — NDIS participant data must remain in Australia. All infrastructure deployed in ap-southeast-2 with no cross-region replication. S3 bucket policies enforce geographic data residency

Next.js with offline-capable PWA for field workers — Support workers operate in areas with unreliable mobile coverage. Service worker caching allows incident reports and service notes to be drafted offline and synced when connectivity returns. Zero data loss from coverage gaps