Looking for ideas on remote scribing - Linda Posted: Feb 9th, 2016 - 11:18 am
Yesterday I saw a specialist and as he was typing my history, I asked him how he liked EMR and not having an MT. He said "An MT would be a LUXURY! Then I could spend more time with my patients". I handed him my card. He admitted to sending his dictation to India and getting it for 6 CPL, but the poor quality was unacceptable so he went with an MTSO paying them 16 CPL, for 36-hour turnaround, which he thought was too much, so he tried VR. He said VR was atrocious so he is typing. He said what he would really like is a scribe so he could have immediate turnaround. He said he also has a PA who is not a good or fast typist and will probably be giving me a call.
This got me wondering if remote scribing could keep us working. I don't think any providers are happy with EMR or the requirement to do their own data entry. If they could have quality work for an good price AND immediate turnaround, I think many would go for it. An in-house scribe would cost them more than a remote IC MT. Could we offer immediate turnaround at a good price? If patient visit were recorded and downloaded to a remote MT immediately after the visit, and we had more than one account or a practice with multiple doctors, we could keep working and not have to wait for the next office visit. Since this would be creating the patient record in almost real time and entering it directly into their EMR, I'm not sure what would be appropriate to charge, but more than today's standard line rate. If we could charge less than what the MTSOs are charging for 12-hour turnaround, I think there would be a lot of interest. What would it cost to receive audio files online for a few doctors? This would not require the doctors even dictate. Imagine their making a choice between:
A) Having to dictate for an MTSO with 12-hour turnaround for 16 CPL.
B) No need for dictation with 1 hour turnaround for 12 CPL?
Any ideas?
Post A Reply Reply By Email Options
Complete Discussion Below: (  marks the location of current message within thread)
|
