In CDH, Actions are not responded from container,if I use properties inside embedded data in any engagement policy ex.eligibility
In my CDH application, I want to reuse few of the data objects from Pega foundation for HC. Ex. clinical conditions.
I have included Pega foundation app as a built-on and In my main customer context class, i created a pageList to access the clinicalConditions data object (it is added as embeddedData in my main customer data object).
After marking it as relevant record for my engagement categories, I am able to use it in engagement policy- ex. eligibility.
But when i use one of the properties in this clinicalConditions, to check the eligibilty criteria, the actions are not sent in container response. when i remove these conditions and use those fields present directly in customer data object, it works
i.e. ClinicalStatus (in clinicalConditions) is equal to Active - as eligibility criteria.
Please help me if this is not the approach or any other options are available to reuse other existing data objects to define criteria for my actions.
***Edited by Moderator Marije to add Support Case Details**
SoftServe
DE
Just an update about this approach: I already used and added an association to the customer context in Data sources and configured it in profile Designer. Still i was not able to receive any actions in my container response.
Kindly help with your valuable suggestions to rectify the issue
Pegasystems Inc.
US
@Archana It is hard to follow your question without an understanding of the model of the data and the setup of the system. A few pictures of the context dictionary, an example of the data and the engagement policy conditions you are trying to use and for what situation would probably go a long way to explaining your question and getting further help.
SoftServe
DE
@Saleem_A thank you for the response. Below are the details about the issue I am facing.
Please refer to image - "myApp.jpg" - My CDH implementation Application - myApp , included PegaHC application for reusing pega foundation for healthcare data objects.
Please refer to image "dataSetsAssociated.jpg" for customer profile designer screenshot.
the primary customer context class is Org-app-data-patient. I have associated two other datasets to it in addition to History.
@Saleem_A thank you for the response. Below are the details about the issue I am facing.
Please refer to image - "myApp.jpg" - My CDH implementation Application - myApp , included PegaHC application for reusing pega foundation for healthcare data objects.
Please refer to image "dataSetsAssociated.jpg" for customer profile designer screenshot.
the primary customer context class is Org-app-data-patient. I have associated two other datasets to it in addition to History.
| DataSets | class | class's ruleset | Table schema | context |
| Patient | Org-myApp-data-patient | myApp-Rules | ExternalMKTData.Patient | Primary (inherited from PegaMKT-Data-Customer) - PatientID is the key |
| ClinicalCondition | PegaHC-Data-ClinicalCondition | PegaHC | pegaData.ClinicalCondition | Associated data (joined using PatientID - refer Association.jpg) |
| PatHist | Org-myApp-data-PatHist | myApp-Rules | pegaData.PatHist | Associated data (joined using PatientID ) |
all three of these datasets are present in Ruleset: myApp-Rules.
I have a property named ClinicalStatus in ClinicalCondition, with values Active/Inactive.
please refer to image "Criteria.jpg". In engagement policy (eligibility), I am checking ClinicalStatus (in ClinicalCondition) equal to "Active" to display my group of actions. Later I want to build other action engagement criteria's based on other fields present in this table.
-- But this fails to output any of the actions and not able to see the value present inside ClinicalCondition data object.
-- I have created PatHist data object to test the association to a new table and copied the properties (ClinicalStatus) to this class with some sample records. Used the same criteria as explained above. i.e checking ClinicalStatus (in PatHist) = Active- The actions are displayed and we are able to see the data inside PatHist.
But this is just a temporary workaround , as i would need to reuse so many other data objects also from the PegaHC application.
I undestand that we must use the primary context class inherited from PegaMKT-Data-Customer. so i created that Patient context instead reusing the class/data object from Pega foundation for HC.
Is it not possible to reuse the data from existing tables by creating an association to that existing class ? or please help me if this can be working using any other approach?
Pegasystems Inc.
US
@Archana , From the details you outline, both the associations (ClinicalConditions & PatHist) should behave the same way, so if it worked for one and its configured the same, it should work for the other. I shared this with a few colleagues and the only plausible explanation is that ClinicalConditions class/table point to a BLOB based data source and the data you are querying is not in exposed fields. I'm not directly knowledgable of the PegaHC foundation to know if this is the case.
I have 2 suggestions:
1. Open a support case for them to investigate.
2. If you are technical enough, run preview on the data flows that support the context dictionary to read in the data to make sure the data is actually accessible and available for the ClinicalCondition portion of the model. Support can help you with this if you are not able to. If the data is indeed in the blob, you will need to expose the columns you intend to use in your conditions.
SoftServe
DE
@Saleem_A thank you so much for checking this. Before getting your response, I came to an assumption that CDH criterias will not work with old class/table elements. I will create a support case to check if the issue.
In addition, following are the further details about dataFlow preview and other ways that I tried to make it work with old table data.
Yes, I ran the data flow preview (image dataFlow.jpg) and it could fetch the records that matches with PatientID and also the columns that I intend to use in my criteria. It also has a blob column but the PatHist does not have one.
The only difference between ClinicalConditions & PatHist is the Class hierarchy (PegaHC-Data-ClinicalCondition) and Ruleset (PegaHC).
Even if i create a new class in the CDH implementation application (myAPP) to point to the old table it is not reading the data.
Class:Org-myApp-data-ClinicalCondt and Ruleset: myApp-Rules
DB table instance to- pegaData.ClinicalCondition. this is the same old table where data fetch is working fine using old class and its Report Definitions, but not with the new class & respective RDs.
Pegasystems Inc.
US
@Archanaif the ClinicalConditions indeed has blob data, then make sure to expose/optimize the ClinicalStatus property, otherwise this will likely impact performance if not break things.
I also noticed and was reminded by the preview screenshot that ClinicalConditions is a page list. Your condition, however, is treating it like a page. For page list conditions, you must use the "Instances include" operator, by first clicking the + icon on the ClinicalConditions page list property in the condition builder. I've included 3 screenshots of how to do this. Without doing this, the condition will try to evaluate a page list a a page which is likely impacting you.
SoftServe
DE
@Saleem_A Thank you for the inputs. I have just tried this way and tested. Still the actions are not returned in results
The Case is same with PatHist, it is also a pageList with exact data mimicked as clinicalConditions where it works fine.
all the columns in clinical conditions, that are necessary for the criteria are already present in exposed columns. I double checked specifically for ClinicalStatus too in the DB Schema landing pages in pega.
Also, the support ticket is raised and waiting for their response . thank you again for the latest input with screenshots, it helps me in building other set of criterias.
Pegasystems Inc.
US
Hi @Archana,
Please let us know the Support Case ID so that we can link this thread to it to assist the Support Engineer who is looking into this for you.
Thank you!
Pegasystems Inc.
GB
@Archana I have added the Case details to this forum question which will help us track progress on the investigation, many thanks!