Previously, a Care Journey was built by first creating an Encounter in the Care Journeys Targeting screen using Encounter Config. An Encounter was defined as one or more patient/diagnosis code groups (which are created in Markets). Then, you could create a Care Journey by mapping two Encounters over time using the Care Journeys Configuration.
Now, Care Journeys are built entirely in Markets, and the terminology has been updated:
Procedure / Diagnosis Group: Unchanged. A collection of codes that define a specific clinical event.
Patient Code Group: Previously called a Care Journeys Encounter. Uses one or more Procedure/Diagnosis Groups to represent a point in time when a patient had one or more of the associated codes recorded.
Patient Pathway: Previously called a Care Journeys Configuration. Created by mapping two Patient Code Groups over time. It can be used as a Strategy in Patient Cohort Targeting and may also represent a Care Journey visualized in charts.
Admin changes:
The CJ Admin role is being removed.
Users can only configure Care Journeys if they are an Org Admin or a Markets Admin.