Home > CDX > Business Rules and DOH Tasks > Create a Business Rule

Create a Business Rule

With CDX, you can supplement business rules for existing NEMSIS guidelines with flexible business rules (FBRs) created according to your departmental protocols and/or unique needs. 

Once you have a specific rule in mind, the rule must be named and a NEMSIS software version must be selected. Rule names should be unique and clearly indicate the rule’s action, parameters, and/or purpose so that you can readily identify it from others.

Further, when creating a rule, you must select a software version. The software versions available to you are those which your departments adhere. If you manage multiple departments and some abide by the NEMSIS 3.4.0 standards whereas others adhere to those set by 3.3.4, you will have to select which particular version this rule should apply to.

To create a flexible business rule

Note: Required fields are marked with an asterisk (*).

  1. From any page, go to Administration: Business Rules. The Business Rules page opens. 
    Note: The image below reflects the page as seen by Department Administrators. What you see may be slightly different if you are a DOH Administrator.


  2. To create a rule, click Create Event Rule or Create Demographic Rule as appropriate. The Create Rule page opens.


  3. Click the Edit Details button and then enter or update information in the Rule Details section, selecting a name, level, input type, and software version for this rule.
    Tip: See Business Rules Fields for a description of the fields to complete in this section.

  4. If this rule is not part of the NEMSIS standard and is specific to TripTix, select the TripTix check box.
    Tip: States should avoid checking this box. Rules containing TripTix fields cannot be exported in a schematron file. Unchecking this box hides all TripTix-specific fields from the rules editor pick lists.

  5. To add requirement groups as needed, in the IF section, click Add Requirement Group.


  6. Make selections for each field as appropriate.

  7. Optionally, perform any of the following actions:

    • To clone a requirement group, click Clone.

    • To reorder the requirement groups, click Order Down.

    • To delete a requirement group that was added by accident or is no longer necessary, click Remove Group.

  8. To add an Else-If element, if applicable, click Add Else-If.

    • Complete the associated fields in this new section as appropriate.

  9. In the THEN section, for Statement Severity, select either Warning or Error depending on whether this rule, if conditions are met, should trigger a warning or an error.
    Tip: See Action Severity for details on making the appropriate selection for your rule.


  10. To add a resulting action when the rule’s conditions are met:
    Tip: See Actions for the definition of each option in this drop-down menu.

    • For the first field, indicate which devices this rule should apply to.

    • For Select a Field, indicate to which field this action applies to.

    • For the third field, select the desired action. 

  11. If you chose Display message for the third field, in the field to the right, enter the message users should see when this action is triggered.

  12. To add subsequent actions, to the right of the first action, click the blue plus icon and repeat step 9. 

  13. To clone an action, to the right of the applicable action you wish to clone, click the clone icon and repeat step 9. 

  14. Click Save.

When you have finished creating a business rule, you can generate a schematron file so the rule is implemented during the file validation process. This action is necessary for state uploads only.

Further, it is always best practice to test your rule in both TripTix Web and Windows. Testing ensures the rule is working properly and effectively. 
If you are a state administrator, you may wish contact Support for options on how to test changes or additions to state-level rules outside of the production environment.

Business Rule Fields

Rule Name
A descriptive name for the rule.

Note: Rule names must be unique.

The level of the system this rule should be implemented for. Options include State or Department.

Note: You may only create rules at your own administrative level.

Input type
Select either Event or Demographic to describe which option applies to the rule you are defining.

Note: If you change the rule type while editing, you lose the existing rule data.

Software version
Select either a TripTix or NEMSIS version to which the rules apply. The options in this list are dependent on the data standards your state and/or department accepts. By default, the primary data standard for the state is selected.

Tip: You can select multiple versions for this field. Selecting multiple versions can be helpful for departments undergoing an active transition from one data standard to another.

Note: The software version selected directly affects the options available in the IF section. If more than one standard is selected, only fields mutual to both versions are available; the element must exist in both versions.

If this this rule is not part of the NEMSIS standard and is specific to TripTix, select the TripTix check box. By default, this check box is selected.

Tip: States should avoid having this box checked as rules containing TripTix fields cannot be exported in a schematron file. Unchecking this box hides all TripTix-specific fields from the rules editor pick lists.

IF/THEN Fields
Modify the IF/THEN fields to make correct IF/THEN statements for your rule.

  • Data Fields – Select a field option from the drop-down that represents the ePCR data field you want to represent in your rule.

  • Arithmetic Operators – Indicate whether the data fields should be added (Plus), subtracted (Minus), multiplied (Times), or divided (Divided By).

  • Boolean Operators – Indicate the relationship between the data fields, such as Equals, Not Equal, Greater Than, Less Than, and more.

  • Statement Severity – Select Error or Warning to indicate how the system should flag fields when they do not meet the above criteria.

  • Action – Indicate what should happen in the system when the IF/THEN statement is broken. Indicate the type of device the rule applies to, the data field, and a message to display on the screen.

Add Requirement Group
Click this link if you would like to add an OR/AND statement to the IF statement. Note that if you change the logical operator from AND to OR, it changes it for all instances. 

Add Else-If 
If you would like to add an ELSE-IF statement after the IF/THEN statement, click this button.

Last modified



This page has no classifications.