Skip to content
Corella

Your words

Corella speaks your organisation's language, not ours.

Every sector has its own word, and in each one it is the word. A community nursing service says patient. An NDIS provider says participant, because that is the word in the Act. Supported accommodation says resident, aged care says care recipient, and a peer-support service says consumer on purpose. There is no correct default — which is exactly what a setting is for. So in Corella it is one, and the interface follows whatever you choose.

How it flows

Terminology flow: an administrator picks the word their organisation uses for the people it supports, Corella stores all four word forms rather than deriving them, and one save carries the word through every screen and into exported report and CSV headers — while three things deliberately never follow the setting: web addresses stay as they are, documents a funding scheme requires keep the scheme's own wording, and no record is changed because it is a display setting rather than a migration.singular · plural · titlesone savedown to the headerswhat it never changesnor the scheme's wordingso it is safe to change your mindand no record movesPick your wordeight choices or your ownFour forms storednever derivedEvery screen followsnav · headings · filtersReports & CSV headersthe word travelsWeb addresses/clients — unchangedScheme documentsparticipant, by lawYour recordsdisplay only — nothing moves

The word travels everywhere you read it — and deliberately nowhere that a link, a statute or a stored record depends on it.

One picker, and the whole interface changes its mind

Settings → Roster display → “What you call the people you support”. Eight ready-made choices — client, patient, participant, resident, care recipient, consumer, customer, member — plus the option to type your own. Save, and the word changes in the sidebar, the page headings, the table column headers, the filters, the empty states, the pickers, the dialogs, the confirmation messages, the report titles, and the headers of every CSV you export. It is one setting for the organisation, not a per-person preference.

Eight ready-made choicesOr type your ownDown to the CSV headers
your-organisation's Corella
Corella with its terminology set to Patient: the sidebar reads Patients, Episodes of care and Consumables, and the list heading and table column both read Patient
One setting — and the sidebar, headings and table columns all follow

All four word forms are stored, never guessed

Singular, plural, title case and title-case plural are kept as four separate values, because deriving them breaks in ways you would notice every day. Adding an s turns person into persons, so an organisation that wanted to say person and people would have been stuck with the wrong plural. Capitalising the first letter renders care recipient as Care recipient on one screen and invites Care Recipient on the next. Corella asks for all four and then uses the right one in the right place — the patient's plan mid-sentence, Patients on a nav item.

Singular & pluralYour capitalisationperson → people

Nothing in the address bar moves

This is the first thing a switching provider asks, and the answer is that web addresses never follow the setting. /clients stays /clients whatever you call the people listed there. Bookmarks your team has kept for months keep working, links inside emails already sent keep working, and the magic links that get a family into the portal keep working. The word is a label on the screen, not a route — which is precisely why changing it is safe.

/clients stays /clientsBookmarks keep workingPortal links unaffected

Documents a scheme requires keep the scheme's own words

Some words are not yours to choose, and software that pretended otherwise would be doing you a disservice. An NDIS service agreement says participant because that is the word in the Act. An NDIA payment request says Participant because the scheme's own file says so. A Support at Home statement says care recipient. Those documents carry the scheme's vocabulary no matter what you have set, and that is correct behaviour rather than a limitation. The honest way to put it, and the way the product puts it: the interface follows your words; documents a scheme requires keep the scheme's.

The Act's word winsInterface follows youNo surprises at audit

A display setting, not a migration

Choosing a different word does not touch a single record. The underlying data, the relationships and the history all stay exactly as they were, so there is no migration to schedule, no downtime to plan and no risk to weigh — you can try patient on a Tuesday and go back to client on a Thursday. Documents you have already generated keep the wording they were issued with, because an invoice or an agreement is a record of what was sent; re-rendering history in new vocabulary would be the wrong thing to do, so Corella leaves it alone.

No data changesReversibleIssued documents untouched

And the word for your own people

The people you support are only half of it. The generic word for the people who deliver the work is its own setting too — carer, support worker, nurse, clinician, care worker or staff member — so a nursing service's screens read visible to nurses rather than visible to carers. The two settings pair up the way real organisations do: a wound service says patient and nurse, an aged-care provider says care recipient and care worker, and a supported-accommodation house says resident and support worker. Being straight about the boundary: this is four settings — the people you support, your role names, the episode of care, and the people who deliver it — not a rename of every noun in the product. And where a form asks about a family carer, that word deliberately stays carer, because there it means the person's own family rather than your staff.

Carer → nurse → clinicianPairs with your other wordFour axes, not every noun

The same choice for an episode of care

The word for a funded piece of work is its own setting, built the same way: case, episode of care, referral, claim, or something you type. A clinic that thinks in referrals and a nursing service that thinks in episodes both get to say so, and the same three rules hold — interface only, addresses unchanged, history intact.

CaseEpisode of careReferralClaim

Works with the rest of Corella

Clinical & episodes of care

the capabilities that came with the wider vocabulary

Care management

the record the word appears on, everywhere

Compliance & documents

where the scheme's own wording takes over

Fair questions

Asked about this, often.

So Corella isn't only for NDIS providers?
Correct, and this setting is the clearest evidence of it. The operational spine — rostering, records, evidence, invoicing, payroll — is the same work whether you are a disability provider, a community nursing service, an allied health practice, a supported accommodation service or an aged-care provider. What differed was the vocabulary, and that is now yours to set. The NDIS specifics are still there in full for the providers who need them; they are simply no longer imposed on everyone else.
What if our word isn't one of the eight?
Type your own. You supply the four forms — singular, plural and both title-case versions — and Corella uses them exactly as you wrote them, up to forty characters each. That limit exists so a long word cannot break a nav item, not to discourage you.
Can different teams inside one organisation use different words?
Not today — it is one choice per organisation, deliberately, because a shared record that two teams describe differently is a record two teams read differently. If you run genuinely separate services that need separate vocabularies, that is a conversation worth having on the call, and the honest answer today is that it would mean separate instances.
Will an NDIS service agreement say our word instead of participant?
No, and it should not. The Act uses participant, so the generated agreement uses participant. The same goes for the NDIA payment request and a Support at Home statement. Your interface follows you; the statutory paperwork follows the scheme. Anyone who offers you the other version of this has not thought about what happens at audit.
Is there any risk in changing it later?
No. It is a display layer, so there is nothing to migrate and nothing to undo — the setting can move as often as you like, and the records underneath never notice. The only thing that stays fixed is documents already issued, which keep the wording they went out with.
Does it change what our staff see on their phones?
Yes — the carer app is the same application, so it follows the same setting. A nurse sees patient and a disability support worker sees participant without anyone maintaining two versions of anything.

See your organisation in Corella.

A 30-minute walkthrough with the people who built it — your workflows, your terminology, not a canned demo.

Book a demoor email sales@corellacare.com.au