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

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • Framework
    • 3.7.1.3
    • 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"
    • Riki Merrick / Craig Newman: 3-0-1
    • Clarification
    • Non-substantive

      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.

            Assignee:
            Unassigned
            Reporter:
            Sean McIlvenna
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: