2022 CDC Clinical Practice Guideline for Prescribing Opioids Implementation Guide, published by CDC / Security Risk Solutions, Inc. (SRS). This guide is not an authorized publication; it is the continuous build for version 2022.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/security-rs/opioid-cds-r4/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

ValueSet: Synthetic opioid medications

Official URL: http://fhir.org/guides/cdc/opioid-cds/ValueSet/synthetic-opioid-medications				Version: 2022.1.1
Active as of 2023-05-25				Computable Name: SYNTHETIC_OPIOID_MEDICATIONS
Other Identifiers: OID:2.16.840.1.114222.48.41
Copyright/Legal: © CDC 2016+.

Opioid medications that are not exclusively and solely derived from the opium plant. These are synthetic or semisynthetic opioids.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This ValueSet does not have a formal definition; instead, the value set must be prepared by hand using these instructions.

https://mor.nlm.nih.gov/RxMix/ Script: Step 1a Create Batch text input file (SCT-Synthetic-Opioids.txt) with following SCT identifier (for the concept "Product containing opioid receptor agonist (product)") as an input within the file: 360204007

Step 1b Submit batch job using the above SCT-Synthetic-Opioids.txt file to following workflow by uploading file (SCT-Synthetic-Opioid-wf.config) with the following in the file: <WFE><filteredOutputs>RXCUI|name|term_type</filteredOutputs><input>NOINPUT</input><FS><service>NOINPUT</service><function>findClassById</function><level>0</level><paramSize>1</paramSize><param order ='0'>?</param></FS><FS><service>NOINPUT</service><function>getClassMembers</function><level>1</level><paramSize>5</paramSize><param order ='0'>?</param><param order ='1'>SNOMEDCT</param><param order ='2'>isa_disposition</param><param order ='3'>0</param><param order ='4'>IN,MIN,PIN</param></FS><FS><service>NOINPUT</service><function>getRelatedByType</function><level>2</level><paramSize>2</paramSize><param order ='0'>?</param><param order ='1'>BPCK,GPCK,SBD,SCD</param></FS></WFE> This will produce a result file with all Opioid clinical drugs included

Step 2 To remove all cough and bowel transit formulation codes and to remove the injectable codes filter out all codes with the following strings: Ingredient strings: Guaifenesin, Chlorpheniramine, Pseudoephedrine, Brompheniramine, Phenylephrine, Phenylpropanolamine, Promethazine, Bromodiphenhydramine, guaiacolsulfonate, homatropine Form strings: inject, cartridge, syringe

Step 2a To remove all non-synthetic opioid codes filter out all codes with the following strings:: Ingredient strings: codeine, morphine, opium

 

Expansion

---

Explanation of the columns that may appear on this page:

Level	A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System	The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code	The code (used as the code in the resource instance)
Display	The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition	An explanation of the meaning of the concept
Comments	Additional notes about how to use the code