Lumary AH - The Lumary AH 4.0 release makes it easier to cancel appointments, claim for cancellations, notify clients about cancellations and apply global settings to your environment.
Click to see how to subscribe to new release notes
If you'd like to receive email alerts when new release notes are added to this section:
- Go to the Lumary AH releases section.
- Click on the Follow button.
- If you're not already logged in, you'll be prompted to log into the Help Centre. You'll need a Help Centre account.
- Select New Articles.
A message will appear confirming that you are now following this section. The system will send you an unstyled version of new or updated pages. You can cancel these notifications at any time by clicking on Unfollow.
Users can only follow sections on Lumary's Help Centre, rather than individual articles. This means you'll get email notifications whenever a new article is published in this section, or when an article is republished.
Available: 2 October 2023
This release includes:
- a streamlined cancellation pathway with automated billing based on cancellation reasons
- custom cancellation reasons
- notifications based on cancellation reasons
- a new ‘Lumary AH Settings’ interface to manage all your settings from one place, and
- updates to the case note Service drop-down list.
Streamlined cancellation with automated billing
We're excited to announce that we've made cancelling appointments a whole lot easier. Based on your feedback, we've removed the multiple paths previously used to record different types of cancellations. Therapists and schedulers can now use a single, simpler option. The Cancel Appointment button will launch a form to capture all the details of the cancellation.
Therapists and schedulers can trigger cancellation billing or claiming simply by selecting the relevant cancellation reason. Our system will automatically handle billing based on the reason selected. This saves time, requires less manual work and reduces the risk of incorrect billing.
Find out how to:
Custom cancellation reasons
To give providers more options and control, we've added custom cancellation reasons. System administrators can now:
- define how these reasons appear to schedulers and therapists, and
- determine when and how the system charges for cancellations.
Providers can use cancellation reasons to automate claiming for specific types of cancellations. This makes billing and claiming easier, as therapists and schedulers will no longer need to decide whether to bill clients who cancel.
We’ve also included pre-configured cancellation reasons to support NDIS short-notice cancellation claims.
Find out how to create custom cancellation reasons.
Notifications based on cancellation reasons
We understand there are times when you need to handle notifications with sensitivity. Providers using Pendula can now use cancellation reasons to manage automated notifications.
System administrators can use the Send Notification field to indicate if a particular cancellation reason should trigger automated notification.
This also means that schedulers and therapists won’t need to decide whether or not to notify clients about cancellations at sensitive times.
Please note that this feature requires some initial setup from Lumary. If you're interested in using the Send Notification feature, please log into the Help Centre and submit a support request. Our support team will help provide you access to this feature.
Lumary AH Settings interface
We've introduced a new Lumary AH Settings interface for system administrators to manage global settings for their Lumary AH environment. From this single view, system administrators can set defaults and set up templates for their users, which saves time and helps maintain data consistency.
Find out more about Lumary AH Settings.
Updated Service field on case notes
To help users identify services when adding them to case notes, the Service field that appears when adding a billable item now includes the item code for each service. We've also adjusted the remaining funding (Rem) value, which was previously referencing an incorrect field.