A statement of relationships from one set of concepts to one or more other concepts - either code systems or data elements, or classes in class models.

An absolute URI that is used to identify this concept map when it is referenced in a specification, model, design or an instance. This SHOULD be globally unique, and SHOULD be a literal address at which this concept map is (or will be) published.

Allows the concept map to be referenced by a single globally unique identifier.

Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The URL SHOULD include the major version of the concept map. For more information see Technical and Business Versions.

A formal identifier that is used to identify this concept map when it is represented in other formats, or referenced in a specification, model, design or an instance.

Allows externally provided and/or usable business identifiers to be easily associated with the module.

Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this concept map outside of FHIR, where it is not possible to use the logical URI.

The identifier that is used to identify this version of the concept map when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the concept map 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.

There may be different concept map instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the concept map with the format [url]|[version].

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

Support human navigation and code generation.

The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.

A short, descriptive, user-friendly title for the concept map.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

The status of this concept map. Enables tracking the life-cycle of the content.

Allows filtering of concept maps that are appropriate for use vs. not.
This is labeled as "Is Modifier" because applications should not use a retired concept map without due consideration.

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

Enables experimental content to be developed following the same lifecycle that would be used for a production-level concept map.

Allows filtering of concept map that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental concept map in production.

The date (and optionally time) when the concept map 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 concept map changes.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the concept map. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

The name of the individual or organization that published the concept map.

Helps establish the "authority/credibility" of the concept map. May also allow for contact.

Usually an organization, but may be an individual. The publisher (or steward) of the concept map is the organization or individual primarily responsible for the maintenance and upkeep of the concept map. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the concept map. This item SHOULD be populated unless the information is available from context.

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

May be a web site, an email address, a telephone number, etc.

A free text natural language description of the concept map from a consumer's perspective.

The description is not intended to describe the semantics of the concept map. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes.

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 for appropriate concept map instances.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

A legal or geographic region in which the concept map is intended to be used.

It may be possible for the concept map to be used in jurisdictions other than those for which it was originally designed or intended.

Explaination of why this concept map is needed and why it has been designed as it has.

This element does not describe the usage of the concept map Instead it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this concept map.

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

Consumers must be able to determine any legal restrictions on the use of the concept map and/or its content.

null Frequently, the copyright differs between the concept map, and codes that are included. The copyright statement should clearly differentiate between these when required.

The source value set that specifies the concepts that are being mapped.

Should be a version specific reference. URIs SHOULD be absolute. If there is no source or target value set, the is no specified context for the map.

The target value set provides context to the mappings. Note that the mapping is made between concepts, not between value sets, but the value set provides important context about how the concept mapping choices are made.

Should be a version specific reference. URIs SHOULD be absolute. If there is no source or target value set, the is no specified context for the map.

A group of mappings that all have the same source and target system.

An absolute URI that identifies the Code System (if the source is a value set that crosses more than one code system).

The specific version of the code system, as determined by the code system authority.

The specification of a particular code system version may be required for code systems which lack concept permanence.

An absolute URI that identifies the code system of the target code (if the target is a value set that cross code systems).

Target may be omitted if all the targget element equivalence values are 'unmatched'.

The specific version of the code system, as determined by the code system authority.

The specification of a particular code system version may be required for code systems which lack concept permanence.

Mappings for an individual concept in the source to one or more concepts in the target.

Generally, the ideal is that there would only be one mapping for each concept in the source value set, but a given concept may be mapped multiple times with different comments or dependencies.

Identity (code or path) or the element/item being mapped.

The display for the code. The display is only provided to help editors when editing the concept map.

The display is ignored when processing the map.

A concept from the target value set that this concept maps to.

Ideally there would only be one map, with equal or equivalent mapping. But multiple maps are allowed for several narrower options, or to assert that other concepts are unmatched.

Identity (code or path) or the element/item that the map refers to.

The display for the code. The display is only provided to help editors when editing the concept map.

The display is ignored when processing the map.

The equivalence between the source and target concepts (counting for the dependencies and products). The equivalence is read from target to source (e.g. the target is 'wider' than the source).

This element is labeled as a modifier because it may indicate that a target does not apply.

A description of status/issues in mapping that conveys additional information not represented in the structured data.

A set of additional dependencies for this mapping to hold. This mapping is only applicable if the specified element can be resolved, and it has the specified value.

A reference to an element that holds a coded value that corresponds to a code system property. The idea is that the information model carries an element somwhere that is labeled to correspond with a code system property.

An absolute URI that identifies the code system of the dependency code (if the source/dependency is a value set that crosses code systems).

Identity (code or path) or the element/item/ValueSet that the map depends on / refers to.

The display for the code. The display is only provided to help editors when editing the concept map.

The display is ignored when processing the map.

A set of additional outcomes from this mapping to other elements. To properly execute this mapping, the specified element must be mapped to some data element or source that is in context. The mapping may still be useful without a place for the additional data elements, but the equivalence cannot be relied on.

What to do when there is no match in the mappings in the group.

This only applies if the source code is in the system defined for the group.

Defines which action to take if there is no match in the group. One of 3 actions is possible: use the unmapped code (this is useful when doing a mapping between versions, and only a few codes have changed), use a fixed code (a default code), or alternatively, a reference to a different concept map can be provided (by canonical URL).

The fixed code to use when the mode = 'fixed' - all unmapped codes are mapped to a single fixed code.

The display for the code. The display is only provided to help editors when editing the concept map.

The display is ignored when processing the map.

The canonical URL of the map to use if this map contains no mapping.