An issue has been raised that Person Attributes are not synchronized when Using “fhir” as Resource Client , see this Ticket.
Sync2 does all the Synchronisation(pushes and pulls) using rest calls , this can be done using
“fhir” e.g /ws/fhir/Resource
“rest” e.g /ws/rest/v1/resource
as a Resource preferred client.
There some standard fhir patient resource specs that could match some of our “person attributes” like
fhir “telecom” can match openmrs “Telephone Number”
hence a telephone number can be easily synchronised using fhir Resource client
Note that when Sync2 , does the Synchronisation of Patients using our openmrs “rest” Resource client , all person attributes will be synchronised since person attributes is a property of the Openmrs patient Resource. This is not the same case with “fhir” , because the standard specs for for a Fhir patient resource do not match a “person attribute” property.
see standard template for a fhir Patient Resource
To have all person attributes synchronised via “fhir” would mean adding “person attribute” extension to the Fhir Patient Resource.
Would this be necesary ,given the fact that we can still synchronise the “person Attributes” using our openmrs rest Resource client ??