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

Add endpoint discovery expectations

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • 2.0.0
    • Payer/Provider Information Exchange
    • (NA)
    • Hide

      Background

      From FHIR-46443 document https://docs.google.com/document/d/1WiKR6OD3rmLNovFvxTn7D_5AawdDex391LFtd7cIt0Q/edit

       

                      X12 270 “Beneficiary Eligibility Check”
      Provider -------------------------------------------> Payer
                       x12 271 Response (FHIR Coverage)
      Provider <------------------------------------------ Payer

       

      x12 271 Response (FHIR Coverage) has a well known URL field to supply the endpoints including

      davinci_cdex_attachsubmit_endpoint: The ‘base’ for the endpoint used to invoke the $submit-attachment operation

      Rationale

      Reviewing the CDex transactions for Data Consumer endpoints

      Endpoint Discovery Needed For

      1. Unsolicited Attachments: The Data Consumer Endpoint is not discoverable in-band.  Therefore, for this transaction, there is a need for Payer-supplied endpoints.

      Endpoint Discovery Not Needed For

      1. Solicited Attachments: The $submit-attachment endpoint is a mandatory Task.input slice in the [CDex Task Attachment Request Profile](http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request)
      2. Direct Query: HTTP response so no endpoint discovery is needed
      3. Task Based Transactions:
        1. The FHIR endpoint for queried data is not needed because the `Task.output` supplies the URLs that are pulled ( or contained in the Task ) by the consumer.
        2. URL to canonical* for questionnaires in the conditionally mandatory `Task.input` slice in the [CDex Task Attachment Request Profile](http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request) and [CDex Task Data Request Profile](https://hl7.org/fhir/us/davinci-cdex/StructureDefinition-cdex-task-data-request.html)
      4. other possible requirement is to know the endpoint to retrieve the Questionnaire (and associated value sets, CQL Libraries, etc.)  However, this function is handled by DTR and there's no reason for CDex to define a mechanism as well.
      5. The $submit-attachment endpoint coming from PAS responses will need endpoint discovery, but that will be managed by PAS.

       

      Pre-applied here: https://hl7.org/fhir/us/davinci-cdex/sending-attachments.html#submit-attachment-operation

      Show
      Background From FHIR-46443 document https://docs.google.com/document/d/1WiKR6OD3rmLNovFvxTn7D_5AawdDex391LFtd7cIt0Q/edit                   X12 270 “Beneficiary Eligibility Check” Provider -------------------------------------------> Payer                  x12 271 Response (FHIR Coverage) Provider <------------------------------------------ Payer   x12 271 Response (FHIR Coverage) has a well known URL field to supply the endpoints including davinci_cdex_attachsubmit_endpoint: The ‘base’ for the endpoint used to invoke the $submit-attachment operation Rationale Reviewing the CDex transactions for Data Consumer endpoints Endpoint Discovery Needed For Unsolicited Attachments: The Data Consumer Endpoint is not discoverable in-band.  Therefore, for this transaction, there is a need for Payer-supplied endpoints. Endpoint Discovery Not Needed For Solicited Attachments: The $submit-attachment endpoint is a mandatory Task.input  slice in the [CDex Task Attachment Request Profile] ( http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request ) Direct Query: HTTP response so no endpoint discovery is needed Task Based Transactions: The FHIR endpoint for queried data is not needed because the `Task.output` supplies the URLs that are pulled ( or contained in the Task ) by the consumer. URL to canonical* for questionnaires in the conditionally mandatory `Task.input` slice in the [CDex Task Attachment Request Profile] ( http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request ) and [CDex Task Data Request Profile] ( https://hl7.org/fhir/us/davinci-cdex/StructureDefinition-cdex-task-data-request.html ) other possible requirement is to know the endpoint to retrieve the Questionnaire (and associated value sets, CQL Libraries, etc.)  However, this function is handled by DTR and there's no reason for CDex to define a mechanism as well. The $submit-attachment endpoint coming from PAS responses will need endpoint discovery, but that will be managed by PAS.   Pre-applied here: https://hl7.org/fhir/us/davinci-cdex/sending-attachments.html#submit-attachment-operation
    • Enhancement
    • Non-substantive
    • Yes

      HRex is adding a standard mechanism to support payer endpoint discovery via https://jira.hl7.org/browse/FHIR-44696.  This IG needs to point to that IG and indicate:

      "Implementers of this IG SHOULD support the [endpoint discovery] mechanism defined in the HRex specification to allow discovery of the endpoints used in this IG - specifically the ???? endpoints which are used for ????".

      Review the endpoints proposed and make sure they are a) appropriate and b) complete for your IG's needs.

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: