Distinguishing referencing an existing slice vs. constraining a new slice

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • StructureDefinition
    • Profiling
    • Hide

      Will add a new boolean on ElementDefinition.slicing called "constraining" with a definition "if true, indicates that this slicing definition is constraining a slicing definition with the same name in an inherited profile"

      requirements "Allows detection of a situation where an ancestor profile adds or removes slicing with the same name where that might impact the child profile."

      comments "If set to true, an ancestor profile SHALL have a slicing definition with this name. If set to false, no ancestor profile is permitted to have a slicing definition with this name."

      Approval contingent on public review

      Show
      Will add a new boolean on ElementDefinition.slicing called "constraining" with a definition "if true, indicates that this slicing definition is constraining a slicing definition with the same name in an inherited profile" requirements "Allows detection of a situation where an ancestor profile adds or removes slicing with the same name where that might impact the child profile." comments "If set to true, an ancestor profile SHALL have a slicing definition with this name. If set to false, no ancestor profile is permitted to have a slicing definition with this name." Approval contingent on public review
    • Grahame Grieve/Sean McIlvenna: 5-0-0
    • Enhancement
    • Compatible, substantive
    • STU3

      When we have a profile and it uses the slice name of a parent profile, then we presume it's constraining the slicing declared in the parent profile. When we use a different slice name, we presume we're defining new slices. However, if the original profile is updated to add a new slice name (that happens to match the existing name in a derived profile) or is updated to change the name of an existing slice name, unexpected things will happen.

      Should we have a way of explicitly indicating in a derived profile that we're constraining an existing slice? That way we could detect (and error) if the parent profile changes in a way that breaks the child profile.

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

              Created:
              Updated:
              Resolved: