Does anybody happen to know, as we’re looking through the code trying to find exactly what it does, what the intended behavior of the eRX interface is supposed to be in regards to retrieving new RX/Allergy records from NewCrop/Ensora ?
It seems like in past versions, opening the Patient Summary caused an automatic retrieval of RX/Allergy data, whereas in Version 7, you have to open the patient, and then deliberately open the eRX portal under the patient before it refreshes in OpenEMR. I could be wrong, just wondering if anybody happens to know if there was a community consensus from the developers’ point of view as to how the interface was planned to work in the real world.
Yes, as a matter of fact. But I wonder if the issues you’re trying to track down are partly a result of the fact that maybe you are working with an improperly configured/ unauthorized connection with Ensora?
See the post for some fundamental details, the upshot of which is that the code of the interface is FOSS and eligible to be modified, but the functionality can only be used on an instance of OpenEMR which is licensed with a (the) Ensora vendor.
The function of the Ensora (originally known as ‘NewCrop’ and probably still called that in the code) interface is basically to error check and to rearrange the eRx/ PII data that passes between the OpenEMR and Ensora into the format each system requires. It is a compromise between the data requirements of OpenEMR’s native Prescription module and Ensora’s data structures and as one might imagine, not every single difference can be accommodated. But enough is that it is certified for MU for use with Ensora, while leaving the EMR’s native prescription module intact and functioning as originally designed.