What you have to find out is what standards to does the insurance company use to communicate with platforms outside of theirs.
That is going to govern what you build.
Please forgive these basic questions as I am just learning about all this stuff.
Can you explain to me the idea of how the message will be export from my system and import to the suitable place at X System? how the idea will work “Not Tecchnically”)
As what I understood after going through MirthConnect tool, the general process in my case will be as follow :
My OpenEMR is the source
X System is the destination
A message from my system will be export contains (database name, table name, field name, data type …)
It will be filter at the destination side and the values will import to the suitable field in their database.
Hi Fatimah,
I think you got it wrong and here is the explanation.
As Sherwin said, you need to find out what standard data and type the insurance company expects from your EMR side.
For example, lets consider you need to send x12 (standard type) message to insurance company.
Once identified that the format is X12, you need to build x12 message from you openemr (from database) and send to insurance company through their preferred data transfer commnuication mode(like TCP,SFTP,HTTP)
MirthConnect tool will be used while building the x12 message and transferring the same to insurance company