A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this concept map 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 concept map is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the concept map is stored on different servers. 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. 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. 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. A short, descriptive, user-friendly title for the concept map. The status of this concept map. Enables tracking the life-cycle of the content. 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. The date (and optionally time) when the concept map 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 concept map changes. The name of the organization or individual that published the concept map. Contact details to assist a user in finding and communicating with the publisher. A free text natural language description of the concept map from a consumer's perspective. 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 concept map instances. A legal or geographic region in which the concept map is intended to be used. Explanation of why this concept map is needed and why it has been designed as it has. 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. Identifier for the source value set that contains the concepts that are being mapped and provides context for the mappings. The target value set provides context for 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. A group of mappings that all have the same source and target system. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. An absolute URI that identifies the source system where the concepts to be mapped are defined. The specific version of the code system, as determined by the code system authority. An absolute URI that identifies the target system that the concepts will be mapped to. The specific version of the code system, as determined by the code system authority. Mappings for an individual concept in the source to one or more concepts in the target. What to do when there is no mapping for the source concept. "Unmapped" does not include codes that are unmatched, and the unmapped element is ignored in a code is specified to have equivalence = unmatched. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. 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. A concept from the target value set that this concept maps to. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. 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 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). 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 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. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. 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 somewhere 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/text 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. A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. Defines which action to take if there is no match for the source concept in the target system designated for the group. One of 3 actions are 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 canonical reference to an additional ConceptMap resource instance to use for mapping if this ConceptMap resource contains no matching mapping for the source concept. Provided Code Fixed Code Other Map Defines which action to take if there is no match in the group. If the element is present, it must have either a @value, an @id, or extensions