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

Polling frequency

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • STU
    • Task Based Approach
    • 4.8.1
    • Hide

      Change

      "Data Consumers SHOULD perform this operation in an automated/background manner no more than every 5 minutes for the first 30 minutes and no more frequently than once every hour after that."

      to

      Data Consumers SHOULD perform this operation in an automated/background manner after 1 minute to return automated responses and after that no more than every 5 minutes for the first 30 minutes and no more frequently than once every hour after that.

       

      Note: find this same polling timing for PAS and update it to the language above.

      Show
      Change "Data Consumers SHOULD perform this operation in an automated/background manner no more than every 5 minutes for the first 30 minutes and no more frequently than once every hour after that." to Data Consumers SHOULD perform this operation in an automated/background manner after 1 minute to return automated responses and after that no more than every 5 minutes for the first 30 minutes and no more frequently than once every hour after that.   Note: find this same polling timing for PAS and update it to the language above.
    • Eric Haas/Jay Lyle: 7-0-1
    • Enhancement
    • Compatible, substantive

      Are these parameters for polling across all use cases? Is there going to be one guideline, regardless if it is provider polling for a PA answer or a payer polling for an answer to a query? I guess it is easier to have one guideline across use cases, but seems like they are very different in terms of how fast you could expect response.

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: