Draft2.16.840.1.113883.4.642.4.18 - ConceptMapEquivalence - FHIR: http://hl7.org/fhir/concept-map-equivalence
| Level/ Type | Code | Display Name | Code System | Code System Version | Designations | Description |
|---|---|---|---|---|---|---|
| 0‑S | relatedto | Related To | ConceptMapEquivalence | 2019-11-01T09:29:23 |  Preferred: Related To | The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known. |
| 1‑S | equivalent | Equivalent | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Equivalent | The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical). |
| 2‑L | equal | Equal | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Equal | The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical). |
| 1‑L | wider | Wider | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Wider | The target mapping is wider in meaning than the source concept. |
| 1‑L | subsumes | Subsumes | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Subsumes | The target mapping subsumes the meaning of the source concept (e.g. the source is-a target). |
| 1‑L | narrower | Narrower | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Narrower | The target mapping is narrower in meaning than the source concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. |
| 1‑L | specializes | Specializes | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Specializes | The target mapping specializes the meaning of the source concept (e.g. the target is-a source). |
| 1‑L | inexact | Inexact | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Inexact | The target mapping overlaps with the source concept, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is inexact SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. |
| 0‑S | unmatched | Unmatched | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Unmatched | There is no match for this concept in the target code system. |
| 1‑L | disjoint | Disjoint | ConceptMapEquivalence | 2019-11-01T09:29:23 | Preferred: Disjoint | This is an explicit assertion that there is no mapping between the source and target concept. |
