Events

Events can be automatically created based on key milestones in a patient's program journey. A trigger for a milestone can be set either on the Trigger Handler Setting (mvn__PJN_Trigger_Handler_Setting__mdt) custom metadata type or via a custom implementation, but it must call the Event Automation Handler (PJN_EventAutomationHdlr) global Apex class to retrieve a list of Event Configuration (mvn__PJN_Event_Configuration__mdt) metadata records for the triggered object. The Event Automation Handler class then checks the criteria that is defined on each event configuration to determine whether or not the criteria is met and therefore whether or not an event should be created. If so, then an Event record of the specified record type is created with the status and sub-status values specified on the event configuration.

To define a trigger on an object for a specific milestone and then configure an event to be subsequently created:

For more guidance on how to configure a milestone event automation, reference the Example 4, “Create a therapy status update event when a patient is eligible for PAP” below.

In addition to creating events based on milestones, you can also track the amount of time it takes for each milestone to be hit. For more information, reference the Milestone event measurement section below.

{
  "AllTrue": [
    {
      "path": "mvn__PJN_Record_Type__c",
      "operator": "Equals",
      "value": "Patient Assistance Program"
    },
    {
      "path": "mvn__PJN_Outcome__c",
      "operator": "Equals",
      "value": "Eligible"
    }
  ]
}

In addition to creating events based on key milestones in a patient’s program journey with the above milestone event automation feature, you can also track the amount of time that a patient takes to go from one milestone event to another, which may be helpful for understanding the velocity of a program journey and measuring the average turnaround time for certain milestones across all patients in a care program. When an Event (mvn__PJN_Event__c) record is created or updated, the Trigger Handler Setting (mvn__PJN_Trigger_Handler_Setting__mdt) custom metadata type calls the non-global PJN_EventMeasurementHdlr Apex class to first check if the Event record contains the record type, status, and sub-status values identified on an Event Configuration (mvn__PJN_Event_Configuration__mdt) metadata record and then evaluate if the Event Configuration metadata record represents a starting or stopping milestone event on any Event Measurement (mvn__PJN_Event_Measurement__mdt) metadata record. If the Event record is determined to be a starting milestone event, then a new Milestone Event Measurement (mvn__PJN_Milestone_Event_Measurement__c) record is created where the Start Event (mvn__PJN_Start_Event__c) field is populated with the Event record and the Status field is set to Open; if the Event record is determined to be a stopping milestone event, then existing Milestone Event Measurement record(s) are updated accordingly such that the Stop Event (mvn__PJN_Stop_Event__c) field is populated with the Event record and the Status field is updated to Closed.

Milestone Event Measurement (MEM) records are only created automatically with a starting milestone event and cannot be created manually or with a stopping milestone event. Additionally, every starting event can have one or more stopping events and every stopping event can have one or more starting events, but only a single open MEM record may exist for the same pair of a starting event and a stopping event. This means that if a second starting event occurs after the first stopping event occurs, a new MEM will be created since the previous MEM record will have already been closed, but if a second starting event occurs before the first stopping event occurs, no new MEM record will be created since an open MEM record already exists. The duration fields on every MEM record update automatically with the amount of time that has passed since the starting milestone event. If the MEM record is open, then the time is calculated based on the current date and time; if the MEM record is closed, then the time is calculated based on the stopping milestone event.

To configure the milestone events for which the time in between should be measured and tracked: