SaaS vs Custom

Eighty-bed residential aged care facility (Queensland, Aged Care Quality Standards compliance, 45 staff, 160 residents, AN-ACC funding model, $8.2M annual revenue): Procura Care Management System (market legacy in AU aged care, $120k setup + $3.2k/month = $58.4k/year running cost, Windows-only, zero API, zero mobile app). Monday morning: resident Doris Campbell (age 89, dementia, ACQS high care, family on Sunshine Coast 2 hours away) falls in bathroom (2:15pm, staff member Susan finds her on floor). Susan calls manager Tom (incident occurred, Doris alert, no apparent injury but confused, risk assessment needed). Tom comes (assesses Doris: no bones broken, confusion post-fall, risk of head injury, document incident required). Tom hand-writes incident report (paper form: date, time, resident name, incident type "fall in bathroom", location, witness, description "Doris slipped on wet floor near shower", injuries "no visible bleeding, resident confused post-incident", action taken "resident moved to lounge, vital signs checked, family notified by phone"). Tom file: incident report in folder (Procura doesn't have incident module, paper only). Family call: Tom calls Doris's son Brian (overseas time zone, call missed, Tom leaves voicemail "Doris had a fall, she's okay, call me back"). Brian calls Tom 6 hours later (misses call again, calls back 2 hours later, conversation "My mum fell? Why didn't you email me? Is she in hospital?" = alarm, inadequate communication). Facility liability: Tom didn't document time of family notification (if incident escalates, liability exposure, "did you inform family promptly?"). Falls pattern: Tom now worries (Doris = 3rd fall in 4 weeks, pattern emerging, root cause unknown: dementia + bathroom hazard, or medication side effect, or inadequate supervision?). Tom checks Procura (no incident analytics, can't see fall pattern). Tom recalls manually (Doris fall 1: Week 1 bathroom, Doris fall 2: Week 3 hallway, Doris fall 3: Week 4 bathroom). Tom suspects: bathroom hazard (wet floor). Tom recommends: install non-slip mats in bathrooms (facility spends $1.2k on mats). Doris falls again Week 5 (non-slip mat installed, but fall still occurs = bathroom hazard not root cause). Root cause: Doris's blood pressure medication increased Week 3 (doctor changed dose), side effect = dizziness, causes falls. Tom never correlated medication change + fall pattern (no data system, manual analysis impossible). Medication round verification: current process. Care worker Sarah (morning medication round, 08:00). Sarah pushes medication trolley (160 resident medications on card file, organized by room number). Sarah enters room 12 (Doris Campbell). Sarah reads Procura screen (medications: metformin 500mg tab × 2/day, amlodipine 5mg tab × 1/day, donepezil 10mg tab × 1/day = 3 tablets for Doris this morning). Sarah opens medication drawer (pulls metformin bottle, takes 2 tablets, gives to Doris with water). Sarah marks Procura: "metformin signed off" (Sarah initial + time logged 08:03am). Sarah gives amlodipine (1 tablet). Sarah marks Procura: "amlodipine signed off" (08:05am). Sarah gives donepezil (1 tablet). Sarah marks Procura: "donepezil signed off" (08:07am). Doris swallows (Sarah moves to room 13). Actual: Sarah distracted, didn't confirm Doris swallowed medications (Doris spat out amlodipine into cup, kept under pillow). Procura logged: "amlodipine given" (false). Doris blood pressure unmedicated → week later, Doris blood pressure spike (staff notice dizziness), manager investigates (Doris says "I spit out the white tablet, didn't like it"). Damage: 1 week unmedicated → high blood pressure complication risk → heart attack risk, stroke risk. Procura audit: says all medications given (no barcode, no photo, no confirmation swallowed = unreliable). Incident escalates: family complaints, Aged Care Quality Standards (ACQS) audit finds "medication administration not verified, risk of under-medication detected via clinical review"). Facility cited: "Medication round verification inadequate." Fine: $15k. Staff rostering: current process. Manager Tom (rostering 45 staff across 3 shifts: morning 6am–2pm (12 staff), afternoon 2pm–10pm (12 staff), night 10pm–6am (12 staff), 9 relief staff available for cover). Week 1: morning shift Susan (6am start, usual shift 6am–2pm = 8 hours). Tom calls Susan Friday afternoon "Can you work Saturday morning?" Susan agrees (Saturday morning shift = 8 hours @ weekend rates = 1.5× pay = $36/hour × 8 hours = $288 Saturday shift). Monday: Tom manually updates roster (writes Susan on Saturday). Tuesday: Tom realizes (Susan told to check Award rates, she's entitled to penalty rates for weekend = 1.5× base pay). Tom unsure: "Is it 1.5× or 2× for Saturday?" Tom looks at Award (Fair Work Aged Care Award, state-specific penalty rates, complex rules). Tom guesses: "1.5× base, I think." Tom doesn't adjust payroll (Susan gets base pay Saturday, should get penalty rate). Sarah (afternoon staff, 2pm start): Tom schedules Sarah morning shift Saturday (Sarah says "I can't, I have kids to drop off"). Tom schedules Sarah anyway (Sarah doesn't show up Saturday, emergency shift cover needed, Tom works shift himself, overtime 8 hours + no break = exhausted, patient safety risk). Payroll: Tom manually compiles roster (45 staff × 2 weeks of shifts = 90 lines). Tom enters into payroll spreadsheet (errors: Susan Saturday paid base rate not penalty = underpay $144, 2 other staff similarly underpaid). Tom submits payroll to accountant. Accountant signs off (doesn't double-check Award rates). Sarah (who didn't work Saturday): payroll shows worked Saturday 8 hours (Tom forgot to remove her, Sarah gets paid for no-show). Payroll errors: underpay 3 staff ($432 total), overpay Sarah ($288 total) = wage disputes month later (Staff: "I'm underpaid." Tom: "Award rates are complex, I didn't calculate correctly." Facility: pays arrears, bad feelings). AN-ACC funding: current process. Facility funded via AN-ACC (Aged Care National Funding Model). Residents in 5 care categories: (1) Basic Care, (2) Low Care, (3) High Care, (4) Complex Care, (5) Specialist Dementia Care). Funding per resident per day: Basic $120/day, Low $180/day, High $260/day, Complex $380/day, Specialist $420/day. Facility census: 160 residents. Current distribution (Tom's best guess): Basic 20, Low 40, High 60, Complex 30, Specialist 10 = total daily funding $26,800 = annual $9.78M (but facility only charges $8.2M, underfunding). Tom submits AN-ACC claim (annually): estimated census (December: 160 residents as above). AN-ACC processes claim → facility paid $9.78M funding. Reality: March reassessment. Resident allocation changes. Betty (High Care 6 months, now improving, mobility increasing) → downgraded to Low Care (funding drops $260 → $180/day = $80/day loss). Tom doesn't update Procura (facility keeps Betty in "High Care" in system). Betty funds facility as High Care (incorrect), AN-ACC overpays. Year-end audit: AN-ACC finds (Betty should be Low Care, facility received overpayment $29.2k over 365 days = overpay). AN-ACC demands refund: $29.2k. Facility doesn't have reserve (cash flow tight), forced to pay. Reverse: Richard (Low Care 6 months, now declining, requires higher supervision) → upgraded to High Care (funding increases $180 → $260/day = $80/day gain). Tom doesn't update Procura (facility still bills Richard as Low Care). Facility underfunded (1 month = $2.4k loss × 12 months = $28.8k annual shortfall). Facility discovers year-end (AN-ACC audit: "Richard should be High Care, facility underfunded $28.8k"). Facility can't claim retroactively (too late). Revenue loss: $28.8k. Family communication: current process. Doris's family (son Brian, daughter Sophie): facility policy = monthly printed newsletter. Newsletter: "June Highlights: Garden BBQ was lovely, 45 residents attended, activities included bingo, gardening, music. Medication review underway. Staff changes: 2 new care workers joined." Newsletter printed (generic, no Doris-specific updates). Sophie worried: "What's Doris doing? Is she engaged? Is she eating well? Any incidents?" Sophie calls Tom (facility manager). Tom: "Doris is doing well, she's in the activity lounge, she likes bingo." Sophie: "Can I see a photo?" Tom: "We don't send photos, you'd have to visit." Sophie: "Can you email me a weekly update?" Tom: "I can try, but I'm too busy, maybe monthly." Sophie doesn't get updates (she's 2 hours away, can't visit weekly). Sophie stressed (is Doris okay? No idea). Incident occurs (Doris falls), Tom calls Brian (voicemail, no follow-up email, Brian learns hours later via phone tag). Family frustration: "We pay $8k/month, can't even get weekly updates?" Compliance exposure: ACQS Standard 2 (Ongoing assessment and planning with consumers) requires "regular family communication, incident reporting to family within 24 hours". Facility partially non-compliant (family communication irregular, incident reporting delayed via phone). ACQS audit: flags (communication plan inadequate). Friction total: family communication manual + no incident alerts = family frustration, compliance risk. Falls/incident reporting: manual + no pattern detection = preventable injuries undetected. Medication verification: pen-on-paper + no barcode/photo = undiscovered medication non-administration. AN-ACC assessment: outdated + no tracking = funding category changes missed = $28.8k–$29.2k annual variation risk. Staff rostering: manual + Award rate confusion = underpayment/overpayment disputes, ACQS compliance risks (inadequate supervision). **Total: $350k+ annually (revenue loss + compliance fines + wage disputes + liability).** Manager Tom evaluates: custom aged care add-on software ($85k build + $6.2k/year ops).

Five Custom Features That Layer Above Procura Care Management

1. Family Communication Portal with Real-Time Updates, Photo Sharing, Incident Alerts, Activity Logs — Digital Family Dashboard, Daily Resident Updates, Photo Gallery, Instant Incident Notifications, Emotion Check-Ins, Visit Scheduling, Privacy-Compliant, ACQS Audit Trail

Current: family communication manual (monthly printed newsletters, no photos, no incident alerts, poor family engagement). New system: family portal. Setup: web + mobile app, HIPAA/Privacy Act compliant. Doris Campbell family (son Brian, daughter Sophie): both download portal app. Portal home: Doris photo (updated daily), status card "Doris is well today, mood happy, appetite good". Daily update: Sophie opens portal (Tuesday morning). Dashboard: "Doris Tuesday: Attended morning bingo (won 2 games!), enjoyed lunch (beef stew, ate 80%), afternoon rest, active evening (watched Strictly, laughed lots)". Photo gallery: 3 photos (Doris at bingo table smiling, Doris with volunteer gardener, Doris lunch plate). Sophie shares with Brian (forwards portal link, Brian logs in same app). Brian feels: "Mum is engaged, eating well, happy — that's what I needed to know." Emotion check-in: facility staff (after activity, staff asks Doris "How are you feeling? Happy, okay, sad?"). Doris says "Happy". Staff taps app: "Doris happy today" (logged 11:00am with staff name). Portal shows: emotional trend (Doris happy 18 days/month, okay 10 days, sad 2 days = overall positive mood, trend tracked). Sophie interprets: "Mum's mood is stable, activities working well." Incident alert: Doris falls Wednesday (2:15pm). Susan (staff member) documents: app incident report (resident name, time, location bathroom, description "fall on wet floor", injuries "none apparent", response "vital signs checked, resident moved to lounge"). Tom (manager) reviews (incident flagged MEDIUM severity, fall + potential confusion = monitor). App sends Brian + Sophie (SMS + email notification "Doris had a fall Wednesday 2:15pm in bathroom. She's okay, vital signs normal. Manager Tom has documented incident. [Link to full report]"). Brian: notified within 15 minutes (vs 6 hours via voicemail in old system). Brian calls Tom (informed conversation: "What happened? What did you do?" Tom explains via phone, shows incident detail in app during call). Tom: "See in the app: incident logged, vital signs documented, I recommend monitoring bathroom safety.") Brian: "Should we take her to hospital?" Tom: "Vital signs okay, consciousness normal, I'm monitoring closely. Let's review tomorrow."). Brian: "Update me tomorrow." Tom: "Yes, I'll send update in app by 9am." Sophie: calls Tom also (same details). Sophie reassured (incident documented, monitored, family involved). Visit scheduling: Sophie wants to visit (portal has calendar). Sophie books: "Friday 2–4pm visit". App notifies Tom (visit scheduled). Tom confirms: "Friday 2–4pm, Doris in lounge, activities paused during visit"). Tom reminds staff: "Sophie visiting Friday afternoon, Doris to lounge by 2pm." Staff prepares (Doris groomed, lounge ready, calming music). Sophie arrives (Doris remembered visit, good visit experience). Scheduling visibility: other family members can avoid double-bookings (multiple family visiting same day = chaotic). Tom prevents: excessive visits that tire residents (app tracks visit pattern, recommends "3 visits/week optimal for dementia residents to maintain routine"). Privacy compliance: portal HIPAA-compliant (authentication required, IP logging, encrypted end-to-end). Brian + Sophie can access Doris data only (no access to other residents). Audit trail: every photo, update, incident notification logged (timestamp, staff who accessed, family who viewed). ACQS audit: facility shows (family communication documented, incidents reported <24 hours, communication plan active). Compliance verified. **Value: family engagement 90%+ (vs current 40%), incident reporting ACQS compliant <24 hours, preventable incidents caught early via family feedback (photo shows resident safety concern), family satisfaction 95%, zero family disputes from "we didn't know". Estimated compliance + satisfaction + litigation prevention = $25k/year.**

2. AN-ACC Funding Assessment Tracking and Category Change Management — Resident Care Category Monitoring, Funding Calculation Real-Time, Indexation Tracking, Category Change Alerts, Compliance Justification, Revenue Forecasting, Audit Trail for AN-ACC Claims

Current: AN-ACC assessment outdated + no tracking = care category changes missed = $28.8k–$29.2k annual revenue variation. New system: AN-ACC tracking platform. Setup: 160 residents in care categories (Basic, Low, High, Complex, Specialist Dementia). System monitors each resident's needs (mobility, cognition, behavioural changes, medical complexity). Betty's scenario: currently High Care (funding $260/day = $94.9k/year). March: Betty's condition improves (mobility increasing, less supervision required, toileting independent, medication stable). Care team: assesses Betty (meets Low Care criteria, upgrade not needed). System flags: "Betty eligible for care category downgrade from High to Low". Manager Tom reviews app (system shows: "Betty declining High Care supervision, meets Low Care criteria, recommend assessment review"). Tom initiates: formal reassessment (system prompts assessment date, coordinates with aged care assessor). Assessor reviews Betty: confirms Low Care appropriate (funding downgrade necessary). Tom updates system: "Betty moved to Low Care, effective 2 April 2026". System calculates: funding change = $260 → $180/day = -$80/day from 2 April forward. System forecasts: funding impact April–December ($80 × 273 days = $21.84k less funding for Betty in remainder of year). Tom checks: impact on facility revenue (Betty alone, forecasted impact tracked). System also tracks: other residents in transition (Richard assessed Low → High, +$80/day; Margaret cognitively declining, recommends complex care assessment). Revenue forecast: facility manages care category mix proactively (before surprise AN-ACC audit). Indexation tracking: AN-ACC applies annual indexation (funding amounts increase each July 1st). Current: system outdated, Tom doesn't know July indexation amount. New system: tracks indexation schedule (July 1 indexation posted by AN-ACC, system auto-updates funding rates). Tom checks portal (July 1, app shows "Indexation applied: funding rates increased 3.1% for FY2027"). System recalculates: all 160 residents at new rates. Tom forecasts: annual revenue increase $254.6k (160 residents × average $260/day × 3.1% × 365 days). Financial planning: Tom budgets (pay rise allocations, capital improvements based on indexed revenue). Resident category change documentation: system maintains assessment records (each category change documented, date, reason, assessor name). An-ACC compliance: facility required to track category changes (system generates compliance report). ACQS audit: facility shows (180-day history of category changes, all documented, revenue claims match category data). Audit trail: facility protected (every change documented, justified, timestamped). Revenue visibility: facility tracks (160 residents × funding tier distribution = daily revenue forecasted, monthly revenue variance analyzed). Facility discovers: March Richard underfunded, immediately requests AN-ACC adjustment (backdated reimbursement approved, $28.8k recovered = 0 loss vs current system). **Value: category change tracking = zero revenue leakage ($28.8k recovery vs current loss), indexation visibility = budget forecasting confidence, AN-ACC audit compliance = zero fines (current $15k risk eliminated). Payback: 8 weeks.**

3. Medication Round Verification with Barcode + Photo Audit Trail — Digital Medication Administration Record (MAR), Resident Barcode Scanning, Medication Barcode Verification, Photo Confirmation Swallowed, Real-Time Alerts for Missed/Refused Medications, ACQS Compliance Logging, Medication Error Prevention

Current: medication verification pen-on-paper, no barcode, no confirmation swallowed = undiscovered medication non-administration. New system: digital medication round with barcode + photo. Morning medication round (Sarah, 08:00). Sarah uses trolley tablet (medication app loaded). Sarah scans Procura resident barcode (room 12 = Doris Campbell). App displays: medications for Doris this morning (metformin 500mg × 2, amlodipine 5mg × 1, donepezil 10mg × 1). Sarah scans metformin bottle (barcode on bottle matches system-expected medication = verified). Sarah gives Doris 2 metformin tablets. Sarah takes photo (Doris holding tablets, about to swallow, timestamp 08:03am). App processes photo (verifies resident identity via facial recognition, confirms tablets in hand, documents swallow moment). Sarah taps "Confirm given" (app logs: metformin given, 08:03am, Sarah verified, photo attached). Doris swallows (visible in photo). Sarah then gives amlodipine (scans bottle, gives tablet, takes photo, logs). Photo shows: Doris holds amlodipine (white tablet), puts in mouth, drinks water. App confirms: medication administered, timestamp 08:05am, photo audit trail. Donepezil follows (same barcode + photo + confirmation process). Medication round complete (3 medications, 3 barcodes scanned, 3 photos captured, 3 confirmations logged = audit trail 100% documented). Alternative scenario: Doris spits out amlodipine (post-photo). Photo shows: amlodipine in Doris's mouth (Sarah didn't see spit-out because she's moved to next resident). 30 mins later, staff member finds amlodipine under pillow (alerts Sarah). Sarah logs in app: "Amlodipine refused — tablet found under pillow, resident didn't swallow". App alerts Tom (manager): "Amlodipine refused 08:05am, Doris Campbell, undiscovered until 08:35am". Tom checks: photo evidence (amlodipine in mouth, but spit-out before swallow confirmed). Tom calls doctor (blood pressure medication missed, Doris needs replacement dose or schedule adjustment). Doctor changes plan: "Give amlodipine with lunch instead, easier to monitor swallow". Tom updates system: medication administration changed (amlodipine moved to lunch, 12:30pm, noted "difficult swallow, monitor closely"). System alerts: lunch care worker (Sarah) "Amlodipine with lunch, monitor Doris swallowing closely, take photo confirmation". Lunch round: amlodipine given (photo shows Doris swallowing visibly, confirmed logged). Medication error prevention: system catches missed/refused medications (audit trail prevents silent undiscovery). Medication trends: system tracks (Doris = 2 refused medications past month, pattern emerging, suggests swallowing difficulty, recommend swallowing assessment). Tom requests swallowing assessment (therapist reviews, finds mild dysphagia). Therapist recommends: crush tablets, mix with yogurt. Facility updates system (Doris medication administration method changed to crushed). Next round (staff crush amlodipine into yogurt, photo shows Doris eating yogurt with medication). Compliance verified (medication given, confirmed swallowed, zero future refusals). ACQS audit: facility shows (medication administration 99.8% verified via photo, 100% barcode matched, medication errors caught <30 mins, corrected proactively). Audit trail: 6-month record of every medication administered, barcode matched, photo timestamp. Facility cited: "Medication administration excellence, zero serious medication incidents". **Value: medication error prevention (estimated 1–2 serious medication incidents prevented/year = $50k litigation cost avoidance), ACQS compliance (zero fines), staff confidence (error-free auditable process). Payback: 6 weeks.**

4. Falls & Incident Reporting with Pattern Detection, Root-Cause Analysis, Environmental Hazard Tracking — Digital Incident Form, Automatic Pattern Detection, Environmental Hazard Assessment, Root-Cause Recommendations, Staff Safety Alerts, Preventive Action Tracking, ACQS Incident Audit Trail

Current: falls/incident reporting manual + no pattern detection = preventable injuries undetected. New system: incident analytics platform. Doris falls (Week 1, Thursday, 2:15pm, bathroom, "slipped on wet floor near shower"). Susan documents: app incident form (resident, date, time, location, incident type fall, description, injuries assessed none serious, response "moved to lounge, vital signs checked"). System logs (incident 1 recorded). Week 3: Doris falls again (Monday, 3:40pm, hallway, "didn't use walker, tripped on carpet edge"). Staff documents (incident form filled). System logs (incident 2). Week 4: Doris falls (Friday, 1:50pm, bathroom again, "slipped on wet floor"). System detects: pattern alert (Doris 3 falls in 4 weeks, frequency high, locations alternating). System flags: "HIGH FALL RISK — Doris Campbell, 3 incidents in 28 days, pattern suggests environmental hazard + mobility concern". Manager Tom reviews app (system shows incident timeline: Week 1 bathroom, Week 3 hallway, Week 4 bathroom). System recommends: "Environmental assessment: bathroom wet floor hazard, slippery surfaces. Mobility assessment: walker not used Week 3. Medication review: blood pressure medication increased Week 3 (amlodipine dose change). Correlation: medication change → dizziness → falls post-Week 3. Recommendation: (1) Install non-slip mats bathroom (addresses environmental), (2) Medication review with doctor (addresses side effect), (3) Mobility training (walker use)"). Tom initiates: (1) non-slip mats purchased, installed immediately, (2) doctor called, medication review, amlodipine dose reduced back to original, (3) care worker retrains Doris on walker use, bathroom supervision increased. System tracks: preventive actions logged (non-slip mats installed, doctor note documented, walker training session recorded). Follow-up: Week 5 onward, Doris has no more falls (medication change corrected, bathroom safer, walker used). System trend: Doris fall rate drops to zero (success documented). Trend analysis: facility system now tracks (across all 160 residents, incident patterns). System report monthly: "Top incident types: falls 45% (23 incidents), medication refusals 18% (9 incidents), behavioural incidents 22% (11 incidents), other 15% (8 incidents)". Facility analysis: falls disproportionate (45%), facility investigates (common factors: bathroom environment, medication side effects, insufficient supervision). Facility implements (across 160 residents): (1) bathroom non-slip mats all 60 bathrooms ($8k investment), (2) medication review program (all residents on BP/dizzy-inducing meds reviewed quarterly), (3) supervision ratios adjusted (staff-to-resident ratio increased during high-risk times 3pm–4pm peak fall hour). Fall rate facility-wide drops (Year 1 = 47 falls, Year 2 = 22 falls = 53% reduction). Incident environmental assessment: system tracks environmental hazards (carpet edges, loose rugs, bathroom wet floors, corridor lighting). Facility prioritizes (repairs logged in system). Environmental audit: system maps (all 60 bathrooms inspected, environmental hazards documented, repairs tracked). Staff safety alerts: if incident suggests staff injury risk (heavy resident fall = lifting injury for staff), system flags (staff injury prevention plan activated). Resident safety alerts: if incident frequency suggests resident at imminent serious-harm risk (10+ falls/month despite interventions), system recommends (hospital assessment, higher level of care). Preventive action tracking: system maintains (corrective action log, completion date, effectiveness check post-action). ACQS audit: facility shows (incident pattern analysis, preventive actions documented, incident reduction measured, zero preventable incidents left unaddressed). Audit trail: 12-month incident record, all root causes analyzed, all actions tracked. **Value: incident prevention (from 47 falls → 22 falls = 53% reduction = 25 prevented falls/year = reduced injuries, reduced staff injury, improved resident safety, reduced liability $35k/year). ACQS compliance + incident trend analysis. Payback: 10 weeks.**

5. Staff Roster + Aged Care Award Rates Compliance — Digital Roster Scheduling, Automated Award Rate Calculation, Penalty Rate Compliance (Weekend, Late Night, Public Holiday), Shift Swap Management, Compliance Reporting, Payroll Integration, Fatigue Risk Management, ACQS Staffing Compliance

Current: staff rostering manual + Award rate confusion = underpayment/overpayment disputes, ACQS compliance risks. New system: roster + Award compliance platform. Setup: 45 staff, 3 shifts (morning 6am–2pm, afternoon 2pm–10pm, night 10pm–6am), AN Award state-specific rates. Susan (care worker): Tom needs Saturday morning coverage. Tom opens roster app. App shows: Susan current shift pattern (Mon–Fri morning 6am–2pm = weekday ordinary rate $24/hour). Tom considers: Saturday shift (weekend rate = 1.75× ordinary = $42/hour). System calculates: Susan Saturday 8 hours = $336 (vs weekday $192 = weekend premium $144). Tom checks: roster availability. App shows Susan available Saturday (confirmed previous Friday). Tom adds: Susan Saturday 6am–2pm shift. App notifies Susan (SMS "You're scheduled Saturday morning. Award rate 1.75× ordinary ($42/hr). Reply confirm/decline."). Susan confirms (she needs extra income). Saturday: Susan works 6am–2pm (8 hours). Payroll auto-calculates: Susan Saturday pay = 8 hours × $42/hour = $336 (vs base $192). Tom never manually calculates (system handled). Sarah (care worker): Tom needs Saturday morning. Sarah has childcare conflict (can't work). Tom removes Sarah Saturday (roster updated, Sarah's schedule back to normal). Tom finds alternative: relief staff member Pete (available Saturday). Pete: normally works Friday nights (10pm–6am night shift = night loading 1.4× ordinary = $33.60/hour). Tom schedules Pete Saturday morning (Pete's Saturday = Saturday loading 1.75× ordinary = $42/hour, NOT night loading = higher rate applies). System calculates: Pete Saturday = $42/hour (system defaults to correct loading rate, no manual confusion). Payroll compilation: Tom compiles 2-week roster (45 staff × 14 days = 630 shifts). Payroll system auto-calculates: each shift (shift time → Award rate lookup → automatic calculation). No manual entry. Payroll errors: eliminated (system always applies correct Award rate). Payroll submission: Tom submits roster to accountant (system shows: total payroll cost forecast $67,400 for 2 weeks, broken down by rate type: ordinary 340 hours @ $24 = $8,160; weekend 48 hours @ $42 = $2,016; night 42 hours @ $33.60 = $1,411.20; other penalties = $1,812.80). Accountant reviews (breakdown clear, rates verified against Award, no disputes). Shift swap management: care worker Julie (Monday morning shift, wants to swap with Emma for Friday night). Julie requests in app (swap request: Julie Tuesday morning ↔ Emma Friday night). System checks: Julie Tuesday morning ordinary rate $24, Emma Friday night ordinary rate $24 (same rate, no penalty issue). System approves (both staff confirmed). Roster updated (Julie Friday night, Emma Tuesday morning). Fatigue risk management: Tom notices (night shift staff worked 5 nights straight past week). System flags: "Fatigue risk — 5 consecutive nights without break, fatigue policy recommends max 3 nights consecutive". Tom immediately schedules: night staff member off 2 days (priority relief). System tracks (fatigue risk actively managed, ACQS standard 8 (governance) requires "sufficient staffing, fatigue management"). ACQS compliance reporting: system generates monthly report (staff ratios: 45 staff ÷ 160 residents = 1:3.56, exceeds ACQS minimum 1:4 requirement = compliant). Award compliance: system shows (100% shifts at correct Award rates, zero underpayment, zero overpayment). Staffing trends: system tracks (turnover rate, sick leave patterns, overtime trends). Tom monitors (high turnover suggests fatigue, low wages). Tom considers (salary increase 2% for staff retention). Tom runs forecast (extra payroll cost = $20.8k/year for 2% increase across 45 staff). Tom decides: invest in increase (retention + quality improve). Payroll integration: system syncs with accounting software (no manual re-entry, payroll processed error-free). **Value: Award rate compliance 100% (zero disputes), payroll accuracy (zero underpay/overpay corrections), fatigue management (zero burnout-related incidents), ACQS compliance reporting (staffing audit trail), estimated compliance + payroll efficiency + staff retention = $18k/year cost savings + $12k wage dispute avoidance + $15k turnover cost reduction. Payback: 9 weeks.**

Australian Aged Care Context: ACQS, AN-ACC, Aged Care Code, Regulatory Compliance

**Aged Care Quality Standards (ACQS)** — Australian regulatory framework requiring residential aged care facilities to meet 8 standards: (1) Consumer Dignity and Choice, (2) Ongoing Assessment and Planning with Consumers, (3) Personal Care and Clinical Care, (4) Safe and Hygienic Environment, (5) Restrictive Practices, (6) Feedback and Complaints, (7) Secure, Confidential, Accurate, Complete and Accessible Information Management, (8) Governance and Management. Breaches → fines ($25k–$500k), suspension risk, reputational damage. **AN-ACC (Aged Care National Funding Model)** — Commonwealth funding for residential care via care category allocation (Basic, Low, High, Complex, Specialist). Residents assessed annually, care category assigned, facility funded per diem. Category changes require documentation, incorrect categorization = funding recovery. **Aged Care Code of Conduct** — mandatory for all staff, requires dignity, respect, informed consent, privacy, professional boundaries. Violations investigated, staff disciplinary action possible. **Procura & AlayaCare Legacy** — market entrenched software (appointment book, resident records, medication tracking, zero API). 60% of AU aged care facilities use Procura, 25% use AlayaCare. Customization: minimal. Replacement: high risk (patient data migration, regulatory approval, retraining staff). **Medication Administration Records (MAR)** — legal requirement, must document every medication given (resident, drug, dose, time, staff name, signature). Paper MAR = error-prone, illegible signatures, missing entries. Digital MAR with barcode/photo = audit trail, error prevention, ACQS compliance. **Falls Prevention** — most common serious incident in aged care (cost per fall: $10k–$50k medical + litigation). ACQS Standard 4 requires environmental assessment + falls prevention plan. Facilities track falls, analyze patterns, implement preventive actions. **Staff Rostering Compliance** — Fair Work Aged Care Award mandates specific shift rates (ordinary weekday, weekend loading 1.75×, night loading 1.4×, public holiday 2× or time-in-lieu). Breaches = wage underpayment claims (staff can claim back pay with interest + penalties = costly). ACQS Standard 8 requires adequate staffing, fatigue management. Understaffing → safety risk, ACQS audit failure.

Six FAQs

How does family communication portal improve engagement and meet ACQS compliance for incident reporting?

Current: monthly printed newsletters, no incident alerts. Doris falls → facility calls family 6 hours later via voicemail → family learns hours later = alarm, ACQS non-compliant (standard 2 requires timely family communication). New system: family portal. Incident occurs → staff document immediately (app form, 2 minutes). Manager approves → SMS + email to family (within 15 minutes, not 6 hours). Family opens app (sees incident detail, photos, action taken, ongoing monitoring). Family feels: informed, reassured, heard. ACQS audit: facility shows (incident reporting timeline logged, family notifications documented <24 hours, communication plan active). **Value: family satisfaction 95%, ACQS compliance verified, compliance fine $0 (current $15k risk eliminated), preventable incidents caught via family feedback (photo shows resident concern). Payback: 8 weeks.**

How does AN-ACC funding assessment tracking prevent revenue leakage from missed category changes?

Current: AN-ACC assessment outdated, care category changes untracked. Betty High Care (1 year, should be Low Care based on improvement). Facility unknowingly bills High Care → year-end AN-ACC finds error → facility refunds overpayment $29.2k. Richard Low Care (should be High Care) → facility bills Low Care → facility loses $28.8k. Total annual variation risk: $50k+. New system: assessment tracking. System monitors each resident's care needs (mobility, cognition, supervision). System alerts: "Betty eligible for category downgrade". Manager reviews, initiates reassessment, updates system. System forecasts: funding impact. Manager proactively manages revenue. Year-end: AN-ACC audit shows (all residents correctly categorized, zero over/underfunding, revenue claims match resident needs). Facility gains: zero surprise refunds, zero revenue loss, predictable funding. **Value: revenue protection $28.8k–$29.2k/year, audit efficiency, financial forecasting confidence. Payback: 12 weeks.**

How does barcode + photo medication verification prevent medication administration errors?

Current: pen-on-paper MAR, no barcode, no confirmation swallowed. Doris spits out amlodipine → medication not given → blood pressure unmedicated 1 week → complication risk. Facility doesn't discover (no audit trail). New system: barcode + photo MAR. Sarah scans medication barcode (matches system expected drug). Sarah gives tablet, takes photo (Doris holding + swallowing visible). App logs (timestamp, staff, photo audit trail). If resident refuses/spits out (staff notes in app "Refused"). Manager alerted immediately (Doris refused amlodipine, blood pressure medication missed, recommend doctor review). Doctor adjusts plan (give with lunch instead). Future doses monitored (photo confirms swallow). **Value: medication error prevention (1–2 serious undiscovered medication errors prevented/year = $50k litigation cost avoidance), ACQS compliance (medication administration 99.8% verified), staff confidence. Payback: 6 weeks.**

How does incident pattern detection identify preventable falls and root causes?

Current: falls reported manually, no pattern analysis. Doris falls 3 times in 4 weeks, root cause unknown. Non-slip mats purchased (wrong intervention, root cause was medication side effect, falls continue). New system: pattern detection. System flags: "Doris 3 falls, pattern = environmental + medication". System recommends: "Install non-slip mats (bathroom hazard), reduce amlodipine dose (dizziness side effect), increase walker supervision". Manager implements (all 3 interventions). Falls stop. Facility-wide: system detects (falls 45% of all incidents, common factors bathroom + peak time 3–4pm). Facility implements (non-slip mats all bathrooms, supervision increase 3–4pm). Fall rate drops 53% (Year 1 47 falls, Year 2 22 falls). **Value: preventive incident reduction 25 falls/year prevented = reduced injuries, reduced liability $35k/year, ACQS compliance. Payback: 10 weeks.**

How does automated Award rate calculation eliminate payroll disputes and ensure Fair Work compliance?

Current: manual rostering, Award rate confusion. Tom guesses: Susan Saturday 1.5×? Or 1.75×? Susan underpaid $144 (Tom thought 1.5×, actually 1.75×). Month later: Susan claims back pay. Facility pays $144 arrears + interest + bad feelings. 3 other staff similarly underpaid ($432 total). New system: automated Award calculation. Tom schedules Susan Saturday morning. System auto-looks up (Saturday rate 1.75× for this state). System shows: Susan $42/hour (not $36/hour). Tom never calculates (system always correct). Payroll auto-calculates (45 staff × 14 days, every shift at correct rate). Tom submits payroll (no disputes, no back-pay claims). **Value: Award rate compliance 100%, payroll accuracy (zero disputes), wage claim avoidance $432/incident, ACQS compliance reporting (staffing audit trail). Payback: 9 weeks.**

How do custom add-ons complement Procura without replacing it?

Procura is immovable: resident records, medication chart, rostering backbone, ACQS audit trail. Full replacement = insane risk (lose resident data, lose medication history, regulatory investigation, fines $100k+). Aidxn approach: custom add-ons layer above Procura (family portal reads resident names from Procura, posts updates + incidents to family dashboard; AN-ACC tracking reads resident assessments from Procura, monitors category changes, tracks funding; medication round system writes verification photos to Procura MAR notes, syncs back; incident reporting reads resident flags from Procura, analyzes patterns, recommends actions; roster system reads staff + shift data from Procura, applies Award rates, syncs payroll). Best of both: Procura handles resident records + medication chart + rostering backbone (immovable), custom tools unlock family engagement + AN-ACC revenue optimization + medication safety + incident prevention + Award compliance (differentiation). **Result: Procura stays, custom tools win family satisfaction + revenue protection + medication safety + incident prevention + payroll compliance.** No replacement needed.

The Bottom Line

Eighty-bed residential aged care facility (Queensland, 45 staff, 160 residents, AN-ACC funded, $8.2M revenue): Procura locked-in ($58.4k/year, zero engagement tools, zero funding tracking, zero medication verification, zero incident analytics, zero Award compliance automation). Friction: family communication manual (monthly newsletters, no incident alerts, ACQS compliance risk), AN-ACC assessment outdated (care category changes missed, $28.8k–$29.2k annual funding variation), medication rounds pen-on-paper (undiscovered medication non-administration, 1–2 serious errors/year, $50k litigation cost). Falls + incident reporting manual (preventable falls undetected, 25+ falls/year × $10k cost = $250k annual liability). Staff rostering manual (Award rate disputes, 3–5 wage claims/year, ACQS staffing compliance unclear). **Total: $475k+ annually.** Custom aged care add-on software ($85k build + $6.2k/year ops): family portal (engagement + ACQS compliance = $25k value), AN-ACC tracking (revenue protection $28.8k–$29.2k/year), medication verification (error prevention $50k litigation avoidance), incident analytics (fall reduction 53% = $35k safety + liability value), staff roster + Award automation (payroll accuracy + compliance = $18k + $12k + $15k value). **Year 1 value: $188.2k** (conservative estimate, doesn't include resident safety improvements or staff retention). Payback: 5.5 months (custom investment $85k ÷ $188.2k year 1 value = 0.45 years). Start custom aged care software if: (1) Procura or AlayaCare user (locked-in, no family engagement, funding tracking, medication verification, or incident analytics), (2) AN-ACC assessment lags (more than annual updates), (3) medication administration verification pen-on-paper, (4) falls + incident reports manual (no pattern analysis), (5) staff Award rate disputes quarterly, (6) ACQS audit findings on family communication or staffing. Reach out: book a time to discuss your facility size, resident mix, current friction points (family complaints, AN-ACC surprises, medication errors, falls, payroll disputes), staffing challenges, and revenue targets, or check platform pricing for a custom build quote.