Fusion Enterprise understands that managing all of your cases is a critical function of any practice. We have ensured that you can run all of your practices front office needs through Fusion Enterprise and make it as easy as possible. This series of introductory articles will cover the essential aspects of managing Tasks & Alerts with Fusion Enterprise.
Defining the Condition
Conditions can be set up to check a wide variety of variables and these variables are all related to the type of event that has been triggered. For instance, we can look at a particular patient and his related information when he is checked in, but only for that particular patient.
So what is a condition and how do we define it? A condition is a statement that the system will evaluate and if it is true then the action will occur. For example, a condition statement might read something like the following:
“If the case does not have a valid prescription and the primary insurance carrier is Medicare then…”
If this statement was ‘true’ then the action would occur. (Actions are defined after we define the condition)
While the above statement is simple to write we need to get it into a format that the system will understand. The Alert Condition dialog appears as follows:
If we knew exactly what we wanted and how to state it we could write the condition into the box provided. If we right-click on the condition box we get the following menu:
Condition Menu
|
Edit Condition |
Displays the Condition Formula Builder. |
|
Edit Variables |
Displays a list of variables that may be used in the condition. |
Selecting Edit Condition from the menu displays the following Formula Builder:
The formula builder has the power to create very complex and involved formulas and uses the same system Microsoft Excel uses in its formulas.
The dialog is divided into three areas. The left side contains a list of Operands and Functions and the right side contains the formula editor.
If you look at the Operands tab you will see a list of named references as shown below:
We will continue with our “Valid Prescription” example. If we open up the Visit node we see the following list of References:
With some reading, most of these are fairly self-explanatory. The P1, P2, and P3 mean Primary Policy, Secondary Policy, and Tertiary Policy, so P1Carrier equates to the Primary Carrier Name, the P1Charges equates to the charges entered against this carrier for this patient and on down the list.
If we wish to evaluate the VisitHasPrescription we simply double click the VisitHasPrescription node, and it is added to the formula window on the right as shown below:
Note that the ‘If’ is implied. This Condition would resolve to True and activate the action IF the Visit Has a Prescription.
However, in our example, above we wanted to know if the visit had a valid prescription AND the primary insurance carrier was Medicare. If you are following along press the Clear button to clear the above formula and we will start over.
If you flip over to the Functions tab you will see a list of Functions.
You will probably never have a use for most of the functions available. The ones you will be primarily interested in are the Logical functions.
In our case, we are looking for the AND function. Double Click the AND operator and a new dialog will appear, which is the Function Builder dialog.
This dialog works with the AND operator and allows you to set up various conditions. A list of all the available references is available in the list on the left. On the right side will be a list of true/false statements separated, in this case, by an AND.
To continue with our example we would find the VisitHasPrescriptions reference and either double-click it or drag it into the Logical0 expression on the right side. VisitHasPrescriptions is either True or False, so it can stand on its own as a statement. After we add this, a new line will appear, logical1, where we can add our next statement.
In this, we will put the second part of our argument, which is Primary Policy equals Medicare. So we would select P1Carrier from the list and add it to logical1. With this, however, we need to add a bit more since P1Carrier does not resolve to true or false, it contains the name of the primary carrier. In the logical1 box we would add the text ‘= Medicare’ after the Carrier reference so it would look as follows:
You could continue to add more arguments if required; however, this is all we need for our example. In looking at this what we are saying is ‘When the visit has a prescription AND the Primary Carrier is Medicare then return true to the formula’. When you click OK the formula will be added to the condition box and will be formatted correctly.
This should give you an idea of how formulas work. The scope of this manual is not sufficient enough to cover the expanse of what could be done with the formula editor and all of the nuances of the formula syntax. There are many books written on this subject whose length is longer than this entire manual.