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

$davinci-data-export operation not defined for Attribution List Import

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci ATR (FHIR)
    • 2.0.0-ballot
    • Financial Mgmt
    • ATRGroup
      DaVinci ATR Producer
      DaVinci Data Export
      DaVinci Patient List
    • Detailed Specification
    • 4.1.7. Requirements for Implementation of the $davinci-data-export operation
    • Hide

      All the questions have been answered, no changes are made to the IG.

      Question 1: The initial list creation by the Consumer in the Producer system uses the POST API on the Group resource and does not use the davinci-data-export operation. Thus an Import operation is not required for the creation of the initial list. 

      Once the initial list is created, the Consumer can use the member-add/member-remove APIs to add and remove members from the Group (Attribution List).

      For the response from the operation, please refer to https://hl7.org/fhir/operations.html#response on what needs to be returned. This will be added to the each of the operation's pages. 

      For all operations, add Operation Response and clarify that authorization is required for accessing the status of the member.

      Question 2: The IG does not use the Bulk Import specification currently and it is not required to implement the requirements of the IG.

      Question 3: The davinci-data-export is an export of the Attribution List by the Payer and the Consumer is invoking the API to export the Attribution List and hence the name export is used as part of the operation definition. The IG does not require or use the import operation currently and uses basic POST calls on the resources to create them. Please refer to the Capability Statements of the Producer and Consumers for further details on the operations that need to be supported. 

       

      Show
      All the questions have been answered, no changes are made to the IG. Question 1: The initial list creation by the Consumer in the Producer system uses the POST API on the Group resource and does not use the davinci-data-export operation. Thus an Import operation is not required for the creation of the initial list.  Once the initial list is created, the Consumer can use the member-add/member-remove APIs to add and remove members from the Group (Attribution List). For the response from the operation, please refer to https://hl7.org/fhir/operations.html#response on what needs to be returned. This will be added to the each of the operation's pages.  For all operations, add Operation Response and clarify that authorization is required for accessing the status of the member. Question 2: The IG does not use the Bulk Import specification currently and it is not required to implement the requirements of the IG. Question 3: The davinci-data-export is an export of the Attribution List by the Payer and the Consumer is invoking the API to export the Attribution List and hence the name export is used as part of the operation definition. The IG does not require or use the import operation currently and uses basic POST calls on the resources to create them. Please refer to the Capability Statements of the Producer and Consumers for further details on the operations that need to be supported.   
    • Nagesh Bashyam/Jeff Brown: 15-0-0
    • Clarification
    • Non-substantive

    Description

      Question 1:

      There is a need to define the import operation.  Here this operation seems to be suggesting that the difference between an import and an export when using the $davinci-data-export operation is a GET or POST.  Irrespective of whether the action is an import or an export the IG seems to be suggesting that the name of the operation in the API's URI is "$davinci-data-export".  However, the naming is confusing for the payer since we would be receiving the list from the provider's EHR as a starting point for STU2.  Will there be a "$davinci-data-import" operation defined as well or only the POST on "$davinci-data-export"?

      For the response from the operation, please refer to https://hl7.org/fhir/operations.html#response on what needs to be returned.

       

      Question 2:

      Thus, the IG needs to call out what the import operation and naming should be.  Also, the specs for the import operation are vague and we are unsure if we should be doing a synchronous or asynchronous API call.  The IG seems leave that decision up to the payers.  Is it a synchronous or asynchronous API call?

       

      Question 3:

      Moreover, there is no Bulk Data Import defined in the IGs.  Only Bulk Data Export and therefore we are unsure if the Import steps/process should be a reverse of the export or something else.  Finally, we don't know what the data structure is for an import but we have this (https://build.fhir.org/ig/HL7/davinci-atr/OperationDefinition-davinci-data-export.html) for the export.  What are the definitions for the Bulk Data Import and the respective data structure?

       

      Please advise on the above 3 questions.

      Attachments

        Activity

          People

            Unassigned Unassigned
            peartk Kelly-Ann Peart
            Kelly-Ann Peart
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: