Plandefinition-opioidcds-07 - FHIR v6.0.0-ballot2

FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example PlanDefinition/opioidcds-07 (Narrative)

Clinical Decision Support Work Group

Maturity Level: N/A

Standards Status: Informative

Compartments: No defined compartments

This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile PlanDefinition.

Generated Narrative: PlanDefinition opioidcds-07

StructureDefinition Work Group: cds

identifier: Uniform Resource Identifier (URI)/urn:oid:2.16.840.1.113883.4.642.11.6, cdc-opioid-guidance (use: official, )

version: 0.1.0

name: Cdcopioid07

title: CDC Opioid Prescribing Guideline Recommendation #7

type: ECA Rule

status: draft

date: 2018-03-19

publisher: HL7 International / Clinical Decision Support

contact: http://www.hl7.org/Special/committees/dss

description:

Clinicians should evaluate benefits and harms with patients within 1 to 4 weeks of starting opioid therapy for chronic pain or of dose escalation. Clinicians should evaluate benefits and harms of continued therapy with patients every 3 months or more frequently.

UseContexts

Code

Value[x]

UsageContextType focus: Clinical Focus

Medication requested (situation)

UsageContextType focus: Clinical Focus

Chronic pain (finding)

jurisdiction: United States of America

purpose:

CDC’s Guideline for Prescribing Opioids for Chronic Pain is intended to improve communication between providers and patients about the risks and benefits of opioid therapy for chronic pain, improve the safety and effectiveness of pain treatment, and reduce the risks associated with long-term opioid therapy, including opioid use disorder and overdose. The Guideline is not intended for patients who are in active cancer treatment, palliative care, or end-of-life care.

usage:

If benefits do not outweigh harms of continued opioid therapy, clinicians should optimize other therapies and work with patients to taper opioids to lower dosages or to taper and discontinue opioids.

copyright:

topic: Opioid Prescribing

author: Kensaku Kawamoto, MD, PhD, MHS: , Bryn Rhodes: , Floyd Eisenberg, MD, MPH: , Robert McClure, MD, MPH:

relatedArtifact
type: documentation
display: CDC guideline for prescribing opioids for chronic pain
Documents

- Url

* https://guidelines.gov/summaries/summary/50153/cdc-guideline-for-prescribing-opioids-for-chronic-pain---united-states-2016#420

relatedArtifact
type: documentation
display: MME Conversion Tables
Documents

- Url

* https://www.cdc.gov/drugoverdose/pdf/calculating_total_daily_dose-a.pdf

library: http://example.org/fhir/Library/opioidcds-recommendation-07

action
Strength of recommendation: Strong
Quality of evidence: Low quality
title: Existing patient should be evaluated for risk of continued opioid therapy.
description:

Checking if the trigger prescription meets the inclusion criteria for recommendation #7 workflow.

Documentations

- Type

* documentation
Triggers

- Type Name

* named-event medication-prescribe
condition
kind: applicability
Expressions

- Description Language Expression

* Check whether the existing patient, without an end of life condition or risk assessment in the past 90 days, has taken an opioid-with-abuse-potential for 7 of the past 10 days or 63 of the past 90 days. text/cql Inclusion Criteria
groupingBehavior: visual-group
selectionBehavior: exactly-one
dynamicValue
path: action.title
Expressions

- Language Expression

* text/cql Get Summary
dynamicValue
path: action.description
Expressions

- Language Expression

* text/cql Get Detail
dynamicValue
path: action.extension
Expressions

- Language Expression

* text/cql Get Indicator
Actions

- Description

*
Will schedule assessment of risk for opioid use for the patient

*
Risk of overdose carefully considered and outweighed by benefit; snooze 3 mo

*
N/A - see comment; snooze 3 mo

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.