Release 4

Namingsystem-example.xml

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any 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> 
  <name value="SNOMED CT"/> 
  <status value="active"/> 
  <kind value="codesystem"/> 
  <date value="2014-12-13"/> 
  <publisher value="HL7 International on behalf of IHTSDO"/> 
  <contact> 
    <name value="FHIR project team"/> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </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.