Live DEX Training Session for DSS Funded Providers April 2026

Okay. Well, we'll make a start. I'd like to start by acknowledging traditional custodians of the land on which we meet today and their connections to land, water, culture, and community. I pay my respect to elders past and present and extend that to all Aboriginal and Torres Strait Islander peoples today. Thanks very much for joining us. 

As mentioned, we're recording the session and we're doing three of these sessions. So from the three of them we'll aim to publish a video of the best one that people who've missed the session can then watch or if you want to go back and look at the detail of anything you can do that in the video on the DEX website. I'm Tristan and I work for the DEX policy and Operations team and Christoph who's from our team will be presenting along with me today. Also towards the end Tushar who's from the reporting team will come in to give us a demo of reports.

So the team that we work for, the DEX Policy and Operations team we oversee the technical management of the data system setting rules and policies about the system and the use of the data and we manage program specific guidance that hopefully you're familiar with that outlines DEX reporting requirements for each funded program. Our team's not directly involved in talking with providers about the details of grants. today we'll cover some of the basics the changes that have recently come in to DEX reporting requirements for DSS providers. We'll talk through Privacy, consent, deidentification. There's system demonstrations throughout so we'll talk about the theory but also then show how that works in practice. We'll talk about SCORE and then Tushar will give a demo of how you can access the data that you upload for your organisation in DEX and there'll be hopefully some time for question and answer at the end. I think we might already have put a note up, if you have questions, stick them in the chat. I'm hopeless at reading chat as I present, but there's a few people who will answer. We're standing by and we'll answer things that can be answered in the chat and we'll try and do a bit of a recap at the end.

Anything we don't get to, we'll circulate a document responding to that. So thinking about DEX, the first question is why do we do it? Why do we collect data? Data answers questions for government and providers. It provides insight to help providers help clients. So it can be used to help you develop your services. It helps government make investment decisions. DEX was set up in 2014 as a systematic way of recording appropriate data. It's offered by the DSS through the Community Grants Hub and the Community Grants Hub also make it available to other departments and state governments to use. So I'm sure for example some agencies here today may report on their DSS programs in DEX but also Commonwealth Health or Attorney General's programs as well.

The name Data Exchange is about a two-way partnership with data to be used by service providers and communities. So by you guys as well as by government and funders. It's used for client- facing programs. That is services that engage directly with clients and people. And data can be entered manually into DEX through a web-based portal or it can be bulk uploaded or transferred from your own case management or client database if you have one of those that can talk to DEX. As DEX is used to collect and manage potentially sensitive information, there are a several steps required to access the system. If you use the MyGov app, then you probably have already set up My ID. My ID and RAM are both managed by the ATO, Australian Taxation Office. So while in DSS and the DEX areas we do provide some guidance and information around these, anything tricky ends up needing to go to the ATO to get support from them about those systems.

While digital ID is the Department of Social Services preferred secure way to log into DEX, to discuss other options for accessing DEX providers can email the DEX help desk. DSS is in the process of changing reporting requirements in DEX for DSS providers. Providers have been telling us that we need to simplify reporting and make it more standard across programs. This shows the list of data items that service providers may have been asked to report before the changes. The changes aim to reduce overall reporting for providers in DEX. But within this there are increases in reporting for some providers and decreases for others. You can see here in that second column items crossed out that DSS will no longer mandate for most programs. If you still if you collect those and want to still collect them, it's still possible to do that in the system. So, we're not taking that function away, but DSS will no longer require those items to be collected.

Over in the left hand column, down at the bottom, you can see one of the new items, which is a Group Session Census, it's been added to run in April and November. And we're going to go into a bit more detail on that in the next slide or the one after. And across on the right, SCORE is a new requirement for some providers now. it's now mandatory for most programs and for at least 50% of clients. So there are some programs out there that did not used to need to report SCORE. most ongoing and client-facing DSS programs, these changes applied from the 1st of March 2026.

For programs that end by the 30th of June 2026 these changes don't impact them. So group sessions, first of all in talking about the Group Session Census it's important to be aware of the difference between what unidentified client is and what a deidentified client is. Unidentified is where a person is just recorded as a number in a group. there's no further information entered in DEX about them. Whereas deidentified is what happens when a client is set up in DEX but consent is not given to keep their name or street level address, like their home or the number of their house or premises in DEX. So if that consent's not given the record is deidentified and this information is removed. It's become clear that a small number of organisations were recording all or most of their clients as unidentified group clients, meaning there's no usable data for about 20% of clients in DEX.

The Group Session Census has been introduced to try and improve on that. a lot of organisations …. most organisations weren't recording lots of clients in this way. So for them the census is unlikely to be a big change. At a minimum under the census providers are required to request to collect client details data for attendees at group sessions during April and November.

Organisations may wish to record to record data for sessions outside of these months and many organisations already do that and are encouraged to keep doing so but it's not mandatory. Community Sessions have been defined. So up the top right there you can see about Community Sessions as a separate definition from group sessions and these are for where services are not delivered directly to individuals. So something like a presentation at a school assembly or an information stall at a community event. For these types of sessions you can continue to record aggregated unidentified attendance.

We touched earlier on the different ways you can get data into DEX. The majority of data uploaded in DEX comes from larger providers who use bulk uploading methods that tend to reduce the need for double entry and increase organisation’s ability to tailor the way that and manage the way that data is entered. The majority of DEX users though, so most actual users use a manual entry method. Establishing a bulk upload method is likely to require that a provider engages someone with technical expertise to configure their system and requires there being an existing case management system. Today's demonstrations show that, and we're going to go to Christoph shortly, demonstrating what manual entry looks like for providers using the DEX portal for manual entry. This is what DEX looks like for and I think most people will be familiar with that. It's the landing screen that's used for manual entry.

and it's also where you go if you have bulk upload files that you are going to upload. And at the bottom right there you can see ‘access my DEX Reports’. That’s the button that's used to access Qlik reports. and Tushar is going to give us a demonstration later about what happens when you go there. But I'll now throw over to Christoph who's going to start the first demonstration of manual entry in DEX. Thanks Tristan.

Can I just get a couple of thumbs up from people who can see the screen? Fantastic. Okay. This is the opening screen when you enter your, DEX portal. This is the ‘my DEX Dashboard’ screen. So, as you can see, there are several tiles here, under find, view, and add. And, there are some other hyperlinks on the bottom Left hand corner here. So we'll navigate over to the manage organisation screen for now. So I should also mention that we are here in the what's called the staging environment or the sand pit environment.

You find some basic organisational details. So your name ABN and other ids. The next thing to display would be your list of outlets and then program activities that you are funded for. The first thing that you have to do is add an outlet and attach an activity to it. So I'm just going to demonstrate how we do that. So firstly, we need to create an outlet name. So this can be anything that you want to call it. We'll call it the ‘friendly outlet’.

And then you need to enter some address details. So now I should mention an outlet is the location that you deliver your services from. So that could be your organisation's head office or community centre or anything like that. Next, we'll hit save. And then we've got the little green tick indicating that the data item has been successfully saved. The next thing we need to do is add an activity to the outlet.

Again, if you are funded for a single activity, only one activity would display on the drop-own list. If you have funding for more than one activity, you will make a selection at this point. Now, the start date always defaults to the start date of the current reporting period and the end date is prepopulated from the activity end date on your contract. So, now that we've saved that detail, we received the next screen tick. And as we scroll down, we can see the outlet activity details here. And the status is currently set to ready for approval. So, the DEX help desk team are the ones that action the outlet items. It can take up to 10 days depending on capacity, that's 10 business days for an outlet to be approved. But generally speaking, they get this, job done, much earlier than 10 days.

Okay. So, let's navigate back to the manage organisation screen. one of the next things that I could demonstrate is how to enter a client. However, I think Tristan, you have a couple of slides that we usually demonstrate on the difference between Yeah. the identified and identified client.

Sure. I'll stop share for the moment. Yep. And I'll just try and reshare my screen. Okay. So this is we're moving now to thinking about privacy deidentification and consent.

This is the kind of information that when service providers input information into DEX. So you can see on the left we've got an example of what manual entry of a session looks like and you can see the information about the session and the people that attended it. On the right, you can see what manual entry of a clients details looks like. And you can see there the person's name. This is just an example that we use for demonstrating a made-up client details. The date of birth, gender, the cases that they've been a part of, and the sessions that they've been a part of. So at the provider end it's detailed depending on what you choose to put in. At the DSS end this is the more we're thinking about and interested in looking at. Information about groups of programs or services to clients over time. This slide gives a good information a good sense of how widely DEX has been used over time. it shows 70 million attendances by 15 million clients over a decade. We get a lot of questions around privacy and consent. Client names and addresses are only collected and stored in the Data Exchange when the client has given consent. Such Consent is voluntary and not linked to being eligible to use a service. When a client doesn't consent to their name and street level being address being kept in their DEX record, a client record is still created. But when their lack of consent is recorded, this information is removed from the record and it is becomes deidentified. Records are always deidentified at the DSS end. So we never see people's names or that that level of detail.

DSS does not access a client's name, address and instead because we still need to group some people's data together. For instance, you know, we might be interested to know if a person has attended a play group in their earlier life, what does that mean for their employment in later life or something like that? So people's data still does need to be grouped together and the way that that is done in a deidentified way is using a thing called a statistical linkage key which is created. DSS and you as users of DEX are bound by the privacy act of 1988. and when clients think about whether to consent for their data to be shared or Not, one point is that they can help support your services when they give consent as it means the data collected about your service is stronger and can be used in a greater variety of ways. We're commonly … ah… thinking more about storing of participant data.

personal data is not shared with DSS and is only stored in DEX if an organisation wants these details visible for their own use. If you don't want this information, if you don't need to have this information in DEX, you or if you do, sorry, if you do want this information to be visible in DEX, you must seek and record consent as outlined in the DEX protocols. if you don't want to record names and street level address, details are initially entered for the purpose of creating an SLK, but are then removed by not checking the consent for to collect box. consenting to provide their information in DEX as I as I mentioned is a way that people can support your services. Over on the left there that comes from the DEX protocols. There's a whole section on privacy but the it outlines the requirement on organisations which is that you must use best efforts to request collection of priority requirement client level data.

So we'll switch back to Christoph who can now demonstrate what those various options look like in the system when you do them using manual entry. Thanks Tristan. so I've navigated back to the manage organisation screen. Over here we have the purple headed ‘I want to’ box. so let's go to the add a client link. So firstly I'm going to demonstrate what a client looks like who did not consent to have their first name last name and street level address stored in DEX. So we're going to call this person sorry the client ID we're going to call this not consent or consented maybe it's grammatically better. So, what we ask you that you do even in instances where a client did not consent, you would always have to enter the person's name and their date of birth and their gender.

So Tristan I think you mentioned the statistical linkage key or SLK. The SLK is used to deidentify clients within the system. and there are some letters I think it's the second and third letter from a first name, the fourth and fifth letter of the family name, the date of birth and the gender value that make up the SLK. So it would be fair to assume that if a client comes to seek help from your organisation that you would record their name and date of birth and these sort of demographic data fields for your own records. So when you enter it into DEX we have reached this point here and then down here it says client consents for DSS to collect personal info from providers for storage in the Data Exchange. Now, if the client did not give consent or you chose not to collect it because you have a different way of identifying clients in the DEX system, you would simply untick this box. What you need to pay attention to here as I do this, the given name and family name value will be greyed out. But what the system does is it quickly forms the SLK before we navigate to the next page. So, I'll click this button now. And then we go to the next button. And you saw on the previous page, it was greyed out. So similarly, the system now will prevent you from adding the address line one and address line two or commonly referred to as the street level address part of the address. You still have to enter the suburb.

So we’ll choose this one for purposes of today's training. And then we go to next. So then there are some other demographic details that you would need to enter. some of you may be familiar with this already. any of these lists you can start typing with the first few letters of a given result that you wish to find and the system will navigate towards that option. So here we're going to say that this person is not of Aboriginal or Torres Strait Islander origin for today's Demonstration, and that they do not have any impairments, conditions or disabilities. next.

We've landed on the review page. The review pages always give you the option to hit the back button and amend any of the details you've entered before you submit the client into the system. Now, here is the extended demographics page. Tristan has already mentioned for most DSS programs, none of these fields are mandatory anymore. you can of course add them if you wish to. But you do not have to. So you can hit the skip button here if you prefer. And then we’ve landed on the finish page. So again, we have the green tick.

Now you note here given name and family name is blank because the client did not consent. So if we press the hyperlink to view the client profile, the client shows as name hidden. So any of the support staff at the department that have access of some sort to the system to assist you with questions that you may raise with the help desk, we see all clients like this. However, if a client does not consent, you also see name hidden. This is why it's important that you choose a client ID that you know represents the client that you've just entered here with these demographic details. Okay.

So, conversely, let's enter a client that has consented. Now, So we'll leave these boxes as ticked. We go to the next page. If you want to, you can enter the street level address, but again it's not a mandatory field. So, we can we can just select a different, just take those bits out. Excuse me. And again, I'll just go quickly through these selections again. I've reviewed it. I want to submit the client in. I'll skip the extended demographics and I have the green tick. So now Frank Mueller has been entered as well. If we now hit the hyperlink to view the client profile detail, , at your end, you would then see the client's name, making it a bit easier to find this client as you start entering sessions for this client.

Okay. So now the next data item would be adding a case. So let's do that. So the case in DEX terms is kind of like a folder that you group clients into and record service delivery information into as well. So we can just make this a random ID of your choosing or you can let the system assign a numerical value. So I'm just going to let it assign a value. First you have to link it to an outlet and then to a program activity. So it is at this point that you can enter ident…. sorry unidentified clients to the case as well. So you would do that by using the scroll button or you can manually enter numeric value.

But again where possible we always encourage minimal use of unidentified clients. So next we would have to attach clients. So depending on the number of clients there would be several pages that you could choose from or in this case we don't have as many clients entered the system which makes the selection a little bit simpler. So, we can add Frank that we created into this case. And it now tells us who the clients are.

What I might do is… I might actually add Jenny into this case as well. So, let's hit next. Here we have a review page. Again, I'm happy with the selections I've made. I will submit the case. Okay. So, once again, we have the green tick up there.

And from down here, the ‘what can you do now selection’, we can add a session to this case. So, let's do that. Once again, the ID field is a non-mandatory field. We can just let the system assign a numeric value. And the session date is something that does have to be put in. So, as you know, you do not have to record all the sessions on the same day that you deliver them. You can choose to report more frequently.

in this instance, let's say we delivered the first session on the 5th of January. Now, depending on your program that you're funded for, the list of service types would be specific to your program. here we will say we used an information advice referral service type. Let's hit next.

Okay, so we have two persons entered into the system. So I'm trying to address a question that I saw in the chat. And the question was why do we have to get date of birth for parent and carer? So here we are saying that Frank is the client and then we are going to say that Jenny is the support person. So within DEX parents or carers who are there to assist the actual client they're called support persons. Now, the only way that we can record a support person is by creating them as a client and then indicating that they were there to support the person that the session was delivered for. I hope that makes sense. So, let's say Jenny is here to support Frank. Down here, before we hit the next button, the system gives us a participation type, clearly indicating Frank was the client and Jenny was the support person. Once again, we have a review page giving us the option to go back and change things if required.

Otherwise, let's submit the session into the system. So, we've reached the finish page. Here we can see the green tick. And the last data item that we would be demonstrating would be how to enter a SCORE into the system. But Tristan, I think you have a couple of slides that you'd like to share with everyone and some information about why we record score. (Tristan) Some services will be new to SCORE which is the standard client community outcomes reporting tool.

It's worth thinking at the beginning about what we mean when we say outcomes. We think about inputs, outputs and outcomes. And to aid in thinking about that, we have used the example of a vaccination program. An input is the vaccine or the the worker and their time. An output is the kids getting vaccinated. the outcome is the reduction in the rate of infection. So with funded services, we do want to understand, how many people are employed and what money is spent on it, the number of sessions delivered and that sort of stuff. But we're also interested in measuring, has the change that that service been, set up to achieve… has that been achieved? What change has that service resulted in? It's worth noting that you know if a for service providers, like all data SCORE outcomes data can be useful to you in making your case for the outcomes and what's being achieved by your service.

So these are the SCORE domains. The domains to be used for programs like …. the program supporting specific guidance details the domains that are to be used for specific programs, providers are required to collect SCORE for at least 50% of clients. And in talking about score, we're mostly talking about the two left-hand Columns, circumstances and goals. Satisfaction is to be recorded for at least 10% of clients and towards the end of their engagement. Community SCORE is recorded at a group or a community session where it's not feasible to record the changes for individual clients. So mostly in thinking about SCORE, we're thinking about those left two categories or columns.

A way to think about SCORE is that when you or I work with a client, my view on whether things have got better or worse for that person might be quite different to your view or quite different to the client's view. But we do want to have some understanding of what … changes happened and how. and SCORE is a tool to try and make that a bit more consistent. SCORE can be entered by ideally …… or the SCORE not entered but the SCORE rank rating can ideally be determined by the client themselves. but it can also be done by a practitioner. So by the person who's working with the client or could be done by a carer. Or it could be done by a combination. So say the practitioner and the carer together.

These are some examples of SCORE domain questions. And this is for circumstances domain for community participation and networks. and these are the questions, and we're talking about a one to five scale where one is not doing so well, five is doing great. and then there we've got the numbers in the middle. So the question for community participation and networks……a description that would result in a rating of 1 is on the left hand column and this is the sort of academic wording from the DEX protocols significant negative impact of poor community participation and networks on independence participation and well-being. There's also a docent available on the DEX website called how to use SCORE with clients and we will drop a link in this chat and it's also linked in the slides that we're sharing. It has a go at offering a more plain English option for each of the questions. So the plain English version of that same question here is ‘I feel very isolated. I have little contact with friends, family or people in the community. I have no support’. And then you can see the other questions. You know, a five is ….. looking at the plain English the plain language version. ‘I feel very connected. I have lots of contact with friends or family’. So they're questions to look at in deciding how to rate people using score.

Importantly, it's about rating people at least before and after. So we ask you to do the score early in people's engagement in your service and then towards the end of their engagement in your service at Least. If they're engaged for a long time then ideally every six months and they need to be against the same question. So the PSG document which again we're linking here, it tells you which questions are the ones you have to do or can choose from for your project. and it's important that the before and the after are asked using the same question. This is an example of how you can use SCORE data. This comes from an Aboriginal organisation in Central Australia who collected SCORE and they did their own evaluation using the data. It was an employment-based project and you can see in that chart on the right they were able to map the change that participation in that project led to for employment. So across the top line 22% of people in that project got worse in terms of their employment status. 61% stayed the same, 17% got better. behaviours which were things like workplace behaviours like turning up on time etc.

There was a no change or positive change for more people. So that's the sort of measurement that you can do using SCORE data. So, we'll go to Christoph now to show what it looks like when you enter SCORE manually in DEX. Thanks again, Tristan. So, SCORE assessments are linked to sessions. So, I've left the session open. Oh, well, I've left the system screen open on the session that we just created. an easy way to enter a SCORE against a client at a session is to view the session details screen.

So I've just accessed that via the hyperlink on the previous page. And down here at the bottom right you can see a little symbol with a yellow outline which represents a client SCORE. So because Frank was the client and SCORE is ideally recorded mainly for clients, what we can do here is we can press this little symbol and it will take us to the next screen. So this is the add a client SCORE screen. Now Tristan already mentioned for individuals there are three different SCORE types circumstances, goals and satisfaction. and I believe my colleague Alistair has been answering questions about the Program Specific Guidance (in the chat). It is when within the program specific guidance where you would find advice on what SCORE types and the domains under each SCORE type program policy for your program is most interested in.

So I'm just going to select circumstances here. and let's have a look at the domains. So under circumstances, there are 11 domains. I'm just going to quickly show the Program Specific Guidance. So these are Families and Children programs.

so depending on what you're funded for, you would navigate to the relevant one. So I can just select this very first one here. once you go past the program description and these other items you find partnership approach information and then there's a section that says what areas of SCORE are most relevant. and then there's a listing of the ones that are most relevant. So the reason I'd like to point this out is when we go back to the system, you don't have to record all the domains only the ones that are listed in your Program Specific Guidance document. So now before we make a selection on the 1 to 5 Lykert scale, you can also look at the definition for client circumstances here where there is the academic description of SCORE that Tristan showed in a slide a couple of minutes ago. So here the academic language is written as it is written there but there's also a handy document called How to Use SCORE with Clients that you can find on the DEX website and I believe we'll be providing links later and it has more sort of common language that may be a bit more useful as you enter the SCORE for the various SCORE domains.

So let's say for this session the assessor or the client decided that they felt comfortable entering the domains on the on the lower end of it. So what we do now is we hit the save button. Once again, we have the green tick box. And as we scroll down on the session detail screen, you notice that this little yellow outline over here is now filled in. That indicates that a SCORE has been recorded.

And then if you press this little toggle button here, you can see the details of the of what you've just entered into the system there. Now you can either delete that if you realise you've assigned it to the incorrect client profile or you can edit it with a little pen symbol here too. Now one important thing about SCORE is you would obviously typically record a SCORE assessment with the first session that you have with a client and then further down the track, depending on how long your program on the ground runs for, say if it's a 6 to 12 month program, we would suggest that you record SCORE at the 6 month mark again and then again at the 12th month mark. It is important that when you record the second or subsequent SCORE that you choose the same SCORE domains under the SCORE type because that way the system will recognize that the client is counted as fully assessed. If you only record for one of these or two of them and it doesn't exactly match, while the system recognises you've recorded two SCOREs, the client would remain partially assessed only within the reports. That is pretty much it for the system demonstration. Tristan do we want to hand over to Tushar now to demonstrate the reports? Got one more slide before we go to Tushar. Thanks Christoph. Certainly just …..

organizing my screens. Sorry everyone. Two more slides. with outcomes measurement with SCORE outcomes measurement in First Nations settings there's feedback that as SCORE stands it doesn't work well in some First Nations settings. DSS is has heard that feedback and is working on looking at that and is doing work to try and update that at the moment. So, and we're going to go to Tushar. , but just a reminder before Tushar takes charge of the screen that when you open DEX, this is the spot to click to open the Qlik reports where you can view and get analysis of the data that you've uploaded for your organisation.

Tushar, take it away. I'll stop sharing. Looks good. Okay, good afternoon everybody. Apologies for the technical glitch.

but yeah, as Tristan mentioned on the DEX portal, you will click on the area that says access your reports and it will take you to our reporting infrastructure known as Qlijk which is a very powerful reporting tool that we use within DSS to share our reports with you. I've opened up a sample report but you will have access to a range of reports within your access and depending on what that is and there's a detailed training overview and videos that are provided separately and at the they're linked at the back of the PowerPoint slides that will be shared with you. But I've opened up one of those reports which is some training data for a report called the organisational overview report. The filters that I've chosen is to filter by a specific service provider known as service provider 25 and I've selected a single reporting period which is a six-month window. As you can see the report itself is provides a summary here of sessions attendances client and support people the number of cases and some other metrics like that and at the bottom there's some interesting charts that trend client individual clients group clients and support people at the bottom and sessions and cases at the moment you can see in this particular view that I have a monthly view for this reporting period extending from the beginning to the end of that reporting period. I can also click on this little table here and it will give me a daily view for that reporting period. So I can see a day-by-day breakdown of what is happening for that reporting period. As you can see, you scroll across and you can see the full picture.

You can also then go to the reporting period and in this particular instance if I take out the session reporting period filter it will give me more historical information for this particular lead organisation and in this case it’s six reporting periods of data. So, a couple of things you can do. If, for example, you're putting a presentation together, you may want to use the underlying data that sits behind these tables or you may want to actually, grab these visualisations and put them into a slide pack or share them via your internal communication mechanisms. So to do that you would right click on the report and you would click on in this instance combo chart and then you can click on view data and that will then bring a data version of this that particular view onto the screen and then what you can do is you can click on the same thing but then you can grab the data and then you can see a menu a screen pops up, a little window that pops up that says click here to download your data file and you click on that and it will open up and then I'll open it and show you what it looks like. Drag Excel onto the appropriate window if it behaves. No, it keeps wanting to go to the other screen. It's a bit got a bit of stage fright. So, and you can see that reporting data that's been downloaded there as a bit of a table. Alternatively, you may want to download the actual image. So, in this instance, we can right click again. We can click on this top option which is reverting back to the view the chart mode and it takes us back to the chart mode. So, you don't have to refresh the screen or anything like that. And then you can do exactly the same thing. Right click, combo chart and download as. And you may want to download that as an image file or a PDF or a data file.

But in this case, we want to download the image file and we will select the resolution. The default one generally is okay. We'll run an export. It is doing its thinking. And then you click to download image. Once again, you'll see that it's created an image for me. Of course, it's gone to the other screen. And here we have an example of what that download would look like. And then you can grab that. It's a PNG file, which is a type of image format, which once you've downloaded, you can just drop that into a PowerPoint pack or drop it into a Team's message or wherever you want to use that or share that information or a Word document as well.

but that's essentially it and as I said there's a detailed overview of the reports that I run that's available on the portal for your reference whenever you wish to do that. Thank you Tristan. I'll stop sharing. Thank Thanks, Tushar. And I just note we're nearly got to the end of our hour and so I'll try and wrap it up on time.

When we share this PowerPoint, these links all work. So, I did see one question which was about can we have all the links in one spot and some sort of description of what you know what … the links in one spot with a bit of description of what they're for. This might help with that. And Tushar's got three videos that are detailed videos showing you how to work with those reports. So if you want to, now that you've seen roughly what you can get out of those reports, check out those videos and you can take your own time sort of stop and start the videos to learn about using those reports. So that's that top right link. There's here's our website and details for the Data Exchange help desk. I did see one question about there not being a phone number for the for the help desk anymore and that's correct. But if you lodge a request for the help desk they will follow up and get back to you. and yeah, I think other than that we're that's the end of the slideshow and that's the end of the presentation. Thank you everyone. I hope it was helpful. Thanks for taking the time to join today and have a good day.

Summary

A one hour presentation for DSS funded providers. The presenters talk through a range of topics and demonstrate how these translate to manual data entry in DEX.

Topics covered include:

  • Summary of DEX Reporting changes that apply from 1 March 2026
  • Privacy, consent and deidentification including demonstration of options in DEX
  • Standard Client Community Outcomes Reporting (SCORE):
    • why it is needed
    • how it is used
    • how to enter it in DEX
  • A look at the DEX Reports
  • Key resources / where to get help

Uploaded date

Category:
Policy

Tags