Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-25923

Codes in concept-map-relationship have ambiguous implicit meaning

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      R5
    • Work Group:
      Vocabulary
    • Related Artifact(s):
      ConceptMap
    • Grouping:
    • Resolution Description:
      Hide

      End Result for the ConceptMapRelationshipType Code System:

      related-to (no change from FHIR-25373)

      equivalent (no change from FHIR-25373)

      source_is_narrower_than_target (was "broader" in FHIR-25373)

      Description = "The source concept is narrower than the target concept"  

      source_is_broader_than_target (was "narrower" in FHIR-25373)

      Description = "The source concept is broader than the target concept"

      not-related-to (no change FHIR-25373)

      Show
      End Result for the ConceptMapRelationshipType Code System: related-to  (no change from FHIR-25373 ) equivalent  (no change from FHIR-25373 ) source_is_narrower_than_target  (was "broader" in FHIR-25373 ) Description = "The source concept is narrower than the target concept"   source_is_broader_than_target  (was "narrower" in FHIR-25373 ) Description = "The source concept is broader than the target concept" not-related-to  (no change FHIR-25373 )
    • Resolution Vote:
      Reuben Daniels/Carmela Couderc: 3-0-1
    • Change Category:
      Enhancement
    • Change Impact:
      Non-compatible

      Description

      (See http://build.fhir.org/codesystem-concept-map-relationship.html)

      The concept map relationship codes for both the broader and narrower relationships between source and target concepts are inherently directional.  If the single words "broader" or "narrower" are used for these code, then they are subject to misinterpretation when presented in different contexts.  For example, in a table with columns "source" "relationship" "target", or in the ConceptMap resource where the "relationship" element hangs off the "target" element.

      Thus the codes for these concepts MUST explicitly state the directionality to avoid ambiguity.

      These codes should thus be replaced with:

      source_has_broader_target "The source is included in target"

      source_has_narrower_target "The target is included in the source"

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mjlawley Michael Lawley
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: