Unclear about mandatory vs. Optional - SDC #1

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium High
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • SDC Home Page
    • SDC Home Page
    • Hide

      Will go through the specification and try to identify specific places where we can be tighter about conformance expectations and explicitly make them SHALL or SHOULD (will come back to the WG to verify these changes). Will also clarify that large portions of the specification are "MAY" - i.e. they're defining behavior/capabilities that can be adopted, but there isn't necessarily an expectation for adoption in order to be SDC-conformant. We'll also be revisiting the capability statements with an objective of making them stricter and better-aligned with the refactored SDC specification.

      Show
      Will go through the specification and try to identify specific places where we can be tighter about conformance expectations and explicitly make them SHALL or SHOULD (will come back to the WG to verify these changes). Will also clarify that large portions of the specification are "MAY" - i.e. they're defining behavior/capabilities that can be adopted, but there isn't necessarily an expectation for adoption in order to be SDC-conformant. We'll also be revisiting the capability statements with an objective of making them stricter and better-aligned with the refactored SDC specification.
    • Robinette Renner/Clem McDonald: 7-0-0
    • Clarification
    • Non-substantive

      Comment:

      The current specification is unclear regarding mandatory and optional parts of the specification. I suggest to adopt the use of MUST, SHOULD, … as is specified in RFC 2119 and RFC 8174 and update the specification accordingly. This does happen in some locations but not consistently throughout the spec.

      Summary:

      Unclear about mandatory vs. Optional

            Assignee:
            Lloyd McKenzie
            Reporter:
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: