Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
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
-
-
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.