Subsumes operation is too time-costly

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • TerminologyCapabilities
    • Hide

      Will defer this discussion and any future changes to R5 (noting that this is a normative candidate).

      Show
      Will defer this discussion and any future changes to R5 (noting that this is a normative candidate).
    • Correction

      Existing wording: outcome, type=code; There are 4 possible codes to be returned: equivalent, subsumes, subsumed-by, and not-subsumed.

      Proposed wording: outcome, type=boolean; There are 2 possible codes to be returned: true (A subsumed-by B), false (A not subsumed-by B).

      Ballot comment: Convert to boolean and limit checking to just subsumed-by. Rationale is that our use case only needs to test 'subsumed-by', and also testing for subsumes and equivalence takes too long for real-time checking.

            Assignee:
            Unassigned
            Reporter:
            Bob Dolin
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: