A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this code system is (or will be) published. The URL SHOULD include the major version of the code system. For more information see Technical and Business Versions. This is used in [Coding]{datatypes.html#Coding}.system.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code 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 sequence. This is used in [Coding]{datatypes.html#Coding}.version.

A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation.

A boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.

The date (and optionally time) when the code system was published. The date must change if and 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 code system changes.

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

The name of an individual to contact.

The contact details for the individual (if a name was provided) or the organization.

A free text natural language description of the code system from a consumer's perspective.

A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system.

If code comparison is case sensitive when codes within this system are compared to each other.

True If code system defines a post-composition grammar.

This flag is used to signify that the code system has not (or does not) maintain the definitions, and a version must be specified when referencing this code system.

How much of the content of the code system - the concepts and codes it defines - are represented in this resource.

The total number of concepts defined by the code system. Where the code system has a compositional grammar, the count refers to the number of base (primitive) concepts.

A human readable string that is the recommended default way to present this concept to a user.

The formal definition of the concept. The code system resource does not make formal definitions required, because of the prevalence of legacy systems. However, they are highly recommended, as without them there is no formal meaning associated with the concept.

A code that details how this designation would be used.