The doc would like the updated prescription to be saved as new.
The reason being is for medication history. When the doc makes a change the prescript to increase or decrease the dosage. To him, these should be different entries without having to write a new script.
I am trying to talk this out because when I chased down the function that updates the record. It is the persist() function in the ORDataObject class. It uses the replace into to write the data.
In Prescription class line 208 is where the persist function is called.
It seems like the feature that he wants would work if I took out the record ID in flight. Check to see if the modified date is different than the current date. If they are different, set $this-> = “”; Then the system should write a new record.
Could someone check my pseudo code and let me know if you think this would work?
Hi Sherwin,
Narcotic’s (maybe all scripts) should discontiue therefore physician should not have to worry unless in unlikely event he needs to reissue(sometimes happen due to nobody’s fault and should discontinue current and rewrite). So, prescriptions should be smart enough to auto discontinue i.e check upon next view and write discontinue date to table. Then, that prescription becomes medication history and left alone.
I believe you are correct about replace because I use it this way all the time. Just while you are there maybe a look see in to the handling workflow may be worth while.
On different matter, do you know if Weno network gives a pharmacy failed delivery attempt status back to proxy that can be past on to user in some way? Maybe fax or e-mail or a cron job on user server that checks.
What happens, in that case, is the patient arrives at the pharmacy and request the prescription and the pharmacy says they don’t have it. They call the doc and the doc says I sent. Weno investigates the transmission and validates if it was received. 99% of the time the fax did go through. Weno can’t control what the pharmacy does with the faxes.
I am sure this happens with regular faxes done with human hands. It is very difficult to code humans out of the process.
As long as the practice has a valid fax number, the prescription will be sent. But let’s say that there is a bad fax number. We have not coded out the feature to send a message to say that the transmission failed. The Weno system can send a message to our server and it stored be not delivered to end user at this time.
Not to be curt:) but I know for a fact, on several occasions using long time relationships with pharmacy, that have had success previous, where fax is not received. (these are folks I know) but were successfully accepted by Weno. Be nice to know failure rate and cause(busy, interrupted or hangup e.t.c) and come up with feedback to user. I know this would be a boon to the feature and I would be willing to help with the interface.
Not curt. We are both stating fact.
With faxing there will always be the possibility where the Weno fax server will say successful and the pharmacy will say they did not receive the fax. It’s electronics. I am amazed it does what it does.