Rostering sits in one product, claims in another, incident forms in a shared drive and participant notes in three places. Then a support worker asks which version of a behaviour support plan is current, and nobody can say. The usual answer is a bigger spreadsheet. The better answer is deciding which parts of your provider software you should buy, which you should connect and which, if any, are worth building.
Devvista is a software development company. This page is for registered NDIS providers in Australia. It covers build versus buy, what the NDIA publishes for software developers, which Commission rules touch software, and how to keep participant data safe.
Build, buy or connect: which parts of NDIS provider software to own
Most providers are best served by a ready NDIS platform for the core job, and we say so plainly. A purpose-built product already carries years of fixes for claiming rules, roster edge cases and reporting. Building that from nothing rarely pays back for a single provider.
Custom work earns its place at the edges: the intake and referral flow that is specific to how you win participants, a staff or family portal, a bridge between two products that do not talk to each other, or a reporting view your board actually reads. The table is our view, not a market survey.
| Part of the job | Usually best to | Why |
|---|---|---|
| Rostering and shift allocation | Buy a ready product | Award rules, shift swaps and worker availability take years to get right |
| Claiming and plan management | Buy or connect to a product | Claim rules and payment-system links change, and a vendor tracks them for every customer |
| Incident reporting and register | Buy, or build a thin layer | Fixed timeframes and record rules make this a fit for a standard form and workflow |
| Participant records and notes | Buy first, build only for gaps | Privacy and access control matter more than features |
| Referral intake and follow-up | Build or configure | This is where your process differs from the next provider; see our NDIS CRM page |
| Reports across systems | Build a small layer | A dashboard that reads from the products you already use |
If your gap is a single workflow and not a whole platform, read our notes on custom software development in Australia and business management software before assuming you need to replace anything.
What the NDIA publishes about API access
The NDIA has built APIs for registered providers, plan managers and software developers. They give approved entities controlled, secure access to specific NDIA data. Access is approved by the type of entity and its cyber security maturity, and applying does not guarantee access (Connecting with NDIA systems; API access for software developers, 30 June 2020). The same news item says the terms were widened so software developers working with registered providers can reach the APIs.
The NDIA asks you to contact its Digital Partnership Office at dpo@ndis.gov.au before applying, and not to start the forms or the cyber assessment first. Here is how the two routes differ, as the NDIA describes them.
| Route | What the NDIA says is needed | What it means for you |
|---|---|---|
| Direct integration | The Digital Provider questionnaire, evidence for the cyber clearance framework, a copy of the planned architecture, a current ASIC company extract dated within 4 weeks, and signed API terms and conditions | Real certification, testing and paperwork before any build starts |
| Software developers and aggregators | Partner with a registered provider, and complete additional cyber security activities | A developer cannot connect on its own; it needs a registered provider alongside |
| Indirect integration | A registered provider connects through an aggregator that is already a digital partner. The aggregator applies with the provider's ABN, provider number, address, email and phone, a primary contact, data residency information (stored within Australia) and a signed declaration from both | Usually the faster route for a single provider |
Standards sit on top. Applicants agree to the api.gov.au standards, hold suitable ICT certification as the cyber clearance framework specifies (ISO 27001:2022 is the example given), show appropriate cyber security maturity, use secure coding practices and, where appropriate, run penetration testing. Entities must test against all NDIA APIs whatever they need, and early testing does not mean approval. If approved, the NDIA sends a technical pack with an onboarding guide and PRODA (Provider Digital Access) guides, then a PRODA test account, then access to the API specifications in the vendor developer portal.
The practical reading: a provider rarely needs direct API access. If your product must talk to the NDIA, ask whether an aggregator that is already a digital partner already covers it. A custom build that needs direct access carries certification and testing work, and no guarantee of approval at the end.
- Before you hire anyone: work out which NDIA data your product truly needs, and whether an aggregator route covers it.
- Ask every vendor: do you connect directly or through an aggregator, and who holds the access?
- Our position: Devvista holds no NDIA API access and does not promise any. We are not endorsed, approved or registered by the NDIS or the NDIA. We build the software around your products and read these conditions with you.
Which NDIS Commission rules touch your software
The NDIS Commission sets the rules that registered providers work under. Three instruments matter most when you choose or build software. The text below comes from the Federal Register of Legislation: the Provider Registration and Practice Standards Rules 2018 as amended to 1 July 2026, the Incident Management and Reportable Incidents Rules 2018 and the Code of Conduct Rules 2018 (compilation of 19 December 2023).
| Rule | What it says | What it means for software |
|---|---|---|
| Practice Standards, Core module, information management (Provider Registration and Practice Standards Rules 2018, as amended to 1 July 2026) | Management of each participant's information ensures that it is "identifiable, accurately recorded, current and confidential", and is "easily accessible to the participant and appropriately utilised by relevant workers" | One record per participant, version history, role-based access, a way for a participant to see their own information |
| Practice Standards, incident management | Each participant is safeguarded by the provider's incident management system, so that incidents are "acknowledged, responded to, well managed and learned from" | An incident register with an owner, status and actions, not a loose form |
| Practice Standards, complaints management | Each participant has knowledge of and access to the complaints system, and complaints are "welcomed, acknowledged, respected and well managed" | A complaints log with dates and outcomes, linked to the participant |
| Code of Conduct (Rules 2018, 2023 compilation) | Covers NDIS providers and people they employ or engage; obligations include respecting the privacy of people with disability | Access limited to those who need it, and an audit trail of who opened what |
None of this tells you to use a particular product. It tells you what the product must let you show. Treat the Practice Standards text as the checklist your software has to support when an auditor asks how you manage records.
Incident reporting: what the software needs to do in the first 24 hours
Reportable incident rules are where software helps most, because the clock is short and the people involved are busy. Under the Incident Management and Reportable Incidents Rules 2018, reportable incidents include death, serious injury, abuse or neglect, unlawful sexual or physical contact or assault, sexual misconduct, and some uses of restrictive practices. Alleged incidents are treated the same as actual ones (Incident Management Rules 2018).
The same instrument sets the timing. The clock runs from when the provider became aware of the incident. Notification is due within 24 hours for the most serious categories, with remaining details within 5 business days if they were not available at first, and within 5 business days for other reportable incidents. The Commissioner can ask for a final report. Records must be kept for at least 7 years, and the Rules' own note says other laws may require longer.
The Commission says that from 12 October 2026 new incidents are lodged in the new NDIS Commission Portal (NDIS Commission, reportable incidents). Check that page for the current process before you design any export or hand-off.
What a good incident module does:
- Capture fast. A phone-friendly form a support worker can complete on shift, with the date and time the incident became known.
- Flag the clock. Mark likely reportable categories and show the deadline to key personnel.
- Assign an owner and keep a status, so nothing sits unread.
- Keep the record with edits tracked, and retain it for the period the rules set.
- Support review. Report counts by type and site, because the rules ask for statistics to find systemic problems.
Participant records and privacy: what the law expects of your system
The Australian Privacy Principles are the core of the Privacy Act 1988 and there are 13 of them (OAIC). Three bear directly on software choices: APP 6 on using or disclosing personal information, APP 8 on disclosure overseas, and APP 11, which includes taking "reasonable steps to protect personal information it holds" (OAIC quick reference).
Do the Privacy Act and the APPs apply to your business? The OAIC says most small businesses are not covered, but a health service provider is covered whatever its turnover, with allied health professionals among its examples (OAIC small business guidance). Whether a particular NDIS provider counts is a question for your adviser; do not assume either way.
| APP | Question to ask of any provider software | What to look for |
|---|---|---|
| APP 6 | Who can see a participant record, and can we limit it by role? | Role-based access, not a shared login |
| APP 8 | Where is data stored, and does anything leave Australia? | A named hosting location and a list of subprocessors |
| APP 11 | How is data protected and what happens when we stop using it? | Encryption, backups, an export of all your data, deletion on request |
| APP 12 | Can a participant ask for their record and can we produce it? | A single export per person |
| Notifiable breaches | Can we tell what was accessed after an incident? | An audit log |
A data breach brings its own duties. An eligible breach is one likely to result in serious harm, "likely" meaning "more probable than not". If you suspect one you must take all reasonable steps to complete an assessment within 30 calendar days, and notify affected people and the OAIC as soon as practicable when there are reasonable grounds to believe one has occurred (OAIC data breach guide). A system that records who accessed what makes that assessment faster.
Security checks to make before you sign with a vendor or a developer
These are our working checks, not a legal standard. They come from how we would review any system holding sensitive personal records, and your adviser may add to them.
- Access: individual logins, multi-factor sign-in, and a quick way to remove a leaver.
- Separation: support workers see the participants they work with, not everyone.
- Logging: an audit trail of views, edits and exports, kept where staff cannot change it.
- Data location: a stated hosting region, in writing.
- Exit: a full export in a usable format, so you are never locked in.
- Testing: a staging copy with made-up data, so real participant records never sit in a test system.
When we build for a provider, we usually propose staging with made-up data, a weekly demo and a written handover. These practices vary by project and are agreed in the quote.
Rostering, claiming and payroll: when not to build
These three are where we talk providers out of custom builds most often. Rostering must follow award conditions and last-minute swaps. Claiming depends on rules and connections the vendor maintains. Payroll must stay correct when pay rules change. A product used by many providers absorbs those changes for you.
The sensible custom work sits around them: a feed from your roster into a board report, a link that creates an incident record from a shift note, or an intake form that lands in the right queue. Our AI automation work covers that style of job, such as turning typed shift notes into a draft summary that a person reviews before it is saved.
Not sure which side of the line you are on? Describe the manual job you want gone. If it happens in only one product, ask that vendor first. If it spans two products, a small bridge is a realistic project.
Questions to ask any NDIS software vendor or developer
Use these on a sales call, whoever you speak to, including us.
- How does your product connect to NDIA systems, directly or through another product?
- Where is participant data stored, and which companies can reach it?
- Can I export everything, including notes, incidents and attachments, in a usable format?
- What does the incident module record, and can it show which incidents are reportable?
- Who owns the code and the data if we leave?
- How are releases tested, and can we see changes before they go live?
- What happens to our data if your company is sold or closes?
A confident vendor answers these in writing. Hesitation is useful information.
If you do build: a phased plan that limits risk
Build in small releases so the first one pays off before the second starts. This is the plan we usually propose, and the order can change with your needs.
- Map one process end to end. Pick the job that costs most time, such as incident capture or referral follow-up.
- List the systems around it and decide what connects to what, including whether an NDIA connection comes through an aggregator.
- Write the privacy rules first: who sees what, where data lives, how long it is kept.
- Build the smallest useful release on a staging copy with made-up data.
- Run it alongside the old method for a few weeks with a couple of staff.
- Hand over with documentation, admin training and a named person who owns the system.
We aim for each release to be usable on its own. A short call comes first, and the proposal follows from it.
How to tell your provider software is working
Pick a few numbers and read them monthly, rather than judging by how the system feels.
| Measure | Where it comes from | What a good change looks like |
|---|---|---|
| Time from incident to notification | Incident register | Shorter, and always inside the rule's timeframe |
| Records with missing fields | Participant record check | Fewer each month |
| Manual re-entry between systems | Staff time sample | Down after a bridge is built |
| Access requests handled | Request log | Handled and logged, not ad hoc |
These are labelled examples. Set your own baseline first.
Where Devvista fits
We can build the connecting layer for NDIS providers: intake and referral systems, incident and reporting tools, portals, and integrations between products you already use. We work online, and we design for participant data to sit in access-controlled systems with logging.
One more rule to know about. The NDIS Commission page on digital platforms says that from 1 July 2026 NDIS digital platform providers must register under a new class of support. These are online systems that act as intermediaries between participants and the people providing supports, with payments processed using plan amounts (NDIS Commission, mandatory registration of digital platforms). The page quotes a draft definition and refers to the final Rules. Software that a provider runs for its own service is generally outside that kind of definition, but check the Rules and ask your adviser before you assume.
A good fit if you have one or two workflows that no product covers well, or products that need connecting. Not a fit if you want us to replace a rostering or claiming product that already works; we will say so and point you to the buy route.
Related: NDIS CRM, NDIS provider marketing, NDIS website design, SEO for NDIS providers, software development for Sydney businesses, mobile app development, API development, our work and the Australia contact page, or return to the Australia hub.
Sources
- www.ndis.gov.au/providers/working-provider/connecting-ndia-systems
- www.ndis.gov.au/news/4886-api-access-software-developers
- api.developer.ndis.gov.au/sharedservices/ndis-api
- www.legislation.gov.au/F2018L00631/2026-07-01/2026-07-01/text/original/epub/OEBPS/docum...
- www.legislation.gov.au/F2018L00633/asmade/2018-05-18/text/original/word
- www.ndiscommission.gov.au/rules-and-standards/reportable-incidents-and-incident-managem...
- www.ndiscommission.gov.au/about-us/ndis-commission-reform-hub/mandatory-registration/ma...
- www.legislation.gov.au/F2018L00629/2023-12-19/2023-12-19/text/original/epub/OEBPS/docum...
- www.oaic.gov.au/privacy/australian-privacy-principles
- www.oaic.gov.au/privacy/australian-privacy-principles/australian-privacy-principles-qui...
- www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/orga...
- www.oaic.gov.au/privacy/notifiable-data-breaches/quick-reference-guide-for-responding-t...