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.

The descriptive name of this particular identifier type or code system.

The"symbolic name" for an OID would be captured as an extension.

Indicates whether the namingsystem is "ready for use" or not.

Indicates the purpose for the namingsystem - what kinds of things does it make unique?

The name of the individual or organization that published the naming system.

Helps establish the "authority/credibility" of the naming system. May also allow for contact.

Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.

Contacts to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number (tel:), etc.

The name of an individual to contact regarding the naming system.

If there is no named individual, the telecom is for the organization as a whole.

Contact details for individual (if a name was provided) or the publisher.

The name of the organization that is responsible for issuing identifiers or codes for this namespace and ensuring their non-collision.

This is the primary organization. Responsibility for some aspects of a namespace may be delegated.

The date (and optionally time) when the system was registered or published. The date must change when the business version changes, if it does, and it must change if the status code changes. in addition, it should change when the substantiative content of the registration changes.

Additional specific dates may be added as extensions.

Categorizes a namingsystem for easier search by grouping related namingsystems.

This will most commonly be used for identifier namespaces, but categories could potentially be useful for code systems and authorities as well.

Details about what the namespace identifies including scope, granularity, version labeling, etc.

The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of naming systems.

Assist in searching for appropriate content.

Provides guidance on the use of the namespace, including the handling of formatting characters, use of upper vs. lower case, etc.

Indicates how the system may be identified when referenced in electronic exchange.

Multiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc.

Identifies the unique identifier scheme used for this particular identifier.

Different identifier types may be used in different types of communications (OIDs for v3, URIs for FHIR, etc.). Other includes RUIDs from v3, standard v2 code name strings, etc.

The string that should be sent over the wire to identify the code system or identifier system.

If the value is a URI intended for use as FHIR system identifier, the URI should not contain "\" or "?" or "," since this makes escaping very difficult.

Indicates whether this identifier is the "preferred" identifier of this type.

Identifies the period of time over which this identifier is considered appropriate to refer to the namingsystem. Outside of this window, the identifier might be non-deterministic.

Within a registry, a given identifier should only be "active" for a single namespace at a time. (Ideally, an identifier should only ever be associated with a single namespace across all time).

For namingsystems that are retired, indicates the namingsystem that should be used in their place (if any).