This article lists some of the settings you'll need to set up or include in order to generate a successful DEX extract and claim.
To make sure your DEX extracts are properly created and lead to successful claims, there are a few settings you may need to check. The following table shows you where to find the relevant records, and what they need to include.
The table lists:
- the Lumary record type that includes the fields
- the settings that are required for a successful DEX extract, and
- how to find the record and fields in the Lumary system.
You can find more about the steps in the DEX reporting process in the introductory article on DEX reporting.
| Record | Key settings | How to get there |
| Rate Type | Include in Extracts: the Include in Extracts field on the rate type needs to have a value that is a DEX extract type, for example DEX - CHSP. | Reference Data > Rate Type form |
| Service |
DEX Case Structure: a case structure type must be selected. The options are:
|
Services > Service form > DEX Information section |
| Client (Contact) | DEX ID: client's DEX ID must be provided. | Contacts > Client record> Associations tab |
| Address Information: the client's city and state address information must be provided. Check the address details as incorrect or mistyped information can cause matching errors. | Contacts > Client record | |
| Client Demographics: the main language spoken at home, Indigenous Status and Country of Birth fields in the Client Demographics section must be provided. | Contacts > Client record | |
| Gender: client's gender field must be populated in the Client Details section. | Contacts > Client record | |
| Gender Detail: optional when Gender value is [I/They] Use a different term | Contacts > Client record | |
| Primary Disability: client's Primary Disability must be provided in the Medical Details section. | Contacts > Client record | |
| Consent: client must have provided consent for sharing information, otherwise they will be de-identified in the extract. | Contacts > Client record > Legal tab | |
| Service Agreement (SA) | Block Service Agreement: client must be on a block service agreement with a relevant DEX support category. The service agreement must use a rate type that is set up for DEX reporting. | Service Agreements > Service Agreement form |
| Outlet Activity ID: the relevant Outlet Activity ID must be provided in the Additional Information section of the Block Service Agreement. | Service Agreements > Service Agreement form | |
|
Funded clients: the clients must be added to the block service agreement. The funded client ID (FSCC) must be included in the Case ID field (this should auto-generate when you add and save a client). The three DEX-reportable fields on the form are:
|
Service Agreements > Funded Clients tab > Funded Clients form | |
| Session via Sessions Calendar |
DEX-reportable fields: the DEX-reportable fields for an individual or group session are:
|
Sessions Calendar >Session form |
| Session via Skedulo |
DEX-reportable fields: the DEX-reportable fields for a Skedulo session are:
|
Contacts > Client record > Schedule job link |
| Service Delivered (SD) | Total inc GST:amount must be greater than $0. This amount should auto-populate based on the rate or negotiated rate. | Service Delivery Entry > Total Cost and Payment Details section |
| Client Accepted: checkbox must be ticked. | Service Delivery Entry > Total Cost and Payment Details section | |
| Client Contribution: the field must be populated with an amount. If the client contribution has been set up as a separate rate, this will be included on the child SD record. | Service Delivery Entry > Service Delivery Details section | |
| Extract (EXT) | Extract Type: should be set to DEX. | Lumary Extracts |
For more troubleshooting, also see this article on how DEX XML fields are populated from Lumary fields and objects.