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

Versions Compared


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


/ws/fhir/Encounter/{id}This request will retire the Encounter with the given uuid. If the resource does not exist, a 404 is returned. If the OpenMRS API refuses to retire the encounter, the status code 405 is returned.

OpenMRS specific constrains

  • To implement FHIR Encounter we have used both OpenMRS Visit and OpenMRS Encounter resources. For every Encounter an OpenMRS Visit resource will be created. In a case where the patient is trasfered between different sections, a new OpenMRS Encounter will be created and that will be attached to the relevant OpenMRS Visit.