Medication Usage Dates for Improved Reporting

Available with the v3.5.5 release of Chronic Pain Tracker, you now have the ability to define a Start Date and End Date for each custom Medication item in the Medication Tracker. Although this feature is optional, we do encourage our users to take advantage of it where applicable.

The feature has been added for two key reasons. First, it helps avoid mistakes at the time of entry creation, and second, it improves the accuracy of medication usage reporting. Let’s take a look at how to enable this feature and also how these benefits are achieved.

Defining Medication Usage Dates

To apply a Start or End Usage Date to your Medication items, you’ll need to open the Tracker List editing table for the Medication Tracker object. You can access this table either by (1) Going to the Settings tab, selecting Diary Preferences -> Medication Taken -> Edit Medication List, OR (2) Starting a new Diary Entry, adding the Medication Taken tracker to the entry, and selecting the “Edit Table Entries” from the medication table.

Once you have opened the Medication List, you can select the medication you wish to edit. In the example shown here, we’re going to edit the usage dates for “Dilaudid 4mg”. Once selected, you will see the details for this medication item. By default the Start/End dates will show as “Not Defined”.

Medication List Medication Details showing Usage Dates as Not Defined
Medication Tracker ListMedication Item Showing Start/End Dates as Not Defined

By tapping on the Start Date row, you will be presented with options for setting the date value. As you can see in this image, you have the option to (1) Manually Set the Date, (2) Automatically Set the Date, (3) Clear the Date, or (4) Cancel the Change. If you choose to Manually Set the Date, you will be presented with a Date Picker as shown in the second image below. Adjust the Month, Day & Year values to the appropriate date.

If you choose to use the Automatic option, the app will determine the Start/End Usage Date by looking up the First/Last time you used that particular medication and use that date as the new value. This usually will be sufficient, so we recommend using the automatic selection option first, and if necessary using the manual option to fine tune the date value.

If you set a date incorrectly (eg. setting an End Usage Date for the medication, but you are actually still taking it), you can use the Clear the Date option to reset the date to the “Not Defined” value.

MedicationAvailabilityStartDateEntryOptions MedicationAvailabilityStartDateManualSelection
Options for Setting the Start/End Date ValuesUsing the Date Picker to Set a Start Date Value

Once you’ve set the Start/End dates as desired, you will tap on the Done button in the upper left corner and then you’ll need to save the changes (green checkmark in upper right) to the Medication List.

For CPT users that have Device-to-Device Sync Enabled

We have identified a bug with v3.5.5 that prevents the proper saving of Tracker List changes when device-to-device sync is enabled. Although the changes appear to be saved, if you re-open the tracker list item, you’ll see the same previous values in place for that item. This bug is being addressed in the next update, but until then, you can do the following to avoid this problem.

Before you make any Tracker List changes, go to Settings tab -> Cloud Services -> Device Sync Services. Scroll to the bottom of the screen and tap on Turn Off Sync Services for Device to disabled the sync processing. Then you can make your Tracker List changes. Once those are complete, you can re-enable the Sync services. We do suggest going through the process of Uploading your Master DB to the cloud repository and Downloading the Master DB to your secondary devices after this step to ensure that all devices are starting from the same synchronized baseline.

Improved Medication Input with Usage Dates

One of the benefits of assigning usage dates to your medication items is that CPT can now help you avoid errors when creating new diary entries. This is done by giving you a warning message if you try to enter the usage of a medication for a diary entry that is before or after the associated usage date range.

For example, consider the situation where you have indicated that your “Dilaudid 4mg” medication was used from Nov 22, 2011 to Jan 10, 2014 via the new Start/End Dates. You then begin a new diary entry input for Feb 3, 2014. If you select the “Dilaudid 4mg” during that entry, you will receive a warning like the one shown below. This warning indicates that you are trying to indicate medication usage outside the defined timeframe.

Warning Shown During Diary Entry When Selecting a Medication Beyond Its Availability Date Range

Improved Medication Reporting with Usage Dates

The more significant benefit of setting the usage dates comes when we look at CPT’s reporting features – specifically the Medication Tracker Summary Report. There are 4 standard graphs created per medication item in the current Summary Report format. Of these 4, the first graph, “Daily Medication Qty Totals per Day”, is the one where this change is most obvious.

The impact comes from the way we evaluate usage of the medication item. This is most easily explained by using the example of a breakthrough pain medication that is used a variable number of times per day – as needed for pain. There are some days where the pain is high and you may use the medication 3 or 4 times; maybe other days it will be moderate and it’s used only once or twice. Still other days, the good days, and you may not use the medication at all. It’s this last situation where the usage dates come into play.

Graph 1 - Daily Qty Totals when Start/End Dates are Not Defined Graph 2 - Daily Qty Total when Start/End Defined
Graph 1 – Daily Qty Totals when Start/End Dates are Not DefinedGraph 2 – Daily Qty Total when Start/End Defined

Graph 1 above shows a situation where usage dates are not defined for the “Dilaudid 4mg” medication item. You can see that there is consistent usage of the medication for the first half of the period, but then it drops to zero for each day. You can also see that there is a Medication Change milestone indicator at the point where the usage stops.

Looking at this you could assume that this was a situation where you were continuing to have the Dilaudid 4mg available for use but didn’t need it once you added some other medication to your treatment strategy (Scenario A). Or, perhaps this was a situation where you were using Dilaudid 4mg for the first part of the period, but then stopped using it in favor of a different medication (Scenario B). Although these situations are similar, they are unique and you’d probably want to report on them differently.

Graph 1 matches well to Scenario A since we continue to plot data points for the days after the medication change, and the moving average plot (green line) continues for the full width of the plot accounting for the reduced usage levels in the period after the medication change. The overall period average qty used indicated by the horizontal line labeled 1.1 tablets per day also reflects the average usage of Dilaudid 4mg during the period.

But for Scenario B when the usage of Dilaudid 4mg was discontinued after Jan 10, we would prefer a different view of the data, and that’s where Graph 2 is relevant. Here, we have the Jan 10, 2014 End Date defined in the Medication item. So now you can see that the Daily Qty data points past Jan 10 are shown, but they are grayed out indicating that the medication was not available during those days. You can also see that the moving average plot stops at the Jan 10 date since this was the last day the medication was available for use. And finally, the overall period average qty used is calculated only for the days when the medication was available and shows a 2.3 tablet per day use of the Dilaudid.

We believe the inclusion of Start/End Dates for the Medication items will allow you to generate more accurate summary data like those shown here. Both scenarios are realistic and therefore we saw a need to enable both to be reflected in the summary analysis and graphs. Enabling the definition of Start/End Dates now gives you the ability to deal with both of those situations.

Sorting your Medication Items

As of CPT v3.5.5 (released Feb 20, 2014), you have the ability to define a manual sort order for your list of Medication Items. This can be helpful if you have a large number of items in the Medication table and want to move current meds towards the top of the list.

Using this feature is quite easy. To begin, open the Medication Tracker List by either:

  • go to the Settings tab -> Diary Preferences -> Medication Taken – Edit Medication List, OR
  • create/edit a diary entry, add the Medication Tracker and select “Edit Table Entries” at the bottom of the list

With the Medication list open, you’ll see that each table entry will include a sort order control on the far right side of the row. It’s the icon with the three stacked gray bars. To change the position of an item in the table, tap/hold on the icon and drag the item up or down in the list. Once it’s in the location you want, just let go of the item and it will pop into place.

Once you have manually changed the sort order of the table, the items will remember their new positions and will display in this order for all new diary entries. As you add new Medication items, you can continue to adjust the sort order as needed.


Chronic Pain Tracker v3.5.5 has been released to the App Store

Chronic Pain Tracker v3.5.5

Our latest version of Chronic Pain Tracker, v3.5.5, is now available from the App Store. If you have automatic App Store updates enabled, you are probably  already running the new version; otherwise, download it from the App Store today. To check which version you are running, open CPT and tap on the Setting tab. You will see a line labeled “Version” which will show the current app version. You should see something like “v3.5.5 (140218) Pro” or “v3.5.5 (140218) Lite”

As always, if you have any issues applying the update or questions about the new features, please drop us an e-mail with your questions. It’s always best to use the “Send E-Mail to Support Team” option (also found in the Settings tab) to contact us as it includes lots of diagnostics information about your installation that can help us resolve issues more quickly.

New Features

This version was mainly intended to address some minor bugs identified in previous versions, but it also includes some new features that have been requested by our users. Here are the new features included with the update. We’ll provide some additional posts over the next few days which describes each feature in more detail.

  • User Definable Medication Sort Order
    • You can now change the sort order for your medication list to make data entry more efficient
  • Medication Start/End Dates
    • CPT now provides a means to define a start and/or end date for each medication. This is an optional feature which can improve the accuracy of the medication usage reporting.
    • Start/End dates can be set manually by the user, OR they can be set automatically based on the first and last usage dates of the medication item

Bug Fixes

In addition to these features, the following bugs were resolved by this update:

  • FIXED – Weather Tracker Lunar Phase plot had an issue with inconsistent size of the lunar images used as labels on the plot.
  • FIXED – Bug related to the Sleep History Tracker’s Sleep Quality Level summary plot that could arise in a situation where there was only a single sleep quality value specified within a range of entries being reported on.
  • FIXED – In the case where a Medication cited in a diary entry is not found in the Medication Tracker List (eg. it has been previously removed from the list) and that diary entry is included in a summary report, the report will now assume an 8 hour window for the Pain Reduction analysis graph. Previously this could cause an error in the Summary report.
  • FIXED – Also in the Pain Reduction Analysis report, a bug was fixed so that diary entries that include a medication usage, but not a pain intensity level value, are filtered out so that they do not impact the analysis of the graph.
  • FIXED – Weather Tracker summary plot relating pain levels to weather conditions could generate an incorrect avg pain level if one or more of the diary entries included a weather tracker item but did not include a corresponding pain intensity level tracker item.
  • FIXED – A minor bug related to the methods used to create data ranges in certain summary graphs
  • FIXED – After editing an existing diary entry, the diary history table display was not immediately refreshing the diary entry icons in the table view.
  • FIXED – Internal image caches were not properly releasing cached images older than set lifespan. Caches are now functioning as intended.
  • FIXED – Display of General Comment Tracker entry cell on iPhone with iOS 6.x was incorrectly sized.