Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). 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

4.11 Resource NamingSystem - Content

FHIR Infrastructure Work GroupMaturity Level: 1 Trial UseSecurity Category: Anonymous Compartments: Not linked to any defined compartments

A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types.

4.11.1 Scope and Usage

Defines a specific code system or identifier system, so that it can be noted in a registry for other systems to find and understand an identifier.

4.11.2 Boundaries and Relationships

The CodeSystem resource defines the content of a code system, and also its preferred identifier. The NamingSystem resource identifies the existence of a code or identifier system, and its possible and preferred identifiers. The key difference between the resources is who creates and manages them - CodeSystem resources are managed by the owner of the code system resource, who can properly define the features and content of the code system. NamingSystem resources, on the other hand, are frequently defined by 3rd parties that encounter the code system in use, and need to describe the use, but do not have the authority to define the features and content. Additionally, there may be multiple authoritative NamingSystem resources for a code system, but there should only be one CodeSystem resource.

4.11.3 Background and Context

For discussion of policy for creating well maintained OIDs and URIs for resources, see The HL7 Confluence site .

4.11.4 References

No resources refer to this resource directly.

This resource does not implement any patterns.

4.11.5 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. NamingSystem TUCanonicalResourceSystem of unique identification
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
+ Rule: Root systems cannot have uuid identifiers
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension, url, identifier, version, name, title, status, experimental, date, publisher, contact, description, useContext, jurisdiction, purpose, copyright
... url Σ0..1uriCanonical identifier for this naming system, represented as a URI (globally unique)
... version Σ0..1stringBusiness version of the naming system
... name ΣI1..1stringName for this naming system (computer friendly)
... status ?!Σ1..1codedraft | active | retired | unknown
PublicationStatus (Required)
... kind Σ1..1codecodesystem | identifier | root
NamingSystemType (Required)
... date Σ1..1dateTimeDate last changed
... publisher Σ0..1stringName of the publisher (organization or individual)
... contact Σ0..*ContactDetailContact details for the publisher
... responsible 0..1stringWho maintains system namespace?
... type 0..1CodeableConcepte.g. driver, provider, patient, bank etc.
IdentifierType (Extensible)
... description 0..1markdownNatural language description of the naming system
... useContext Σ0..*UsageContextThe context that the content is intended to support
... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for naming system (if applicable)
Jurisdiction (Extensible)
... usage 0..1stringHow/where is it used
... uniqueId Σ1..*BackboneElementUnique identifiers used for system
.... type Σ1..1codeoid | uuid | uri | v2csmnemonic | other
NamingSystemIdentifierType (Required)
.... value Σ1..1stringThe unique identifier
.... preferred I0..1booleanIs this the id that should be used for this type
+ Rule: Can't have more than one preferred identifier for a type
.... comment 0..1stringNotes about identifier usage
.... period 0..1PeriodWhen is identifier valid?
.... authoritative I0..1booleanWhether the identifier is authoritative
+ Rule: Can't have more than one authoritative identifier for a type/period combination (only one authoritative identifier allowed at any given point of time)

doco Documentation for this format

UML Diagram (Legend)

NamingSystem (CanonicalResource)An absolute URI that is used to identify this naming system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this naming system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the naming system is stored on different serversurl : uri [0..1]The identifier that is used to identify this version of the naming system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the naming system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequenceversion : string [0..1]A natural language name identifying the naming system. This name should be usable as an identifier for the module by machine processing applications such as code generationname : string [1..1]A short, descriptive, user-friendly title for the naming systemtitle : string [0..1]The status of this naming system. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements)status : code [1..1] « null (Strength=Required)PublicationStatus! »Indicates the purpose for the naming system - what kinds of things does it make unique?kind : code [1..1] « null (Strength=Required)NamingSystemType! »The date (and optionally time) when the naming system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the naming system changesdate : dateTime [1..1]The name of the organization or individual that published the naming systempublisher : string [0..1]Contact details to assist a user in finding and communicating with the publishercontact : ContactDetail [0..*]The name of the organization that is responsible for issuing identifiers or codes for this namespace and ensuring their non-collisionresponsible : string [0..1]Categorizes a naming system for easier search by grouping related naming systemstype : CodeableConcept [0..1] « null (Strength=Extensible)Identifier Type + »A free text natural language description of the naming system from a consumer's perspective. Details about what the namespace identifies including scope, granularity, version labeling, etcdescription : markdown [0..1]The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instancesuseContext : UsageContext [0..*]A legal or geographic region in which the naming system is intended to be usedjurisdiction : CodeableConcept [0..*] « null (Strength=Extensible)Jurisdiction ValueSet+ »Provides guidance on the use of the namespace, including the handling of formatting characters, use of upper vs. lower case, etcusage : string [0..1]UniqueIdIdentifies the unique identifier scheme used for this particular identifiertype : code [1..1] « null (Strength=Required)NamingSystemIdentifierType! »The string that should be sent over the wire to identify the code system or identifier systemvalue : string [1..1]Indicates whether this identifier is the "preferred" identifier of this typepreferred : boolean [0..1]Notes about the past or intended usage of this identifiercomment : string [0..1]Identifies the period of time over which this identifier is considered appropriate to refer to the naming system. Outside of this window, the identifier might be non-deterministicperiod : Period [0..1]Indicates whether this identifier ie endorsed by the official owner of the associated naming systemauthoritative : boolean [0..1]Indicates how the system may be identified when referenced in electronic exchangeuniqueId[1..*]

XML Template

<NamingSystem xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <url value="[uri]"/><!-- 0..1 Canonical identifier for this naming system, represented as a URI (globally unique) -->
 <version value="[string]"/><!-- 0..1 Business version of the naming system -->
 <name value="[string]"/><!-- ?? 1..1 Name for this naming system (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Title for this naming system (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <kind value="[code]"/><!-- 1..1 codesystem | identifier | root -->
 <date value="[dateTime]"/><!-- 1..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <responsible value="[string]"/><!-- 0..1 Who maintains system namespace? -->
 <type><!-- 0..1 CodeableConcept e.g. driver,  provider,  patient, bank etc. --></type>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the naming system -->
 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for naming system (if applicable) --></jurisdiction>
 <usage value="[string]"/><!-- 0..1 How/where is it used -->
 <uniqueId>  <!-- 1..* Unique identifiers used for system -->
  <type value="[code]"/><!-- 1..1 oid | uuid | uri | v2csmnemonic | other -->
  <value value="[string]"/><!-- 1..1 The unique identifier -->
  <preferred value="[boolean]"/><!-- 0..1 Is this the id that should be used for this type -->
  <comment value="[string]"/><!-- 0..1 Notes about identifier usage -->
  <period><!-- 0..1 Period When is identifier valid? --></period>
  <authoritative value="[boolean]"/><!-- 0..1 Whether the identifier is authoritative -->
 </uniqueId>
</NamingSystem>

JSON Template

{doco
  "resourceType" : "NamingSystem",
  // from Resource: id, meta, implicitRules, and language
  "url" : "<uri>", // Canonical identifier for this naming system, represented as a URI (globally unique)
  "version" : "<string>", // Business version of the naming system
  "name" : "<string>", // C? R!  Name for this naming system (computer friendly)
  "title" : "<string>", // Title for this naming system (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "kind" : "<code>", // R!  codesystem | identifier | root
  "date" : "<dateTime>", // R!  Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "responsible" : "<string>", // Who maintains system namespace?
  "type" : { CodeableConcept }, // e.g. driver,  provider,  patient, bank etc.
  "description" : "<markdown>", // Natural language description of the naming system
  "useContext" : [{ UsageContext }], // The context that the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for naming system (if applicable)
  "usage" : "<string>", // How/where is it used
  "uniqueId" : [{ // R!  Unique identifiers used for system
    "type" : "<code>", // R!  oid | uuid | uri | v2csmnemonic | other
    "value" : "<string>", // R!  The unique identifier
    "preferred" : <boolean>, // Is this the id that should be used for this type
    "comment" : "<string>", // Notes about identifier usage
    "period" : { Period }, // When is identifier valid?
    "authoritative" : <boolean> // Whether the identifier is authoritative
  }]
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:NamingSystem;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  fhir:NamingSystem.url [ uri ]; # 0..1 Canonical identifier for this naming system, represented as a URI (globally unique)
  fhir:NamingSystem.version [ string ]; # 0..1 Business version of the naming system
  fhir:NamingSystem.name [ string ]; # 1..1 Name for this naming system (computer friendly)
  fhir:NamingSystem.title [ string ]; # 0..1 Title for this naming system (human friendly)
  fhir:NamingSystem.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:NamingSystem.kind [ code ]; # 1..1 codesystem | identifier | root
  fhir:NamingSystem.date [ dateTime ]; # 1..1 Date last changed
  fhir:NamingSystem.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:NamingSystem.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:NamingSystem.responsible [ string ]; # 0..1 Who maintains system namespace?
  fhir:NamingSystem.type [ CodeableConcept ]; # 0..1 e.g. driver,  provider,  patient, bank etc.
  fhir:NamingSystem.description [ markdown ]; # 0..1 Natural language description of the naming system
  fhir:NamingSystem.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support
  fhir:NamingSystem.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for naming system (if applicable)
  fhir:NamingSystem.usage [ string ]; # 0..1 How/where is it used
  fhir:NamingSystem.uniqueId [ # 1..* Unique identifiers used for system
    fhir:NamingSystem.uniqueId.type [ code ]; # 1..1 oid | uuid | uri | v2csmnemonic | other
    fhir:NamingSystem.uniqueId.value [ string ]; # 1..1 The unique identifier
    fhir:NamingSystem.uniqueId.preferred [ boolean ]; # 0..1 Is this the id that should be used for this type
    fhir:NamingSystem.uniqueId.comment [ string ]; # 0..1 Notes about identifier usage
    fhir:NamingSystem.uniqueId.period [ Period ]; # 0..1 When is identifier valid?
    fhir:NamingSystem.uniqueId.authoritative [ boolean ]; # 0..1 Whether the identifier is authoritative
  ], ...;
]

Changes since R3

NamingSystem
NamingSystem.url
  • Added Element
NamingSystem.version
  • Added Element
NamingSystem.title
  • Added Element
NamingSystem.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status|4.0.0 to http://hl7.org/fhir/ValueSet/publication-status|4.6.0
NamingSystem.kind
  • Change value set from http://hl7.org/fhir/ValueSet/namingsystem-type|4.0.0 to http://hl7.org/fhir/ValueSet/namingsystem-type|4.6.0
NamingSystem.uniqueId.type
  • Change value set from http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.0.0 to http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.6.0
NamingSystem.uniqueId.authoritative
  • Added Element

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 3 tests that all execute ok. 1 fail round-trip testing and 3 r3 resources are invalid (0 errors).)

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. NamingSystem TUCanonicalResourceSystem of unique identification
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
+ Rule: Root systems cannot have uuid identifiers
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension, url, identifier, version, name, title, status, experimental, date, publisher, contact, description, useContext, jurisdiction, purpose, copyright
... url Σ0..1uriCanonical identifier for this naming system, represented as a URI (globally unique)
... version Σ0..1stringBusiness version of the naming system
... name ΣI1..1stringName for this naming system (computer friendly)
... status ?!Σ1..1codedraft | active | retired | unknown
PublicationStatus (Required)
... kind Σ1..1codecodesystem | identifier | root
NamingSystemType (Required)
... date Σ1..1dateTimeDate last changed
... publisher Σ0..1stringName of the publisher (organization or individual)
... contact Σ0..*ContactDetailContact details for the publisher
... responsible 0..1stringWho maintains system namespace?
... type 0..1CodeableConcepte.g. driver, provider, patient, bank etc.
IdentifierType (Extensible)
... description 0..1markdownNatural language description of the naming system
... useContext Σ0..*UsageContextThe context that the content is intended to support
... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for naming system (if applicable)
Jurisdiction (Extensible)
... usage 0..1stringHow/where is it used
... uniqueId Σ1..*BackboneElementUnique identifiers used for system
.... type Σ1..1codeoid | uuid | uri | v2csmnemonic | other
NamingSystemIdentifierType (Required)
.... value Σ1..1stringThe unique identifier
.... preferred I0..1booleanIs this the id that should be used for this type
+ Rule: Can't have more than one preferred identifier for a type
.... comment 0..1stringNotes about identifier usage
.... period 0..1PeriodWhen is identifier valid?
.... authoritative I0..1booleanWhether the identifier is authoritative
+ Rule: Can't have more than one authoritative identifier for a type/period combination (only one authoritative identifier allowed at any given point of time)

doco Documentation for this format

UML Diagram (Legend)

NamingSystem (CanonicalResource)An absolute URI that is used to identify this naming system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this naming system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the naming system is stored on different serversurl : uri [0..1]The identifier that is used to identify this version of the naming system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the naming system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequenceversion : string [0..1]A natural language name identifying the naming system. This name should be usable as an identifier for the module by machine processing applications such as code generationname : string [1..1]A short, descriptive, user-friendly title for the naming systemtitle : string [0..1]The status of this naming system. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements)status : code [1..1] « null (Strength=Required)PublicationStatus! »Indicates the purpose for the naming system - what kinds of things does it make unique?kind : code [1..1] « null (Strength=Required)NamingSystemType! »The date (and optionally time) when the naming system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the naming system changesdate : dateTime [1..1]The name of the organization or individual that published the naming systempublisher : string [0..1]Contact details to assist a user in finding and communicating with the publishercontact : ContactDetail [0..*]The name of the organization that is responsible for issuing identifiers or codes for this namespace and ensuring their non-collisionresponsible : string [0..1]Categorizes a naming system for easier search by grouping related naming systemstype : CodeableConcept [0..1] « null (Strength=Extensible)Identifier Type + »A free text natural language description of the naming system from a consumer's perspective. Details about what the namespace identifies including scope, granularity, version labeling, etcdescription : markdown [0..1]The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instancesuseContext : UsageContext [0..*]A legal or geographic region in which the naming system is intended to be usedjurisdiction : CodeableConcept [0..*] « null (Strength=Extensible)Jurisdiction ValueSet+ »Provides guidance on the use of the namespace, including the handling of formatting characters, use of upper vs. lower case, etcusage : string [0..1]UniqueIdIdentifies the unique identifier scheme used for this particular identifiertype : code [1..1] « null (Strength=Required)NamingSystemIdentifierType! »The string that should be sent over the wire to identify the code system or identifier systemvalue : string [1..1]Indicates whether this identifier is the "preferred" identifier of this typepreferred : boolean [0..1]Notes about the past or intended usage of this identifiercomment : string [0..1]Identifies the period of time over which this identifier is considered appropriate to refer to the naming system. Outside of this window, the identifier might be non-deterministicperiod : Period [0..1]Indicates whether this identifier ie endorsed by the official owner of the associated naming systemauthoritative : boolean [0..1]Indicates how the system may be identified when referenced in electronic exchangeuniqueId[1..*]

XML Template

<NamingSystem xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <url value="[uri]"/><!-- 0..1 Canonical identifier for this naming system, represented as a URI (globally unique) -->
 <version value="[string]"/><!-- 0..1 Business version of the naming system -->
 <name value="[string]"/><!-- ?? 1..1 Name for this naming system (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Title for this naming system (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <kind value="[code]"/><!-- 1..1 codesystem | identifier | root -->
 <date value="[dateTime]"/><!-- 1..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <responsible value="[string]"/><!-- 0..1 Who maintains system namespace? -->
 <type><!-- 0..1 CodeableConcept e.g. driver,  provider,  patient, bank etc. --></type>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the naming system -->
 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for naming system (if applicable) --></jurisdiction>
 <usage value="[string]"/><!-- 0..1 How/where is it used -->
 <uniqueId>  <!-- 1..* Unique identifiers used for system -->
  <type value="[code]"/><!-- 1..1 oid | uuid | uri | v2csmnemonic | other -->
  <value value="[string]"/><!-- 1..1 The unique identifier -->
  <preferred value="[boolean]"/><!-- 0..1 Is this the id that should be used for this type -->
  <comment value="[string]"/><!-- 0..1 Notes about identifier usage -->
  <period><!-- 0..1 Period When is identifier valid? --></period>
  <authoritative value="[boolean]"/><!-- 0..1 Whether the identifier is authoritative -->
 </uniqueId>
</NamingSystem>

JSON Template

{doco
  "resourceType" : "NamingSystem",
  // from Resource: id, meta, implicitRules, and language
  "url" : "<uri>", // Canonical identifier for this naming system, represented as a URI (globally unique)
  "version" : "<string>", // Business version of the naming system
  "name" : "<string>", // C? R!  Name for this naming system (computer friendly)
  "title" : "<string>", // Title for this naming system (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "kind" : "<code>", // R!  codesystem | identifier | root
  "date" : "<dateTime>", // R!  Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "responsible" : "<string>", // Who maintains system namespace?
  "type" : { CodeableConcept }, // e.g. driver,  provider,  patient, bank etc.
  "description" : "<markdown>", // Natural language description of the naming system
  "useContext" : [{ UsageContext }], // The context that the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for naming system (if applicable)
  "usage" : "<string>", // How/where is it used
  "uniqueId" : [{ // R!  Unique identifiers used for system
    "type" : "<code>", // R!  oid | uuid | uri | v2csmnemonic | other
    "value" : "<string>", // R!  The unique identifier
    "preferred" : <boolean>, // Is this the id that should be used for this type
    "comment" : "<string>", // Notes about identifier usage
    "period" : { Period }, // When is identifier valid?
    "authoritative" : <boolean> // Whether the identifier is authoritative
  }]
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:NamingSystem;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  fhir:NamingSystem.url [ uri ]; # 0..1 Canonical identifier for this naming system, represented as a URI (globally unique)
  fhir:NamingSystem.version [ string ]; # 0..1 Business version of the naming system
  fhir:NamingSystem.name [ string ]; # 1..1 Name for this naming system (computer friendly)
  fhir:NamingSystem.title [ string ]; # 0..1 Title for this naming system (human friendly)
  fhir:NamingSystem.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:NamingSystem.kind [ code ]; # 1..1 codesystem | identifier | root
  fhir:NamingSystem.date [ dateTime ]; # 1..1 Date last changed
  fhir:NamingSystem.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:NamingSystem.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:NamingSystem.responsible [ string ]; # 0..1 Who maintains system namespace?
  fhir:NamingSystem.type [ CodeableConcept ]; # 0..1 e.g. driver,  provider,  patient, bank etc.
  fhir:NamingSystem.description [ markdown ]; # 0..1 Natural language description of the naming system
  fhir:NamingSystem.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support
  fhir:NamingSystem.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for naming system (if applicable)
  fhir:NamingSystem.usage [ string ]; # 0..1 How/where is it used
  fhir:NamingSystem.uniqueId [ # 1..* Unique identifiers used for system
    fhir:NamingSystem.uniqueId.type [ code ]; # 1..1 oid | uuid | uri | v2csmnemonic | other
    fhir:NamingSystem.uniqueId.value [ string ]; # 1..1 The unique identifier
    fhir:NamingSystem.uniqueId.preferred [ boolean ]; # 0..1 Is this the id that should be used for this type
    fhir:NamingSystem.uniqueId.comment [ string ]; # 0..1 Notes about identifier usage
    fhir:NamingSystem.uniqueId.period [ Period ]; # 0..1 When is identifier valid?
    fhir:NamingSystem.uniqueId.authoritative [ boolean ]; # 0..1 Whether the identifier is authoritative
  ], ...;
]

Changes since Release 3

NamingSystem
NamingSystem.url
  • Added Element
NamingSystem.version
  • Added Element
NamingSystem.title
  • Added Element
NamingSystem.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status|4.0.0 to http://hl7.org/fhir/ValueSet/publication-status|4.6.0
NamingSystem.kind
  • Change value set from http://hl7.org/fhir/ValueSet/namingsystem-type|4.0.0 to http://hl7.org/fhir/ValueSet/namingsystem-type|4.6.0
NamingSystem.uniqueId.type
  • Change value set from http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.0.0 to http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.6.0
NamingSystem.uniqueId.authoritative
  • Added Element

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 3 tests that all execute ok. 1 fail round-trip testing and 3 r3 resources are invalid (0 errors).)

 

See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) , the spreadsheet version & the dependency analysis a

4.11.5.1 Terminology Bindings

PathDefinitionTypeReference
NamingSystem.status RequiredPublicationStatus
NamingSystem.kind RequiredNamingSystemType
NamingSystem.type ExtensibleIdentifier Type Codes
NamingSystem.jurisdiction ExtensibleJurisdiction ValueSet
NamingSystem.uniqueId.type RequiredNamingSystemIdentifierType

4.11.5.2 Constraints

idLevelLocationDescriptionExpression
cnl-0Warning (base)Name should be usable as an identifier for the module by machine processing applications such as code generationname.matches('[A-Z]([A-Za-z0-9_]){0,254}')
nsd-1Rule (base)Root systems cannot have uuid identifierskind != 'root' or uniqueId.all(type != 'uuid')
nsd-2Rule NamingSystem.uniqueId.preferredCan't have more than one preferred identifier for a typeuniqueId.where(preferred = true).select(type).isDistinct()
nsd-3Rule NamingSystem.uniqueId.authoritativeCan't have more than one authoritative identifier for a type/period combination (only one authoritative identifier allowed at any given point of time)uniqueId.where(authoritative = true).select(type).isDistinct().select(period).isDistinct()

4.11.5.3 Dealing with duplicate entries

In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or knows the same concept with a different name. If this occurs, one of the system entries should be deleted and the remaining entry should have its uniqueId updated to include any identifiers present on the original entry (and possibly have its descriptive information modified to include additional information from the duplicate entry).

4.11.6 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionExpressionIn Common
contact NstringName of an individual to contactNamingSystem.contact.name
contexttokenA use context assigned to the naming system(NamingSystem.useContext.value as CodeableConcept)
context-quantityquantityA quantity- or range-valued use context assigned to the naming system(NamingSystem.useContext.value as Quantity) | (NamingSystem.useContext.value as Range)
context-typetokenA type of use context assigned to the naming systemNamingSystem.useContext.code
context-type-quantitycompositeA use context type and quantity- or range-based value assigned to the naming systemOn NamingSystem.useContext:
  context-type: code
  context-quantity: value.as(Quantity) | value.as(Range)
context-type-valuecompositeA use context type and value assigned to the naming systemOn NamingSystem.useContext:
  context-type: code
  context: value.as(CodeableConcept)
date NdateThe naming system publication dateNamingSystem.date
description NstringThe description of the naming systemNamingSystem.description
id-type Ntokenoid | uuid | uri | otherNamingSystem.uniqueId.type
jurisdictiontokenIntended jurisdiction for the naming systemNamingSystem.jurisdiction
kind Ntokencodesystem | identifier | rootNamingSystem.kind
name NstringComputationally friendly name of the naming systemNamingSystem.name
perioddateWhen is identifier valid?NamingSystem.uniqueId.period
publisher NstringName of the publisher of the naming systemNamingSystem.publisher
responsible NstringWho maintains system namespace?NamingSystem.responsible
status NtokenThe current status of the naming systemNamingSystem.status
telecomtokenContact details for individual or organizationNamingSystem.contact.telecom
typetokene.g. driver, provider, patient, bank etc.NamingSystem.type
url NuriThe uri that identifies the naming systemNamingSystem.url
value NstringThe unique identifierNamingSystem.uniqueId.value
version NtokenThe business version of the naming systemNamingSystem.version