Understanding Pathways

Article author
Dan Jordan
  • Updated

What's the context?

Pathways in Meddbase provide a rich range of capabilities. They enable the setup of workflows made up of a series of steps where actions are carried out. What may not be clear, is the capabilities available within Pathways and to whom they are available. This article can help.

What is the purpose of the article?

This article gives you an overview of:

Who can work with Pathways?

Pathways can be used by:

  • Meddbase users who
    • Have been given permission through security policies to work with Pathways and related Pathway tasks
    • Are members of a role group that is assigned tasks within a Pathway
  • Patients who have been assigned tasks in the Patient Portal
  • Authorised employer managers who have been assigned tasks in the Occupational Health Portal

What can you do through Pathways?

When they have been specified and configured, a wide range of workflows can be completed through Pathways. These use Pathway tasks.

The sub-sections below outline the different tasks that you can complete using Pathways.

Send a questionnaire to a patient

A_-_Document_icon_with_question_mark_above.png A Pathway task can send a questionnaire to a patient to complete. When sent, the patient receives an email with a 2-factor authentication link.

Book an appointment for a patient


From within a Pathway, a task can be used to launch the Slot Finder.

This includes the automatic definition of the appointment type.

Decide on the next task when an appointment is arrived, cancelled or DNA'd

D_-_forked_arrow_icon.png This works with the Book an appointment task noted above. It is based on whether an appointment is arrived, cancelled or DNA’d (Did Not Arrive). This can also decide on the next task in the Pathway.

Attach a document to a patient record


A Pathway task can ask the user to upload a document to the patient’s record in Meddbase.

If a template is provided, it will automatically create and attach the document.

Review a document


A Pathway task can work with the Attach a document task above.

When used it creates a side by side view of the attached document and a clinical form.

Contact the patient


A Pathway task can ask the Meddbase user to call the patient.

This same Pathway task can also be configured to automatically send the patient an SMS or e-mail using a template.

Prompt the patient for a response


SMS messages sent from a Pathway can prompt the patient to respond.

The response can determine the next step in the pathway workflow giving the patient more control over their care journey.

Create a General task


A Pathway can create a general task that can have a customised description.

This is a flexible method of generating a task not covered by other areas.

Create a Form


A Pathway task can create a form that asks the Meddbase user to complete field values.

This form is similar to a Clinical form.

Make a referral for a patient


A Pathway task can work in a similar way to the Referral feature available from a patient record.

However, the creation of a referral is integrated into the Pathway itself.

Find a list of patients using filters


A Pathway task can use the reporting system to find a list of patients that meet any criteria set in filters. Typically it is used together with other features described below to find a set of patients and then delete them.

Alternatively, this could be used to bulk start Pathways for a set of patients. 

Delete a selected list of patients


A Pathway task can use a patient query described above to allow the user to review a list of patients and delete them from a chamber.

Undo deletion of a selected list of patients


A Pathway task can undo the wiping of patient records if a mistake was made.

Select services to add to an appointment


A Pathway task can allow the user to select services to add to an appointment. This would typically be used before a "book an appointment" task.
This feature can also be used to change the chargeband or the payer for a patient.

Show Pathway as 'Completed'


An automatic task to display a message to users at the end of a Pathway to know that it is completed.

Show a Pathway 'Failure'


A message that can be presented to a user when something fails in a Pathway.

Manage Service Level Agreements (SLAs)


Using the functions and features outlined below, Pathways can be used to manage Service level agreements.

What are the functions and features of Pathways?

The list above shows examples of what jobs can be completed through Pathways. The table below outlines some of the features and functions available within Pathways that enable users to complete the jobs they need to do.

This can be helpful to understand the toolkit available for Pathway design.

Create a recurring task


This can work with other tasks in a Pathway to create recurring tasks under certain conditions.

As an example, this could be used with the Contact account task to send a patient an e-mail every day at noon for 1 week.

Evaluate a condition value


The ‘Condition’ feature is a component of a Pathway that evaluates a value.
It checks a value and uses the ‘true’ or ‘false’ logic to evaluate the result to push the Pathway down a specific path.

For example, where a value is ‘0’ (‘false’) it could load a ‘Book an appointment’ task. But where a value is ‘1’ (‘true’) it could alternatively ‘Send a questionnaire’.

Evaluate a list of conditions to perform an action


The ‘Switch’ feature is a component of a Pathway that is like a ‘Condition’ but can work with a list of conditions.

Where it finds a condition that is true, it can then perform the action assigned to that condition.

Make a decision and choose a Pathway direction


The ‘Make a decision’ feature asks the user to make a decision using up to 5 options.

The Pathway then is routed in a specific direction based on the user's decision.

Run tasks in parallel and complete all to go to next step


There are two flavours of this feature.

In the ‘When all’ flavour is used, a series of tasks can be added to a container (i.e. a group). The tasks within the container can be completed in any order.

But to move through to the next stage of the Pathway, all tasks within a container need to be completed.

Run tasks in parallel and complete any to go to next step


In this flavour of the parallel tasks feature of a Pathway, multiple tasks can be added to a container as above.

But when the user completes any one of the tasks, the other tasks will be automatically skipped so that the user moves on to the next step in the Pathway.

Manage task actions available to users


For each task, the Pathway designer can define whether a user can skip a task, edit a task or delete a task.

Share task with a patient


For each task, the Pathway designer can define whether the task is shared with the patient in the Patient Portal.

Share task with the employer representative


In the Occupational Health context, for a task, the Pathway designer can define whether a task is shared with an authorised employee manager on the OH Portal.

Managing the timing of tasks


For each Pathway task, there can be a time set for when a task should start, when it is overdue or when it will automatically be skipped.

These timings can be calculated from other tasks in the Pathway.

Assign tasks to role groups


Tasks in a Pathway can be assigned to role groups of users for action.

What's the next step to get going with Pathways?

It’s a good idea to get in contact with us to help understand your requirements to see how we can help you build the Pathway you need.

You can either Submit a request to the Support team or contact our customer account management team.


Review date

This article was last updated on 18 October 2021 in the context of Meddbase version