PACE Onboarding, Consent, and Coordinated Care
This episode breaks down the PACE migration’s access hurdles, from setting up myID and RAM to securing participant consent through the my NDIS portal. It also explores how providers can connect clinical plans to frontline support by coordinating early with support coordinators, families, and daily care teams.
Show Notes
- myID and RAM: https://www.ndis.gov.au/media/7836/download?attachment
Chapter 1
The PACE Friction Point When myID and RAM Become Your Best Onboarding Tools
Will, EnableUs Community
So, Winter, I was talking to this provider the other day, and they were, they were absolutely pulling their hair out because they tried to do a simple plan lookup for a new participant and hit this complete, um, like a digital brick wall. They were still trying to use their old PRODA details, and, well, since the NDIA moved over to the PACE system, that just does not fly anymore. If you do not have things sorted, you are locked out. Completely.
Winter, EnableUs Community
Oh, yeah, the PACE migration. It is a massive friction point. I mean, to access the NDIS provider portals you will need to set up your myID. That is the first thing. And then you have to use RAM, the Relationship Authorisation Manager, to link that ID to your organization's ABN. But, Will, so many providers are still catching up to this. They assume it is just, you know, the same old system with a new coat of paint.
Will, EnableUs Community
Right, right. But it is not. It is a completely different architecture. And if you do not have at least a Standard identity strength on your myID, you are not getting in. It is like trying to cross a border with a library card. But, but, okay, let us say you actually get past that digital gatekeeper. You have your myID, you have RAM set up. You still cannot see a single thing about that participant's plan until they, or their nominee, actively log into their own my NDIS participant portal and say, yes, I give this specific provider consent to view my info.
Winter, EnableUs Community
Exactly. It is a consent first protocol. And, look, some people see that as, um, like a annoying administrative hurdle, but think about what it actually does. It puts the power back in the participant's hands. I think about it this way, it is like myID is your secure digital passport, right? It proves you are who you say you are. And then RAM is like the official letter of authority linking you to your company. But even with those two things, you cannot just walk into someone's house and look at their private files. They have to open the door. The participant portal is the key that unlocks that door.
Will, EnableUs Community
That is actually a really great way to frame it. It forces a conversation right at the start. Instead of just quietly pulling data in the background before you even meet them, you have to talk to them about consent. You have to explain why you need to see their budget, how it helps you design their services, and how it keeps things aligned. It turns what used to be a dry, back office admin task into this genuine, ethical check in.
Winter, EnableUs Community
Yes. It stops providers from, you know, flying blind. If you start delivering services without actually seeing the current PACE budget categories, you are taking a huge financial risk, and, honestly, a quality risk for the participant. If the funding is not there, or if it is in a different category than you thought, you might end up delivering supports that cannot be funded, and then everyone is in a really, really difficult position.
Will, EnableUs Community
Totally. It is about building that foundation of trust from day one. Or, well, technically, within the first forty eight hours.
Chapter 2
The Collaborative Handshake Turning Therapy Plans into Daily Care
Winter, EnableUs Community
Which leads us right into the whole, um, the coordination side of things. Once you are actually in, you are rarely the only provider in their life. But so often, we see this fragmentation. You have a physiotherapist doing their thing, a speech pathologist doing theirs, and then the daily support workers just, kind of, doing whatever they think is best, completely separate from the clinical goals. And the research on this is so clear, Will. Participants with coordinated, multiple services show significantly better functional outcomes compared to those with fragmented care. It is not even close.
Will, EnableUs Community
It makes total sense, doesn't it? If everyone is rowing in different directions, the boat just spins in circles. But when you coordinate, you actually make progress. The big issue I see is that these incredibly high value clinical plans, like a mealtime management plan from a speech pathologist, or a positioning protocol from an occupational therapist, they get sent to the provider during onboarding, and then they just... they just sit there. They get buried in the onboarding coordinator's email inbox. The actual frontline support worker who is there at dinner time or helping the person transfer out of bed, they never even see it.
Winter, EnableUs Community
That is a massive operational risk. It really is. If that clinical plan is not integrated directly into the worker's active digital profile on their shift management app, it basically does not exist. We need to bridge that gap between clinical theory and daily frontline support. I actually, um, I remember a case where a support worker was trying to help a participant with a physical therapy routine, but they did not know the correct settings on the specialized mobility aid. They were just guessing, trying to be helpful, but they ended up, you know, inadvertently causing a lot of physical strain and actually undermining the progress the physio had been making for months. All because a PDF was sitting in an inbox.
Will, EnableUs Community
Man, that is such a clear example of the cost of not connecting. And it is why making that connection with the support coordinator within the first forty eight hours is so vital. You need to call them or email them straight away. Establish who is who, confirm the communication preferences, and, critically, clarify consent. Like, which family members are actually involved in daily decision making? Some participants want their family involved in every single email, and others value their privacy and want to keep things strictly between themselves and the support team. You cannot assume anything.
Winter, EnableUs Community
No, you cannot. Support coordinators should be asking participants about their specific cultural and privacy preferences directly, rather than making assumptions based on their background. And as a service provider, we have to align with that. When you do that initial outreach, keep it brief, keep it professional. Just a quick update to say, hey, we have started supports, here is who our primary contact is, and here is how we are aligning our daily activities with the goals in the participant's plan. It shows you are proactive, and it builds that referral relationship for the long term.
Will, EnableUs Community
And it means when there is an issue, you already have an open line of communication. You are not calling them for the first time when there is a crisis. You already have that, that collaborative handshake, as you put it, established. It just makes the whole ecosystem work so much better for the person at the center of it all.
Winter, EnableUs Community
Absolutely. At the end of the day, that is what person centred support actually means. It is not just a buzzword. It is the practical work of connecting the dots across the whole support network.
Will, EnableUs Community
Well said. Alright, that is a wrap for today. Let us make sure those digital profiles are updated, and we will talk to you all in the next one.
Winter, EnableUs Community
See ya.