Appointment Services

Learn how to configure Appointment Services in Maica

How do I configure Appointment Services?

To correctly configure an Appointment Service, please follow the steps indicated below.

1. Search for Appointment Services in the App Launcher

In the Salesforce App Launcher, search for Appointment Services and choose it to open the list view of all Appointment Services in your Maica instance, as shown below.

The Salesforce App Launcher is found in the top left corner of your interface.

2. Create new Appointment Service

Once you are viewing your Appointment Services, simply click the New button located in the top right hand corner of your interface to bring up the New Appointment Service pop-up, as shown below.

After the pop-up is displayed, you will be prompted to fill-in the following fields:

Field	Description
Name	This will be the name of your Appointment Service. As an Appointment Service is essentially a parent object for your Support Items, we recommend naming your Appointment Services generically based on the Support Items it will contain.
Claim Types	Available: Lists all potential Claim Types that can be associated with the Appointment Service. Chosen: Select the relevant Claim Types for this Service that match the associated Support Items. Only selected Claim Types in this section will apply to the Appointment Service.
Tags	These are custom tags to categorise or group Appointment Services. Tags can assist in easy search and filter of Services when assigning a Service to an Appointment.
Available Sections	Available: Lists different sections that can be added to the appointment service. Chosen: Select the sections relevant to this Service. This customises what fields or information will be displayed when setting up an Appointment using this Service.
Start & End Date	This field represents the beginning date (when the Appointment Service becomes active) and when the end date (when the Appointment Service is no longer valid). If the End Date is left blank, the Appointment Service will be active indefinitely.
Participant Note Template	Participant Note Template: This assigns a template for Participant Notes that will be associated with the Service. Select a pre-existing template or search for one to guide standard note-taking. Pre-load Template: If checked, this option will automatically load the selected Note template whenever this Appointment Service is used.

Finally, once populated, simply click Save to create your Appointment Service.

3. Assign relevant Skills and Checklists

Select your newly created Appointment Service to open up the record. Once open, you will see the related list fields on the right hand side of your interface, as shown below.

This step is only going to focus on Skills and Checklists. Both of these related lists work the same way, which is:

1. Click the New button to add Skills and Checklists

2. Select which Appointment Service you wish to assign the Skill or Checklist too. The Service you open the selector from will be selected by default.

3. Select which Skill or Checklist you wish to assign, and set its associated Requirement Level to either Required or Recommended.

4. Click Save to finalise your selection.

Note, you can also assign Skills and Checklists to an Appointment Service through the related lists on the relevant Skills and Checklists records.

4. Assign Support Items to an Appointment Service

Note, you must have configured your Support Items before assigning them an Appointment Service. In order to learn how to configure Support Items, click here.

Please note that depending on the version of Maica you are using, Support Items may be referred to as Products (the NDIS term) in your instance.

Again, on your newly created Appointment Service, refer to the related list fields on the right hand side of your interface to identify the Support Items list. Here you will see all associated Support Items within an Appointment Service.

It is crucial to note here that assigning Support Items does not work in the same way as assigning Skills and Checklists. Clicking the New on the Support Item related list directly from your Appointment Service record will create an entirely new Support Item, not assign an exisiting one. In order to assign a Support Item to an Appointment Service, you must do it directly from the Support Item record.

As mentioned, in order to assign a Support Item to an Appointment Service, you must do it directly from the Support Item record. This is due to the fact that one Support Item can only ever belong to one Appointment Service.

To explain how this process works, please refer to the demonstration below. In the Demonstration, the following examples will be used and referenced:

• Appointment Service: Recovery Coaching

• Support Item: Psychosocial Recovery Coaching - Saturday

Now, your Appointment Service is ready to be used.

Things to look out for: Basic Details

1. Duplicate Support Items

When configuring Appointment Services, it is crucial that no Support Items with the same configuration are assigned to the same Appointment Service, as this will disrupt Maica's ability to accurately validate the Participants funding, and potentially disrupt the Billing Flow.

If two Support Items (with identical configurations) were to be assigned to the same Appointment Service, the Billing Automation would face ambiguity. Maica’s Billing Automation relies on identifying a unique Support Item within an Appointment Service to bill correctly. If multiple Support Items with identical identifiers were present, the Automation wouldn’t know which one to bill against, potentially leading to billing errors or incorrect Invoicing. To learn more about the Billing Flow, click here.

The following four fields in a Support Item decide whether they are considered 'identical' within the Maica system:

1. Service Day

2. Service Time

3. Support Category

4. Registration Group

So, in summary, no two Support Items with identical inputs to the four fields listed above can exist within the same Appointment Service. If one field differs, they can exist.

Please note, Maica's SupportItemServiceValidation_MDTM trigger based Automation will prevent this from occurring given this trigger is enabled.