We currently use the MESH client and MESH UI for a workflow ID (SPINE_OVM_READRESP_DSC1) that allows an OVM (Overseas Visitors Manager) working in Secondary Care (or other authorised user) to submit a list of NHS Numbers with identifying Date of Birth and optional Family and Given Names to Spine via MESH and receive relevant demographic and Visitor and Migrant (V&M) data in response.
This is currently an ad-hoc (MESH UI) or over night (MESH Client) process. We are currently exploring the feasibility of using the MESH API with this workflow ID (SPINE_OVM_READRESP_DSC1) to send a batch query based on A&E activity in certain intervals (let’s say every 15 mins).
Our integration engine is Intersystems, which provides a MESH API adapter and we are already using it for other workflow IDs, so they have the technical conformance to use the MESH API.
For the Path to Live - Integration environment, we got a MESH mailbox created to be used with this workflow ID (SPINE_OVM_READRESP_DSC1) and the MESH API. During our initial exploration with Postman to send and read MESH messages, we found it only works when a specific header is there in the request,.i.e “mex-partnerid” that too in a particular format as below “MESHCLIENTUPLOAD|USERID|ORG Code”.
Is the MESH API then not approved to work for this workflow ID (SPINE_OVM_READRESP_DSC1), how can we get our use case approved for Production through our Integration Engine (Intersystems)?