# Data model for the revised cohort definition

**URL:** <https://talk.openmrs.org/t/data-model-for-the-revised-cohort-definition/5999>\
**Category:** Development\
**Tags:** cohort-builder\
**Created:** [April 28, 2016, 5:34pm UTC](https://talk.openmrs.org/t/data-model-for-the-revised-cohort-definition/5999 "2016-04-28T17:34:26Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![darius](https://talk.openmrs.org/user_avatar/talk.openmrs.org/darius/32/8082_2.png) [@darius](https://talk.openmrs.org/u/darius)\
**Post date:** [May 11, 2016, 10:08pm UTC](https://talk.openmrs.org/t/data-model-for-the-revised-cohort-definition/5999/14 "2016-05-11T22:08:57Z")

</div>

Well, my suggestion is that you should do this work in a branch of openmrs-core, since I think that’s the most straightforward, and least likely to run into other dependencies.

If you’re doing this in a module, I guess that nothing prevents you from dropping a constraint on a table that’s in core, though any core code that references the table may break as a result. And in a module, to change the way that cohorts work you may have to jump through the hoops at the [Extending a Table Through a Module](https://wiki.openmrs.org/x/sw8z) wiki page.

---

_[View the full topic](https://talk.openmrs.org/t/data-model-for-the-revised-cohort-definition/5999)._