FHIR resources:
Fields mapping:
| OpenIMIS field | DB type | FHIR field | Description | Note | STPH |
| InsureeID | PK, int | identifier | |||
| FamilyID | FK (tblFamilies) | RelatedPerson | To represent the relationship between patients we can use the RelatedPerson resource. | It could be related to Group entity but not in this direction Another solution is to use the contact field and relate to another Patient (the head of the family) | |
| CHFID | ncarchar(12) | Identifier | |||
| LastName | nvarchar(110) | name | |||
| OtherNames | nvarchar(110) | name | |||
| DOB | date | birthDate | Date of birth | ||
| Gender | FK (tblGender) | gender | |||
| Marital | char(1) | maritalStatus | |||
| IsHead | bit | RelatedPerson.relationship | I'm not sure if this information is important for external systems. | It depends on how we relate to the Family | |
| passport | nvarchar(25) | identifier | Identification Number | https://hl7.org/fhir/STU3/datatypes.html#identifier | 0..* relation on identifier |
| Phone | nvarchar(50) | telecom | |||
| PhotoID | FK (tblPhotos) | photo | |||
| PhotoDate | date | photo.creation | |||
| CardIssued | bit | I'm not sure if this information is important for external systems. | not important | ||
| ValidityFrom | datetime | Audit information. More information can be found here (on page 113): https://github.com/openimis/openimis_docs/blob/master/specs/Web%20application%20-%20Functional%20Design%20Specification.pdf | this could be used to update the insuree information | ||
| ValidityTo | datetime | ||||
| LegacyID | int | ||||
| AuditUserID | int | ||||
| RowID | timestamp | I'm not sure but this is probably some unique value used to distinguish database rows. Probably not useful for external systems. | |||
| Relationship | FK(tblRelations) | 1 Brother/Sister 2 Father/Mother 3 Uncle/Aunt 4 Son/Daughter 5 Grand parents 6 Employee 7 Others 8 Spouse | The FHIR representation doesn't provide this information. We can consider adding the FHIR extensions if needed (if it will be useful for external systems). | not for Claiming | |
| Profession | FK(tblProfessions) | 1 Housewife 2 Employee 3 Self Employee 4 Others | not for Claiming | ||
| Education | FK(tblEducations) | 1 Nursery 2 Primary school 3 Secondary school 4 University 5 Postgraduate studies 6 PHD 7 Other | not for Claiming | ||
| nvarchar(100) | telecom | ||||
| isOffline | bit | I'm not sure but this is probably used to determine the source of row (offline/online app). Probably information isn't valuable for external systems. | |||
| TypeOfId | FK(tblIdentificationTypes) | identifier | Identification Type D - Driver's License N - National ID P - Passport V - Voter Card | As far as I am concerned this is the type of identifier from "passport" field. We can put these values into one FHIR identifier object. | |
| HFID | FK (tblHF) | managingOrganization | It depends on mapping the HF to FHIR resource. If the FHIR Organization will be choosen then it shouldn't be an issue but when the FHIR Location will be used there can be an issue. Probably we can add in this field reference to Location instead of Organization (should be verify). | ||
| CurrentAddress | nvarchar(200) | address | |||
| GeoLocation | nvarchar(250) | address | If this information is important for external systems we can put that information as other address. The patient can contain multiple addresses. | ||
| CurrentVillage | int | I'm not sure if this information is important for external systems. |