List of content:

...

1. Create base ClaimAdmin using FHIR Practitioner resource
2. Use FHIR PractitionerRole resource to create a relation

Notes / Assumptions:

• The endpoint uses the UUID as a primary key
• The current version of mapping will be focused on aspects of claiming.
• In the current version of the openimis-be-claim_py (0.0.7) missing services layer which can be used to perform operations (CRUD - Create, Read, Update, Delete) on ClaimAdmin entities. That's why the current version of API use directly database layer manager for managing the ClaimAdmin objects. This leads to differences between operation between legacy and new OpenIMIS, for instance, the update operation doesn't create the database row with a history of the object and the delete operation permanently remove the object from the database.
• Practitioner resource needs to be created before PractitionerRole can be created because of the PractitionerRole resource has reference to the Practitioner resource
• The DELETE operation on PractitionerRole removing only the relation between ClaimAdmin and HealthFacility

FHIR resource:

• Practitioner- used to represent base fields of Claim Administrator (without relation with health facility- FHIR Location)
• PractitionerRole- used to represent a relation between base ClaimAdmin (FHIR Practitioner) and Health facility (FHIR Location)

...

...