Lumary 16.5 release notes

A new field called Delivery Ratio has been added that will appear when you add a line item to a service agreement.

When adding a new line item to a service agreement, you'll now be required to define the Delivery Ratio, which is the ratio of workers to clients.

If you intend to deliver the service on a 1:1 basis, you'll only need to select the 1:1 option, which is selected by default.

If you intend to deliver the service as part of a group, you'll need to add multiple instances of the same service line item, with each individual line item having a different delivery ratio specified.

Top

This release included changes to sessions to support the introduction of apportionment functionality. These are explained in the sections below:

• Scheduled Delivery Ratio
• Change the apportionment of a service when completing a session record, and
• Lumary Setting.

A new field called Scheduled Delivery Ratio has been added that will appear when you add a planned service to a session. 

When creating a new appointment for an individual client session or a group session, you'll now be required to define the Scheduled Delivery Ratio, which will determine how the service is apportioned and service delivered (SD) records are generated when the session is completed.

Existing articles on creating a new appointment for an individual client session or a group session have been updated.

Top

New functionality has been added so that when you complete a session through the session record, you'll have the ability to change how a service is apportioned. This allows users to make changes when the apportionment has changed between creating the session and completing it due to cancellations or to reflect the actual time spent by a worker with individual clients during a group session.

New articles have been created to explain how to:

• change the apportionment of a group-based service when completing a session record, and
• change the apportionment of a group-based service when there is a cancelled client.

Top

A new Lumary Setting has been introduced to control whether apportionment is enabled in your environment.

By default, apportionment will be enabled in provider environments and users will have the ability to change the apportionment when completing a session through the session record.

System administrators can change apportionment settings in Lumary Settings.

New articles have been created to explain:

• environment and records settings that impact apportionment, and
• how system administrators can change apportionment settings in Lumary Settings.

The new functionality added to service agreements, sessions and the Service Delivery Entry screen will support providers to set up and claim the new group support services introduced by the NDIA.

The new line items for group support services don't have delivery ratios built-in as part of the service, so users must define a delivery ratio for the service when adding line items to a service agreement or services to a session.

When delivering services through sessions or the Service Delivery Entry screen, you'll only be able to select services based on the service line items in the client's service agreement, unless the client has unrestricted categories.

Services can also be apportioned when delivering through the Service Delivery Entry screen.

New articles have been added to explain how to set up a service agreement to claim the new NDIS group supports and how to apportion group services through the service delivery entry screen.

Top

Previously, centre capital costs were automatically charged as part of services that occurred at a centre. With the release of L16.5, centre capital costs must be charged separately and can be given their own funding in client service agreements.

Centre capital costs will now create their own service delivered records when they're delivered.

Providers can now allow centre capital cost claiming on client service agreements and on site records to claim centre capital costs. Lumary will update and maintain the relevant services to allow centre capital cost claiming as per the NDIA's pricing.

Top

Claim types can now be set when a service is added to a client appointment in either an individual client's calendar or the Sessions Calendar so that the correct code is displayed on the NDIS extract.

This includes:

• Non Face-to-Face
• Telehealth
• Report Writing, and
• Irregular SIL.

These are all claim types allowed under the NDIS. Any service not being claimed against one of these claim types should be set to Face-to-Face. This is the default claim type in Lumary. When services with the Face-to-Face claim type are included in an extract, the claim type column will display as blank.

This does not include travel and transport as these are managed separately.

Existing articles on creating a new appointment for an individual client session or a group session have been updated.

Top

The following permission sets have been updated to provide access to the objects and fields listed.

Following the release of Lumary 16, there were two minor releases to address minor or urgent issues. These were applied to affected environments as they became available. The releases are listed in reverse date order, from most recent to earliest:

• minor release 2, and
• minor release 1.

Date available: 14 July 2021

For this minor release, we have:

• made changes to support the NDIS Pricing Arrangements and Price Limits 2021-22
• modified decimal rounding calculations to avoid service agreement item overclaiming
• included DVACardStatusCode on ICSS and CHSP DEX extracts
• included CaseClient information on DEX extracts, and
• added ResidentialAddress information required for unidentified clients in DEX extracts.

Minor | Top

Version: 16.13.3
Date available: 17 June 2021

The following fixes have been applied for this minor release:

• travel and transport service delivered (SD) records will create successfully for service agreements created prior to the Lumary 16.0 release
• Beds Calendar will not misalign when a long site name is entered
• changes made to the session wizard ensure that overclaim prevention is triggered upon completion of a session
• ability to add, roster and complete sessions with services from associated service agreements in Rollover status
• SD records and buttons will not disappear on the Service Delivery Entry tab, even if a high number of SD records were created on the date being viewed, and
• rolled over service agreement items are now looking up to their support category correctly.

Minor | Top