...
work on smartphone (OS?/Windows?) and computers (laptop/desktop/chromebook?)
Technical approach:
The propose technical approach is based on FHIR
the resource have an Identifier section which is a list of identifier object
the identifier object has a system parameter, and a code
the proposal is to enable the definition of the system (does not have to be resolvable) naming convention to be defined ? use of apikey name ?
all the references inside FHIR payload should use the system like system/resource/id
Sync steps:
2- generate a new id and new matching identifier (system = FGQN of the TO server) will be added on the resource identifier list
3- upon saving, the reference should be translated to ID of the main server (based on the identifier with the remote system )
Sync Back steps
When loading the data, the local server will do the same as the main server (same resource will have different id on different server) BUT the search should enable the usage if the system
task to do:
properly support identifier in openimis resource (Json_ext ?)
implement the sync
implement the search
for the next