FHIR Resource - Patient
Open
Description
The openIMIS Insuree object (from the openimis-be-insuree_py module) was mapped to the FHIR Patient resource.
...
The current version of mapping will be focused on aspects of claiming.
In the current version of the openimis-be-insuree_py missing services layer which can be used to perform operations (CRUD - Create, Read, Update, Delete) on entities. That's why the current version of API use directly database layer manager for managing the Insuree 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.
familyId - missing in the current version of the Insuree model (from the openimis-be-insuree_py module). That's why the current version of API doesn't cover that field. Attribute needs to be nullable type in the Database Schema.
photoId - missing in the current version of the Insuree model (from the openimis-be-insuree_py module). That's why the current version of API doesn't cover that field. Attribute need to be nullable type in the Database Schema.
typeofid - missing in the current version of the Insuree model (from the openimis-be-insuree_py module). That's why the current version of API doesn't cover that field. Attribute need to be nullable type in the Database Schema.
Mapping
FHIR Resource - Patient
FHIR field | OpenIMIS openIMIS field | notesNotes | mapping Mapping status |
|---|---|---|---|
Identifier | InsureeID / CHFID / passport / TypeOfId | there is a 0..* relation on identifier | InsureeID / CHFID / passport is mapped |
RelatedPerson | FamilyID | not mapped | |
name | LastName / OtherNames | name field contains values that are being mapped for both LastName and OtherNames fields | mapped |
birthDate | DOB | mapped | |
gender | Gender | mapped | |
maritalStatus | Marital | mapped | |
RelatedPerson.Relationship | IsHead | not mapped | |
telecom | Phone / Email | telecom field contains values that are being mapped for both Phone and Email fields | mapped |
photo | PhotoID | not mapped | |
photo.creation | PhotoDate | not mapped | |
managingOrganization | HFID | not mapped | |
address | CurrentAddress / GeoLocation | The patient can contain multiple addresses | mapped |
...