I can agree with your point and @robert.down point. The first time that I integrated Weno. I leveraged the existing prescription interface. I added the function to transmit and everything else stayed intact.
Then the thing that you two may not be aware of is that the FDA has to approve the interface. That is why the iFrame is used. Otherwise the interface that would be built out in OpenEMR would have to go through the FDA approval process and be certified to meet their standards. That has a cost associated with it. The easier thing to do is to use the iFrame approach because the service provider has already borne the cost of getting the FDA approval. Now, what I can hope to do is in the process of time if enough providers are using the Rcopia. We can look to leverage that to build out the interface in an API only design.
The inconsistency of data is a problem of poor design in my opinion. The communication between both the EMR and the eRx supplier should be seamless. Just like what was done with the telehealth signup where the credentials are passed back from the service provider and entered into the globals without the user having to do anything. (Thanks to @sjpadgett and @adunsulag ) The eRx should be the same so there is no data gap. These are the things that we will be looking to build with the Rcopia system. I have been assured that we can close the data gap and sync records between the two systems.
Contract came yesterday and we are starting our review of the service contract before signing.