Details
-
Bug
-
Status: Closed
-
TBD
-
Resolution: Duplicate
-
Core 2.1.0
-
None
-
None
-
None
-
Undetermined
-
Description
For backwards compatibility with legacy Cohort implementation, and in order to be able to represent Cohort Membership as "always a member" regardless of recording a specific start date, we propose changing Cohorts to allow memberships with a null start date.
This has particular implications in the implementation of intersect/union/subtract methods. One should be able to construct two Cohorts, containing the same patients, and perform Set operations on these successfully even if the sets were constructed at different times.
This is in reaction to the talk conversation here:
https://talk.openmrs.org/t/reporting-module-row-per-diagnosis-report/12749
darius FYI
Gliffy Diagrams
Attachments
Issue Links
- is related to
-
TRUNK-5379 Cohort Membership: Resolve design inconsistents
-
- Closed
-
-
TRUNK-5380 Cohort Membership: Performance Issues
-
- Closed
-
-
TRUNK-5331 CohortMembership should not require a startDate
-
- Ready for Work
-
- relates to
-
TRUNK-5375 New Core 2.1 Cohort module significantly slows down Cohort manipulation
-
- Closed
-