This example and updated wording was pre-applied: Mappings between code system concepts are only intended to be defined in the context of the specified source and target value sets - they are specific to a particular context of use. The mappings may be useful in other contexts, but this must be determined based on the context of use and meaning; it cannot be taken for granted automatically. An example of where the usage context is important for choosing the correct mapping is mapping from a clinical terminology (e.g. SNOMED CT) to a classification (e.g. ICD-10) for either data analysis or billing. Mappings in the data analysis context would be targeted for the appropriate aggregate classification, whereas in the billing context there may be specific additional requirements to be met (e.g. leaf level codes only) which may result in multiple candidate target mappings that are dependent on additional information beyond the meaning of the source concept itself for determining the final mapping selection. Will further update the wording and replace the first sentence above with: Mappings between code system concepts are only intended to be defined in the context of a particular business usage. The business use case is normally defined by the specification of the source and target value sets.