Entities with parent-child relationships

An entity is a group of participants that you want to monitor and analyze together. When you create entities with parent-child relationships, your dashboard offers a bespoke view of participant data.

Parent-child relationships among entities offer a few advantages:

• The dashboard shows the relationship among the entities.
• The dashboard organizes participant data the way that you analyze it.
• Permissions are a little easier to assign. For instance, someone with access to a parent entity also has access to all of its child entities.

However, you can also create standalone entities.

Example of entities with parent-child relationships

Your organization might want to create parent-child relationships among your entities. For example, consider the following hierarchy of participant groups for a chain of pharmacy stores:

• Store 1639
  • Store 1639 Employees
  • Store 1639 Clinic Customers
  • Store 1639 Prescription Customers
    • Store 1639 Prescription Customers - Acute
    • Store 1639 Prescription Customers - Chronic
  • Store 1639 Vaccinated Individuals

An Oracle Customer Success manager creates each of the bulleted entries as an entity. An organization can decide whether the parent entities (in this example, Store 1639 and Store 1639 Prescription Customers) have participants. Allowing parent entities to have participants is a good idea if you expect to add participants who aren't a logical fit for the child entities.

This parent-child approach, when paired with thoughtful entity planning, offers a few advantages:

• Faster data analysis on the dashboard and increased flexibility for data analysis.

  When you carefully plan your entities, you can easily monitor your population groups both separately and together on the dashboard.

• Easier assignment of permissions.

  A person who is granted access to a parent entity also has access to its child entities, simplifying your administrative work.

Example of entities without parent-child relationships

Here's an alternate way to group the previous entities:

• Store 1639 Employees
• Store 1639 Clinic Customers
• Store 1639 Prescription Customers - Acute
• Store 1639 Prescription Customers - Chronic
• Store 1639 Vaccinated Individuals

This flat structure allows you to analyze your entities both individually and together. However, when analyzing data, you might need a few extra clicks and filters to see the data that you're interested in. Additionally, setting up permissions might take a little big longer if multiple people are responsible for monitoring participant data.