Patient Program Outcome Management uses Einstein generative AI to generate patient and
program outcome summaries. These summaries are generated using a screen flow, which in turn uses
context service to fetch the data. Before context service performs its magic, you must turn on
context definition.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health Cloud
or Life Sciences Cloud, and Einstein GPT Platform and Einstein GPT Prompt Builder
Add-On licenses
Patient Program Outcome Management comes with two predefined context definitions,
CareProgramOutcomeSummary and PatientOutcomeSummary, that enable the efficient retrieval and
consumption of data in program and patient outcome summary.
Important You can’t edit or remove the CareProgramOutcomeSummary and
PatientOutcomeSummary context definitions. If you want to change anything, first clone it, and
then make the changes.
Each context definition has two mappings, CareProgramSummaryMapping, and
OutcomeSummaryMapping. These two mappings are created to fetch data for indicator results at
the care program and outcomes levels.
CareProgramOutcomeSummary
The CareProgramOutcomeSummary context definition hydrates data for program outcome summary
generation. The nodes and attributes in this structure are mapped to the Indicator
Assignment, Indicator Performance Period, Indicator Result, and Outcome Activity
objects.
PatientOutcomeSummary
The PatientOutcomeSummary context definition hydrates data for patient outcome summary
generation. The nodes and attributes in this structure are mapped to the Indicator
Assignment, Indicator Performance Period, Indicator Result, Party Indicator Result, and
Outcome Activity objects.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
