STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Daf\valueset-daf-substance-rxnorm.xml

Raw XML (canonical form)

Definition for Value SetDAF Substance RxNorm Codes

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="daf-substance-rxnorm"/>
  <meta>
    <lastUpdated value="2016-03-31T08:01:25.570+11:00"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>DAF Substance RxNorm Codes</h2>
      <p>All RxNorm codes that have TTY = IN,PIN,MIN,BN, but TTY != OCD.</p>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include codes from http://www.nlm.nih.gov/research/umls/rxnorm where TTY  in  IN,PIN,MIN,BN</li>
        <li>Exclude codes from http://www.nlm.nih.gov/research/umls/rxnorm where TTY  =  OCD</li>
      </ul>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113762.1.4.1010.7"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/daf-substance-rxnorm"/>
  <name value="DAF Substance RxNorm Codes"/>
  <status value="draft"/>
  <publisher value="FHIR Project team"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <description value="All RxNorm codes that have TTY = IN,PIN,MIN,BN, but TTY != OCD."/>
  <compose>
    <include>
      <system value="http://www.nlm.nih.gov/research/umls/rxnorm"/>
      <filter>
        <property value="TTY"/>
        <op value="in"/>
        <value value="IN,PIN,MIN,BN"/>
      </filter>
    </include>
    <exclude>
      <system value="http://www.nlm.nih.gov/research/umls/rxnorm"/>
      <filter>
        <property value="TTY"/>
        <op value="="/>
        <value value="OCD"/>
      </filter>
    </exclude>
  </compose>
</ValueSet>

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.