This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). 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
FHIR Infrastructure Work Group | Maturity Level: N/A | Ballot Status: Informative |
Definition for Code System NamingSystemType
{ "resourceType": "CodeSystem", "id": "namingsystem-type", "meta": { "lastUpdated": "2018-04-03T12:05:46.262+10:00" }, "text": { "status": "generated", "div": "<div>!-- Snipped for Brevity --></div>" }, "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode": "fhir" }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status", "valueString": "Trial Use" }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger": 1 } ], "url": "http://hl7.org/fhir/namingsystem-type", "identifier": { "system": "urn:ietf:rfc:3986", "value": "urn:oid:2.16.840.1.113883.4.642.1.491" }, "version": "3.3.0", "name": "NamingSystemType", "status": "draft", "experimental": false, "date": "2018-04-03T12:05:46+10:00", "publisher": "HL7 (FHIR Project)", "contact": [ { "telecom": [ { "system": "url", "value": "http://hl7.org/fhir" }, { "system": "email", "value": "fhir@lists.hl7.org" } ] } ], "description": "Identifies the purpose of the naming system.", "caseSensitive": true, "valueSet": "http://hl7.org/fhir/ValueSet/namingsystem-type", "content": "complete", "concept": [ { "code": "codesystem", "display": "Code System", "definition": "The naming system is used to define concepts and symbols to represent those concepts; e.g. UCUM, LOINC, NDC code, local lab codes, etc." }, { "code": "identifier", "display": "Identifier", "definition": "The naming system is used to manage identifiers (e.g. license numbers, order numbers, etc.)." }, { "code": "root", "display": "Root", "definition": "The naming system is used as the root for other identifiers and naming systems." } ] }
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.