User story:
We may need to remove the version number from the importer template/script. The user will not have information on how to go about tracking the version number for each resource. At the moment, any mismatched version number stops the tool from updating resources to the HAPI FHIR Server
Acceptable behavior :
Each import should update the current version of the resource in case there is a change to the fields that are being submitted for import from the CSV template provided
User story: We may need to remove the version number from the importer template/script. The user will not have information on how to go about tracking the version number for each resource. At the moment, any mismatched version number stops the tool from updating resources to the HAPI FHIR Server
Acceptable behavior : Each import should update the current version of the resource in case there is a change to the fields that are being submitted for import from the CSV template provided