Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

Library-opioidcds-recommendation-10

Clinical Decision Support Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

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

Generated Narrative with Details

id: opioidcds-recommendation-10

identifier: OpioidCDS_REC_10 (OFFICIAL)

version: 0.1.0

title: Opioid CDS Logic for recommendation #10

status: active

experimental: false

type: Logic Library (Details : {http://terminology.hl7.org/CodeSystem/library-type code 'logic-library' = 'Logic Library', given as 'Logic Library'})

date: 25 Mar. 2018, 1:49:09 pm

publisher: Centers for Disease Control and Prevention (CDC)

description: Opioid decision support logic to evaluate whether the patient has had a urine screening in the past 12 months and provide analysis.

useContext: ,

jurisdiction: United States of America (Details : {urn:iso:std:iso:3166 code 'US' = 'United States of America', given as 'United States of America'})

purpose: The purpose of this library is to determine whether the patient has had a urine screening in the past 12 months. Is so, then check the results for missing opioids that are prescribed, present opioids that aren't prescribed or present illicit drugs.

usage: This library is used to notify the prescriber/user whether the patient has had a urine screening in the past 12 months and to provide analysis if true.

copyright: © CDC 2016+.

topic: Opioid Prescribing (Details )

author: , , ,

relatedArtifact: ,

dataRequirement: , , ,

content:

 

Other examples that reference this example:

  • PlanDefinition/OpioidCDSRecommendation10

    •  

    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.