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

Clarity needed to differentiate re-writing URLs (out of scope) and destination re-population of new urls

    XMLWordPrintableJSON

Details

    • Icon: Technical Correction Technical Correction
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Hybrid/Intermediary Exchange (FHIR)
    • current
    • FHIR Infrastructure
    • Specification
    • 2.2, 5.4
    • Hide

      Clarify the fourth bullet in section 2.2 Scenario Overview by changing from:

      • the originator directs its exchange to the intended destination’s public FHIR service address, and the destination populates any elements referencing the destination server in returned FHIR resources (e.g., fullUrl) using its pubic FHIR service base URL

      To 

      • the originator directs its request to the destination’s public FHIR service URL, and the destination likewise uses that public FHIR service URL when referring to itself in the response (the destination populates elements referencing the destination server in returned FHIR resources, e.g., fullUrl, using the pubic FHIR service base URL)
      Show
      Clarify the fourth bullet in section 2.2 Scenario Overview by changing from: the originator directs its exchange to the intended destination’s public FHIR service address, and the destination populates any elements referencing the destination server in returned FHIR resources (e.g., fullUrl) using its pubic FHIR service base URL To  the originator directs its request to the destination’s public FHIR service URL, and the destination likewise uses that public FHIR service URL when referring to itself in the response (the destination populates elements referencing the destination server in returned FHIR resources, e.g., fullUrl, using the pubic FHIR service base URL)
    • Correction
    • Non-substantive
    • 0.1.0

    Description

      Rewriting URLs is stated in multiple locations as not supported - does this just mean re-writing by the intermediary? Since in the 4th bullet in 2.2 Scenario overview reads like the destination is doing rewriting/population of new urls when it sends its response back to the intermediary

      Submitted by: sheridancook

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: