Lumary AH - This article provides definitions for key terms as they relate to the Lumary AH product.
From our system to Salesforce to the range of funding sources, there are a lot of Lum-AH-words to remember! This glossary provides explanations about what they mean when they're used in and around the Lumary AH product.
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
Term | Definition |
Access met |
Access met means that a participant is eligible for NDIS funded supports. |
Account |
An account is a type of Salesforce record that stores information about businesses and groups that interact with your organisation. In Lumary, this includes agencies, clinics and education settings. Household accounts are used to store information about clients and the people involved in their care, such as family members and healthcare providers. |
Activity based transport |
Under the NDIS, activity based transport refers to the transportation of a participant to or from a funded service as part of the provision of that service. This is available for several community activities and selected capacity building activities. If the participant approves, providers can claim for labour and/or non-labour costs associated with activity based transport. |
Ad hoc service |
In Lumary, ad hoc services are services delivered without a service agreement. They are often used for consumables or over-the-counter purchases. Users cannot include services marked as ad hoc in service agreements. |
App Launcher |
The App Launcher is a panel that shows all of the Salesforce apps available to the user. It also lists all of the items that the user can select and can be used to access objects that don't appear as navigation tabs. It can be opened by clicking the grid of nine dots at the top of each page. |
Apportioning |
The NDIS refers to apportioning as dividing costs when travel or transport involves two or more participants. In Lumary we've extended this to include services where the cost can be divided between multiple clients. |
Top | |
Care plan |
A care plan outlines a person's assessed care needs and describes how a provider will meet those needs. |
Case note |
Case notes can be added throughout the Lumary system to provide further information about things like a client's progress or what happened during an appointment. |
Contact |
A contact is a type of Salesforce record that stores information about individuals that interact with your business and clients. In Lumary, this includes your clients and workers, but can also include other people involved in client care, such as healthcare providers and family members. |
Customisation |
A customisation is a deviation from the baseline Lumary package, either by a third-party developer or the Lumary Delivery Team. While the Salesforce platform provides a great deal of flexibility to adapt our product to your specific circumstances, it’s important to be aware that this can cause issues when we make improvements to the system. Find out more about avoiding issues with Salesforce configuration and settings. |
Top | |
Delivery Ratio |
Delivery Ratio is the ratio of workers to clients when services are delivered. In Lumary, the Scheduled Delivery Ratio is set when a service is added to a client appointment and determines how the cost of the service is apportioned between clients who received it. See also Scheduled Delivery Ratio. |
Top | |
Enquiry |
When an organisation is contacted with a request for information about their services, the system can be used to capture the details. This is stored in an enquiry (ENQ) record. If the person that the enquiry is about becomes a client, their enquiry record can also be used to generate their client record. |
Extract |
An extract (EXT) retrieves data from relevant records and puts it into a file format for submission to a funding body to claim funds. Extracts can also be used to share information with financial packages like MYOB or Xero. Extracts use service delivered (SD) records to create extract items (EXIs). Lumary includes extracts tailored to the requirements of specific funding bodies, including the NDIA, DSS and DVA. These include all of the information required for a claim to be processed and to ensure that it complies with the funding body's reporting requirements. |
Top | |
General transport |
Under the NDIS, general transport refers to the transportation of a participant to an activity that is either not a support or is a support delivered by another provider. |
Top | |
Household |
In Lumary, client contact records are often organised under household accounts. The household includes the client's contact record, as well as the records for other people involved in their care, such as healthcare providers and family members. |
Top | |
Intake |
Intake is a type of contact record that can be used for potential clients who require further assessment before being converted into a full client. |
Top | |
Labour costs |
Under the NDIS, there are labour costs that can be claimed for travel and transport. They refer to the cost required to compensate the worker for their time spent travelling to and from a participant, or their time spent transporting the participant. |
Local area coordinator (LAC) |
A local area coordinator (LAC) is a service provider contracted by the NDIA to:
|
Lumary Settings |
Lumary Settings is where system administrators can apply and adjust settings that affect all users of the Lumary application. Settings include:
|
Top | |
myplace portal |
Participants and providers use the NDIA's myplace portal to create service bookings and request payment for services. They can also access a copy of their NDIS Plan and share them with their provider. Registered providers need to have a Provider Digital Access (PRODA) account linked to myplace to access the portal. |
Top | |
NDIA |
The National Disability Insurance Agency (NDIA) is the Commonwealth government organisation responsible for implementing the National Disability Insurance Scheme (NDIS). |
NDIA managed |
Also referred to as 'agency-managed', this means that the NDIA manages the participant's funding. Service providers must claim through the NDIA's myplace portal to receive payment for services that they have provided. |
NDIS |
The National Disability Insurance Scheme (NDIS) is a funding source that provides support to Australians with disability, their families and carers. The scheme is administered by the NDIA. The agency sets price limits for some of the supports that can be claimed under the scheme. NDIS pricing arrangements and support catalogues are regularly updated and explain pricing limits and which supports can be claimed under the scheme. |
Non-labour costs |
Under the NDIS, non-labour costs can be claimed for travel and transport. These include:
|
Top | |
Participant |
The NDIA uses the term participant to describe a person living with disability who receives supports from the NDIS. In Lumary, participants and their information are stored in client records. |
Permission sets |
Permission sets are used to refine the level of access provided to different groups of users. They provide more flexibility than profiles and can be used to give users access to the parts of the system they need without being overwhelmed by functionality that they don't use. |
Private funding |
Private funding refers to payments that will be paid out-of-pocket by the client and/or claimed from their private health insurance fund. |
Private travel |
Private travel refers to travel costs that will be paid for out-of-pocket by the client and/or claimed from their private health insurance fund. |
Process |
In Lumary AH, a process is a series of steps or tasks that users can add to a record. Processes help users save time by capturing key steps and information in one place. Where multiple users are working on the same process, they can help users quickly see what still needs to be done. |
Production environment |
The term production environment is used to describe the version of Lumary and Salesforce that contains your live data. It’s where you usually log in to use the system to work with your client’s data, schedule your workers and/or manage claims for funding and payment. While test data can be used in a production environment, it’s important to take care as this can affect the accuracy of reporting and may cause other unexpected results. A production environment may also be referred to as a live environment or org, or a production org. |
Profile |
A profile establishes the base level of accessibility for each of your users. Each user can only be assigned one profile. Further access can be provided using permission sets. There are three main profiles used in Lumary:
Older users of the system may have an Enrite Care prefix in their profile names. Some clients may also be using custom profiles. These profiles may require additional configuration to ensure access to some Lumary updates. |
Provider travel |
Under the NDIS, provider travel refers to a worker's travel to a participant to deliver a service. There are also a limited number of services that allow for the claiming of travel from an appointment. The NDIS pricing arrangements set out complex rules around what can be claimed as provider travel. For example, the amount of time that can be claimed for travel is different depending on the classification of the area the worker is travelling to. If the participant approves, providers can claim for labour and/or non-labour costs associated with provider travel. |
Top | |
Related list |
Related lists display data from other records that are related to the record you are viewing. They typically appear under tabs that organise them into relevant categories. For example, things like case notes, assessments and service agreements appear as related lists on a client's record. |
Top | |
Sandbox |
A sandbox is a testing environment that does not use or affect the live data in your production environment. Lumary uses sandboxes to provide access to releases for testing prior to updating production environments. They can also be used for training staff or to trial business processes without risking an impact on your live data. A sandbox environment may also be referred to as a user acceptance testing (UAT) environment or org, or a sandbox org. |
Scheduled Delivery Ratio |
Scheduled Delivery Ratio represents the ratio of workers to clients when services are delivered. In Lumary, the Scheduled Delivery Ratio is set when a service is added to a client appointment and determines how the cost of the service is apportioned between clients who received it. For example, for a group appointment, the Scheduled Delivery Ratio may be 1:4, meaning the service will be apportioned at 25% to each client. For an individual client appointment, the Scheduled Delivery Ratio would always be 1:1. See also Delivery Ratio. |
Self management |
Self management is when an NDIS participant chooses to manage their own funding and pay service providers directly for the services they receive. |
Service agreement |
A service agreement is a contract between a client and a provider that outlines the costs and expectations of both sides. They are a key part of the Lumary system. In Lumary, service agreements:
|
Service booking |
Service bookings relate to NDIS funding. They are made through the myplace portal to set aside funding so that providers can claim payments. A service booking will show the type of support to be provided and the length of time that it is needed. Service bookings can be recorded in Lumary against service agreements, categories and/or service line items. |
Service delivered record |
A service delivered (SD) record stores information about a service that you've provided to a client or account. It includes information like the rate and quantity of the service, which is used to claim funds. Service delivered records have an SD prefix followed by a numerical identifier, for example, SD-0000200. |
Service provider |
A company or organisation providing services to clients. |
Session |
A session is a record that stores information about an appointment. This could be for the provision of client services or the scheduling of a worker's shift or both. It usually includes the client or clients that are attending and which workers are providing services. Sessions can be scheduled and reviewed via the:
|
Shift |
A shift is a block of work completed by a worker. It can include multiple appointments (or sessions). In Lumary, information about a shift is stored in a record with an SH prefix. |
Support budget |
Under the NDIS, there are three types of support budgets:
|
Top | |
Transport |
Transport involves a worker accompanying a client on a community outing and/or transporting a client from their home to the community. Transport is sometimes confused with travel but is distinctly different, particularly in relation to NDIS funding. Under the NDIS, providers can claim for transport costs if an NDIS participant has transport funding included in their plan, or if the service agreement outlines the expected transport costs, any additional contributions and how these costs will be paid. |
Travel |
Travel refers to the movement of a worker between appointments. This can include travelling to, from or between appointments. Under the NDIS, there are restrictions to the time that can be claimed for provider travel. Providers can usually only claim the time a worker spends travelling to an appointment to deliver supports. There are some exceptions that allow providers to charge for return travel. |
Top | |
UAT environment |
User acceptance testing (UAT) environment is another way of describing a sandbox. |
Top |