Actually the following also needs to be addressed.
As we implement this, I’m sure that merged data(father instance) should be in a read only format. Loosely meaning it has an impaired scope. A merged Encounter shouldn’t be 100% of same utility with the original.
So what should a merged Encounter be expected of/to contain by a Provider. Technically speaking what are the crucial attributes of the Encounter Resource?
To be more specific, I’m confused with @dkayiwa’s dev notes
Site level users and metadata are not synced, neither are concepts and forms, as they are expected to be similar. The merged data (father instance) would be read-only, used reporting and analysis purposes.
How to address this. While syncing Obs, you mean we just need the Concept ID?
The challenge with is for sync2, it just makes use of the Openmrs REST API which make syncing its Resources easy and with less headache. But for our implementation, it just impossible to use REST Since data should be physically in a file