Industry foundation data model benefits
Pega's industry foundation data models allow you to leverage and extend an existing logical data model instead of building one from scratch. Pega offers industry data models for Healthcare, Communications and Media, Life Sciences, Insurance, and Financial Services. Instead of building data classes yourself, you can map the system of record properties to the data class and properties of the industry data model.
You can embellish the industry foundation data classes to include additional properties from external systems of record as needed.
Pega's industry foundation data models apply the Separation of Concerns (SoC) design principle: Keep the business logic separate from the interface that gets the data. The business logic determines when the data is needed and what to do with that data after it has been retrieved. The interface insulates the business logic from having to know how to get the data.
In Pega Platform, data pages connect business logic and interface logic. The following image illustrates the relationship between the data page, the data class, and the mechanism for retrieving the data.
This design pattern allows you to change the integration rules without impacting the data model or application behavior.
Rather than directly extend the industry foundation data model, your project may mandate that you use an Enterprise Service Bus (ESB) dictated data model. An ESB aims to implement a canonical data model that allows clients who access the bus to talk to any service advertised on the bus.
In a situation where an ESB is used, the Pega development team does not define the canonical data model. However, the team may maintain the mapping between the canonical data model and the foundation data model.