A guide to pulling up Trip History in MediRoutes Desktop and understanding changes commonly seen there
The Trip History feature in MediRoutes Desktop allows you to track all changes made to a trip from its creation onwards. By reviewing these changes, you can easily identify any issues or miscommunications that may have occurred, such as accidental no-shows or changes in the trip's schedule. Understanding how to utilize this feature effectively will make it a valuable tool in your MediRoutes toolkit.
Viewing Trip History
To access the Trip History, go to the Home tab and look for the trip options on the left-hand side. Next to the Edit icon, you will see a stopwatch icon with a blue arrow on it.
And when you click on that icon, you will see something like this:
Every line includes the date and timestamp of when the change occurred, the username of the user responsible for the change, the specific field or data that was modified, and both the previous and new values for easy reference. This information will assist you in identifying the timing and details of trip scheduling, reassignments to different runs, or cancellations. Understanding these aspects can be beneficial in troubleshooting any trip-related issues. If you encounter any changes in the Trip History that are not clarified in this guide, do not hesitate to contact Support for assistance.
Note: If the user field displays API in the username, you may also notice the Broker's name before or after it. These changes were initiated by the Broker using the API, rather than by the MediRoutes system or any users within your organization.
Scheduling/Unscheduling Changes
When a trip is scheduled, you will see in the trip history that the Run field is updated from (unscheduled) to reflect the name of the specific Run that the trip was scheduled for.
If a trip is unscheduled, the field that was modified will remain the Run field. The previous value will display the name of the Run the trip was originally scheduled for, while the new value will show as (unscheduled).
If a trip was moved from one run to another, the trip history will show three events. First, you will see when the trip was initially scheduled. Next, you will notice the trip being unscheduled, followed by the trip being scheduled again but to a different Run name.
The trip history feature can also display how the trip was scheduled. This information is displayed in the user field within brackets next to the username.
In the example above, it states [Force No Move] next to the username. This indicates that the trip was scheduled using the Force No Move option instead of the Force With Move or Shopping options for scheduling. Each scheduling method will be shown in brackets next to the username on the line where the scheduling change occurred. Here are a couple other examples:
Trip is Cancelled or a No Show
A trip can be cancelled in advance on the Home tab, or it can be cancelled by the driver in the mobile app, which then makes it a no-show trip. Each of these cancellation scenarios will show differently in the trip history.
When a trip is cancelled ahead of time, the trip history will display the IsCancelled field on the line where the change occurred. The value will switch from False to True, indicating that the trip has indeed been cancelled.
If the trip results in a no-show, the trip history will indicate a change in the DriverCancelConfirm field, with the value transitioning from False to True.
Auto-Confirm and Auto-Cancel on No-Shows/Dry Runs
Two settings in MediRoutes can automatically confirm a driver no-show and cancel the return trip for the same passenger. For more information on how to enable and configure these settings, please refer to the article linked below.
When the AutoConfirmDryRun setting is turned on, it will appear in the trip history alongside the driver's username who marked the trip as a no-show. You will see the DriverCancelConfirm field switch from False to True.
And if the AutoCancelReturnTrip setting is enabled, and the appointment trip is a no-show, then the trip history on the return leg will show AutoCancelReturnTrip by the username, and the field IsCanceled will be changed from False to True.
Revised Date: 10/17/24 ARB