125,000+
28,800+
340M+
$670M+
Healthcare can be complicated. We're here to simplify it, across every part of how you deliver care.
The Planner and Schedule Manager, with recurring Appointments, bulk actions and the whole roster on one screen.
Match workers by skills, availability and travel, with the shifts still open broadcast to everyone who can take them.
Every funding type on one agreement, with Agreement Items priced from your linked Price List and tracked as they are delivered.
Utilisation and over-budget status held on every Agreement Item, so remaining funding is known before the next service is booked.
The Participant Profile holds the whole record in one place: demographics, contacts, documents, Preferences and Connections. [COPY TBD]
Goals and plan structure sit against the participant, so what changes for delivery when a plan changes is visible in Maica. [COPY TBD]
Participant Notes support templates and are written on any device, with a separate note created for every participant in a group Appointment. [COPY TBD]
Incidents, near misses and hazards are logged from the Mobile Worker App against the Appointment and the participant. [COPY TBD]
Match the right worker to the right shift, and use Shift Broadcasting for the ones still open. [COPY TBD]
Check-in captures time and location, alongside notes, incidents, expenses and participant signature. [COPY TBD]
[CONFIRM scope: worker records, availability, payroll export, qualification tracking] [COPY TBD]
A single Service Agreement supports every funding type, including Combination, with rates from your linked Price List. [COPY TBD]
Funding is committed at Support Category or Support Item level, with Utilisation and over-budget status on each item. [COPY TBD]
Generate Invoices, Claim Batches and Payment Requests, submit by API or file, and reconcile remittance back to the Invoice Line Item. [COPY TBD]
Integrated Payments are taken through a compliant gateway and reconciled against the Invoice they belong to. [COPY TBD]
Every record Maica creates is reportable through Salesforce's own reporting tools, built and changed by your team. [COPY TBD]
Alerts and Dynamic Alerts are raised on the conditions your team sets. [COPY TBD]
Audit Trails, sharing rules and field-level permissions come from the Salesforce platform itself. [COPY TBD]
%201.svg){kind=icon}
Whether you deliver under the NDIS, Support at Home, Residential Aged Care, or any other funding structure. Maica is built to support it.
A fully connected NDIS solution, integrated natively with the agency and covering the whole participant lifecycle.
Support at Home, including everything from Budget Syncs to Monthly Statements and integrated Claiming.
From the day a resident moves in to the day they leave, with fees, Accommodation Deposits and Care Minutes all accounted for.
One note becomes the Appointment, the Participant Note and the Invoice Line Item behind it.
Maica talks to the NDIS, Services Australia, your payments and your finance system directly, from inside the same platform your team already works in.
%20white.png)
Plans, budgets and Service Bookings sync in from PRODA, and Payment Requests go straight back out.
Support at Home and Residential Aged Care, claimed end to end through the B2G channel.
Invoices and payments synchronise, so your finance team and your care team work from the same numbers.
Maica connects to the NDIS through PRODA. Participant details, Plans and Plan Budgets sync onto the Funding Record. Claims go out as Payment Requests. Responses come back against the line they came from.
Pull a participant's details, Plan and Plan Budgets straight from the NDIS. Maica keeps a single PACE Funding Record per participant, updating it as plan dates extend rather than creating a second one.
Maica subscribes to eleven NDIS events. Plan and participant changes arrive as they happen, so the Funding Record reflects the agency without anyone going to look.
Payment Requests are generated from Invoice Line Items and submitted in bulk. Responses return against the line item, and anything already inside an active claim cycle is locked out of reclaiming.
Classifications, Approved Services, Supplements, Individual Contributions and Budgets come straight from Services Australia against the active plan. Usage comes with them, by period and category.
Select the Invoice Line Items to claim. Maica builds the Claim Batch and its Payment Requests, submits them, and brings back status, the Payment Statement and payment detail to the line item.
Care Management funds are pooled at provider level, not per client. Maica retrieves them against your Service Provider ID, so the balance sits with everything else.
Entry, Departure, Leave and Supplement Events submit through the B2G channel on PRODA. Classifications, Approvals, Supplements and Balances return to the resident record, on demand or in bulk.
Payments run through Stripe and reconcile against the Invoice they belong to, inside Maica.
Take a payment against an Invoice and Maica records it, matches it, and updates the balance owing.
Every payment lands against the Invoice it came from. No exported list, no separate spreadsheet, no month end guessing which payment was whose.
Stripe handles the payment. Maica records the outcome. Card details never sit in your Salesforce org.
Invoices and payments synchronise with Xero. Your finance team and your care team work from the same figures.
Invoices raised in Maica appear in Xero. Payments recorded in Xero come back against the Maica Invoice.
Billing stays where care is delivered. Accounting stays where accounting belongs. Neither team re-keys the other's work.
Claiming, client contributions and private billing all resolve to Invoices in Maica, so what reaches Xero is already reconciled.
Maica Healthcare is a managed package built natively on the Salesforce platform. Not connected to Salesforce. Built on it.
Maica installs into your Salesforce org and runs beside whatever else you already have there. Same users, same login, same permission model.
Profiles, permission sets, sharing rules, field level security, encryption and audit history all come from Salesforce. Who saw a client's record, and who changed it, is answerable.
Every Maica object is reportable with Salesforce's own reporting tools. Your team builds and changes reports without raising a request with us.
Custom objects, custom fields, Flows, validation rules and Apex apply to Maica records like any other. Your process, not ours.
Sales Cloud, Service Cloud, Experience Cloud and Tableau work against the same records. AppExchange apps install alongside Maica rather than around it.
Short clips from providers using Maica every day, talking about what changed for their clients and their teams.
“Maica gives us structure, data and processes to help us understand how we are making a difference in the life of our customers”
See all Stories
“It is the cornerstone for us. Ensuring the information is correct, current and visible for everybody”
See all StoriesOffering all the benefits of Salesforce's security, reliability, and scalability, Maica provides seamless Data Management, comprehensive Reporting, and powerful Automation.
Sharing rules, field-level permissions and audit history come from Salesforce, maintained by the people who build the platform.
Learn MoreEvery record Maica creates is reportable through Salesforce's own reporting tools, built and changed by your team.
Learn MoreCustom objects, fields and Salesforce Flows are yours to configure. Maica runs on Flows throughout, so your team amends the process in the same place they built it.
Learn MoreMaica sits alongside everything else running on your Salesforce platform, sharing the same data, the same permissions and the same login.
Learn MoreThe questions providers ask us most about the core care management product.
Yes. Maica Healthcare is a managed package built natively on the Salesforce platform, so it runs inside Salesforce. That is deliberate: the security model, sharing rules, audit trails, reporting and extensibility come from the platform rather than being rebuilt by us.
Yes, and that is the point. Agreements, budgets, claiming and reporting all understand which program a participant sits under, so a provider delivering across NDIS, Home Care Packages, CHSP and Support at Home runs all of it in one system.
Yes. Maica is natively integrated with the NDIS APIs for participant, plan and claiming data, and with Services Australia for Support at Home and residential aged care recipient sync and claiming. The release of those digital integration APIs is what made Maica possible in the first place.
Yes. Workers check in and out of appointments, complete checklists, record notes, log travel and attach files and photos from a phone. Everything they capture lands on the same records your office team is working from.
Maica validates against overtime while you are scheduling, so the cost implication surfaces before a shift is committed. It also integrates with KeyPay for payroll and award interpretation.
Yes. Maica uses Salesforce Flows extensively, so business processes can be amended to match how your organisation works. Custom objects, fields, reports and permissions are all yours to configure.
Forms, Docs, Portals and Learning are separately licensable products that read and write the same Salesforce data. So a form can create a record, a document can be generated from it, and a participant can see the result in a portal, with no copy of your data in between.
