Generalize excludeNotForUI - 2018-Jan Core #306

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • ExpansionProfile [deprecated]
    • Hide

      Need to add documentation to make it clear how excludeNotForUI relates to expansion.contains.abstract and how this is used with different code systems. Need more description of the implemented use case(s) - e.g. in the FHIR build, V3, etc. Also consider whether the use case(s) are in the 80% for requiring this element in the core specification.

      Show
      Need to add documentation to make it clear how excludeNotForUI relates to expansion.contains.abstract and how this is used with different code systems. Need more description of the implemented use case(s) - e.g. in the FHIR build, V3, etc. Also consider whether the use case(s) are in the 80% for requiring this element in the core specification.
    • Rob Hausam/Grahame Grieve: 8-0-3
    • Enhancement
    • Non-substantive
    • STU3

      Existing Wording: ExpansionProfile.excludeNotForUI is unclear and unnecessary; different code systems identify UI (or notForUI) codes with different kinds of properties. HL7 V3 uses one way, others use different ways.

      Proposed Wording: Generalize this to identify the propery and value for codes to be exclued from the expansion.

      Summary:

      Generalize excludeNotForUI

            Assignee:
            Unassigned
            Reporter:
            Ted Klein
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: