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

Asynchronous calls - why no restamping?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Hybrid/Intermediary Exchange (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • STU
    • Specification
    • Hide

      In the conventions described in this version of the IG, the intermediary is passive and prohibited from rewriting URLs in content returned by the destination.

      However, the destination can specify a content-location URL that differs from the public URL used in the first step of initiating the async request. The example doesn't intend to state that the content-location must be at the intermediary

       

      Show
      In the conventions described in this version of the IG, the intermediary is passive and prohibited from rewriting URLs in content returned by the destination. However, the destination can specify a content-location URL that differs from the public URL used in the first step of initiating the async request. The example doesn't intend to state that the content-location must be at the intermediary  
    • Frank McKinney / Christiaan Knaap: 11-0-0

    Description

      The specification indicates the destination uses the intermediary URL for retrieval of the content.

      I think an approach in which the intermediary receives the standard address and replaces it with its own is much cleaner. Please change the specification accordingly.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: