Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

What this module does

The module exposes the OpenMRS API as REST web services.  if an OpenMRS instance is running the Webservices.REST module, other programs (and languages) can connect to retrieve and post certain information to an OpenMRS database.

Downloads

Source at: https://github.com/openmrs/openmrs-module-webservices.rest
Download at: http://modules.openmrs.org/modules/view.jsp?module=webservices.rest

Example Client (SVN) https://project-development-software-victor-aravena.googlecode.com/svn/trunk/ClientOpenMRSRest/

User Documentation

Required OpenMRS Version

The REST Web Services module requires at least OpenMRS 1.9.0 or 1.8.1 to run.

Configuration Options

Unknown macro: {html}

<dl>
<dt><b>webservices.rest.maxResultsDefault</b></dt>
<dd>This [Global Property] determines the maximum number of resources that can be accessed on any webservice call.  The default is 50.</dd>

<dt><b>webservices.rest.maxResultsAbsolute</b></dt>
<dd> This [Global Property] determines the absolute maximum number of resources that can be accessed on any webservice call. If the client requests more than this limit, then receives an error. The default is 1000.</dd>

<dt><b>webservices.rest.uriPrefix</b></dt>
<dd>This should point at the root of your exposed web application.  This is typically <i>http://localhost:8080/openmrs</i> during testing, but after being deployed will be something like <i>http://192.168.1.100/openmrs</i> or <i>http://yourdomainname.org/openmrs</i>. If this is empty or not filled in, the user will see NEEDSTOBECONFIGURED/ws/rest/ as the "self" urls on all objects.</dd>

<dt><b>webservices.rest.allowedips</b></dt>
<dd>By default this is an empty string: "", which means anyone can access the rest URLs. If you put any IP addresses into this list, only calls from those are allowed. IPs should be separated by a whitespace or a comma. IPs can be declared with bit masks to denote whole subdomains e.g. 10.0.0.0/30 matches 10.0.0.0 - 10.0.0.3 and 10.0.0.0/24 matches 10.0.0.0 - 10.0.0.255. Non matching IP addresses will receive a 403 HTTP error. Both IPv4 and IPv6 addresses are supported.</dd>

</dl>

Technical Documentation

The module exposes the OpenMRS API through light-weight resource objects off of the core OpenMRS objects. The structure is very similar, but not guaranteed to match up exactly.

This module uses Spring 3 annotations to expose URLs. Primary transport language is currently JSON with XML to be added at a later date.

For Creators of Web Service Core/Module Methods

Adding a Web Service Step by Step Guide for Core Developers
Adding a Web Service Step by Step Guide for Module Developers

For Web Service Client Developers

See [REST Web Services API]

Development History

Initial project page: Enhanced Web Services (Design Page)
Development sprint 1: [2011-05-16 Development Sprint]
Followup sprint: [2011-05-30 Development Sprint]
Development sprint 2: [2011-07-05 Development Sprint]
Development sprint 3: 2013-02-07 [RES:Integration of RESTWS]

Example Client code

Release Notes

  • 2.0 (see [docs:Migration from REST 1.x to 2.x])
    • Integrated Webservices.rest 1.9 extension module
    • Removed controllers (single point of entry)
    • Added search handlers
    • Added support for Concept mappings
  • 1.1
    • (23 bugs/features fixed/added)
    • Fixed concept.answers
    • Fixed patient.identifiers
    • Made more resources editable
    • Added ability to return retired resources generally
    • Added Provider and Visit support to the 1.9ext module
  • 1.0
    • Main functionality realized with no new bugs
  • 0.9 (Beta)
    • Bugfixes
  • 0.8 (Alpha)
  • No labels