Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-26289

Suggest removing 0..0 constraints, or clarifying why 0..0 is required for use-case in the profile description

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive with Modification
    • Specification:
      US Da Vinci Alerts (FHIR)
    • Raised in Version:
      0.2.0
    • Work Group:
      Infrastructure & Messaging
    • Related Page(s):
      Framework
    • Related Section(s):
      3.7.1.3
    • Grouping:
    • Resolution Description:
      Hide

      The messaging Bundle type prohibits these elements via invariants, the Notifications Bundle profile simplifies these prohibitions for the reader so there is no risk of trying to use them in a non-conformant way.

      Will add a comment to element definition/comment
      "This element is constrained out because of invariant <bdl-xxx> applies to messaging"

      Show
      The messaging Bundle type prohibits these elements via invariants, the Notifications Bundle profile simplifies these prohibitions for the reader so there is no risk of trying to use them in a non-conformant way. Will add a comment to element definition/comment "This element is constrained out because of invariant <bdl-xxx> applies to messaging"
    • Resolution Vote:
      Riki Merrick / Craig Newman: 3-0-1
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Whenever I see profiles that have 0..0 for any elements, I question whether that is really needed. This is very limiting… Profiles that may want to extend upon your profiles may not be able to because you've required that (for example) Bundle.total NOT be present. I don't see value in asserting that the "total" cannot be specified... If this guidance is truly required, please indicate why in the description of the profile.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              seanmcilvenna Sean McIlvenna
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: