hi @prondubuisi ,
I wouldn’t try to import directly to the database, or else you will likely go mad trying to sort out all the relationships after get beyond basic demographics. Would instead recommend importing the data through the OpenEMR API. Then can take advantage of the code that already exists to create patients, medications, allergies, encounters, etc. This may require building out the API to support things, but much easier to leverage processes that are already there to bring data into the database than trying to reinvent that very, very complicated wheel
If possible, would rec trying to keep the modularity of the main OpenEMR docker since that then makes it much easier to support and maintain (ie. rather than building out a separate openemr/synthea combination docker). It looks like that Synthea static build docker dumps the data into a shared folder so should be able to share that between dockers. Regarding dockers, the sky is really the limit. For example, could have the synthea docker, the openemr docker, and then a “utility docker” that runs synthea (that curl call) and imports the data into openemr via the api.
Note these are just some initial thoughts and feel free to go the way that you think is best.
thanks,
-brady