RIM Persist ReferenceModifier.CREATE_OR_UPDATE/UPDATE causes excessive SQL execution
(Doc ID 2928553.1)
Last updated on FEBRUARY 23, 2023
Applies to:
Oracle Healthcare Data Repository - Version 8.1.3 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Healthcare Data Repository 8.1.3 version
ACTUAL BEHAVIOR
---------------
User noticed a performance issue and excessive SQL execution when the ReferenceModifier.CREATE_OR_OVERLAY is used.
When data is persisted and a ClinicalDocument created using the code below, the performance is acceptable:
htbDoc = (oracle.hsgbu.hdr.hl7.rim.Document)af.newAct(ActClass.DOCCLIN,ActMood.EVN, docCode, df.newSET_II(cdadocID2));
However, when trying to do an update to an existing ClinicalDocument using the code below, the user noticed a performance degradation:
htbDoc = (oracle.hsgbu.hdr.hl7.rim.Document)af.makeReference(ReferenceModifier.CREATE_OR_OVERLAY, ActClass.DOCCLIN, ActMood.EVN, docCode, df.newSET_II(cdadocID2), 0);
It appears that the SQL that's being generated is looking across all tables in HDR, not just the clinical document table.
EXPECTED BEHAVIOR
-----------------
It is expected that the creation and updating of ClinicalDocument using ReferenceModifier.CREATE_OR_OVERLAY should not have performance issue.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |