Contacting the OCVC helpline with a query
Contact us
For further support and to enable us to deal with your enquiry effectively make sure you include the following information when you contact us:
- organisation name and ODS code
- description of the issue.
- specify if the issue is about a Test submission or a Live submission.
- date and time of submission.
- number of files submitted.
- MESH mailbox ID
- how are you sending the data to us: MESH API, MESH Client or MESH UI?
- contact name
- contact email
Further support
LocalID field in the .ctl file
We recommend you populate the localId field with the file type of the submission i.e. either "JSON", "XML" or "CSV".
Organisation name
Supplier organisation codes and names should be exactly as per the NHSD spine services directory. To find out your organisation name, append your organisation code to the end of the following URL and it will be returned in the JSON response as the "Name" element https://directory.spineservices.nhs.uk/ORD/2-0-0/organisations/
For example, Doctorlink with organisation code 8JM39 returns the organisation name "DOCTORLINK": https://directory.spineservices.nhs.uk/ORD/2-0-0/organisations/8JM39
Submission reports from the pipeline
First, check that your MESH message has been sent successfully by confirming that you have received a message back from MESH indicating that MESH has delivered your submission with a SUCCESS <status> field.
If you have confirmed that MESH has transferred the message from your mailbox to the OCVC pipeline mailbox and still have not received a submission report back after waiting a couple of hours, please contact the OCVC helpline.
CSV submissions
When using a CSV submission, if you have no data for a particular table you do not have to send a blank file, just exclude this file from your submission and the pipeline will process just the tables it receives. Similarly, if a supplier only collects online consultancy data and not video consultancy then there is no need to send blank VCAgg, VCPractice and VCRecord data.
Failed to read CSV file table not found error
For a CSV submission, this error is generated when the pipeline cannot determine which table the submitted file belongs to.
Please ensure that all the fields applicable to each table are included in each file. If a field is misspelt or missing then the pipeline will reject the submission with the error "Failed to read CSV file Table not found".
Last edited: 17 August 2023 11:56 am