ElementDefinition normative and ValueSet resource-slicing-rules still draft FMM 0

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Terminologies - Valuesets
    • Hide

      fix up these missed FMM levels (something wrong in the tooling)

      Show
      fix up these missed FMM levels (something wrong in the tooling)
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Enhancement
    • Non-substantive
    • STU3

      The value set of slicing rules is in FMM 0. Is this compatible with ElementDefinition going normative?

      The slicing rules "open", "closed", "openAtEnd" cannot disappear in the future. So FMM of this value set should be higher, at least 4 or 5, if not candidate normative.

            Assignee:
            Unassigned
            Reporter:
            Francois Macary
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: