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

change SHOULD to SHALL

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Da Vinci DEQM (FHIR)
    • 4.0.0-ballot
    • Clinical Quality Information
    • STU
    • Data Exchange
    • 2.2.3.0.2.1.
    • Hide

      Change: An OperationOutcome SHOULD be returned stating that the [snapshot/incremental] update is not supported as shown in the following example:"

      to:

      An OperationOutcome SHALL be returned stating that the [snapshot/incremental] update is not supported as shown in the following example:"

      http://hl7.org/fhir/R4/operations.html#response

      Show
      Change: An OperationOutcome SHOULD be returned stating that the [snapshot/incremental]  update is not supported as shown in the following example:" to: An OperationOutcome SHALL be returned stating that the [snapshot/incremental]  update is not supported as shown in the following example:" http://hl7.org/fhir/R4/operations.html#response
    • Ben Hamlin/Juliet Rubini: 22-0-0
    • Enhancement
    • Non-substantive

    Description

      See sentence "The Consumer SHALL reject the submit data payload if there is mismatch between the Consumer's stated capabilities and the required modifier extension by returning a 400 Bad Request http error code. An OperationOutcome SHOULD be returned stating that the [snapshot/incremental] update is not supported as shown in the following example:"

      The SHOULD needs to be changed to a SHALL. How else will the provider know why the data submission was rejected?

      Attachments

        Activity

          People

            yanheras Yan Heras
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: