This was the project page used while designing the Webservices.rest Module. See that module's documentation for the most up-to-date information

Background

OpenMRS has an explicit API which has not been cleanly or explicitly exposed through web services.  We have a REST module and SOAP-based module(s) where folks have done work in the area.  We need a clear and explicit strategy for supporting web services.

Requirements

API Service and Object Design

Action Plan

  1. Web services will be developed as an augmentation to the existing API... that is, we will not rewrite the current API and then expose them as web services... we will write the web services as an independent activity, hoping that they inform the further maintenance and redevelopment of the existing API.
  2. Support OAuth or an equivalent authentication scheme
  3. An upcoming web services sprint is scheduled. See Development Sprints and the ws sprint page: 2011-05-16 Development Sprint

Interested Parties and Mentors

Unknown User (bwolfe) (mentor)

Burke Mamlin

Unknown User (darius)

Unknown User (sunbiz)

See Also

Result / Output

See the REST Module for the documentation and final output.