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 URL URI that is used to identify this concept map 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 concept map is (or will be) published. The URL SHOULD include the major version of the concept map. For more information see Technical and Business Versions .

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.

Formal 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 values identifiers that can go in a v3 an HL7 V3 II (instance identifier) data type. 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 profile concept map author manually and the value should is not expected to be globally unique. For example, it might be a timestamp. 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 multiple resource versions of the different concept map instances that have this the same identifier. identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the concept map with the format [url]|[version].

A free text natural language name describing 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. navigation and code generation.

Not 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.

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

Identify when/if the concept map should This name does not need to be used. machine-processing friendly and may contain punctuation, white-space, etc.

Allows filtering The status of ConceptMap resources that are appropriate for use. this concept map. Enables tracking the life-cycle of the content.

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

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

Helps establish the "authority/credibility" of Enables experimental content to be developed following the same lifecycle that would be used for a production-level concept map. May also allow for contact.

Usually an organization, but may be an individual. Allows filtering of concept map that are appropriate for use vs. not. This item SHOULD be populated unless the information is available from context. labeled as "Is Modifier" because applications should not use an experimental concept map in production.

Contacts to assist a user in finding The date (and optionally time) when the concept map was published. The date must change if and communicating with when the publisher. 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.

May Note that this is not the same as the resource last-modified-date, since the resource may be a web site, an email address, a telephone number, etc. 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 an the individual to contact regarding or organization that published the concept map.

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

If there is no named individual, Usually an organization, but may be an individual. The publisher (or steward) of the telecom 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 as a whole. 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 for individual (if to assist a name was provided) or user in finding and communicating with the publisher.

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

The date this version of the concept map was 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 substantive content A free text natural language description of the concept map changes. from a consumer's perspective.

Note that this The description is not intended to describe the same as the resource last-modified-date, since the resource may be a secondary representation semantics of the concept map. Additional specific dates may be added as extensions. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes.

A free text natural language description of the use 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 - reason for definition, conditions of use, etc. instances.

Human understandability. Assist in searching for appropriate content.

The description When multiple useContexts are specified, there is not intended to describe the semantics no expectation whether all or any 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. contexts apply.

The content was developed with a focus and intent of supporting A legal or geographic region in which the contexts that are listed. These terms may be used to assist with indexing and searching of concept map instances. 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.

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

This element does not describe the usage of the concept map (that is done in comments), rather it's for Instead it provides traceability of ''why'' the element resource is either needed or ''why'' the constraints exist it is defined as they do. it is. This may be used to point to source materials or specifications that drove the structure of this data element. 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.

An absolute URI that identifies the Code System (if Identity (code or path) or the source is a value set that crosses more than one code system). element/item being mapped.

Identity (code or path) or The display for the element/item being mapped. 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.

An absolute URI that identifies the code system of the target code (if Identity (code or path) or the target is a value set element/item that cross code systems). the map refers to.

Identity (code or path) or The display for the element/item that code. The display is only provided to help editors when editing the map refers to. 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 a specific concept an element that holds a coded value. This can be an element in a FHIR resource, or a specific reference value that corresponds to a data code system property. The idea is that the information model carries an element in a different specification (e.g. HL7 v2) or a general reference to a kind of data field, or a reference somwhere that is labeled to a value set correspond with an appropriately narrow definition. 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.