Replace UsageContext with CodeableConcept

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • STU
    • UsageContext (see Metadata Types) [deprecated]
    • Hide
      • change the description of the useContext element to say that there is no indication of whether multiple contexts mean "all" contexts or "any" (it says "and" now).
      • Define an extension context-group. This can be used on each repetition of useContext to state to which group the repetition belongs. The extension cannot repeat (each useContext belongs to one group). Multiple groups are "or'ed", contexts within a group are "and'ed".
      Show
      change the description of the useContext element to say that there is no indication of whether multiple contexts mean "all" contexts or "any" (it says "and" now). Define an extension context-group. This can be used on each repetition of useContext to state to which group the repetition belongs. The extension cannot repeat (each useContext belongs to one group). Multiple groups are "or'ed", contexts within a group are "and'ed".
    • Bryn Rhodes/Lloyd McKenzie: 8-0-0
    • Enhancement
    • Non-compatible
    • Yes
    • DSTU2

      In all of the infrastructure resources, we just use a CodeableConcept to capture all the different types of contexts. There's no obvious benefit to sub-categorizing them and the list of possible sub-categories is huge - the elements provided here are far from exhaustive. If you need differentiation, you can do so through value sets, code systems, code hierarchy, etc.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie, Melva Peters
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: