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

Split request and response into separate sections

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • Bulk Data (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • SMART Backend Services Authorization
    • 3.6.1
    • Hide

      As this page moves in to the SMART App Launch spec, refactor the "Obtaining an Access Token" sections to break into sub-sections that reflect more granular step-by-step process – the exact wording can be determined later, but we will use the following as a guide:

      1. client preparation
      2. request message format
      3. server processing
      4. response message format
      5. client post processing

      See #FHIR-32200 for context (from SMART App Launch Ballot), and the reciprocal request #FHIR-32338 (from Bulk Data Ballot)

       

      Show
      As this page moves in to the SMART App Launch spec, refactor the "Obtaining an Access Token" sections to break into sub-sections that reflect more granular step-by-step process – the exact wording can be determined later, but we will use the following as a guide: client preparation request message format server processing response message format client post processing See # FHIR-32200 for context (from SMART App Launch Ballot), and the reciprocal request # FHIR-32338 (from Bulk Data Ballot)  
    • Bas van den Heuvel / Dan Gottlieb: 10-0-0
    • Clarification
    • Non-substantive

    Description

      Readability would be improved by splitting off the request and response into separate sub-sections.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: