If your GPIUS file has not processed, it is usually caused by one of the issues listed below. Please review each point and correct your file where needed.
Common reasons for GPIUS file failure
The file name contains more than one full stop.
Example of invalid filename:
09092022.HPT.csv
Corrected version:
09092022HPT.csv
Ensure the filename contains only one full stop, the .csv extension.
The filename is longer than 60 characters.
Shorten the filename so that it contains fewer than 60 characters, excluding .csv.
The file contains more than 5000 records.
Split the file into smaller files with fewer than 5000 records each.
Identical files have been uploaded.
If an identical file has already been processed or uploaded, the system will reject the duplicate.
The file contents are in the wrong format.
Check that all fields and values follow the correct GPIUS template format.
The file points to the wrong system name.
Example: using LIVE when the actual system name is RIOLIVE.
Update the system reference to the correct live environment name.
The file contains clients who already have the immunisation.
The system will prevent duplicates and reject records already applied.
The same client appears in two files processed at the same time.
This triggers warnings such as identical immunisations skipped.
Process files separately to avoid overlap.
Incorrect ImmunisationUploadLocation setting.
Check that ImmunisationUploadLocation in Global.CommonRioInstance is set to the correct system name.
If issue persists
If your file does not match any of the above reasons, please type talk to a person in the Digital Assistant to connect with a live support agent.