# REST API for Programs

**URL:** https://talk.openmrs.org/t/rest-api-for-programs/6615
**Category:** Development
**Created:** [June 5, 2016, 12:09pm UTC](https://talk.openmrs.org/t/rest-api-for-programs/6615 "2016-06-05T12:09:30Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [June 6, 2016, 5:47pm UTC](https://talk.openmrs.org/t/rest-api-for-programs/6615/4 "2016-06-06T17:47:57Z")

</div>

@jdick as you surely noted from Pascal’s link, we named the REST resource “programenrollment” (though it’s PatientProgram in the underlying data model), because this is more consumer-friendly.

Also, note that there is work happening in the community on Episodes Of Care ([Episodes Of Care: Coordinating Bahmni & eSaude needs & work](https://talk.openmrs.org/t/episodes-of-care-coordinating-bahmni-esaude-needs-work/4618)) and you should consider this an alternative. (Programs exist already, they are tried-and-true, but technically they’re supposed to be representing administrative/programmatic enrollment and state, rather than clinical status.

---

_[View the full topic](https://talk.openmrs.org/t/rest-api-for-programs/6615)._