2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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

6.24.4 Resource NamingSystem - Examples

Example Index:

Example of namingsystemXMLJSON

6.24.4.1 General

XML

Example of namingsystem (id = "example")

Raw XML

<NamingSystem xmlns="http://hl7.org/fhir">
  <id value="example"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <type value="codesystem"/>
  <name value="SNOMED CT"/>
  <date value="2014-12-13"/>
  <status value="active"/>
  <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"/>
  </uniqueId>
</NamingSystem>

JSON

Example of namingsystem

Raw JSON (Canonical)

{
  "resourceType": "NamingSystem",
  "id": "example",
  "text": {
    "status": "generated",
    "div": "<div>!-- Snipped for Brevity --></div>"
  },
  "type": "codesystem",
  "name": "SNOMED CT",
  "date": "2014-12-13",
  "status": "active",
  "description": "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 \"semantic drift\" 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 \"fully-specified name\", a preferred term, and, optionally, synonyms.  The description languages include English and Spanish.",
  "uniqueId": [
    {
      "type": "oid",
      "value": "2.16.840.1.113883.6.96"
    },
    {
      "type": "uri",
      "value": "http://snomed.info/sct"
    }
  ]
}

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.