18.02.2017 Views

VA/DoD CLINICAL PRACTICE GUIDELINE FOR OPIOID THERAPY FOR CHRONIC PAIN

2lfFhbO

2lfFhbO

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>VA</strong>/<strong>DoD</strong> Clinical Practice Guideline for Opioid Therapy for Chronic Pain<br />

planning. More frequent follow-up of patients on LOT can affect access to care for all empaneled patients.<br />

VHA providers must also follow VHA policy regarding education and signature informed consent when<br />

providing LOT for patients with non-cancer pain.[101]<br />

Written Informed Consent and Opioid Treatment Agreements<br />

There is a paradigm shift occurring in approaches to ensuring and documenting patient and provider<br />

understanding and expectations regarding the risks and benefits of LOT. The 2010 OT CPG reflected prior<br />

practice of using opioid treatment (or pain care) agreements. OTAs have been described as coercive rather<br />

than therapeutic, lack respect for individual autonomy, can be a barrier to pain care, and may be harmful<br />

to the patient-provider relationship.[102-105]<br />

Given the recognized risks of opioid therapy, an optimal approach to care should include a robust,<br />

signature informed consent process that is patient-centered and provides patients with information about<br />

known benefits and harms of OT and treatment alternatives. In 2014, <strong>VA</strong> established a requirement for<br />

signature informed consent, consistent with <strong>VA</strong> policy for other treatments or procedures with a<br />

significant risk of complications or morbidity. See Appendix A, Taking Opioids Responsibly for Your Safety<br />

and the Safety of Others: Patient Information Guide on Long-term Opioid Therapy for Chronic Pain (found<br />

at<br />

http://www.healthquality.va.gov/guidelines/Pain/cot/OpiodTheraphyforChronicPainPatientTool20May20<br />

13print.pdf), and 38 C.F.R. §17.32 (2012).<br />

Patients may decline offered treatments (e.g., OT) and may also decline risk mitigation strategies (e.g.,<br />

UDT, pill counts) that are recommended in the course of clinical care. However, providers should discuss<br />

this decision with the patient, including the likelihood that their decision may result in the risks of LOT<br />

outweighing its potential benefits. This would require a consideration of patient’s safety, and a clinical<br />

decision may be made not to initiate OT or to discontinue ongoing OT through tapering (see<br />

Recommendation 14 and Recommendation 17).<br />

State Prescription Drug Monitoring Programs<br />

State database queries for detection of multi-sourcing of controlled substances are used throughout the<br />

country. Data comparing states with an implemented state database program to states without one<br />

showed 1.55 fewer deaths per 100,000 people.[106] The CDC currently recommends at least quarterly<br />

checks of the state database system.[33]<br />

Urine Drug Testing and Confirmatory Testing<br />

As substance misuse in patients on LOT is more than 30% in some series,[107] UDT and confirmatory<br />

testing is used as an additional method of examining for patient substance misuse and adherence to the<br />

prescribed regimen. UDTs, used in the appropriate way, help to address safety, fairness, and trust with OT.<br />

Availability of accurate and timely confirmatory testing (e.g., gas chromatography-mass spectrometry<br />

[GCMS]) is critical due to the false positive and negative rates associated with UDTs.[53] Interpretation of a<br />

UDT and confirmatory results requires education and knowledge of the local procedures and clinical<br />

scenario. Local education and access to expert interpretation is necessary.<br />

UDT results are helpful and can help identify active SUD or possible diversion. Accordingly, clinicians should<br />

February 2017 Page 47 of 192

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!