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 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. Indicates the mechanism used to compare versions to determine which ConceptMap is more current. 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 no version of this resource will ever be intended for genuine usage. The date (and optionally time) when the concept map was last significantly changed. 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 responsible for the release and ongoing maintenance of 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 authority that maintains the resource is operating. In general, the jurisdiction is also found in the useContext. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use. 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 notices of intellectual property ownership and can include restrictions on the use and publishing of the concept map. A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are restricted. (e.g. 'All rights reserved', 'Some rights reserved'). The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. The period during which the ConceptMap content was or is planned to be in active use. Descriptions related to the content of the ConceptMap. Topics provide a high-level categorization as well as keywords for the ConceptMap that can be useful for filtering and searching. An individiual or organization primarily involved in the creation and maintenance of the ConceptMap. An individual or organization primarily responsible for internal coherence of the ConceptMap. An individual or organization asserted by the publisher to be primarily responsible for review of some aspect of the ConceptMap. An individual or organization asserted by the publisher to be responsible for officially endorsing the ConceptMap for use in some setting. Related artifacts such as additional documentation, justification, dependencies, bibliographic references, and predecessor and successor artifacts. If the type is `successor` or `predecessor`, the related resource must be a ConceptMap. A property defines a slot through which additional information can be provided about a map from source -> target. An additionalAttribute defines an additional data element found in the source or target data model where the data will come from or be mapped to. Some mappings are based on data in addition to the source data element, where codes in multiple fields are combined to a single field (or vice versa). Identifier for the source value set that contains the concepts that are being mapped and provides context for the mappings. Limits the scope of the map to source codes (ConceptMap.group.element code or valueSet) that are members of this value set. Identifier for the target value set that provides important context about how the mapping choices are made. Limits the scope of the map to target codes (ConceptMap.group.element.target code or valueSet) that are members of this value set. 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. A code that is used to identify the property. The code is used internally (in ConceptMap.group.element.target.property.code) and also in the $translate operation. Reference to the formal meaning of the property. A description of the property - why it is defined, and how its value might be used. The type of the property value. The CodeSystem that defines the codes from which values of type ```code``` in property values. 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 code that is used to identify this additional data attribute. The code is used internally in ConceptMap.group.element.target.dependsOn.attribute and ConceptMap.group.element.target.product.attribute. Reference to the formal definition of the source/target data element. For elements defined by the FHIR specification, or using a FHIR logical model, the correct format is {canonical-url}#{element-id}. A description of the additional attribute and/or the data element it refers to - why it is defined, and how the value might be used in mappings, and a discussion of issues associated with the use of the data element. The type of the source data contained in this concept map for this data element. 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. An absolute URI that identifies the target system that the concepts will be mapped to. Mappings for an individual concept in the source to one or more concepts in the target. What to do when there is no mapping to a target concept from the source concept and ConceptMap.group.element.noMap is not true. This provides the "default" to be applied when there is no target concept mapping specified or the expansion of ConceptMap.group.element.target.valueSet is empty. 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. The set of concepts from the ConceptMap.group.source code system which are all being mapped to the target as part of this mapping rule. If noMap = true this indicates that no mapping to a target concept exists for this source concept. Comments related to the mapping of the source element, potentially including why there is no target. 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 set of concepts from the ConceptMap.group.target code system which are all being mapped to as part of this mapping rule. The effect of using this data element is the same as having multiple ConceptMap.group.element.target elements with one for each concept in the ConceptMap.group.element.target.valueSet value set. The relationship between the source and target concepts. The relationship is read from source to target (e.g. source-is-narrower-than-target). Comments related to the mapping to the target element. A property value for this source -> target mapping. A set of additional dependencies for this mapping to hold. This mapping is only applicable if the specified data attribute can be resolved, and it has the specified value. Product is the output of a ConceptMap that provides additional values that go in other attributes / data elemnts of the target data. 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 a mapping property defined in ConceptMap.property. The value of this property. If the type chosen for this element is 'code', then the property SHALL be defined in a ConceptMap.property element and that ConceptMap.property element SHALL have a system element. 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 the additional attribute that holds a value the map depends on. Data element value that the map depends on / produces. If the data type is a code, that code SHALL come from the .group.source code system for .dependsOn.valueCode or from the .group.target code system for .product.valueCode. This mapping applies if the data element value is a code from this value set. 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 source 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. Comments related to the choice of how to handle unmapped elements. The set of fixed codes to use when the mode = 'fixed' - all unmapped codes are mapped to each of the fixed codes. The default relationship value to apply between the source and target concepts when the source code is unmapped and the mode is 'fixed' or 'use-source-code'. 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. Coding (external reference) string integer boolean dateTime decimal code If the element is present, it must have either a @value, an @id, or extensions code Coding string boolean Quantity If the element is present, it must have either a @value, an @id, or extensions Use Provided Source Code Fixed Code Other Map If the element is present, it must have either a @value, an @id, or extensions