Maree-CareFlow - About & Full Feature Reference
Maree-CareFlow - what the product does. This is the customer-facing feature reference. If something here is not clear, or you want to see it working, ask us for a walkthrough.
About Maree-CareFlow
Maree-CareFlow is an Australian-built, proprietary allied health practice management platform designed specifically for NDIS registered providers, support coordinators, therapy practices, and multidisciplinary allied health teams. It brings together clinical documentation, billing, compliance, scheduling, AI-assisted reporting, and regulatory monitoring into a single integrated system purpose-built for the Australian healthcare landscape.
The platform is designed with zero tolerance for data loss, administrative errors, and billing non-compliance. Every feature is built around the real-world workflows of Australian therapists, case managers, and practice administrators - eliminating the friction of juggling multiple disconnected tools.
Who Maree-CareFlow is built for
| Role | Primary Use |
|---|---|
| Therapists / Practitioners | Scheduling, clinical notes, time entries, AI reports, KPI tracking |
| Case Managers / Support Coordinators | Client oversight, funding plans, goal tracking, injury scheme management |
| Practice Managers / Org Managers | Team KPIs, compliance monitoring, billing approval, funding requests |
| Billing / Finance Staff | Time entry approval, invoice batching, NDIS bulk submissions, payment tracking |
| Compliance Officers | Regulatory monitoring, compliance rule management, SDA standards |
| Super Admins | Organisation configuration, user management, integration settings |
Technical Overview
- Frontend: React 19 + TypeScript, Tailwind CSS, TanStack Query, Radix UI
- Backend: Python FastAPI + SQLAlchemy 2 (async) + Alembic + PostgreSQL 16 + Redis + Celery.
pgvector is optional: AI similarity search uses it where the server has it, and every install path works without it
- AI: your own provider. Local Ollama by default, so nothing leaves your
server; a practice that connects its own Anthropic key is making that choice itself, and the in-app disclosure is computed from what is actually configured. There is no automatic fallback from local to cloud
- Deployment: cPanel, Docker, or bare-metal Linux
- Data sovereignty: you host it, so the database, the documents and the
clinical record sit wherever you install it - for an Australian practice, in Australia. Two things are worth naming rather than leaving you to find them. Built-in telehealth uses the public Jitsi service (meet.jit.si) unless you point it at your own, so a video consultation on a stock install is carried by a service operated overseas; set TELEHEALTH_JITSI_SERVER to your own to keep it in the country. And the optional integrations you connect yourself - transcription, a cloud AI key, accounting, SMS - send data to those providers by design. Nothing else leaves the server
- Security: role-based access control, MFA support, full audit trail, and
AES-256-GCM encryption of the most sensitive columns at rest (identifiers, clinical narrative and contact details). Whole-disk or whole-database encryption is a property of the server you run it on, not something the application can supply
Complete Feature List (at a glance)
Every shipped feature with a one-line description, grouped by area. Detailed write-ups follow in the Feature Reference below.
Core clinical & client management
- Client & Participant Management - demographics, diagnoses, consent, NDIS plan + funding profiles, document vault, activity feed, plus a lifecycle stage machine (prospect -> pre_intake -> onboarding -> active, with on_hold / discharged) and a guided onboarding checklist per client.
- Practitioner Management - profiles, AHPRA + worker-screening + insurance credential tracking with expiry alerts and billing block on expiry.
- Calendar & Smart Scheduling - day/week/month views, conflict detection, RFC 5545 recurrence, telehealth, reminders.
- Clinical Supervision - supervisor-supervisee relationships and recorded supervision sessions.
- Document Management - secure per-client/practitioner file vault with categories, preview and download.
- Clinical Notes & Outcome Measures - SOAP/free-text notes, 22-domain progress ratings, standardised assessments, risk assessments, note lock + approval.
- Client Transfers - therapist-to-therapist handover with accept/decline, org-manager gated.
- Priority Waitlist, Holding Pool & Digital Intake - DB-backed priority queue and intake triage, plus durable public intake forms (submissions + signature persisted, reviewable, one-click convert-to-client) and a first-run organisation setup wizard.
- Participant Portal - participant self-service: schedule, funding balances, agreements, booking requests; plus a public complaint-lodgement page.
- External Case Manager (ECM) Portal - scoped portal for external case managers (referrals, clients, progress, messaging).
Billing, funding & NDIS plan management
- NDIS Billing & Invoicing - support catalogue, price-limit validation, invoice batches, myplace/PRODA CSV export.
- NDIS claiming (bulk payment request CSV) - the file the agency accepts, built, validated and limit-checked; you upload it to the provider portal. Maree-CareFlow has no NDIA API connection.
- NDIS Plan Management (act as a plan manager) - managed participant plans, per-purpose budget ledger (Core/Capacity Building/Capital), inbound third-party provider-invoice capture with a hard budget-drawdown guard, provider disbursement (ABA-ready), trust-account ledger, plan-management fee items (14_033/14_034), NDIA reimbursement claims with CSV export, and participant statements. (Gated module.)
- Group Sessions - NDIS group billing with fan-out, 10-participant cap.
- Travel Billing Engine - MMM-zone travel claim calculation with caps.
- HICAPS / Medicare Better Access Billing - MBS item lookup, Better Access + CDM items, HICAPS/PRODA claim capture (PRODA-ready; direct lodgement needs your Medicare Online credentials + certification), GST.
- Motor Accident & WorkCover Billing - 13 schemes (TAC, MAIB, CTP NSW/QLD/SA/WA, MAIC ACT, MAC NT, WorkCover NSW/VIC/QLD/WA, ReturnToWorkSA) direct-to-insurer invoicing.
- Aged Care & Support at Home - ACAT assessments, Home Care Packages (L1-4), Support at Home claims. (Gated module.)
- Cancellation Analytics - short-notice/no-show analysis, at-risk clients, revenue impact.
AI & clinical documentation
- AI-Powered Clinical Reports - local-first (Ollama) NDIS report generation with mandatory AHPRA consent checkpoint + practitioner attestation; BSP drafting hard-blocked.
- AI Session Transcription - AssemblyAI primary, local Whisper fallback.
- AI SOAP Note Generation - draft clinical notes from session content (human-reviewed).
Compliance & regulatory
- Compliance & Regulation Monitoring - automated rule checking with a traffic-light dashboard.
- Compliance Modules - restrictive-practices register (+ monthly NDIS report CSV), complaints (console + public lodgement), mandatory reporting (all-jurisdiction thresholds), whistleblower, telehealth assessment.
- SDA Property Compliance - SDA Design Standard category checks with measurement recording and AI photo assessment.
- Audit Trail - immutable, trigger-enforced audit log of every read/write.
- Accessibility (WCAG 2.1 AA) - enforced jsx-a11y CI gate + accessible chart data-table alternatives (in progress; specialist audit pending).
Healthcare interoperability & integrations
- HealthLink / Argus Referral Intake - HL7 v2 referral parsing.
- FHIR R4 API - Patient/Practitioner/Appointment/DocumentReference.
- SMART on FHIR - App Launch 2.0 (PKCE) for third-party clinical apps.
- IHI Validation - Individual Healthcare Identifier lookup (HI Service; NASH-cert gated for production).
- My Health Record Upload - clinical document upload (NASH-cert gated for production).
- Electronic Signatures - service-agreement e-signing (DocuSign / AU Post eSign).
- Calendar Sync (ICS Feeds) - per-practitioner secure ICS feed (Google/Outlook/Apple).
- Twilio SMS - appointment reminders, recalls, bulk send.
- Stripe Payments - checkout, invoices, refunds, HMAC webhooks.
- Xero / QuickBooks Online / MYOB - OAuth2 accounting sync.
- Basiq AU Open Banking - bank-feed transaction categorisation + assisted reconciliation (ranked suggested matches for human confirmation; does not auto-mark paid).
- Zapier & Make Webhooks - HMAC-signed outbound webhooks; nine events, sent after the change commits.
- Self-Service Integration Management - per-org in-app config of Twilio/Stripe/Basiq/AssemblyAI/Anthropic/Ollama with live status + usage budgets.
- Application API - the versioned API every screen runs on; not offered for your own integrations (no API keys or client credentials).
Workforce, rostering & payroll
- Rostering Engine (SCHADS Award) - shift rostering with conflict detection and overtime alerts; CSV/JSON export.
- Smart Scheduling - travel-time-optimised slot suggestions (Haversine).
- Single Touch Payroll Phase 2 - PAYG scale-2, 12% super, PAYEVNT.0004 (ATO submit credential-gated).
- ABA Bank Files - APCA-spec direct-entry payment file generation.
Equipment & assistive technology
- Equipment & Assistive Technology - AT assessment, recommendation, approval, direct supply / third-party referral / internal loan pool with checkout-return-condition tracking, full AT history.
Platform, security & commercial
- Role-Based Access Control & User Management - 9-role RBAC, TOTP MFA, session management with remote revocation.
- KPI Dashboard & Performance Analytics - live KPIs, targets, funding-request workflow.
- Data Export & Backup - subject-access export, organisation data export/backup.
- Browser Push Notifications - VAPID Web Push.
- Progressive Web App (PWA) - installable; caches the application itself, and needs a connection to work.
- 3 Deployment Options - cPanel ZIP, Docker/VPS, or Ubuntu bare-metal; Australian self-hosted.
- Admin > Rates & Price Limits (v1.5.0) - dated, sourced regulatory rates with per-practice overrides.
- User Management > Reset two-factor login (v1.5.0)
Feature Reference
The complete capability set is the "Complete Feature List (at a glance)" above. The detailed write-ups below cover each feature: Features 1-16 are grouped thematically in the numbered ### N. sections, and the remaining features are documented individually as ## Feature N sections (including Feature 51 - NDIS Plan Management, the org acting as a plan manager, added in v1.3.35).
1. Client Management
The complete client record - demographics to funding to clinical history in one place.
The Clients module is the central hub of Maree-CareFlow. Each client record holds a comprehensive profile covering personal demographics, contact details, emergency contacts, communication preferences, cultural and language needs, clinical diagnoses (primary + secondary + ICD-10 codes), alerts, risk flags, and full consent history. Clients can be searched, filtered, sorted, and paginated across the entire organisation's caseload.
Key capabilities:
- Comprehensive demographics - Name, preferred name, pronouns, date of birth, gender, indigenous status, country of birth, language, interpreter requirements, communication needs
- Multiple contact records - Mobile, home phone, email, preferred contact method; emergency contacts with relationship types (guardian, GP, specialist, plan manager, support coordinator, carer, advocate)
- Clinical information - Primary diagnosis, secondary diagnoses, ICD-10 codes, behavioural support plan flag, restrictive practices flag, fall risk rating (low/medium/high)
- Funding profiles - NDIS number with format validation, NDIS plan dates, plan management type (agency/plan-managed/self-managed), plan manager and support coordinator details
- Multi-scheme injury funding - Assign any combination of TAC, MAIB, CTP (NSW/QLD/SA/WA), MAIC (ACT), MAC Scheme (NT) alongside NDIS, Medicare, DVA, and General funding (see Section 5)
- NDIS plan detail - Full budget breakdown across all 10 NDIS support categories (Core Supports, Daily Activities, Social/Community, Employment, Home Living, Health & Wellbeing, SDA, SIL, Assistive Technology)
- Funding pool tracking - Per-category budget pools with alert thresholds, period tracking, spend monitoring across all funding types
- Referral tracking - Source, date, intake date
- Consent records - Treatment, privacy, research, photos, telehealth - all individually recorded with timestamps
- Upcoming appointments - At-a-glance view of next scheduled sessions
- Document vault - File attachments (reports, assessments, plans, invoices, credentials)
- Activity feed - Recent interactions, notes, changes
2. Practitioner Management
Manage your clinical team - registrations, credentials, disciplines, and workload.
The Practitioners module manages the full lifecycle of each practitioner's profile within the organisation. It covers professional registration details, AHPRA numbers, discipline classifications, credential expiry tracking, and workload visibility. Credential expiry alerts prevent the common compliance risk of treating clients with lapsed registrations.
Key capabilities:
- Professional profile - Full name, preferred name, a primary discipline and any further disciplines, chosen from one list of over forty allied-health and related disciplines used everywhere in the product (Ahpra-registered professions such as occupational therapy, physiotherapy, psychology and podiatry; self-regulated allied health such as speech pathology, audiology, dietetics, exercise physiology and social work; therapies such as counselling, play therapy, music therapy and art therapy; and support roles such as support coordination and behaviour support). A discipline the list does not name is recorded as Other (specify) with the practitioner's own title, and reports, cards and emails print that title. Shipped report templates and telehealth session guides are written for some disciplines; every other discipline uses the general allied-health ones. Email, phone, employment start date
- Registration management - AHPRA number, provider number, Medicare provider number, DVA provider number, TAC provider registration
- Credential tracking - Professional indemnity insurance, working with children check, police check, first aid certificate - all with expiry dates and alert thresholds
- Credential alerts - Dashboard warnings for credentials expiring within 30 / 60 / 90 days
- Workload view - Caseload summary, billable hours, utilisation rate visible to managers
- Status management - Active/inactive flag; inactive practitioners excluded from scheduling and billing
- Supervisor assignment - Link practitioners to supervisors within the organisation
- Role-based visibility - Practitioners only see their own full profile; managers see all
3. Calendar & Scheduling
Multi-view appointment scheduling with telehealth, recurrence, and time logging.
The Calendar module is the scheduling engine of Maree-CareFlow. Built on a fully custom MIT-licensed calendar component (month, week, and day views), it supports all appointment types used in allied health practice. Time entries flow directly into the billing module for approval and invoicing. The calendar integrates with external calendar providers (Google, Microsoft, Apple) for two-way sync.
Key capabilities:
- Three calendar views - Month (event pills per day), Week (time grid 06:00-21:00, events positioned by time), Day (single-column time grid)
- Six appointment types - Direct Therapy, Telehealth, Home Visit, Group Session, Admin, Supervision - each colour-coded
- Appointment creation - Client assignment (typeahead search), practitioner assignment, date/time, location, telehealth URL, notes
- Recurrence - Weekly and fortnightly recurring appointments with single-event or series management
- Status workflow - Scheduled → Confirmed → Completed → Billable → Cancelled / No-show
- Telehealth support - see the dedicated Telehealth capability below
- Real-time indicator - Live red line showing current time in week/day views
- Practitioner filter - View all appointments or filter by individual practitioner
Telehealth (video consultations): Telehealth is a first-class capability, not just a URL field. Appointments can be flagged is_telehealth with a telehealth_url, and a dedicated Telehealth page (/telehealth, TelehealthPage) lists the practitioner's upcoming and in-progress video appointments straight from the real calendar API, with a one-click join. Built-in video is provided via Jitsi Meet (no third-party account required for the participant), and every telehealth session is still a normal calendar event, so it flows through the same scheduling, status, billing and reminder pipeline as an in-person appointment. Location renders as "Virtual (Telehealth)" in calendar feeds and exports.
- Event type filter - Show/hide appointment types
- External calendar sync - Connect Google Calendar, Microsoft Outlook, or Apple Calendar for two-way synchronisation
- Colour coding - Practitioner-based and event-type-based colour schemes toggle
4. Billing & Invoicing
Time entry management, NDIS catalogue, and invoice batch submission.
The Billing module handles the full financial workflow from time entry creation through to invoice submission. It supports every major Australian healthcare funding type, integrates the NDIS Support Catalogue with state-specific pricing, and generates NDIS bulk payment CSV files for direct upload to the NDIS myplace portal.
Key capabilities:
- Time entry logging - Record billable sessions with date, duration, funding type, support category, support item number, unit price, units, total claimable, GST applicability
- Multi-funding support - NDIS (agency/plan/self-managed), Medicare MBS, Medicare MHTP, Medicare EDP, DVA, Private Insurance, WorkCover, TAC, General, and all 8 motor accident schemes
- NDIS Support Catalogue - Searchable database of support items with item number, name, category, support purpose, and each state and territory's own published price limit (ACT, NSW, NT, QLD, SA, TAS, VIC, WA). A new line is priced from the state your practice is registered in, and you can override the rate on any line. The guide's remote and very remote rates are imported too and are used for provider travel; a session itself is not re-priced by remoteness, because a time entry does not record where the support was delivered
- Approval workflow - Time entries go through a draft → submitted → approved/rejected workflow; managers approve before invoicing
- Bulk approval - Select multiple entries and approve or reject in a single action
- Invoice batches - Group approved time entries by date range into invoice batches
- Batch status workflow - Draft → Submitted → Paid / Rejected / Cancelled
- NDIS CSV export - Generate bulk payment CSV files formatted for NDIS myplace portal upload
- NDIS bulk payment reference - Track and store payment reference numbers from NDIA
- Billing statistics - Monthly totals by funding type, batch counts, total value submitted/paid
- Entry detail view - Expandable panels showing all line items within a batch, grouped by practitioner
5. Motor Accident & Injury Scheme Funding
The only Australian practice management system covering all 8 state/territory CTP and no-fault motor accident schemes.
Maree-CareFlow is the first Australian allied health platform to natively support all eight state and territory motor accident compensation schemes alongside NDIS and general funding. A clinician or case manager can assign any combination of funding sources to a single client, reflecting the real-world complexity of clients who receive treatment under multiple schemes simultaneously.
Schemes supported:
| Scheme | State/Territory | Type |
|---|---|---|
| TAC - Transport Accident Commission | Victoria | No-fault statutory |
| MAIB - Motor Accidents Insurance Board | Tasmania | No-fault statutory |
| CTP / SIRA | New South Wales | Fault-based + statutory benefits |
| CTP / MAIC | Queensland | Fault-based |
| CTP - CTP Insurance Regulator | South Australia | Fault-based |
| ICWA - Insurance Commission of WA | Western Australia | No-fault statutory |
| MAIC - Motor Accident Injuries Commission | Australian Capital Territory | No-fault statutory |
| MAC Scheme - Motor Accidents Compensation Commission | Northern Territory | No-fault statutory |
Key capabilities per scheme record:
- Claim details - Claim number, insurer name, case manager (name, email, phone with clickable mailto/tel links)
- Injury & accident dates - Both fields captured separately as legally distinct dates
- Approval tracking - Approval period (start/end), total approved amount, sessions approved vs sessions used
- Visual session progress bar - Green (< 70% used) → Amber (70-90%) → Red (> 90%) with percentage display
- Visual budget meter - Proportional spend display
- Approval expiry countdown - Amber warning at 30 days, red at 7 days, "Expired" badge past end date
- Treatment plan reference - For a treatment request (NSW), AHMP (SA), rehabilitation plan (QLD), TARP (TAC)
- Approval reference - TAC approval reference, QLD sequential plan numbers, etc.
- Legal status tracking - Active / Disputed / Settled / Closed
- Legal representative firm - Prominently flagged with ⚠ warning when legal proceedings are active
- Scheme-specific fields:
- NSW CTP: the date the treatment request went to the insurer, with the SIRA Motor Accident Guidelines' own clocks stated beside it (cl 4.106: the insurer decides within 10 days and pays an approved account within 20 days of the invoice)
- ACT MAIC: PIA acceptance status (drives invoice destination: insurer if accepted, patient if not)
- NT MAC: Pre-treatment approval confirmation (red warning if not confirmed - do not treat)
- Legal disclaimer - Non-removable notice that records are factual only; Maree-CareFlow does not determine entitlements; records may be subject to legal discovery
6. KPI Dashboard & Performance Analytics
Real-time performance metrics for practitioners and organisation-wide visibility for managers.
The KPI Dashboard gives every practitioner a clear, real-time view of their own performance metrics. Managers see the organisation-wide picture. AI-powered suggestions surface clients at funding risk and identify operational improvements. A built-in funding request system lets practitioners request additional hours with AI-generated justification letters.
Key capabilities:
- Personal KPIs (per practitioner): Billable hours (weekly/monthly), utilisation rate (billable ÷ available hours), cancellation rate, notes on-time percentage, revenue generated, active caseload count
- Weekly trend charts - Recharts-powered line/bar charts of billable hours over the past 8 weeks
- Client funding status - Visual indicators for each active client: budget remaining, burn rate ($/week), projected depletion date, funding expiry warnings
- AI suggestions - AI-generated recommendations for at-risk clients, documentation gaps, billing opportunities
- Funding request workflow - Therapists submit funding increase requests with hours needed, support category, justification; AI generates a professional letter to the plan manager
- Manager approval queue - Managers review, approve, or reject funding requests from the organisation
- Organisation-wide dashboard (managers) - Total billable hours, revenue, utilisation across all practitioners; pending approvals count; compliance status
7. AI-Powered Clinical Reports
Generate, edit, approve, and export professional NDIS clinical reports in minutes - with full Australian regulatory compliance built in.
The Reports module is one of Maree-CareFlow's most powerful features. It runs on the organisation's own AI provider - a locally hosted Ollama model (data stays on-premises) or the organisation's own Anthropic Claude API key - and generates comprehensive clinical reports that practitioners can review, edit section by section, and submit for approval. The practice supplies and manages its own AI account; Maree-CareFlow never supplies AI compute or marks up usage, and falls back to a static template if no provider is reachable. Reports are produced to professional standards with customisable templates covering the most common NDIS report types. Every AI report workflow is governed by the applicable Australian regulatory frameworks.
Five built-in report types:
- NDIS Progress Report - Progress against NDIS goals, support effectiveness, recommended adjustments
- Functional Capacity Assessment - Functional limitations, daily living assessment, capacity for independence
- Assistive Technology Justification Letter - AT recommendation with clinical rationale for NDIA submission
- NDIS SIL Assessment - Supported Independent Living assessment with capacity ratings
- Home Modification Report - Environmental barriers assessment, modification recommendations, cost estimates
Key capabilities:
- 3-step generation wizard - Client selection, report type, context notes, optional progress data inclusion
- AI generation with real-time progress - Step-by-step animation showing AI progress; graceful fallback to template if AI unavailable
- Section-by-section editing - Slide-over editing panel; edit Goals, Progress, Recommendations, Supports Required individually
- Approval workflow - Draft → Under Review → Approved; approver can accept or send back for revision
- PDF export - Generate and download formatted PDF reports
- Status tracking - Colour-coded badges for draft/under-review/approved
- Report templates - Create, edit, duplicate custom templates with AI prompts per section, applicable discipline filtering, HTML colour scheme selection
- Filter and search - Filter by status, report type, practitioner, date range
Australian AI Regulatory Compliance (v1.0.27+):
Maree-CareFlow is compliant with all applicable Australian frameworks governing AI use in clinical settings:
| Regulation | Requirement | Implementation |
|---|---|---|
| AHPRA's "Meeting your professional obligations when using Artificial Intelligence in healthcare" (22 August 2024) | Informed client consent before AI processes health information | Mandatory consent checkbox at Step 2; generation blocked if not confirmed |
| Privacy Act 1988 (Cth) - APP 3, 6, 8, 11 | Consent before AI processes PII; cross-border disclosure controlled | Consent field persisted to DB. With local Ollama, data never leaves the organisation (no cross-border disclosure). If the practice instead configures its own Anthropic Claude key, generation is processed under the practice's own provider account and remains consent- and disclosure-gated - the practice controls that choice under APP 8 |
| NDIS Quality and Safeguards Commission, "Position statement - Use of artificial intelligence in the development of behaviour support plans" (February 2026) | The Commission does not endorse or approve AI use in developing or reviewing BSPs, and does not prohibit it; where a provider uses AI it expects de-identification and no participant personal information disclosed to AI systems | Maree-CareFlow goes further by its own choice: BSP report types are hard-blocked at the service layer and cannot be AI-generated |
| ACSQHC AI in Clinical Use Guide | Clinician remains accountable; human review required | Attestation statement (min 20 chars) required from approver before any report is approved |
| OAIC Health Privacy Guide (May 2025) | Consent before AI processes health data; consent must be recorded | client_consent_confirmed stored on both AgentRun and AiReportDraft DB records |
| TGA AI as a Medical Device (AiMD) | Clinical decision support tools must document limitations | AI Governance Disclosure endpoint (GET /api/v1/ai/governance) exposes full regulatory disclosure |
- Governance disclosure -
GET /api/v1/ai/governancereturns a machine-readable JSON disclosure covering all applicable regulations, limitations, and practitioner responsibilities - Audit trail - Every AI report generation is logged with consent status, PII flag, NDIS participant flag, user ID, and tenant ID
- Usage visibility - Each report records one AI request against the organisation's AI integration; Admin -> Integrations shows the monthly count plus a Manage & top up link to the provider's own billing console. The meter is display-only and never blocks a report from being generated.
- No BSP generation - Behaviour Support Plan report types return HTTP 422 with a regulatory explanation - this cannot be overridden
- Practitioner attestation - Report approval requires a written attestation statement confirming the practitioner has reviewed the AI output and accepts clinical responsibility
8. Compliance & Regulatory Monitoring
Automated compliance rule checking and live regulation monitoring.
The Compliance module ensures organisations stay ahead of their regulatory obligations. It monitors compliance against configurable rules, runs automated checks, and tracks the results over time. A separate Regulations feed monitors official government and regulatory body sources for updates, surfacing material changes with AI-generated summaries.
Key capabilities:
- Compliance rules - Hard limits (must not exceed), soft limits (should not exceed), thresholds - all configurable with jurisdiction and category tags
- On-demand compliance checks - Run checks against all active rules at any time; results show pass/warn/fail for each rule
- Check result detail - Expandable results showing exact values, rule thresholds, pass/fail reasoning, affected records
- Compliance history - Timeline of all previous check runs with overall status; trend visibility
- Regulation sources - Monitor specific URLs (government websites, regulatory bodies, NDIS policy pages) for content changes
- Regulation updates feed - Timestamped list of detected changes with AI summaries, material change flag, added/updated/removed chunk counts
- Jurisdiction and category filtering - Filter rules and results by state/territory and category (billing, clinical, SDA, etc.)
- Status badges - At-a-glance compliant / non-compliant / pending-review / not-applicable indicators
9. SDA (Specialist Disability Accommodation) Compliance
Property-level SDA standards compliance checking against NDIS Design Standards.
The SDA module supports NDIS-registered SDA providers in maintaining design standard compliance across their property portfolio. Each property is assessed against measurable accessibility standards (doorway widths, corridor clearances, bathroom turning circles, bedroom dimensions, ceiling heights, ramp gradients), producing a per-property compliance status.
Key capabilities:
- Property registry - Record SDA properties with address, design category (Improved Liveability, Fully Accessible, Robust, High Physical Support), building typology (apartment, villa, duplex, house), resident capacity, SDA enrolment reference
- Measurement recording - Input accessibility measurements for each property (doorway width/height, corridor width, bathroom turning circle, bedroom dimensions, ceiling height, ramp/step details)
- Compliance checking - Run checks against NDIS SDA Design Standard 2021 thresholds; pass/fail per measurement per standard
- Result detail - Expandable compliance report per property showing each standard, measured value, required value, and outcome
- Portfolio statistics - Total properties, compliant count, non-compliant count, pending assessment count
- Design category standards - Different thresholds applied automatically based on the property's registered design category
- AI photo assessment - Upload site photos for AI-assisted measurement extraction using the locally hosted vision model (Ollama - no images leave the organisation). The AI analyses photos and extracts dimensional measurements for compliance verification. Confidence rating (High / Medium / Low) is returned with every AI measurement.
- CareFlow Measuring Stick (calibration aid) - AI photo assessment works on any site photo, but millimetre measurements are only extracted when a CareFlow Measuring Stick calibration ruler is visible in the image (the vision prompt instructs the model to extract measurements only when the ruler is present). Photos without one still receive a barrier and compliance assessment, but measurement-based findings carry lower confidence and should not be relied on alone for formal SDA compliance documentation - verify on site. To order CareFlow Measuring Sticks contact info@maree-careflow.com.au with subject CareFlow Measuring Stick Order Enquiry.
10. Clinical Supervision
Track supervision relationships, session records, action items, and dual signatures.
The Supervision module supports the clinical supervision obligations of health practitioners. It covers both sides of the relationship - practitioners can view their own supervision history as supervisees, and supervisors can manage their caseload of supervisees. All sessions are recorded with structured notes, topic tags, and a dual-signature capture system.
Key capabilities:
- Dual-role view - "My Supervision" tab (as supervisee) and "As Supervisor" tab (as supervisor) in the same interface
- Supervision relationships - Record supervisor/supervisee pairs with start date, frequency, supervision type (individual/group/peer), active status
- Session recording - Date, format (in-person/video/phone), duration, topics (Clinical, Administrative, Professional Development, Case Review)
- Structured notes - Session notes with action items; each action item has completion status checkbox
- Dual signature capture - Both supervisor and supervisee sign off on session records using name-based signature
- Session history - Chronological table of all sessions with status indicators; click to expand full detail
- Pending signatures - Alert for sessions awaiting signature from either party
11. Document Management
Secure file storage linked to clients, practitioners, and organisations.
Every important document in a client's care journey - intake forms, assessment reports, NDIS plans, invoices, credentials, consent forms, photos - can be stored securely within Maree-CareFlow. Files are categorised, searchable, and linked to the relevant entity.
Key capabilities:
- File categories - Intake, Assessment, Plan, Report, Invoice, Credential, and General
- Client documents - Upload and manage files linked to individual client records
- Practitioner credentials - Store credential documents (registration certificates, insurance certificates, working with children checks)
- Organisation documents - Policy documents, procedure manuals, templates at organisational level
- Metadata - File name, category, uploaded by, upload date, file size
- Download and preview - Download any stored file; office documents and PDFs viewable in-browser
12. Role-Based Access Control
Fine-grained permission control across all modules and actions.
Maree-CareFlow uses role-based access control (RBAC). Every action - reading, creating, editing, deleting, approving - is checked against the caller's role on the server, and every record is confined to the caller's own practice. Billing staff cannot open client records or clinical notes, and administrative functions are restricted to administrative roles. Within a practice, clinical staff see the practice's whole caseload: access is not narrowed to the clients a clinician is assigned, or to a department. A document can be marked Private so that other clinicians cannot open it.
Roles:
| Role | Description |
|---|---|
super_admin | Top account of the install; reaches every organisation on it |
admin | Full practice access; manages users and settings |
org_manager | Approves clinical work and billing; manages users up to their own rank |
dept_manager | Approves clinical work and billing; no user management |
practitioner | Clinical work - clients, scheduling, notes, reports, time entries |
support_coordinator | Views client, clinical and billing records; makes no changes to them |
billing_only | Billing - records payments, downloads the NDIS claim file; no client or clinical records |
readonly | View-only access to clients, clinical records and documents |
13. User Profile & Settings
Personal preferences, security settings, and organisation configuration.
The Profile and Settings modules allow users to manage their own account details, security settings, and notification preferences. Organisation administrators can configure system-wide settings including AI integration, calendar sync, NDIS registration details, and integration settings.
Key capabilities (user profile):
- Update display name, email, phone, avatar
- Change password with current-password verification
- Enable / disable two-factor authentication (TOTP)
- View active sessions; revoke sessions remotely
Key capabilities (organisation settings):
- Organisation name, ABN, NDIS provider registration number
- Default timezone, currency, locale
- AI settings - enable/disable AI features, configure Ollama endpoint or cloud AI API
- Calendar integration - connect Google Calendar, Microsoft 365, Apple Calendar
- NDIS registration details for billing compliance
- Integration settings for external services
14. Audit Trail
Complete, immutable history of every significant action in the system.
Maree-CareFlow maintains a full audit trail of all significant actions: who did what, when, and to which record. This is critical for NDIS audit compliance, motor accident legal proceedings, and professional practice standards. Audit records cannot be edited or deleted.
Key capabilities:
- Timestamped records of all create/update/delete actions
- User identity recorded for every action
- Entity type and entity ID recorded
- Before/after values captured for updates
- Admin view for browsing and searching audit logs
- Filter by user, date range, action type, entity type
- Export capability for audits and legal discovery
16. API
The application's own API - not an integration API.
Every screen in Maree-CareFlow runs on a versioned REST API (/api/v1/) built on FastAPI. It is not offered for a practice's own integrations or automations: it authenticates only a signed-in person's own session token, there are no API keys and no client credentials for a script or another system to use, and the OpenAPI schema is served only on a development install, never in production. Outside clinical applications connect through the Third-party application access (SMART-on-FHIR) add-on, and events reach other systems through signed outbound webhooks (Feature 41). A public integration API with keys, scopes and rate limits is not built.
What the application API does have:
- JWT bearer token authentication of the signed-in user, with revocable sessions
- Tenant-scoped request isolation
- Consistent response envelopes
- Pagination on list endpoints
- Filtering, sorting, and search on key resources
- Versioned API (
/api/v1/) for forward compatibility
Funding Types Supported
Maree-CareFlow supports the broadest range of Australian healthcare funding types of any allied health platform:
| Funding Type | Description |
|---|---|
| NDIS Agency Managed | NDIA manages payments directly |
| NDIS Plan Managed | Registered plan manager processes invoices |
| NDIS Self Managed | Client manages own NDIS funds |
| Medicare MBS | Medicare Benefits Schedule items |
| Medicare MHTP | Mental Health Treatment Plan (Better Access) |
| Medicare EDP | Eating Disorder Program |
| DVA | Department of Veterans' Affairs gold/white/orange card |
| Home Care Package (HCP) | CHSP/HCP funded services |
| Private Insurance | Private health fund billing |
| WorkCover | Workers compensation - all states |
| TAC | Transport Accident Commission (Victoria) |
| MAIB | Motor Accidents Insurance Board (Tasmania) |
| CTP / SIRA | Compulsory Third Party - New South Wales |
| CTP / MAIC | Compulsory Third Party - Queensland |
| CTP | Compulsory Third Party - South Australia |
| ICWA | Insurance Commission of Western Australia |
| MAIC | Motor Accident Injuries Commission (ACT) |
| MAC Scheme | Motor Accidents Compensation Commission (NT) |
| General | General/out-of-pocket private billing |
Feature 17 - External Case Manager System
Maree-CareFlow's External Case Manager (ECM) module provides a secure, fully managed portal for external referrers - NDIS support coordinators, TAC/MAIB case managers, insurer representatives, and other allied health coordinators - to submit and track client referrals without ever accessing internal clinical data.
Invitation & Onboarding
- Admins, Org Managers, and Dept Managers invite external CMs by email
- Secure one-time invite token (cryptographic, SHA-256 hashed)
- External CM accepts invite, sets own password, gains portal access immediately
- ECM record linked to a User account with the
external_case_managerrole
Client Referral Submission
External CMs submit referrals via a 3-step guided form covering:
- Client information - name, DOB, gender, contact details, NDIS/Medicare numbers
- Clinical & scheme details - diagnosis, injury date, referral reason, services requested, discipline, funding scheme, claim number, insurer
- Consent - explicit client consent confirmation with date; submission blocked if consent not given
- Priority - Urgent / High / Routine / Low
Referral Holding Pool
All referrals land in a holding pool visible to internal managers:
- Filter by status, priority, and ECM
- Accept, reject, or waitlist with optional department assignment and internal notes
- Configurable acceptance authority: Practice Manager only, or also Dept Manager
- Dept Manager can enable therapist self-selection from the pool
Configurable Access Permissions
Practice Managers configure exactly what external CMs can see and do, with 18 settings:
Visibility (12 toggles): appointments, appointment notes, reports, clinical notes, invoice totals, session counts, funding balances, goal progress, progress ratings, comment on reports, request appointments, upload documents
Workflow (4 toggles): dept manager acceptance, dept self-select, therapist self-select, consent requirement
Notifications (2 toggles): auto-notify ECM on appointment, auto-notify ECM on report
Per-client overrides can be set for any individual client with an optional expiry date.
Privacy Firewall
- Internal notes (
internal_notes) are never returned to external CMs at the API level is_internalcomments are filtered server-side - ECMs only see non-internal comments- ECMs cannot post internal comments
- All ECM API responses use a separate schema that excludes sensitive fields
- All queries are scoped to the ECM's own organisation - cross-organisation data isolation guaranteed
ECM Portal
A dedicated, simplified portal shell (no sidebar, no internal navigation):
- My Referrals - view all submitted referrals with status tracking; submit new referrals
- My Clients - view accepted clients with scheme/claim details and assignment info
- My Profile - view own ECM record and status
Referral Lifecycle
pending → under_review → accepted
→ rejected
→ waitlisted → accepted
→ rejected
→ withdrawn
↑
└── withdrawn (by ECM at any stage before acceptance)
Feature 18 - Data Export & Backup
Maree-CareFlow provides a fully integrated data export and backup system, meeting Privacy Act 1988 (Cth) obligations, data portability requirements, and disaster recovery best practices.
Client Subject Access Request (SAR) - Privacy Act APP 12
Organisations are legally obligated to provide individuals access to their personal information on request. Maree-CareFlow fulfils this with a one-click export:
- Admin or Org Manager selects any client and clicks Generate SAR Export
- The system assembles all data held for that client: demographics, contacts, NDIS/injury plans, funding pools, goals, appointments, time entries, clinical notes (optional), and a capped audit trail
- Data is packaged as a ZIP containing
client_data.json(machine-readable) andREADME.txt(human-readable summary with record counts and privacy notice) - Export includes regulatory basis statement: Privacy Act 1988 (Cth) - APP 12
- File stored securely in MinIO, available for 7 days via presigned 24-hour download URL
Organisation Data Export
Export all organisation data for data portability, platform migration, or archiving:
- Exports all organisation records as structured CSVs: clients, contacts, NDIS plans, injury plans, funding pools, goals, appointments, time entries, invoice batches, and optionally clinical notes
- Ideal for migrating to another system or maintaining local archives
- Files expire after 7 days
Full Practice Snapshot
Create a JSON snapshot of one practice's own records:
- Every table that holds this practice's records, derived from the schema rather than a hand-written list - clients, contacts, plans, goals, appointments, time entries, invoices, clinical notes, supervision, incidents, complaints, care plans, and the records owned by every service module, whether or not that module is switched on (audit P0-3)
- Carries
schema_versionandrestore_instructions, plusexcluded_tablesandtenant_shared_not_includedso a reader can see exactly what was left out and why - The file is not encrypted. Medicare, NDIS and DVA numbers, clinical note text and bank details are written decrypted, in plain text - store and send it exactly as carefully as the clinical record itself
- Files expire after 30 days and should be stored securely offline
Export Jobs & Management
- All export requests are tracked as jobs with statuses:
generating → ready / failed / expired - Real-time status polling in the frontend - automatically refreshes while generating
- One-click presigned download link once ready
- Job history with file size, creation date, and expiry
- Delete jobs and their files at any time
Access Control
All export functionality is restricted to admin and super_admin roles. Client SAR also accessible to org_manager.
Feature 19 - Travel Billing
(Available from v1.0.29)
Maree-CareFlow includes a complete travel billing system for therapists who travel to client locations.
Organisation Modes:
- Basic Mode - each therapist independently logs travel per client per visit, with simple km entry and billing
- Advanced Mode - day-trip groups allow one practitioner's full day of travel to be automatically split between multiple clients using configurable algorithms
Entry Modes (therapist choice, persisted per device):
- Manual KM - enter one-way km with an optional "Include return trip" checkbox that doubles the km for billing
- Odometer - enter start and end odometer readings for the outbound leg; optional return leg with separate start/end readings; km computed automatically
Advanced Day-Trip Splitting:
equal- shared inter-client leg split 50/50 between adjacent clientsdistance_proportional- shared leg weighted proportionally to each client's own private legssequential- departure leg charged entirely to the departing client
Per-Scheme Rates: NDIS ($0.99/km - the NDIS Pricing Arrangements and Price Limits 2025-26, page 23; not yet confirmed for 2026-27, because the 2026-27 pricing schedules do not state a km rate), iCare, WorkCover, DVA, Private ($0.96/km default), ATO ($0.91/km for 2026-27; $0.88 before 1 July 2026). All rates are configurable by admins in Travel Settings and should be verified against current scheme publications each financial year.
Approval Workflow: draft → submitted → approved → invoiced; rejected from submitted with mandatory reason. Batch operations for managers.
Guard Rails (optional): require notes above a km threshold; hard cap on maximum claimable km per one-way leg.
Access: Travel Billing page is accessible to all staff. Travel Settings (admin only) at /travel/settings.
Feature 20 - Rostering Engine (SCHADS Award)
(Wave 2 - v1.2.1)
Maree-CareFlow includes a full support worker rostering engine built around the Social, Community, Home Care and Disability Services (SCHADS) Industry Award requirements.
Key capabilities:
- Shift rostering - Assign support workers to shifts with client, location, start/end time, and funding type
- Conflict detection - Prevents double-booking of a worker across overlapping shifts
- SCHADS Award overtime alerts - Automatic warning when a worker exceeds 38 ordinary hours per week; supervisors are notified for approval
- Double-shift gap enforcement - Enforces minimum break between consecutive shifts per SCHADS requirements
- Shift status workflow - Draft → Published → Confirmed → Completed
- Roster view - Weekly grid view of all worker shifts across the organisation
Feature 21 - Smart Scheduling (Haversine Travel Optimisation)
(Wave 2 - v1.2.1)
The Smart Scheduling engine suggests optimally ordered appointment slots for practitioners based on geographic proximity using the Haversine formula for great-circle distance calculation.
Key capabilities:
- Haversine distance scoring - Calculates travel distance between consecutive appointments using latitude/longitude coordinates
- 100-point travel score - Each candidate slot starts at 100 and is adjusted for the
practitioner's real day: -30 when it leaves under 15 minutes' gap to the neighbouring appointment, -20 when the travel leg exceeds 30 minutes, +10 when the client is in the same suburb as the previous visit (services/smart_scheduling.py). It scores travel and the shape of the day only - there is no client-preference, skill-match or time-of-day component, and no practitioner home base
- Ranked slot suggestions - Returns top-scoring appointment slot options for a given client and practitioner
- Practitioner home base - Uses geolocation home address as start/end point for daily route optimisation
- Day schedule view - Visual timeline of practitioner's day with travel times between appointments
Feature 22 - Group Sessions (NDIS Group Billing)
(Wave 2 - v1.2.1)
Maree-CareFlow supports NDIS group therapy sessions with full group billing fan-out, complying with NDIA group support billing rules.
Key capabilities:
- NDIS 10-participant cap - Group sessions enforce the NDIS maximum of 10 participants per group billing event; the system blocks creation of groups exceeding this limit
- Billing fan-out - A single group session automatically generates individual invoice line items for each participant, with the support hours divided across participants per NDIA group billing rules
- Group session appointment type - Distinct appointment type in the calendar with group-specific fields
- Per-participant funding validation - Each participant's NDIS funding balance is checked individually before billing fan-out
- Group roster - Manage participant attendance; absent participants are excluded from billing
Feature 23 - Cancellation Analytics
(Wave 2 - v1.2.1)
Maree-CareFlow tracks and analyses appointment cancellations with NDIS short-notice rule enforcement and at-risk client identification.
Key capabilities:
- NDIS short-notice late-fee enforcement - Flags a cancellation as short notice when
fewer than _SHORT_NOTICE_BUSINESS_DAYS (= 2) business days fall in the window counted from the day AFTER the cancellation up to and INCLUDING the appointment day, weekends excluded (_is_short_notice in services/calendar.py), enabling billing of the short-notice cancellation support item. This window is under review and must not be quoted to a customer as the NDIA rule until it is settled - see the note below. Verified behaviour: for a Wednesday, Thursday or Friday appointment it matches the table in docs/NDIS_BILLING_GUIDE.md exactly; for a MONDAY or TUESDAY appointment, where a weekend falls inside the window, it does NOT - it treats a cancellation on the Thursday before a Monday appointment as giving enough notice, where that table says a fee applies. COMPLIANCE_GUIDE.md's worked example disagrees with both. Three sources, three answers, on a path that decides whether a participant is charged 100% of the booked price
- Cancellation rate monitoring - Tracks cancellation rate per client, per practitioner, and organisation-wide
- At-risk client identification - Surfaces clients with high cancellation rates for proactive outreach
- Revenue impact reporting - Quantifies revenue lost to cancellations and recovered via late-fee billing
- Cancellation reason tracking - Records reason codes for all cancellations (client request, no-show, provider, system, other)
Feature 24 - HICAPS / Medicare Better Access Billing
(Wave 2 - v1.2.1)
Health fund and Medicare claim capture and tracking, built against the HICAPS/Medicare PRODA channel. Direct electronic lodgement is credential-gated (see caveat below).
Key capabilities:
- HICAPS/Medicare claim workflow - Build, calculate (fee/benefit/gap) and track Medicare and health-fund claims. The service layer models the full PRODA claim; live lodgement activates once the practice supplies its own Medicare Online credentials and completes certification. Until then the channel runs in dev/preview mode (mock responses) and never emits a plausible receipt as if it were real.
- Medicare Better Access items 10950-10970 - Full support for the Mental Health Treatment Plan MBS item range (individual psychological services under Better Access)
- Chronic Disease Management (CDM) items - GP Management Plans, Team Care Arrangements, and associated allied health items
- PRODA-ready lodgement (credential-gated) - Claim payloads are prepared for the Medicare/PRODA channel; direct electronic submission switches on with the practice's own Medicare Online credentials and certification. Physical HICAPS terminal (swipe-card) integration is not supported - see LIMITATIONS.md Section 3.
- Medicare provider number - Per-practitioner Medicare provider number field; billing blocked if provider number is missing or AHPRA registration is lapsed
- DVA/TAC/MAIB billing - Multi-scheme billing for Department of Veterans' Affairs (gold/white/orange card), TAC (Victoria), and MAIB (Tasmania) as native funding types
Feature 25 - NDIS claiming: the bulk payment request file
(Wave 2 - v1.2.1; the PACE half was deleted in v1.7.9, this section rewritten 2026-09-19 and corrected 2026-10-08.)
Maree-CareFlow claims through the NDIS bulk payment request file, which you upload to the provider portal, and no setting changes that. The NDIA grants access to its APIs, on application and with its approval, to registered providers and their software partners through its Digital Partnership Program, subject to a cyber security clearance; Maree-CareFlow is not connected to it, so it cannot submit a claim on your behalf.
Corrected 2026-10-08. From 2026-09-19 until this correction the paragraph above said "the National Disability Insurance Agency publishes no machine-to-machine claiming interface for providers, so no product - ours or anyone else's - can submit a claim on your behalf". That was wrong: the NDIA's APIs exist and are open to approved digital partners. What was, and is, true is that this product has no connection to them.
What this section used to say, and why the history is kept. It described an "NDIA PACE API Integration" and listed participant verification, funding balance queries, payment request submission and status tracking as capabilities. In 2026-08 that was corrected to say they were an explicitly-marked preview, which was true at the time. In v1.7.9 the preview itself was DELETED -
services/pace_api.py, the whole/pacerouter, and thePACE_API_BASE_URLandPACE_API_KEYsettings - because every one of its answers was a simulation, including a funding BALANCE and a payment request ID for a real, named participant. So this section now described screens that no longer exist and two settings that were removed. It has been rewritten to describe what the product actually does.
What the product actually does, and it is the rail the agency accepts:
- The bulk payment request (BPR) CSV - built from your approved work,
written to the NDIA's published column specification (December 2025 edition of the Bulk payment requests guide), validated row by row before the file is written. Billing > Export NDIS BPR, or from an invoice batch.
- The file's own limits are enforced before you download it - at most 5,000
rows, a filename inside the portal's 20-character cap, and a claim reference inside its own. A file that would be refused is refused here, with a sentence saying what to do instead.
- Only agency-managed participants go in it. A plan-managed participant is
invoiced to their plan manager and a self-managed participant pays you directly; claiming either to the agency is a claim to the wrong payer. A participant whose plan management is not recorded is excluded too, and named.
- Work that cannot be claimed is listed with its reason, rather than
quietly left out - a session that was never claimed cannot be rejected, so nobody notices it.
- You upload the file to the provider portal yourself, then record the
outcome on the batch (submitted, paid, rejected with a reason).
What PACE changed, and what it cost this product: nothing. PACE abolished the service booking - the arrangement a provider used to claim against. This product was never built on one: a claim is assembled from the participant, the support item and the plan budget, which is the PACE shape already. There is no old way to keep alongside a new one.
See docs/NDIS_BILLING_GUIDE.md for the step-by-step, including the portal side, and docs/CAPABILITY_REGISTER.md for the authoritative statement of what is and is not built.
Feature 26 - HealthLink / Argus HL7 v2 Referral Intake
(Wave 2 - v1.2.1)
Automated intake of electronic referrals from HealthLink and Argus clinical messaging networks via HL7 v2 message parsing.
Key capabilities:
- HL7 v2 message parsing - Parses inbound HL7 v2 ADT and REF messages from HealthLink and Argus
- Automatic client pre-population - Extracts patient demographics (PID segment), referring provider (PRD segment), diagnosis (DG1 segment), and referral details (RF1 segment) to pre-populate a new client record
- Celery inbox polling - A Celery periodic task polls the configured inbox path every 60 seconds (configurable via
HEALTHLINK_POLL_INTERVAL_SECS) for new HL7 message files - APP 4 compliance workflow - Unsolicited referrals are held in a pending queue for practitioner review before the client record is created; practitioners can accept or discard
- Referral source tracking - Records the originating HealthLink or Argus provider ID on the client referral record
Feature 27 - AI Session Transcription (AssemblyAI + Whisper Fallback)
(Wave 2 - v1.2.1)
Automated transcription of therapy sessions with SOAP note generation from the transcript.
Key capabilities:
- AssemblyAI cloud transcription - Primary transcription engine; uploads session audio to AssemblyAI for high-accuracy Australian English transcription
- OpenAI Whisper local fallback - When AssemblyAI is unavailable, transcription falls back to a locally running Whisper model (no audio leaves the organisation)
- SOAP note generation - Transcripts are processed by the AI engine (Ollama primary, Claude API fallback) to generate a structured SOAP (Subjective, Objective, Assessment, Plan) note draft
- Transcript storage - Transcripts are attached to the appointment record and stored in MinIO; never auto-saved to the clinical note without practitioner review
- Consent requirement - Client AI consent must be confirmed before any session audio is sent to AssemblyAI (APP 6 / APP 8 compliance)
Feature 28 - Basiq AU Open Banking
(Wave 2 - v1.2.1)
Integration with Basiq's Australian open banking platform for bank feed connectivity, transaction categorisation, and assisted invoice reconciliation.
Key capabilities:
- Bank feed connection - Connect practice bank accounts via Basiq using Australia's Consumer Data Right (CDR) open banking standard
- Transaction categorisation - Incoming transactions are automatically categorised (NDIS payment, Medicare rebate, private invoice, etc.) using AI-assisted classification
- Assisted invoice reconciliation - Incoming bank transactions are scored against outstanding invoices (amount within +/-1%, date proximity, name/reference match) and returned as ranked suggested matches for a human to confirm. The reconciler surfaces matches - it does not auto-mark invoices paid. (Roadmap: write-back to
invoice_batcheson confirmation - see LIMITATIONS.md.) - Basiq API key configuration -
BASIQ_API_KEYandBASIQ_API_URLconfigured in environment
Feature 30 - VAPID Web Push Notifications
(Wave 2 - v1.2.1)
Browser push notifications via the Web Push API with VAPID authentication, implemented using pywebpush.
Key capabilities:
- VAPID key pair - Voluntary Application Server Identification (VAPID) keys authenticate the push server to browser push services (FCM, APNS Web Push, etc.)
- Push subscription management - Users grant push permission in the browser; subscription endpoints are stored per user per device
- Notification types - Appointment reminders (24h and 2h before), funding balance alerts, credential expiry warnings, incoming referral notifications
- In-app notification centre - All push notifications also appear in the in-app notification bell with read/unread status
- Service worker integration - Push events are received and displayed by the PWA service worker even when the browser tab is not active
- pywebpush - Python library handles VAPID signing and HTTP POST to browser push endpoints;
VAPID_PRIVATE_KEYandVAPID_PUBLIC_KEYconfigured in environment
Feature 31 - Progressive Web App (PWA)
(Wave 2 - v1.2.1)
Maree-CareFlow is a Progressive Web App, installable on desktop and mobile devices. It needs a connection to work: it does not offer offline use.
Key capabilities:
- Service worker - a hand-written service worker (
/sw.js, served withCache-Control: no-cacheon every install type, so the browser checks for a new version on every load; the content-hashed files under/assets/are cached for a year, and the service worker fetches pages past the browser's own cache) caches the application shell and static files, so the app opens quickly and shows a clear offline message instead of a browser error when there is no connection - No offline records, no offline saving - participant records are never cached on the device (only published reference data such as the MBS item list and public holidays, and the practice's branding, are cached), and a change made without a connection is refused and reported as not saved, with the entry left on screen - it is not queued. The background-sync code only drains entries an older release may have queued on a device; it queues nothing new
- PWA install prompt - An in-app install banner prompts users on supported browsers to install Maree-CareFlow to their home screen or desktop
- Web App Manifest -
manifest.jsondefines app name, icons, theme colour, and display mode (standalone) for the installed experience - Mobile navigation - Responsive layout with hamburger drawer navigation on screens below 768 px; bottom tab bar for key modules on mobile
- ResponsiveTable and MobileCard components - Data tables reflow to card layout on mobile screens for readability without horizontal scrolling
Feature 32 - Client Transfers
(v1.2.37)
Maree-CareFlow moves a client from one therapist to another through an explicit accept/decline handover workflow rather than a silent reassignment. Moving a client is treated as a clinical handover: the receiving therapist must confirm they have capacity, scope of practice, and no conflict of interest before they become responsible for the client. The request/response trail records who asked, who agreed, when, and why - closing the governance gap a direct reassignment would leave.
Key capabilities:
- Three independent gates before a transfer can be created - the global
FEATURE_CLIENT_TRANSFERSflag (env kill-switch plus the feature_pricing registry row), the per-organisationallow_therapist_transfersswitch (on by default for a new organisation since migration 0235; an organisation that existed before keeps its setting), and a "no existing pending request for this client" rule enforced both in application code and by a partial unique index in the DB so racing requests cannot slip through - Atomic accept-and-reassign - on acceptance the request status change and the client's
primary_practitioner_idupdate happen in the SAME database transaction; a crash between the two can never leave an accepted transfer whose client still points at the old therapist - Ownership-enforced actions - only the receiving practitioner may accept or decline; only the sending practitioner may cancel; checks compare against the acting user's
practitioner_id(not role) so one practitioner cannot act on behalf of another - Optional case-manager carry-over - an
include_case_managerflag records whether the client's case-manager assignment travels with the transfer - Concurrency-safe state machine - every accept/decline/cancel is a guarded
UPDATE ... WHERE status = 'pending'; if a concurrent action won the race the operation returns HTTP 409 and (for accept) rolls back the client reassignment - Scoped, injection-safe listing -
directionof incoming/outgoing/all with managers seeing all org transfers; the list query is a fully parameterised static statement (:param IS NULL OR column = :param) keeping the SQL injection surface at zero
Feature 33 - Priority Waitlist
(v1.2.37)
Maree-CareFlow's waiting list supports operator-monetisable priority flagging that pins urgent referrals to the top of the queue above ordinary position ordering, backed by a full audit trail of who pinned an entry and when. The waiting list itself is database-backed (replacing an earlier localStorage page) with drag-to-reorder, slot offers, and SMS notification.
Key capabilities:
- Dedicated
is_priorityflag separate from clinical urgency - the existing 0-10 priority column is clinical urgency entered at intake; the paid priority flag is an explicit management decision with its ownpriority_marked_by/priority_marked_ataudit columns, and sorts ABOVE position ordering - Org-level opt-in toggle -
organisations.priority_waitlist_enableddefaults to FALSE; the capability changes workflow and billing, so an org manager must consciously enable it per organisation rather than it activating silently on upgrade day - Role-gated pinning - only managers and case-management roles (
admin,super_admin,org_manager,dept_manager,support_coordinator) may set or clear the priority flag - Feature-gated at the hot path - the priority toggle calls
feature_pricing_service.is_feature_active(), fronted by a 300-second Redis cache so the per-request check is a cache GET rather than a DB read - Drag-to-reorder with batch position update -
POST /waiting-list/reorderpersists a new ordering in one call - Slot offers with SMS -
POST /waiting-list/{id}/offer-slotmarks an entry 'offered' and fires a fire-and-forget SMS task (held in a module-level strong-reference set so the event loop does not garbage-collect the task before it completes)
Feature 34 - Participant Portal
(v1.2.38)
v1.5.0: participant screens (/participant/), Invite to Portal on the client record, staff Booking Requests inbox; paid add-on "Participant Portal + Self-Booking".*
The Participant Portal gives clients (and their families) a secure, read-only window into their own schedule, funding, and service agreements, plus self-service booking requests with a staff approve/decline workflow. It never exposes internal clinical data, and staff never see or set the participant's password.
Key capabilities:
- One-time activation token, not staff-set passwords - invitation creates an account with a null password and a random single-use token stored in Redis with a 72-hour TTL; activation consumes it with
GETDELso it is single-use even under concurrent requests, and the participant sets their own password (minimum 10 characters) - Brute-force lockout mirroring staff accounts - 5 failed logins lock the account for 15 minutes; a single generic "Invalid email or password" error prevents email enumeration on this public, internet-facing endpoint
- Read-only self-service views - upcoming (non-cancelled) appointments, own funding-pool balances, and service-agreement document METADATA only (
service_agreement,consent_form,agreementtypes); document binaries are never exposed to participant tokens - participants see what agreements exist and ask staff for copies - Booking requests that create NOTHING automatically -
approve_booking_request()marks intent and notifies the workflow but does not create a calendar event; staff then book through the normal calendar where every scheduling constraint (availability, travel time, caseload, clinical suitability) is validated - Ownership-enforced cancellation - a participant can cancel only their own pending requests; staff approve/decline with a response note
- Past-date guard - booking requests for a date in the past are rejected at creation
Feature 35 - Motor Accident & WorkCover Billing
(v1.2.36)
Maree-CareFlow natively bills across 13 Australian motor accident and WorkCover compensation schemes - the broadest coverage of any Australian allied health platform. A single service handles all of them because they share one operational model: an insurer approves a set number of sessions, the provider delivers against the approval, and invoices are addressed to the insurer (with the client named as recipient) rather than to the client.
The 13 schemes (12 in MOTOR_ACCIDENT_SCHEMES plus TAC VIC handled in hicaps.py):
- MAIB - Motor Accidents Insurance Board (TAS)
- NSW CTP - regulated by SIRA (NSW); invoiced to the insurer recorded on the claim (several licensed insurers, and a separate CTP Care guideline for some claims), never a payer the product assumes
- MAIC CTP - Motor Accident Insurance Commission (QLD)
- SAICORP CTP - SA
- ICWA - Insurance Commission of WA (WA)
- MAIC - Motor Accident Injuries Commission (ACT)
- Motor Accidents NT - Territory Insurance Office (NT)
- WorkCover NSW (iCare) - NSW
- WorkSafe Victoria - VIC
- WorkCover QLD - QLD
- ReturnToWorkSA - SA
- WorkCover WA - WA
- TAC - Transport Accident Commission (VIC), handled in
hicaps.py
Key capabilities:
- Per-session audit log, not a counter - session usage is tracked in
motor_accident_session_log(one row per appointment) rather than a single counter on the plan, giving a complete audit trail of which appointments were billed to which insurer - required by most CTP and WorkCover schemes for retrospective audits and dispute resolution - Pre-approval enforcement -
record_session_used()blocks recording once all approved sessions are consumed, returning a clear "a new pre-approval is required" error so the insurer cannot later refuse payment for over-limit sessions - Insurer-addressed invoices -
create_claim_invoice()generates an invoice with the insurer as the billing party (not the client), marks the included session-log rowsbilled_to_insurer = true, and stamps anINS--prefixed reference - Approval status queries - approved vs used vs remaining with an
is_exhaustedflag and approval start/end dates - Scheme metadata registry - each scheme code resolves to name, state, insurer, and website; an unknown code raises with the list of valid schemes
Feature 36 - Aged Care & Support at Home
(v1.2.36)
Maree-CareFlow manages aged care clients alongside NDIS and injury-scheme caseloads, covering ACAT assessments, Home Care Packages (HCP), and the July 2025 Support at Home (SAH) program - so a multidisciplinary practice can run all funding streams in one system.
Key capabilities:
- Auto-calculated HCP budgets from level - package budgets are derived from
HCP_ANNUAL_BUDGET_CENTS(2024-25 AIHW rates: Level 1 $10,588, Level 2 $18,622, Level 3 $40,529, Level 4 $61,440) rather than entered by hand, preventing data-entry errors and keeping every package on the current published rate; rates are updated annually in the constants dict, not the database, because they apply uniformly to all clients at a level - ACAT assessment records - assessment date, approval type (residential_care / home_care / short_term_restorative / transition_care), assessor and ACAT team, HCP level, SAH approval and classification, approval and expiry dates
- Eight SAH support categories - independence, everyday_living, social, clinical, allied_health, assistive_tech, home_mod, care_management; SAH unit rates are captured per claim (not from a code constant) because they vary by service type and provider metro/regional/remote status, mirroring the NDIS price-catalogue approach
- Balance updated on approval, not submission -
unspent_balance_centsis reduced only when a claim moves to approved/paid (submitted claims may be rejected), so the displayed balance never wrongly drops for claims that never get paid - HCP utilisation calculation - budget, spent (summed from approved/paid SAH claims), remaining, and utilisation percentage per package
- Org aged-care dashboard - active HCP count, pending claim count, and month-to-date approved/paid claim value
Feature 37 - ABA Bank Files
(v1.2.38)
Maree-CareFlow generates ABA (Australian Bankers Association) direct-entry files per the APCA/AusPayNet "cemtex" specification so practices can pay staff through any Australian bank's batch-upload facility instead of typing transfers by hand.
Key capabilities:
- Spec-exact fixed-width records - 120-character records with CRLF endings: a Type 0 descriptive record (financial institution code, user preferred name, APCA user ID, processing date), Type 1 detail records (BSB, account, transaction code 53 = pay, amount in cents, account title, lodgement reference, trace BSB/account, remitter name), and a Type 7 file-total record (BSB 999-999, net/credit/debit totals, detail count)
- Balance validation before a byte is written -
validate_aba_payments()andvalidate_sender()raise on bad BSB format, non-digit account numbers, non-positive or over-limit amounts, empty batches, or a malformed APCA user ID (must be exactly 6 digits) BEFORE the file is built, so a batch a bank would reject can never be downloaded - Employee bank details supplied per request, never stored - Maree-CareFlow does not persist employee personal bank accounts (payroll PII with its own breach consequences); the payroll officer supplies the bank lines at generation time, and only the organisation's own disbursement account is stored
- Net amounts from the single payroll source of truth - gross is computed by the same SCHADS Award calculations used by the payroll export and STP2 pay runs, and PAYG withholding from the STP2 engine is subtracted to give the net amount actually transferred (withholding field in the bank file is zero - PAYG is reported via STP2, not bank-withheld)
- Truncation, not failure, on overlong fields - the ABA spec defines hard field widths; a long account title is truncated to the field width rather than blocking the whole pay run
Feature 38 - IHI Validation
(v1.2.36)
Maree-CareFlow validates and verifies the Individual Healthcare Identifier (IHI) - the unique identifier used by My Health Record, electronic prescribing, and clinical data sharing across the Australian healthcare system. Without a verified IHI, uploads to My Health Record are rejected by the ADHA gateway.
Key capabilities:
- Local format + Luhn validation - IHI numbers are validated as 16 digits beginning with
800360with a Luhn check digit before any network call - SOAP over NASH mutual TLS to the HI Service - the Services Australia HI Service is a legacy SOAP/XML web service requiring mutual TLS with a NASH (National Authentication Service for Health) X.509 certificate that proves the practice's identity via its HPI-O; this is the only SOAP integration in the platform - all other APIs are REST
- Demographic search or direct IHI lookup - verification accepts family name, given name, DOB, and sex, optionally with an IHI number for a direct lookup; the parsed response returns verified status, IHI status (Active), and record status (Verified/Unverified)
- Mandatory lookup logging for Privacy Act / ADHA compliance - every IHI access is written to
ihi_lookup_log(org, client, performed_by, IHI number, status, verified flag, timestamp, error detail) as required by the Privacy Act 1988 and the My Health Record Rules 2017 - Dev-mode mock responses - when
HI_SERVICE_URLis unset (no NASH certificate in dev/test) a mock verified response exercises the full code path; production must configureHI_SERVICE_URL,NASH_CERT_PATH, andNASH_KEY_PATH - Most-recent status retrieval - the latest verification result per client is queryable for display alongside the client record
Feature 40 - MYOB Integration
(v1.2.36)
Maree-CareFlow performs a full MYOB AccountRight OAuth2 + REST API sync, pushing approved invoices and syncing contacts so the practice's books stay reconciled without double entry.
Key capabilities:
- Full OAuth2 lifecycle - authorization-URL generation, code exchange, and token refresh against
secure.myob.com, with a 60-second expiry safety buffer so tokens refresh before they actually expire - Company-file selection - MYOB organises data inside standalone "company files" (one account may have several); the API embeds the selected company file's Uri in every data-request path, so the chosen Uri is stored alongside the tokens
- Tokens in Redis, not the database - access/refresh tokens are short-lived ephemeral credentials (key
mcf:myob:tokens:{org_id}), not business data; Redis TTL and atomic operations suit them better than a Postgres migration per integration - Contacts and sales sync - MCF clients map to MYOB Customer contacts and approved MCF invoices map to MYOB Sales/Invoices
- Dev-mode mock responses - when
MYOB_CLIENT_IDis unset, every API method returns realistic mock data so UI and endpoint tests run without registered MYOB credentials; the mock flag is always False in production - Per-call Redis connections - connections are opened per call and closed immediately, so no persistent pool is needed
Feature 41 - Zapier & Make Webhooks
(v1.2.36)
Maree-CareFlow delivers outbound webhooks with HMAC-signed payloads so no-code automation platforms (Zapier, Make, n8n) can react to platform events while cryptographically verifying every payload is genuine.
Key capabilities:
- HMAC-SHA256 payload signing - each delivery is signed with a per-endpoint secret so the receiver can verify both authenticity (it came from MCF) and integrity (the payload was not tampered with); an API key in a header only proves identity, not integrity - the same reason GitHub, Stripe, and Shopify use HMAC-SHA256
- Nine events that actually fire - invoice.created, invoice.paid, claim.submitted, appointment.created, appointment.cancelled, appointment.completed, client.created, client.updated and note.created. Each is recorded inside the same transaction as the change it describes and handed on only after that change commits, so a rolled-back change sends nothing
- Where sending runs - on the background worker, which Docker and Ubuntu installs run. A shared cPanel install runs no worker, so there a delivery waits in the delivery log until an administrator presses Resend
- Retry - a refused delivery is recorded with its response and marked for retry, but nothing re-sends it automatically yet: an administrator presses Resend
- Auto-deactivation after 5 consecutive failures - an endpoint that fails 5 times in a row likely has a permanent error (deleted server, changed URL); it is deactivated and the admin is notified to re-enable it after fixing the issue
- Full delivery log - every delivery is recorded (with response body capped at 2000 chars) so admins can diagnose why an automation stopped and manually resend failed deliveries without replaying the original event
Feature 42 - FHIR R4 API
(v1.2.36)
Maree-CareFlow exposes a FHIR R4-compliant read API that maps its ORM models into standards-based clinical resources for interoperability with My Health Record, electronic referral systems, GP practice software, and hospital systems.
Key capabilities:
- FHIR R4 specifically - R4 is the current HL7 stable release, the version ADHA mandates for My Health Record, and the version used by the HL7 AU Base IG that defines Australian-specific extensions
- Australian canonical identifier systems - resources use the AU Base IG system URIs for IHI, HPI-I, HPI-O, Medicare, and AHPRA registration numbers, plus SNOMED CT and LOINC, so consumers like My Health Record can recognise and validate the identifiers (ad-hoc URIs would be unrecognisable to other systems)
- Read-only, export-only mapping - MCF is the source of truth; FHIR resources are generated on-demand for read-only export, and inbound FHIR (eReferral intake) is handled separately in
healthlink.py, so malformed FHIR input can never corrupt MCF data - CapabilityStatement - advertises the supported resources (Patient, Practitioner, Encounter, and more) with their read/search-type interactions and search parameters
- Plain-dict serialisation - resources are emitted as plain dicts that serialise directly to the required JSON shape, standard practice for lightweight FHIR servers and avoiding a parallel Pydantic schema library for deeply nested FHIR types
- AdministrativeGender mapping - MCF gender values map to the HL7 AdministrativeGender value set
Feature 43 - My Health Record Upload
(v1.2.36)
Maree-CareFlow uploads clinical documents to the Australian Digital Health Agency (ADHA) My Health Record system using FHIR R4 DocumentReference, improving care coordination for NDIS participants and aged care clients with complex, multi-provider support needs.
Key capabilities:
- FHIR (not CDA) uploads - ADHA transitioned from HL7 CDA to FHIR R4 for new integrations from 2024; FHIR is JSON-based, simpler, and aligns with the MCF FHIR R4 service (CDA remains for legacy only)
- Five LOINC-coded document types - Discharge Summary (18842-5), Referral Note (57133-1), Specialist Letter / Transfer of care (34140-4), Diagnostic Imaging Report (18748-4), and Pathology / Chemistry study (11526-1)
- NASH mutual TLS, shared with the IHI Service - uploads authenticate with the same NASH certificate used for IHI lookups; both services authenticate the provider organisation via the HPI-O on the certificate
- The participant's decision comes first - an upload is refused unless the participant's record carries a recorded information-sharing consent (Consent tab, "Information sharing"), the participant belongs to the uploading practice, and the document is filed against that same participant. The refusal names the consent that is missing and nothing is sent or logged (My Health Records Act 2012 s 45: a healthcare recipient may advise that a document is not to be uploaded)
- Refuses rather than pretends when not configured - with
MHR_FHIR_BASE_URL,NASH_CERT_PATHandNASH_KEY_PATHnot all set, an upload is refused with a message naming the missing settings; no "mock" upload is recorded, so nothing in the product can read as "shared with the care team" when it was not - Upload audit log - every upload actually attempted against ADHA is logged as
uploaded(only when ADHA returns a document id) orfailed, for traceability and ADHA compliance; refused requests are not uploads and are not logged as one
Feature 44 - Electronic Signatures
(v1.2.36)
Maree-CareFlow e-signs service agreements, consent forms, and reports via DocuSign (primary) with Australia Post eSign as an Australian-hosted alternative, producing signatures that are legally binding under the Electronic Transactions Act 1999 (Cth).
Key capabilities:
- DocuSign primary, AU Post eSign fallback - DocuSign offers Australian data residency (AP1 region) and broad NDIS-sector adoption; AU Post eSign stores all document data in Australia and is operated by an Australian government business enterprise for practices that require sovereign hosting
- DocuSign Connect webhooks, not polling - envelope status changes are pushed to a callback URL in near real-time, updating the MCF database immediately when a signer completes signing (polling is rate-limited and adds latency)
- HMAC signature verification on the webhook - the DocuSign Connect webhook is otherwise unauthenticated, so the
X-DocuSign-Signature-1header is verified against the Connect subscription's HMAC key to prevent forged completion events that could mark an agreement signed when it was not - Full envelope lifecycle - create envelope, route to signer, and receive completion; signed documents return to the client's document vault
- Dev-mode mock responses - when
DOCUSIGN_INTEGRATION_KEYis unset, the full envelope lifecycle is simulated so the signing workflow can be developed and tested without live credentials
Feature 45 - SMART on FHIR
(v1.2.38)
Maree-CareFlow implements the SMART App Launch 2.0 standalone launch flow so registered third-party clinical apps can connect securely - the same standard adopted by major hospital systems worldwide.
Key capabilities:
- Standalone launch with PKCE S256 - apps discover endpoints via
/.well-known/smart-configuration, send the user to/fhir/smart/authorize(PKCE S256 for public clients), and exchange the code at/fhir/smart/tokenfor a JWT access token scoped to the granted SMART scopes plus patient context - Single-use authorization codes in Redis - codes live in Redis with a 5-minute TTL per RFC 6749;
GETDELgives atomic single-use semantics even under concurrent redemption, and the TTL enforces expiry without a cleanup job - Mutually exclusive credential classes - SMART access tokens are JWTs signed with the deployment's existing RS256 keys but carry
token_type"smart", so a SMART token can never pass the staffverify_token(expected_type="access")check and a staff token can never pass the SMART check - the two classes are exclusive by construction, with no new key material to manage - Read-only scopes only - write scopes are intentionally absent (the FHIR API is read-only); granted scopes include
openid,fhirUser,launch/patient, andpatient/*.readfamily scopes - Structural scope coverage -
covers_scope()understands SMART hierarchy so apatient/*.readgrant correctly coverspatient/Patient.read, which a naive set-membership check would wrongly reject - Advertised capabilities - launch-standalone, public and confidential-symmetric clients, patient permissions, and standalone patient context
Feature 46 - Calendar Sync (ICS Feeds)
(v1.2.38)
Maree-CareFlow gives each practitioner a secret per-practitioner ICS feed URL that Google Calendar, Outlook, and Apple Calendar subscribe to natively - sovereign calendar sync with no Google/Microsoft API keys, OAuth consent screens, or webhook infrastructure, because the calendar apps poll the URL themselves.
Key capabilities:
- Privacy-minimised event summaries - the event SUMMARY uses first name + surname initial only (e.g. "Sarah M.") because the feed ends up inside Google's/Microsoft's calendar storage and on every synced device; a full client name there would spread identifiable health-service information beyond systems MCF controls
- Suburb-only location - LOCATION carries the suburb only, for the same privacy reasoning - a street address plus an appointment time in an external calendar would disclose where a client lives
- UTC "Z" times, no VTIMEZONE block - DTSTART/DTEND are emitted as absolute UTC per RFC 5545, which every consumer renders correctly in the user's local zone including across AEST/AEDT daylight-saving transitions, sidestepping the error-prone VTIMEZONE alternative
- Instant token rotation - rotating a feed token replaces it in place (practitioner_id is unique), so the old URL dies the instant a new one is issued
- Rolling feed window - 30 days of past events (so recently completed visits stay visible) plus all future events
- RFC 5545-correct escaping - text fields are escaped per section 3.3.11 (backslash, comma, semicolon, newline)
Feature 47 - Single Touch Payroll Phase 2
(v1.2.38)
Maree-CareFlow includes a full STP Phase 2 pay-event engine that builds pay runs from SCHADS shift data, calculates PAYG withholding and the superannuation guarantee, and generates STP2 PAYEVNT.0004 payloads. The pay-run engine is fully built; direct ATO production submission is coming soon, pending the practice's SSP registration, software ID, and machine credential - the engine runs in dev mode until those are configured.
Key capabilities:
- Gross pay from the single payroll source of truth - gross reuses
calculate_schads_rate()and_fetch_payroll_rows()frompayroll_export.py, so the Xero/MYOB payroll exports, the ABA bank file, and the STP2 pay event all agree to the cent; this service only adds tax and super on top - ATO Schedule 1 (NAT 1004) coefficient PAYG - PAYG is computed from the piecewise-linear formula
y = a*x - b(x = floor(weekly earnings) + 0.99), reproducing the printed lookup-table values exactly for any income, using scale 2 (resident who has claimed the tax-free threshold, Medicare levy included) with the stage-3 rates effective 1 July 2024 and the 2026-27 coefficients from 1 July 2026. Since G-199 the scale follows each employee's recorded tax file number declaration, from the 2026-27 withholding schedules (F2026L00716): scale 1 when the threshold is not claimed, scale 3 for a foreign resident, the Schedule 8 coefficients for a study and training support loan debt, and scale 4 (47%, or 45% for a foreign resident) when no TFN was quoted - each proved against every sample row the instrument publishes. A working holiday maker (Schedule 15), a TFN applied for within its 28 days, a claimed exemption, and any scale other than 2 before 1 July 2026 are reported by the pay run rather than withheld a guess - Weekly-equivalent conversion for any pay cycle - period amounts are converted to a weekly equivalent (period_days/7), withheld, then multiplied back, so weekly, fortnightly, and ad-hoc periods all withhold consistently per the ATO method
- 12% super guarantee - the legislated rate from 1 July 2025 (final step of the SG schedule)
- Self-correcting YTD figures - STP2 is a year-to-date REPLACEMENT model, so YTD is recomputed each run by summing all submitted/finalised runs in the financial year plus the current run; a missed run simply means the next run's YTD catches up
- Honest "coming soon" submission status - production ATO submission is pending SSP registration / software ID / machine credential; until configured the engine produces the payload and runs in dev mode rather than transmitting to the ATO
Feature 49 - Equipment & Assistive Technology (AT) Management
(v1.2.45)
A fully integrated, end-to-end module for the entire equipment / assistive-technology lifecycle - from a simple therapist recommendation through chain-of-command approval to direct supply, third-party supply, hire, purchase, or loan from an internal pool. Built for the reality that some organisations run a full AT supply and loan operation while others only capture recommendations, so every capability is independently switchable by the organisation manager.
Key capabilities:
- Organisation-level enable/disable - the module and each capability are opt-in per organisation via seven toggles on the
organisationsrecord:equipment_module_enabled,equipment_require_approval,equipment_loans_enabled,equipment_hire_enabled,equipment_direct_supply_enabled,equipment_third_party_supply_enabled, andequipment_approval_levels(number of chain-of-command levels). Managers control these from the Equipment > Settings tab; the API enforces them server-side. - Self-entered or catalogue items - a recommendation can reference a master catalogue device or a free-typed custom device name and description, so practitioners are never blocked by a missing catalogue entry. The catalogue captures name, description, category, manufacturer, model number, NDIS AT code and AT level (1-4), unit price, GST applicability, default supplier, and whether the item is loanable.
- Six supply modes -
recommendation(advice only),direct_supply,third_party_supply,hire,loan, andpurchase. The create flow only offers the modes the organisation has enabled, and the service rejects any disabled mode defensively. - Flexible approval routing - either a simple therapist recommendation/issue (no approval) or multi-level chain-of-command approval. The pure
next_status_after_approval()helper advancescurrent_approval_leveland resolves the recommendation toapprovedonly once the configured number of levels have signed off; any level can reject. Every decision is written to an immutableequipment_approvalsaudit row (approver, level, decision, comments, timestamp). - Loan-pool management - physical inventory units (
equipment_items) carry asset tag, serial number, condition, status, and location. Checkout is allowed only foravailableunits when loans are enabled; the unit flips toon_loanand anequipment_loansrow is created with a due date. Return records the returned condition and frees the unit. Overdue detection is a pure, testable function. - Supplier directory - direct and third-party suppliers (name, type, contacts, ABN, website) link to catalogue items and third-party-supply recommendations.
- Fully tenant-scoped and audited - every table carries
organisation_id; all reads and writes are organisation-scoped, and the recommendation/approval/loan history forms a complete, defensible record for NDIS plan management and AT funding requests. - Client / representative acceptance and sign-off - whatever the supply mode, the recipient side can sign or otherwise accept the equipment. Each recommendation carries an
acceptance_status(not_required/pending/accepted/declined), seeded from the per-organisationequipment_require_acceptancetoggle. An acceptance record (equipment_acceptances) captures who accepted - client, case manager, family, guardian, advocate, or other - their name and relationship, the method (esignature,portal,verbal,paper,email,in_person), an accepted/declined flag, an optional signature reference (e-sign envelope id, uploaded document, or URL), and the staff member who recorded it. When acceptance is required, billing is blocked untilacceptance_statusisaccepted(the purecan_generate_charge()helper takes the acceptance dimension into account), so equipment is never charged before the client or their representative has agreed. - Integrated billing (org-supplied only) - each recommendation carries a
billing_statusderived from its supply mode. Organisation-supplied modes (direct_supply,hire,purchase,loan) arependingand can be turned into a billable charge withPOST /equipment/recommendations/{id}/bill, which creates aTimeEntryline (quantity x unit price, GST per the catalogue flag) that flows into the normal invoice-batch / NDIS-CSV pipeline and links back viatime_entry_id.third_party_supplyisexternal_third_party- the third-party supplier invoices the client directly and no charge is ever raised in Maree-CareFlow. Advice-only recommendations arenot_applicable.
Feature 51 - NDIS Plan Management (the org acting as a plan manager)
(v1.3.35; gated by the plan_management module - HTTP 402 if not enabled)
When the organisation is itself a registered NDIS plan manager, it manages the funding of its participants' plans: it receives invoices from OTHER providers, pays them out of each participant's NDIS budget, claims reimbursement from the NDIA, charges its plan-management fees, and keeps a trust account of money held on behalf of participants. This is distinct from the org billing for its own delivered supports (Features 11-19).
Key capabilities:
- Managed plans + per-purpose budget ledger - a managed plan per participant
with a budget split across the three NDIS support purposes (Core / Capacity Building / Capital); a budget summary shows committed spend, remaining, and utilisation per purpose.
- Inbound third-party provider-invoice capture - record invoices received
from other providers against a participant's plan.
- Hard budget-drawdown guard - approving an invoice that would exceed the
participant's plan budget is rejected (HTTP 400), so the plan manager never disburses beyond what the NDIA will reimburse.
- Provider disbursement + trust accounting - pay approved invoices
(ABA-ready), recorded against a trust-account ledger with a running balance.
- Plan-management fees - setup (
14_033_0127_8_3) and monthly
(14_034_0127_8_3) fee items, overridable amounts. Each is checked against the practice's imported price guide, or with none imported the NDIA price document the product ships for the fee's date - the 2026-27 Pricing Schedule from 1 July 2026, the 2025-26 Pricing Arrangements (v1.1) from 24 November 2025. Neither publishes the set-up item, so from 24 November 2025 it is refused, with the reason and the document named beside the button.
- NDIA reimbursement claims - bundle paid provider invoices + pending fees
into a claim batch with a CSV export and mark-paid (which credits the trust ledger).
- Participant statements - per-plan spend statements.
pm_plans, pm_budgets, pm_provider_invoices, pm_payments, pm_claims, pm_fees, pm_trust_ledger). API (manager-gated, prefix /plan-management): plans, budgets, budget-summary, invoices (capture / approve / reject), payments, fees, claims (generate / mark-paid / export.csv), trust-ledger, statement. Frontend: Plan Management console at /plan-management.
Feature 52 - In-App Bug / Feedback Reporting (on every page)
(v1.3.80, "Suggest an improvement" added in v1.6.0; permanent, first-class - available to every authenticated user on every page)
A "Report & Suggest" button is present on every authenticated page so a client can report a bug, data issue or idea, or suggest an improvement (saved as the type Suggestion with a helpfulness rating, filterable in the Feedback Inbox), without leaving what they are doing, finding an email address, or logging a ticket elsewhere. It is built once and inherited everywhere: a single FeedbackWidget is mounted as the last child of each authenticated layout (Shell + PortalShell), so every current and future page gets it identically.
Key capabilities:
- Durable, encrypted system of record - each report is stored in the practice's own
PostgreSQL (bug_reports, migration 0072); the free-text description is AES-256-GCM encrypted at rest (a user may paste incidental detail despite the in-widget warning).
- Best-effort notification email to
SUPPORT_EMAIL(defaultsupport@the practice's
own domain - reports never go to the vendor unless the practice routes them there). By default (FEEDBACK_EMAIL_INCLUDE_DESCRIPTION=false) it carries metadata only and keeps the description in the encrypted inbox. The email_notified flag is honest.
- Admin Feedback Inbox (
/mcfadmin/feedback, org-manager+) - org-scoped, paginated
triage (Open -> Triaged -> Closed).
- PHI-safe + abuse-proof by design - auth-only (org/user from the JWT); no screenshot/
DOM/console/app-state capture, only typed text + a best-effort sanitised route pattern; a hard per-user daily cap (429) that is the hard bound on mailbox volume, plus secondary per-org and global email caps (stored-but-not-emailed past them).
migration 0072_bug_reports (1 table + 3 native enums). API (prefix /feedback): POST (any active user), GET + PATCH /{id} (org-manager+). Frontend: