We are helping an NHS client to migrate their integrations to a new platform (InterSystems). They have a some live MESH interfaces running on the old platform, and a mailbox so do not (necessarily) need a new mailbox. I understand InterSystems have conformance for their MESH API client code.
How is onboarding handled when the deploying organisation are not new, but the product is?
Hi Adam,
If you are switching your MESH mailbox from being managed by the Java MESH Client to being managed by InterSystems’ MESH API client code for which they already have a MESH API Conformance Certificate, no further onboarding is required.
You will just need to ensure that you stop your MESH Client before you bring the MESH API client code online to prevent the two from interfering with one another.
Kind Regards
Paddy
Thanks Paddy, will we still be able to test the new API code in INT?
Hi Adam,
Yes, the Path to Live INTEGRATION environment is available for you to test the API code. If you don’t have any mailboxes, or a TLS certificate, please email the ITOC Support Desk who manage the PTL environments and they will happily create them for you. Their email is itoc.supportdesk@nhs.net
Regards
Paddy
If the NHS Client are migrating from using the MESH Java Client to use Intersystems Direct integration method, there is one thing you may also need to consider. This is whether a new TLS certificate is requested for direct integration to the API as opposed to a Java Client version. Getting this update at the point of migration will help prevent any delays/issues when the TLS certificate expires.
Hi Nigel, and thanks, good point.