{"id":367,"date":"2020-06-01T13:36:43","date_gmt":"2020-06-01T17:36:43","guid":{"rendered":"http:\/\/harmsprogram.ca\/?page_id=367"},"modified":"2020-06-08T13:04:48","modified_gmt":"2020-06-08T17:04:48","slug":"administrative-protocols-failure-to-provide-udt-and-unexpected-results","status":"publish","type":"page","link":"https:\/\/harmsprogram.ca\/harms-program\/ii-administrative-protocols-failure-to-provide-udt-and-unexpected-results","title":{"rendered":"Appendix II: Administrative Protocols: Failure to Provide UDT and Unexpected Results"},"content":{"rendered":"
\t\t\t

While clinical administration does not need to be familiar with how to interpret UDT, they should be familiar with when to communicate to the prescriber either concerning automated interpretations on START-IT, or repeated failures to provide UDT. This section covers how clinical administration should respond to these concerning scenarios…
\n<\/em><\/p>\n<\/div>\n\t\t<\/div><\/div><\/div><\/div>

\t\t\t

Unexpected results:<\/strong>
\nThis section really only applies if you are using START-IT for automated UDT interpretation, or if you have been trained in how to interpret IA results. There are numerous different types of unexpected results, some more concerning than others, but generally speaking you should notify the opioid-prescribing physician of any unexpected result. Possible exceptions to this include those patients that may routinely have unexpected UDT, such as \u201cLevel 6\u201d patients prescribed opioids as part of OAT for addictions treatment.<\/p>\n

In addition to notifying the prescribing physician, follow the clinic policy around sending for confirmatory testing. At our clinic, we have historically sent all urines to the lab for confirmatory testing. START-IT now makes recommendations about when to send for confirmatory testing as well depending on the level of discordance between patient self-reports and the IA result. Unexpected results in which the patient self-report is discordant with the observed IA result will automatically result in a \u201cstrong\u201d recommendation for confirmatory testing.<\/p>\n

Equivocal results:<\/strong>
\nThis also only applies if you are using START-IT for automated UDT interpretation, or if you have been trained in how to interpret IA results. There are some UDT results that are not fully unexpected, but not expected either. An example of this would be someone who is prescribed morphine but claims to have not taken it in the last week and UDT is negative for morphine. This result could be simply because the patient is prescribed morphine for intermittent pain flares and hasn\u2019t had any recently, or alternatively it could mean that he either took too much of his medication early in his refill or is even diverting the morphine (trading\/selling). If you are not sure what to do with the result, we recommend you notify the prescribing physician.<\/p>\n

Failure to Provide UDT:<\/strong>
\nThere are numerous reasons that a patient may be selected for UDT but fail to provide one. While the exact reason may be important (on one side of the spectrum is someone who is hospitalized for medical illness so can\u2019t make it in, and on the other side is someone who doesn\u2019t pick up the phone or return messages, or outright refuses), the bottom line is that someone who fails to provide a urine sample despite numerous attempts (arbitrarily 3 attempts, with variability depending on reasons for failure to provide UDT) has a soft concern that may affect if and how the physician prescribes opioids. The physician needs to know this. Message the physician with an explanation of the attempts that have been made and the patient\u2019s response or lack thereof.<\/p>\n

It is probably easiest to keep track of each attempt using the \u201cRecall List\u201d tab in the \u201cHARMS Program UDT Randomization\u201d spreadsheet (same one that keeps the master-list and randomizes patients).<\/p>\n<\/div>\n\t\t<\/div><\/div><\/div><\/div>

\n
\n\t

Chapter Pearls<\/p>\n<\/div>\n<\/div><\/div>

\n\n
\n\t\t\"\"\n\t<\/div>\n\n<\/div><\/div><\/div><\/div>
\n
\n\t
    \n
  • A patient failing to provide a UDT may be concerning. If repeated attempts are made then the prescribing physician should be notified, with as much detail as you have, so that action can be considered.<\/li>\n<\/ul>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"

    While clinical administration does not need to be familiar with how to interpret UDT, they should be familiar with when to communicate to the prescriber either concerning automated interpretations on START-IT, or repeated failures to provide UDT. This section covers how clinical administration should respond to these concerning scenarios… Unexpected results: This section really only […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":615,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"manual-page.php","meta":{"_mi_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"_links":{"self":[{"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/pages\/367"}],"collection":[{"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=367"}],"version-history":[{"count":5,"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/pages\/367\/revisions"}],"predecessor-version":[{"id":463,"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/pages\/367\/revisions\/463"}],"up":[{"embeddable":true,"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=\/wp\/v2\/pages\/615"}],"wp:attachment":[{"href":"https:\/\/harmsprogram.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}