Duplicates for EVERY HS.Message.PatientSearchRequest?

Question

Question

Scott Beeson · Oct 12, 2016

If I run SELECT * FROM HS_Message.PatientSearchRequest ORDER BY ID Desc every row has a unique ID but every other row is an exact duplicate. Why would this be?

Discussion (7)0

Log in or sign up to continue

Justin Lavoie · Oct 12, 2016

I wasn't able to reproduce this result on my system so I can't be sure, but here are some thoughts:

1) It could be that incoming PatientSearchRequest on your system are immediately forward to another component that also forwards them with little or no change, creating two very similar PatientSearchRequest objects. Try going to Ensemble > Message Viewer and looking through the trace diagrams of PatientSearchRequest coming in through HS.Hub.HSWS.WebServices to see if a pattern like this exists.

2) Check the HS_Message.PatientSearchRequest_AdditionalInfo table for more information about each patientsearchrequest

1 0

Jose Ruperez · Oct 13, 2016

I can reproduce. Like someone said before, I get one message going from the business service to the MPI manager and then a second one, exactly the same, from the MPI manager to the HSPI operation. Nothing strange.

1 0

score 0 · Answer 1 · 2016-10-12T14:27:47-04:00

I found that half of them have a value in the RequestId column and the other half don't. All other columns are identical. What is the cause/reason for this?

score 0 · Answer 2 · 2016-10-13T10:13:07-04:00

Looks like it's something to do with our custom consent. I don't completely understand it, but if I limit the SourceConfigName to HS.Hub.MPIManager it obviously eliminates the duplicates.

score 1 · Answer 3 · 2016-10-13T10:08:25-04:00

Just out of curiosity, which part of HealthShare are you running these queries? Are you looking on the Access Gateway, Edge Gateway, Registry?

They all use the same message structure, but in different parts of the "request/response" cycle. The "facing the outside world" context is the Access Gateway, the rest are more "internal to Information Exchange" propagating of the request and motivating the various parts to gather the response, so it's quite likely that (as Justin mentioned) there can be replications of the message content into "new message" records that are NOT actual "new requests".

When you look directly at the SQL table outside of the context of the complete message trace (i.e. a "Session") it should be expected that you will see what appears to be exactly the same content in multiple messages in the table.

score 0 · Answer 4 · 2016-10-13T10:19:08-04:00

I'm simply fumbling around in my never ending quest to find holistic queries that answer basic questions. Right now I'm querying the registry. I don't have SQL access to the buses or hsaccess and we have dozens of edges so that isn't convenient Since the ATNA log is 600+ million rows and takes hours and hours to query (and decypher), HSREG is really my only option.

score 0 · Answer 5 · 2016-11-04T10:24:03-04:00

Yeah, I realized if I join this with the ens_message.header table I get the "source" and "target" configs and they differ which makes more sense.

Thanks for confirming what I'm seeing though.