FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example NamingSystem/example (XML)

Terminology Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

Example of how to use Naming System for a code system (id = "example")

<?xml version="1.0" encoding="UTF-8"?>

<NamingSystem xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <text> 
    <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">
      
      
      <p> 
        
        <b> SNOMED CT</b> 
      
      </p> 
      
      
      <p>  oid: 2.16.840.1.113883.6.96</p> 
      
      
      <p>  uri: http://snomed.info/sct</p> 
    
    
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="vocab"/> 
  </extension> 
  <url value="http://hl7.org/fhir/NamingSystem/example"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.22.1"/> 
  </identifier> 
  <name value="SNOMEDCT"/> 
  <title value="SNOMED CT"/> 
  <status value="active"/> 
  <kind value="codesystem"/> 
  <date value="2014-12-13"/> 
  <publisher value="HL7 International / Terminology Infrastructure"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://www.hl7.org/Special/committees/Vocab"/> 
    </telecom> 
  </contact> 
  <responsible value="IHTSDO &amp; affiliates"/> 
  <description value="SNOMED CT is a concept-based, scientifically validated terminology that provides
   a unique and permanent concept identifier that can be included in multiple HL7
   data types including CD and CE.  The concepts are managed to avoid &quot;semantic
   drift&quot; so the meaning remains constant.  If the concept is found to be ambiguous
   or the meaning changes, the concept is inactivated but still retained and the identifier
   is never reused.    SNOMED CT's concepts are interrelated hierarchically and using
   description logic.    SNOMED CT concepts have a unique &quot;fully-specified name&quot;,
   a preferred term, and, optionally, synonyms.  The description languages include
   English and Spanish."/> 
  <uniqueId> 
    <type value="oid"/> 
    <value value="2.16.840.1.113883.6.96"/> 
  </uniqueId> 
  <uniqueId> 
    <type value="uri"/> 
    <value value="http://snomed.info/sct"/> 
    <preferred value="true"/> 
  </uniqueId> 
</NamingSystem> 

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.