CarePoint EMR Book a demo
About CarePoint

Built on the floor — not in a boardroom.

CarePoint started as an allied-health clinician's frustration with every EMR they'd ever worked in, in every facility they'd ever set foot in. It became a system designed by the people doing the work — from the carer's first ADL of the morning to the DON's NQI submission at quarter's end.

AH Founded by an Australian aged-care clinician
The story

It started with one allied-health clinician and a lot of bad software.

For years, our founder worked across Australian residential aged-care facilities as an allied-health practitioner — moving between sites, using whatever EMR each facility had bought. They were all different. They were all bad in their own way.

Some systems were powerful but ugly, designed for a hospital outpatient clinic and bolted onto aged care as an afterthought. Others were friendly but shallow, with a sweet onboarding video and nothing under the surface to support a complex resident with restrictive practices, a behaviour support plan, and an unstable care minute trajectory. Most were neither — old systems, slow systems, systems that required four logins to record one wound photo.

The strangest part wasn't that the software was bad. It was that everyone knew it was bad. The carer cursing a 12-step ADL form. The RN trying to find a resident's allergies before the med round. The lifestyle coordinator entering the same engagement note in three places. The DON pulling NQI data into a spreadsheet the week before the accreditor came. The family member calling at 7pm because the portal didn't show them whether their mum had eaten lunch.

"Everyone in the building had a complaint about the software. Nobody had ever been asked what would make it better."

So we asked. For two years, before a single line of CarePoint was written, the team sat with carers, RNs, allied-health practitioners, lifestyle staff, facility managers, DONs and family members — across memory-care units, palliative wings, country facilities and metropolitan sites — and listened to every gripe, every wish, every quiet "I just wish it could…" murmured into a coffee at 3pm.

CarePoint is what came out the other side. Not a hospital system adapted for aged care. Not a generic SaaS dressed up in clinical language. A system designed from the resident outward, by the people whose shift it has to survive.

We're still small. We still visit facilities. We still answer our own support emails. We think that's a feature, not a phase — and we intend to stay that way as long as the work allows it.

What we believe

Six principles, written before the first feature was.

They were a hand-written list pinned above the founder's desk. They've moved between offices three times. They're still the lens we apply to every product decision.

01

The software serves the shift.

If a feature doesn't help someone do their work better on the floor today, it doesn't belong in the platform — no matter how good the demo looks.

02

Clinicians design clinical software.

Every screen is reviewed by working aged-care practitioners before it ships. We don't ship something to ask if it's right — we ask before we ship.

03

Compliance is a by-product, not a product.

If the work is documented honestly as it happens, the audit trail writes itself. Building features for accreditors instead of clinicians is how facilities end up resenting their EMR.

04

Configuration belongs to the facility.

You shouldn't have to raise a support ticket to add a chart template. We give you the controls — and our team is on call when you want a hand using them.

05

Names matter. Language matters.

"Care minutes", not "engagement units". "Resident", not "client". "Handover", not "shift transition". If the language of the software doesn't match the language of the floor, the software is in the way.

06

Trust is built one shift at a time.

We earn our place every quarter. No multi-year lock-ins. No hidden seat fees. Direct line to the team that built it. If we stop being worth it, you stop paying us — that's the deal.

Voices we built for

Every gripe became a feature.

Six roles, six recurring complaints we heard in every facility we visited — and the part of CarePoint each of them shaped.

RN
Registered nurses

"Half my shift is documentation I write twice."

"I'm not a typist. I'm a clinician. Every note I write ends up in three places — handover, progress notes, the incident form. I'm copying my own words to satisfy a system."

We built the timeline — every entry from every role threads back to one resident record. Handover composes itself overnight. The RN writes the note once.

PC
Personal carers

"The system fights me, the residents are waiting."

"Twelve clicks to record a shower. I haven't got time. So I either skip the documentation, or I skip the chat with Mrs Bianchi about her grandchildren. Guess which I pick."

We built a mobile-first task list with one-tap ADLs and observations. Recording care should take seconds, not interrupt it.

AH
Allied health

"My notes go into a black hole."

"I write a mobility recommendation. Two weeks later, the RN doesn't know about it because it's filed in a folder no-one opens. So we have the same conversation twice."

We built care plan ownership by discipline. Your note lands on the timeline, the handover and the next shift — colour-coded by role so its origin is obvious.

DN
Director of Nursing

"I find out about problems when it's already too late."

"By the time I see the falls trend in a monthly meeting, three more residents have fallen. I need to know the moment a pattern emerges, not the month after."

We built the clinical alert engine with configurable thresholds. Weight loss, falls frequency, BGL trends — surfaced the moment they cross the line your facility sets.

FM
Facility management

"Adding a casual RN takes a week."

"I want to add a user. I raise a ticket. I wait three days. I follow up. I wait two more. The casual already worked the shift without a login."

We built a full admin panel your team owns. Users, roles, permissions, ward structure — all configurable from inside the system, in minutes, no ticket required.

FY
Family members

"I rang four times today and didn't get a callback."

"I just want to know whether Dad had his breakfast and if he slept. Instead I tie up the nurse-in-charge with a phone call she doesn't have time for."

We built a read-only family portal. Configurable per facility, safe by default. Families see what matters to them. Clinical staff get their phone time back.

What we don't do

The things we deliberately chose not to build.

A product is also defined by its absences. These are the things we've been asked to do, and consciously declined — because saying yes would betray one of the six principles.

No.

We don't build for hospitals.

Acute care has different rhythms, different regulatory frameworks, different documentation patterns. Trying to serve both makes you mediocre at each. We're a residential aged-care platform. Full stop.

No.

We don't sell modules separately.

Your eMAR shouldn't be a paid add-on. Your audit log shouldn't be a paid add-on. Two tiers, no module lockouts. If it's in your tier, you have it.

No.

We don't charge per seat.

A casual EN should not cost more than a permanent EN. An agency staff member should not be a budget conversation. We charge per resident — the same way your facility is funded.

No.

We don't run a tiered support queue.

You don't email a level-one ticket triage team. You reach the clinical and engineering people who built the software. That works because we stay small. When it stops working, we'll figure out how to keep it working without becoming a help desk.

No.

We don't lock you in.

No multi-year contracts. No exit penalties. Your data is exportable in clean formats whenever you want it, for whatever reason — even "we're moving to a competitor." We'd rather earn next quarter than collect last year's penalty.

2yrs
Spent in facilities listening before writing the first line of code.
100%
Of the team has worked clinically in Australian aged care.
0
Multi-year lock-in contracts. Earned month by month.
1
Support queue — direct to the team that built it.
Come talk to us

We'd rather meet you than market to you.

If you're frustrated with your current system, book a demo. If you're not ready for that, just send an email — to a real person, who reads it. That's how this whole thing started, after all.

Book a demo → Just say hi
Book a demo