@samuel34 and how does Sync 2 handle these use cases, my understanding is that we are meant to build on top of that module rather than go all the way from scratch?
Actually I would like to step back a bit, request that we leave coding and go back to planning. What are the gaps in Sync 2 that need to be addressed? Before we start wondering how to address the gaps technically
Actually sync2 is awesome. It syncs Resources one at ago using Rest injections. The gaps could be
Syncing already existing data b4 sync2 was running.
Storing data somewhere for later use or data analysis.
Sync2 mob depencies. It depends on a quite a number of modules like Atom, FHIR, REST.
Merge Patient Data
Light weight
It can actually store data in a special file/format for future use
Currently its not depending on sync2
By the way, could you put me right in this @ssmusoke? Sync2 has a similar functionality with mergepatientdata module but they all achieve this in a very different way.
Your right. Maybe its cause of my little understanding that Iām still blinded. Iām probably thinking within the box. But as for now, we caught up within the middle of the sea. So lets sway in the direction that we shall deliver at the end of the day. @ssmusoke
The module is a state where its blocked by its dependencies.
Currently the module assumes that metadata like Concepts is similar in all instances. But to achieve this, we use tools like metadatasharing module. However, there is a know issue like duplicate Concepts that make exporting this data impossible. Good enough there is the Validation module in place, but this module is in a state that it still needs lots of work like adding support for platform 2.x. I started that here