Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Multi-source configuration in data pages

Updated on April 23, 2021

Pega Foundation for Healthcare provides an option to conditionally invoke a source of data i.e., a FHIR repository (or) Pega database. These out-of-the-box (OOTB) settings allow implementors to easily configure various sources of data based on business needs.

Pega Foundation for Healthcare

This configuration is readily available for below data pages related to member, clinical and care information:

Object typeData Page
Member

D_PatientSearchResults

D_Member

AllergiesD_GetAllergies
ConditionsD_GetClinicalConditionByMember
EncountersD_MemberEncounterDetails
MedicationsD_PatientMedications
ObservationsD_ObservationsByLoincNum
Family Medical History

D_GetNonClaimMedicalHistory

D_FamilyMedicalHistoryByMemberID

we have overridden the above data pages from PegaHCCore layer in PegaHCFhir layer to configure the multiple sources. Hence applications built on top of PegaHCFhir application module can only leverage this feature.

Below data page is configured to conditionally invoke the data source of choice.

Below when rule determines the data source from a configuration data page.

Dynamic settings for configuring data source:

The data sources for all configured resources are fetched through a dynamic settings data page called D_CheckDataSource

The data source configured to fetch the source is a Data Transform rule called CheckDataSource. The rule is configured with PEGA DB as a default source. The rule is marked for Extension and is expected to be updated in your application with the data source of your choice for the different resources.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us