This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Definition for Value SetSNOMED CT Anatomical Structure for Administration Site Codes
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="approach-site-codes"/> <meta> <lastUpdated value="2022-05-28T12:47:40.239+10:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </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 "anatomical structure" (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 "anatomical location" (note: this is the SDTM location concepts; it would also need subsetting to provide a usable 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. "rub into left hand" where "rub in" is the method or "IV into left subclavian vein" where "IV" 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. "rub into left hand" where "rub in" is the method or "IV into left subclavian vein" where "IV" is the route) should not be used in this value set </p> <p> This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org</p> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="fhir"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="draft"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension> <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.3.346"/> </identifier> <version value="4.3.0"/> <name value="SNOMEDCTAnatomicalStructureForAdministrationSiteCodes"/> <title value="SNOMED CT Anatomical Structure for Administration Site Codes"/> <status value="draft"/> <experimental value="true"/> <publisher value="FHIR Project team"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> </contact> <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.