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

Versions Compared

Key

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

...

Operations
URLDescription
/ws/fhir/Patient/{id}
  • If the Patient with the given uuid exists, update the existing attributes according to the representation.
  • If the Patient with the given uuid doesn't exists, Create a Patient Resource with the given uuid.

Update operation cannot update an existing name or address. If you don't wish to update an existing name or address, you should keep those fields empty. All names and addresses contain in the representation will be added to the Person resource, as new names and addresses.

Conditional Update
/ws/fhir/Patient?[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/Patient?name=John

/ws/fhir/Patient?givenName=John

 /ws/fhir/Patient?identifier=432MN

OpenMRS

...

specific constrains

  • When you POST a Patient name and gender attributes are compulsory. In the name attribute there should be atleast one "usual"/"official" name.
  • When you Update an existing Patient Name/Adresses, the existing names and addresses will be retired and new name/addresses will be created. 
  • A valid Patient identifier is required.