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

polling mechanism in question

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci Patient Cost Transparency (PCT) (FHIR)
    • 0.1.0 [deprecated]
    • Financial Mgmt
    • Formal Specification
    • Hide

      Will be moving to the https://build.fhir.org/async-bundle.html pattern for polling, so will rewrite the section on polling (https://build.fhir.org/ig/HL7/davinci-pct/formal_specification.html#polling) based on that. 

      Note that the async pattern does not specify a fixed interval between polling tries. Rather, each payer system will have the ability to communicate when to poll next via the Retry-After HTTP header, thus if a GFE is simple to process they can specify a short interval like a few minutes, but if something requires a longer timeframe, they can say try back in a longer time frame.

      However, will document that there is an industry goal to shorten timeframes, and given the tight timelines required by the NSA it is in everyone's best interest for the industry to attempt quick turnaround times. 

      Also we will not tackle Subscription until phase 2 since it will change dramatically in R5, and I we don't plan to move to FHIR R4B and the new Subscription backport IG in phase 1.

      When copying the async pattern info, make sure that we flag the response codes as SHALL. For instance "HTTP Status Code of 202 Accepted" will become "SHALL respond with HTTP Status Code of 202 Accepted". 

      Once written, will review the adaptation of the async pattern with the public stakeholder group for PCT. 

      Show
      Will be moving to the https://build.fhir.org/async-bundle.html pattern for polling, so will rewrite the section on polling ( https://build.fhir.org/ig/HL7/davinci-pct/formal_specification.html#polling ) based on that.  Note that the async pattern does not specify a fixed interval between polling tries. Rather, each payer system will have the ability to communicate when to poll next via the Retry-After HTTP header, thus if a GFE is simple to process they can specify a short interval like a few minutes, but if something requires a longer timeframe, they can say try back in a longer time frame. However, will document that there is an industry goal to shorten timeframes, and given the tight timelines required by the NSA it is in everyone's best interest for the industry to attempt quick turnaround times.  Also we will not tackle Subscription until phase 2 since it will change dramatically in R5, and I we don't plan to move to FHIR R4B and the new Subscription backport IG in phase 1. When copying the async pattern info, make sure that we flag the response codes as SHALL. For instance "HTTP Status Code of 202 Accepted" will become "SHALL respond with HTTP Status Code of 202 Accepted".  Once written, will review the adaptation of the async pattern with the public stakeholder group for PCT. 
    • Rick Geimer/Paul Knapp: 9-0-1
    • Enhancement
    • Non-compatible

    Description

      Polling is not explained very well. Suggest refining description or removing text entirely to instead reference HRex guide mechanisms section. From a provider perspective, subscription for example seems less costly and more efficient, seems odd this IG only references polling and does so in a convoluted way.

      Attachments

        Activity

          People

            rgeimer Rick Geimer
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: