Skip to main content

Data modeling

Suggest edit
Updated on January 29, 2021

Data modeling is the process of creating a logical representation of the data stored in your database. By modeling data, you bring information into your application in a format that makes sense for your business.

How it works

The data model defines the types of information in your application, such as patient records and physician profiles, and their relationships to one another. For example, your data model might represent the data used by your application to retrieve patient data from a database, pass the home address and medical codes to a service that returns a list of physicians, and then format the results so that case workers process service names and descriptions instead of numeric medical codes.

The following figure illustrates the relationships among components in a data model for a sample billing application.

Example data model

Data models for physicians and patients

Key terms and concepts

To model data, you need the following components:

Data objects
Categories of data that have fields, field mappings, and connections to data sources.
Fields
Properties that store and format the data in your application.
  • Best practices for data modeling

    Follow best practices to save time developing and maintaining your data model.

  • Troubleshooting errors in your data model

    To improve application quality, resolve the errors about the different elements in your data model.

  • Exploring the data model

    Understand the relationships among case types, data objects, and properties in your application by using the Visual Data Model. In addition to viewing relationships, you can add and modify fields, and drill down to the data model for a particular data object or case type.

Did you find this content helpful? YesNo

85% found this useful

Have a question? Get answers now.

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

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