Basically, whenever we submit a message into the MHA PDS submission, we get a message identifier back, which they call a "Bundle ID".  So I went looking for these Bundle IDs and confirmed that we were getting them back for our submissions.  


The way I am checking is to go into the CBI MHA PDS Outbound channel in Mirth.  This is the channel that actually does the web service call to submit data into the MHA PDS Submission (so is the final channel that executes in the submission). 
From there, the destination that actually does the submission is "Outbound to OH MHA PDS" and so I clicked on that destination, then under the message pane below, clicked on the "Response" radio button - this will display the actual response from the submission service.



From there, I looked for the key value of "id", which is typically the second line (in the red box above).  So the Bundle ID returned in the example above was 775798.

To know what Org the submission is associated with, just go into the channel map and take a look for the OrgID variable  




If any messages requires re-processed based on date, we can use the below script.


DECLARE @orgID int, @messagelike varchar(20), @lastdate varchar(20);

 

SET @orgID = 10800;
SET @lastdate = '2023-02-16';

 


SET @messagelike = '%' + CAST (@orgID as varchar(20)) + '%';

 


select COUNT(1) FROM App_QueueArchive
WHERE ApplicationName like '%mha%' and Message like @messagelike
and ArchiveDate >= @lastdate

 


INSERT INTO App_Queue
select QueueId, MessageId, MessageTypeId, ApplicationName, DestinationApplicationName, MessageURL, ContentType, Message, CreateDate, LastSent, NumberSent FROM App_QueueArchive
WHERE ApplicationName like '%mha%' and Message like @messagelike
and ArchiveDate >= @lastdate

 


DELETE FROM App_QueueArchive
WHERE ApplicationName like '%mha%' and Message like @messagelike
and ArchiveDate >= @lastdate