STU 3 Ballot

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). 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 R3 R2

Valueset-approach-site-codes.xml

Raw XML (canonical form)

Definition for Value SetSNOMED CT Anatomical Structure for Administration Site Codes

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="approach-site-codes"/>
  <meta>
    <lastUpdated value="2016-08-11T17:02:54.322+10:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      
      <p>The value set to instantiate this attribute should be drawn from a terminologically robust
         code system that consists of or contains site of administration concepts.</p>
      
      <p>Possible sources include:</p>
      
      <ul>
        
        <li>SNOMED CT - selected children of SCTID:91723000 &quot;anatomical structure&quot; (note:
           there would need to be considerable selection 
          of concepts as the full child subset would be too big and too detailed for use)</li>
        
        <li>ISO 11239 - Intended site</li>
        
        <li>NCIt - selected children of NCIt concept C74444456 &quot;anatomical location&quot; (note:
           this is the SDTM location concepts; 
          it would also need subsetting to provide a useable set of medication administration)
          Note: to avoid confusion with other attributes in this resource concepts that
           are pre-coordinated with method and/or 
          route of administration (e.g.  &quot;rub into left hand&quot; where &quot;rub
           in&quot; is the method or &quot;IV into left subclavian vein&quot; where &quot;IV&quot;
           is the route) should not be used in this value set</li>
      
      </ul>
      
      <p>SNOMED CT is being used here as the example terminology.</p>
      
      <p>Note: to avoid confusion with other attributes in this resource concepts that are pre-coordinated
         with method and/or 
        route of administration (e.g.  &quot;rub into left hand&quot; where &quot;rub
         in&quot; is the method or &quot;IV into left subclavian vein&quot; where &quot;IV&quot;
         is the route) should not be used in this value set
      </p>
      
      <p>This value set includes content from SNOMED CT, which is copyright © 2002+ International
         Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement
         between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.</p>  
    
    </div>
  </text>
  <url value="http://hl7.org/fhir/ValueSet/approach-site-codes"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.2.189"/>
  </identifier>
  <version value="1.6.0"/>
  <name value="SNOMED CT Anatomical Structure for Administration Site Codes"/>
  <status value="draft"/>
  <experimental value="true"/>
  <publisher value="FHIR Project team"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <date value="2016-08-11T17:02:54+10:00"/>
  <description value="This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar."/>
  <copyright value="This value set includes content from SNOMED CT, which is copyright © 2002+ International
   Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement
   between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement."/>
  <compose>
    <include>
      <system value="http://snomed.info/sct"/>
      <filter>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="91723000"/>
      </filter>
    </include>
  </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.