At this moment, CohortMember is modeled as a subresource of Cohort. However, since the CohortMembers are patients, and we allow creation and editing of CohortMembers, we now are breaking caching for patients. It seems to me we have a few possible ways to fix this: (1) not support POST or DELETE for CohortMembers; [makes CohortMember sort of hokey] (2) use GET on a Cohort with a parameter (e.g. ?evaluate) to produce a list of members; [makes Cohort GET polymorphic] (3) use PUT on a Cohort to produce a list of members; [PUT?] (4) have an Evaluate resource that would work with various types of definition objects (e.g. Cohort, LogicRule, Form, Report). [probably would require parameters to identify object and POST for passing parameters to the object]
_________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
