We have more that 7 EMRs that we wish to migrate data from them to our instance of OpenMRS, We need suggestions on the best way to go about this.
We have tried some steps but had a blockage. Below is what we have done so far
We intend to use an API for this data migration
We created a json structure that is like a standard we want to use for data migration,
We implemented rest API on our instance of OpenMRS to accept the json
And We used OpenMRS API to create patients and other patient’s data in our instance
We are not able to return a specific response from the API to the user migrating the data
Is there a better way to migrate data from different EMRs to OpenMRS.
Any suggestion will be greatly appreciated
I will go through the document and see if it will fit into our implementation. But like I said we have at least 7 EMRs to migrate data from.
Also the DMT doc says openmrs version 1.11.3. I don’t yet know if this is supported in newer versions. But other suggestions are still welcome
like you said "Your Implementation " , it implements OpenMRS , the methodology should not divert so much from the Ideal.
We have migrated data from other platforms to OpenMRS. We are open for consultation and based in Abuja. #Reverton.Net
@johnbosco & @jaghatise Can we schedule a call asap to discuss ?
There is a lot of experience in our community around migration. @aojwang and @wanyee come to mind.
Let’s keep the discussion open and going on Talk so that others can both contribute and gain.
Am open to discussions, about migration, I also want to be sure we have gone the right path. So let me know of a time
I literally agree with @jennifer this might be useful to other members of the community. I will appreciate if we can schedule a call for discussion soon. @c.antwi let me know time and date.
Thanks @c.antwi, I will also try out the tool but Moet of these tools won’t work with Openmrs data structure. Once the source database tables and elements are correctly mapped to openmrs(destination), simple sql scripts can move the data in minutes.
What is required is diligent mapping of source to destination databases.
@ssmusoke @slubwama any experiences /practices to share from UgandaEMR ?
@c.antwi thanks for sharing the link.
Thanks for keeping me in the loop. I would love to also join the call on migration since we have a current task to migrate data from a SQL server based system to OpenMRS. Our previous work on migration was somehow not documented for sharing.
@aojwang even without the documentation, is the code available for us to take a look?
It would be great to get an opportunity to share different approaches on how data migration from other EMR’s into OpenMRS have been done, what lessons have been learnt and which modules are currently available to help facilitate this.
Could we choose a design forum slot from the option provided below:
cc: @johnbosco @aojwang @wanyee @ggomez @dkayiwa @valvijo @ssmusoke
@johnbosco do you mind giving us an update on how far you have gone with the json approach? Have you had a chance to try it out with any implementing partner? Or did you go with the spreadsheet import module as mentioned in the migrating data to openmrs link?
I find it easier for implementing partners to create spreadsheets or xls files rather than json files. The second advantage of this approach is that the code already exists in the spreadsheet import module.
@dkayiwa we are at the testing phase and am still making updates to the code, so far we have tested with one implementing partner and am working on the feedback we received.
Also the issue I disccussed with you about returning response from the restAPI is still pending if I must use the restAPI
Since you are in the testing phase, does this mean you used an alternative to the REST API?
Am considering using an alternative, but for now it is still the REST API
How were you able to use the REST API and have something that is ready to test?