9.2.3. Uploading data¶
- How do I obtain a template to upload my data to the MDS?
- What do I do if I have collected the data in Excel or Access?
- Should an upload file only contain new or changed data or should it contain all cumulative data from the start of service delivery?
- How can I edit a record I have previously uploaded?
- How can I delete a record I have previously uploaded?
- How can I review why the status of my upload file shows error?
- How can I view my uploaded data?
- How do I upload the individual CSV files?
- How do I fix upload file errors?
- How do I fix data errors in an upload?
- Has my data uploaded if my file has an error status?
- Will valid data be accepted if there are errors in the file?
- If validation rules change how will you treat legacy data?
- I am receiving an upload error that has a code that is not in my records. What should I do now?
- I am receiving an unknown error in my records. How can I fix this?
- Why am I receiving an error saying I don’t have permission to upload organisation data?
- Why am I receiving an error saying ‘Could not find worksheet [Name]’?
- Why am I receiving an error saying ‘Column [Name] is not valid’?
- Why am I receiving an error saying ‘Organisation_path is not valid on row ….’?
- Why am I receiving an error saying ‘PMHC MDS does not support version 1’?
- Why am I receiving an error saying ‘Column [Name] is required on row …’?
- Why am I receiving an error saying ‘Invalid file …’?
- Why am I receiving an error saying ‘Could not parse worksheet [Name]: Bad request at …’?
Upload templates are available from Upload specification.
Visit the online MDS documentation regarding uploads were a detailed user guide for data uploads is available.
See Upload specification.
220.127.116.11. Should an upload file only contain new or changed data or should it contain all cumulative data from the start of service delivery?¶
All data should be uploaded for the first upload, but subsequently only new or changed data should be uploaded. However, parent records of new or changed data also need to be uploaded in order to keep the file internally consistent.
An example of what this means is that if a service contact record is added or changed, there must be a corresponding episode record in the episode file and a client record in the client file, even if the episode and client data hasn’t changed. Also, as service contacts refer to practitioners, there must also be a practitioner record in the practitioner file.
There is a unique identifying key associated with every record in the PMHC MDS. When you upload a record with the same unique identifying key with updated data, the MDS will recognise the record’s key and update the data already recorded in the system.
When the upload has completed successfully, you will see a summary of the updated records shown in the ‘Upload Change Summary’ table displayed in the View Upload Details for complete uploads. See Complete uploads.
You can delete records via upload.
Please refer to Deleting records.
If the status of your file shows error, you can view the returned errors through Viewing Previous Uploads.
Refer to Error messages.
When the upload has completed successfully, you will see a summary of the updated records shown in the ‘Upload Change Summary’ table. See Complete uploads.
If you have the reporting role, you can produce system reports or extract recorded data. See Reports.
The CSV files must be compressed into a single file by zipping before upload. The filename of the zip file doesn’t matter as long as it has the file extension .zip All the required CSV files must be included for each upload, even if the file contains no data. If choosing to include any optional CSV files, these must be included with the required files in the single upload zip file.
See Upload specification.
Refer to Record formats related to column name for each error. By clicking on the field name this will take you to the field definition which outlines the associated notes that provide guidance on which response to use.
If still unsure, please email the PMHC helpdesk on email@example.com and provide a copy of the error email, and/or a screenshot if possible. The error email is very important for the Helpdesk to quickly identifying the error and to provide you with a clear response on how to rectify the data issue.
No. Only ‘Complete’ uploads that are not in test mode, are recorded in the PMHC MDS.
For example, if we upload 200 lines of service contacts, and there are validation errors in 10 lines - will 190 lines be accepted?
No. All files and records in an upload have to validate before any data is accepted.
When implementing new validation rules or changing existing rules, where possible we prefer to enforce the new rules as of a certain date.
For example, if a data field that is now optional where to be made mandatory, we would specify that it was mandatory as of a particular date. For any data previous to that date the field could still be optional, but for any data after that date the field would be mandatory.
18.104.22.168. I am receiving an upload error that has a code that is not in my records. What should I do now?¶
We have implemented an upload error log that reports when an error is not providing the relevant details. The error log code will be reported to the user after the error message, for example [ABC123ZY]
The [AW97AZRX] error code refers to our internal error log. With this error code, we will be able to quickly source you the relevant key details for this record. And this error log is also reviewed by our developers to diagnose and fix the specific error to ensure that the system reports the relevant details/keys for future uploads.
If you receive this types of errors message, please email the PMHC Helpdesk on firstname.lastname@example.org and provide a copy of the entire error message along with the error code.
If you receive an ‘unknown error’ message, please email the PMHC Helpdesk on email@example.com and provide a copy of the error email, and/or a screenshot if possible. The error email is important, and will assist the helpdesk to quickly identify the error, and provide you with a clear response on how to rectify the issue.
If you receive an error message stating ‘Upload file contains organisations data, but user doesn’t have Organisation Management role’ you do not have permission to upload organisation data. (The Organisation Management role is only available for PHN users - see Users Roles)
The ‘Organisations’ data is optional and does not need to be included in the uploaded file. Please delete the ‘Organisations’ worksheet/file from your upload.
This error occurs when you are uploading and Excel spreadsheet. The worksheet names need to exactly match the name in the ‘Excel worksheet name’ column of the ‘Summary of files to upload’ table at Files or worksheets to upload. If all the required worksheets are not present you will receive the error above.
Each item is a column in the file/worksheet. The ‘Field Name’ should be used for the column headings. These values can be found at File format, or listed on the provided example file at Files or worksheets to upload. If the Column [Name] doesn’t match identically you will receive the error above.
The organisation path provided does not map to a valid organisation. The format should be a combination of your PHN key and the provider organisation key, separated with a colon. Example PHN_key:POrg_key. If the organisation path doesn’t match identically you will receive the error above.
As of 1st July 2020, the PMHC MDS does not support version 1 of the PMHC specification.
Uploads using version 2 and above should use a metadata file or worksheet. The metadata information is documented in the upload specifications on either the core specification or an extension. See Data Specifications.
There is a required field that has not been entered. If not supplied, insert the default ‘Missing’ or ‘Not recorded’ value. These values can be found at Record formats. If the Column [Name] is blank in a mandatory field you will receive the error above.
The system is having trouble identifying your upload file. Please provide a copy of your upload file to firstname.lastname@example.org.
Something has gone wrong with the upload. Please contact email@example.com.