Thanks for your reply. I am working with engineer Clayton Lewis on this matter. It seems that the update that takes place after the MPI link consists of an insert of a row containing a reference to a new HSAA.Patient entry, and a deletion of the row containing the old ID from HSAA.Patient (which now no longer exists). We are operating that the deletion does not occur because our version of the software requires that the analytics table be located in the HSAA root package. Incidentally, we are not able to test this hypothesis even with a custom container class object registration, because there is another error where the correctly qualified SQL table reference is not being generated.

Version string is: Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2017.1.3 (Build 317_0_18225U) Mon Aug 13 2018 12:48:50 EDT [HealthShare Modules:Core:15.03.1007 + Linkage Engine:15.03.1007 + Patient Index:15.03.1007 + Clinical Viewer:15.03.1007 + Active Analytics:15.03.1007]

Thanks so much for your reply. I greatly appreciate the information on how to get the Aggregation Key from the Viewer Cache. However, I have a question about one aspect of your reply:

You are correct that you can then use the Aggregation Key to query for the current patient's data in the Aggregation Cache.

Once I obtain the Aggregation Key, how do I go about querying the current patient's data in the Aggregation Cache? I had been thinking about querying the data from the HS_SDA3_Streamlet.Abstract table, but my understanding is that that table is located on the Edge, and so querying this data would require usage of an ECP link, which is not good practice. Is there a table I can query on the Access Gateway?

Please advise.

Thanks.