Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • Location Resource

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Read (GET Request)

Returns a FHIR Location resource identified by a Location UUID


  • Returns a FHIR location resource if the specified Location exists
  • Returns an Operation Outcome resource with a 404 error message if the specified Location does not exist
Search (GET Request)

Search locations by given id


Search locations by given status value whether active or not

Search locations by name
Delete (DELETE Request)
Will delete a location with given id
Conditional Update(Put Request)
/ws/fhir/Location?[search parameters]

When the server processes this update, it performs a search using its standard search facilities for the resource type, with the goal of resolving a single logical id for this request. The action it takes depends on how many matches are found:

  • No matches: The server performs a create operation
  • One Match: The server performs the update against the matching resource
  • Multiple matches: The server returns a 412 Precondition Failed error indicating the the client's criteria were not selective enough

Ex: /ws/fhir/Location?name=Colombia

PUT(Update Request)
/ws/fhir/Location/{id} or

Send location resource in PUT request body for given URI specified with resource Id will update existing resource while request going

to URI which doesn't have a URI will create a resource.

POST (Post Request)
Create a Location Resource for the given representation.