FHIR R4 Resource - Practitioner

OpenIMIS table - tblClaimAdmin

Endpoint specification:

Example of endpoint URL:

http://localhost:8000/api_fhir_r4/Practitioner/

Supported HTTP operation:

• CREATE - used to create new ClaimAdmin. List of supported fields can be found in the table which shows the mapping between OpenIMIS and FHIR. Should be used the POST HTTP method and the body as JSON representation (example can be found below).

  Note:

  • OpenIMIS ClaimAdmin created by using the Practitioner hasn't relation with OpenIMIS Health Facility

  • the `validity_from` attribute is set as the current value of date when the object is created

  • the `audit_user_id` - the user which interact with the FHIR API is the `TechnicalUser` (Backend security - Models and Concepts) which hasn't representation in tblUsers. That's why the value of the `audit_user_id` attribute is set based on the following algorithm:
    1) Try to get that value from the 'auditUserId' query parameter

    2) If missing get that value then use the value from the module configuration (by default 1)

• READ - by default return list of all available resources. To fetch information about a specific object you should add the primary key to URL for instance:
  http://localhost:8000/api_fhir_r4/Practitioner/UUID
  , where UUID is the value of the UUID key. Should be used the GET HTTP method.

• UPDATE - update the value of the specific object. List of supported fields can be found in the table which shows the mapping between OpenIMIS and FHIR. Should be used the PUT HTTP method and the body as JSON representation (example can be found below). The requested URL needs to point to a specific object to do that you should add the primary key to URL for instance:
  http://localhost:8000/api_fhir_r4/Practitioner/UUID
  , where UUID is the value of the UUID key.
  Note:
  
  

  • the `health_facility` model attribute isn't updated - see note in CREATE section

  • the UPDATE operation will update the specific row of the database and doesn't create the history of changes (like in the legacy OpenIMIS)

• DELETE - the operation can be used to remove the specific object from the database. Should be used the DELETE HTTP method. The requested URL needs to point to a specific object to do that you should add the primary key to URL for instance:
  http://localhost:8000/api_fhir_r4/Practitioner/UUID
  , where UUID is the value of the UUID key.
  Note:
  - the DELETE operation will permanently remove the row from the database
  
  

Example JSON representation of content: