Continuing from our discussion on advancing Cohort support for patient lists, the platform team has cleaned up the cohort module (moving cohort-level visit/encounter/program/obs and cohort role features currently only used by AMPATH into a separate module). As we work to prepare the leaner cohort module to serve as a foundation for cohorts in the OpenMRS Platform and support the needs for patient lists, we have a question of implementers & application teams:
Our initial design was to support these levels:
||Can do anything with cohort (edit, rename, delete). Effectively, one of the owners of the cohort.|
||Can make changes to the definition (e.g., add or edit members for manually managed cohorts or edit the definition for cohorts based on criteria or an expression).|
||View members of the non-public cohort, but cannot make changes|
But for now, we thought that
View could suffice, saving
Edit for a future iteration.
Would this (admin & view support) meet any near-term needs of OpenMRS 3.0 patient lists?