Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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-omtk-logic

Clinical Decision Support Work Group

Maturity Level: N/A

Standards Status: Informative

Compartments: 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: omtk-logic

identifier: OMTKLogic (OFFICIAL)

version: 0.1.0

title: OMTK Logic

status: active

experimental: true

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

date: 05/05/2017

publisher: Centers for Disease Control and Prevention (CDC)

description: Opioid Management Terminology Knowledge Base Logic for use in implementing CDC Opioid Prescribing Guidelines.

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: This library normalizes units to UCUM units, identifies the conversion factor for the given ingredient, identifies the non-surgical opioid ingredients and their strengths that make up a drug identified by the given rxNormCode, calculates daily dose for a specific ingredient based on the ingredient strength, dose form, dose quantity, and daily frequency, calculates daily frequency given frequency within a period, and calculates the Morphine Milligram Equivalency (MME) for a given prescription.

usage: This library is used to gather information about an opioid prescription necessary to offer opioid management guidance for a patient.

topic: Opioid Prescribing (Details )

author: , , ,

relatedArtifact: , ,

content: ,

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.