Hi everyone,
I’m in a bit of a pickle trying to make my SSIS pipeline submit ePMA XMLs to MESH API (because the Java Client is not an option for us - hard ‘no’ from IT).
I’m going through the onboarding process, my manager’s manager has a mailbox that we’re going to use, so I don’t think I need to request a new one. (Though I don’t know if it’s used for anything else - guidance says there must be one thread only and if this is the case, our trust is merging with 2 others that I need to submit - can I do that in the same thread and just name the files accordingly or will I need a new thread for each trust?)
So far, I’ve been chasing this down a rabbit hole and testdata reckon I needn’t have come this far. Anyway, I went to request a TLS certificate on the CSM portal but my SSO doesn’t work and I’ve had no response from the support team after emailing.
To sum it all up, I’m feeling pretty lost. Do I need to connect to Spine and send test data or is this more for third-party developers? Has anyone else had problems with the CSM Customer Service Portal - Customer Support?
Thanks folks.
Hi Cory,
I’m sorry to hear that your experience has not been good.
Which email address did you try and contact the the support team on?
If you need a TLS certificate and the CSM portal is not working for you, please email your Certificate Signing Request to the National Service Desk via ssd.nationalservicedesk@nhs.net
Until you have completed MESH API Onboarding, you will only be able to request a TLS certificate for use in the Path to Live INTEGRATION environment.
Kind Regards
Paddy
Hi Paddy,
I sent the email to itoc.supportdesk in response to them sending me a CSR form.
I phoned the service desk today, who said it was something my local IT should sort-out, who then said it was definitely NHSE’s job, that they hadn’t created an account to link to my SSO.
So I phoned again and it was sorted in minutes.
When you say “until you have completed MESH API Onboarding, you will only be able to request a TLS certificate for use in the Path to Live INTEGRATION environment”, do you mean I cannot complete onboarding without having first tested my solution in the Path to Live INTEGRATION environment? Meaning I categorically do need to request a mailbox and TLS cert for test?
I’m led to believe that for my case, no connection to the test environment is necessary. I feel there’s some ambiguity around this statement:
I read it as: “Do you need X for (Y or Z)” = X for any case.
Instead of: “Do you need X for Y; or do you need X for Z” = Xa for one case, Xb for the other.
Many thanks.
Hi Cory,
Unless you are using the Java MESH Client or the MESH User Interface, it suggests that you are therefore using some software that you (or a supplier) have developed to connect to the MESH API. You will need to go through an onboarding process to demonstrate that what you are using conforms to the MESH API specifications and a witness test needs to be carried out to prove that it does.
Onboarding takes place in the Path to Live INTEGRATION environment.
You will be required to register your product and provide details of your use case. Once your use case has been approved, you will be sent details of the test cases that will need to be witnessed, along with instructions on how to request some MESH mailboxes and a TLS certificate in the INT environment so that you can test your API calls.
Only after successfully completing the MESH API onboarding will you be issued a MESH API Technical Conformance Certificate (TCC) that will allow you to use your product in the Live PRODUCTION environment. Agents creating MESH mailboxes and TLS certificates in PROD for use with your own software that connects to the MESH API will ask for a copy the MESH API TCC as proof of onboarding.
The MESH mailbox request form allows you to request a mailbox for either environment but if you choose Live, your request will be rejected down the line if you are not able to provide a MESH API TCC.
Kind Regards
Paddy
