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

ConceptMap.group.unmapped is missing subelement 'relationship'

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • ConceptMap
    • Hide

      The unmapped element has no current mechanism to specify a value for the mapping relationship in the cases where mode is fixed or provided.

      Add optional property ConceptMap.group.unmapped.relationship(code) with required binding to ConceptMapRelationship.

      Add constraint ConceptMap.group.unmapped: (mode != 'other-map') implies relationship.exists()

      Show
      The unmapped element has no current mechanism to specify a value for the mapping relationship in the cases where mode is fixed or provided. Add optional property ConceptMap.group.unmapped.relationship(code) with required binding to ConceptMapRelationship. Add constraint ConceptMap.group.unmapped: (mode != 'other-map') implies relationship.exists()
    • Carmela Couderc/Michael Lawley : 5-0-0
    • Correction
    • Non-compatible
    • R5

    Description

      ConceptMap.group.unmapped can be used to provide a default fixed mapping, but is missing the ability to specify what the equivalence relationship is.

      Solution is to add is the missing subelement 'ConceptMap.group.unmapped.relationship' (in light of the re-naming of ConceptMap.group.target.equivalence to ConceptMap.group.target.relationship

      Also need to add explanatory text about the link between unmapped.relationship and unmapped.code (and unmapped.valueset, for when GF#15687 is resolved).

      Attachments

        Activity

          People

            Unassigned Unassigned
            mjlawley Michael Lawley
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: