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

In diagram, show 200 ok w/ OperationOutcome

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Da Vinci CDex (FHIR)
    • 1.0.0
    • Patient Care
    • Attachments
    • Hide
      • update narrative in the steps for the diagram:

      "3. Payer responds with an http transactional layer response either accepting or rejecting the transaction.

      • The Payer _SHOULD return an informational OperationOutcome with the http accept response if the attachments can not be associated with a current claim or prior authorization and are being held for association with a future claim or prior authorization."_

       

      • Add additional guidance to the operation definition:
         
        "The operation may be invoked before, at the same time as, or after the claim or pre-authorization has been supplied to the Payer."
         
        "If the attachment is to a non-recognized existing claim or member, the server {}SHOULD{} return an [OperationOutcome](http://hl7.org/fhir/operationoutcome.html) to inform the Data Source that the attachments are being held for subsequent association to a claim or prior-authorization."
         
      • add additional guidance to theUnsolicited Workflow section: 
         
        The attachments may be submitted before, at the same time as, or after the claim or pre-authorization has been supplied to the Payer.
         
      • add example interaction with operation outcome
         
      Show
      update narrative in the steps for the diagram: "3. Payer responds with an http transactional layer response either accepting or rejecting the transaction. The Payer  _SHOULD  return an informational OperationOutcome with the http accept response if the attachments can not be associated with a current claim or prior authorization and are being held for association with a future claim or prior authorization."_   Add additional guidance to the operation definition:   "The operation may be invoked before, at the same time as, or after the claim or pre-authorization has been supplied to the Payer."   "If the attachment is to a non-recognized existing claim or member, the server { }SHOULD{ } return an [OperationOutcome] ( http://hl7.org/fhir/operationoutcome.html ) to inform the Data Source that the attachments are being held for subsequent association to a claim or prior-authorization."   add additional guidance to theUnsolicited Workflow section:    The attachments may be submitted before, at the same time as, or after the claim or pre-authorization has been supplied to the Payer.   add example interaction with operation outcome  
    • Eric Haas/Jay Lyle:9-0-1
    • Clarification
    • Compatible, substantive

    Description

      We need to show a response where the attachment is to a non-recognized claim or member and is being held for subsequent attachment

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: