This article provides an overview on how Lumary can structure cases and generate case ids to support DEX reporting.
Parts of this functionality require at least Lumary 19. It also requires that your environment is set up for DEX reporting.
To ensure that DEX XML generated from Lumary can successfully report through the Department of Social Services’ (DSS) Data Exchange (DEX), Lumary offers several options for structuring cases and generating case ids.
This article provides an overview of:
- what case structures are available
- how case ids are generated or captured
- how rate type and service record settings affect case ids and case structures, and
- where to find out more about how to set up case structures and generate case ids.
Case structures
How you generate or capture case ids in Lumary will depend on how cases need to be structured in the DEX XML report. This can depend on the requirements of the funding program. You may also have your own business reporting needs that affect how you capture case ids.
The three ways cases can be structured in Lumary are as a separate case for each:
- individual
- service agreement item (SAI) on a block service agreement, which includes all clients who received that service, or
- group activity, which includes all clients with service delivered (SD) records with the group case id.
The case structure is controlled by settings on the rate type or the service record.
Generate or capture case ids
The are three sources for case ids:
- the client’s funded client (FSCC) number from the block service agreement
- the service agreement item (SAI) number of the service from the block service agreement, or
- the DEX group activity case ID, which is entered on the service delivered record from the Service Delivery Entry (SDE) screen.
The most common source is the service agreement item (SAI) number from the block service agreement. This is the default approach and can also be used for group sessions where there is no need to separate sessions into separate cases.
FSCC and SAI numbers are automatically generated by the system. However, the DEX group activity case ID is added by the user from the Service Delivery Entry (SDE) screen.
The source of the case id depends on how the rate type or service record is set up to structure cases.
Rate type and service record settings
There are three settings on the rate type that affect the source of the case id and structure of the case:
- Separate case for each individual
- Separate case for each Service Agreement Item, and
- None.
Each of these can be overridden on the service record. The service also allows for the additional setting of 'Separate case for each group activity'.
The following matrix shows how different combinations of settings affect the source of the case id.
| Rate type setting | |||
| Service record setting | Separate case for each individual | Separate case for each Service Agreement Item | None |
| Separate case for each individual | FSCC, automatic | FSCC, automatic | FSCC, automatic |
| Separate case for each Service Agreement Item | SAI, automatic | SAI, automatic | SAI, automatic |
| Separate case for each group activity | SDE, user entry | SDE, user entry | SDE, user entry |
| None | FSCC, automatic | SAI, automatic | SAI, automatic |
Find out more
To learn more about case structures and case ids, check out the following articles that explain how to:
- set a case structure for a rate type
- set a case structure on a service, and
- add a DEX group activity ID to a service delivered (SD) record.
You can also find out more about how DEX XML nodes map to CM fields and objects.