This
page
is
part
of
the
FHIR
Specification
(v3.3.0:
(v3.5.0:
R4
Ballot
2).
#2).
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
| Clinical Decision Support Work Group | Maturity Level : N/A | Ballot Status : Informative | Compartments : Not linked to any defined compartments |
This
is
the
narrative
for
the
resource.
See
also
the
XML
or
,
JSON
or
Turtle
format.
This
example
conforms
to
the
profile
Library
.
Generated Narrative with Details
id : opioidcds-recommendation-07
identifier : OpioidCDS_REC_07 (OFFICIAL)
version : 0.1.0
title : Opioid CDS Logic for recommendation #7
status : active
experimental : false
type
:
Logic
Library
(Details
:
{http://hl7.org/fhir/library-type
{http://terminology.hl7.org/CodeSystem/library-type
code
'logic-library'
=
'Logic
Library',
given
as
'Logic
Library'})
date : 25/03/2018 1:49:09 PM
publisher : Centers for Disease Control and Prevention (CDC)
description : Opioid decision support logic to evaluate benefits and harms with patients within 1 to 4 weeks of starting opioid therapy and harms of continued therapy with patients every 3 months or more frequently.
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 been evaluated for benefits and harms within 1 to 4 weeks of starting opioid therapy and every 3 months or more subsequently.
usage : This library is used to notify the prescriber/user whether an evaluation for benefits and harms associated with opioid therapy is recommended for the patient.
copyright : © CDC 2016+.
topic : Opioid Prescribing (Details )
contributor
author
:
,
,
,
relatedArtifact : ,
dataRequirement : , , , ,
content :
Other examples that reference this example:
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.