# Transition from Reference Application to Bahmni

**URL:** <https://talk.openmrs.org/t/transition-from-reference-application-to-bahmni/6580>\
**Category:** Bahmni\
**Created:** [June 2, 2016, 3:59pm UTC](https://talk.openmrs.org/t/transition-from-reference-application-to-bahmni/6580 "2016-06-02T15:59:39Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![bharatak](https://talk.openmrs.org/user_avatar/talk.openmrs.org/bharatak/32/1960_2.png) [@bharatak](https://talk.openmrs.org/u/bharatak)\
**Post date:** [June 8, 2016, 11:38am UTC](https://talk.openmrs.org/t/transition-from-reference-application-to-bahmni/6580/11 "2016-06-08T11:38:54Z")

</div>

@mksd Your assumption is right about making the Ref App & Bahmni living side by side. It should work fine for all the existing modules developed till date. But eventually, we should arrive to a place where the work can be re-used by following a standard way of extending Bahmni. One suggestion could be to go by [OWA](https://wiki.openmrs.org/display/docs/Open+Web+Apps+Module) (for client side) + OMOD (for server side) and be integrated it into OpenMRS. Interested to listen more approaches.

Regarding the appointment module, one of our customers had a requirement of Appointment Scheduling module and we just plugged-in what is available in openmrs world. It was developed in a way that expects those patient attributes to be available in the system.

---

_[View the full topic](https://talk.openmrs.org/t/transition-from-reference-application-to-bahmni/6580)._