I have reached out to my SAM and opened a case, but no response yet.
]]>We are experiencing a unique issue where a provider is using her correct credentials, signing in to the emobile app and as soon as she clicks “done” on her phone keyboard the app immediately shuts down.
We are working on an iphone, update the ios, we have tried dis-enabling the emobile account, deleting and redownloading the app, etc. Has anyone experienced anything like this or have suggestions on what to try?
Thanks!!
Lila Dykstra
Analyst II
Holland Hospital
The mobile application used to remember the last location used for billing.
Now it takes whatever is the location for the provider on their provider profile in ECW?
It is extra work for the provider to continuously keep changing the location.
ECW replied to us saying its an enhancement request?
Has anyone else experienced this change?
Thank you
]]>Anyone else having this issue? Maybe someone from the eCW team monitoring the forum can look into this.
The open ticket is #9252915
It will take a while and act like it is trying to scribe the note to the encounter, but then gives this error…Server Request TimeOut!
It seems like even if you go back later and try to scribe the note, once the error shows up, it constantly shows up.
Even if you go to another note and scribe it, it will go through no problem.
So, it seems like it is specific to the note that the air happens on.
Anybody else getting this error and is there a fix?
]]>I was able to come up with a slight work around using eclinicaltouch by merging forward the past note and changing the title of “assessments” to “clinical notes” and typing my clinical notes but not able to do that on the mobile app, which I use more frequently.
Let me know if anyone has figured anything out.
Tracy
Do we need another app to dictate on an iPhone with eClinicalMobile? or does it just use the phones microphone?
Thanks!
]]>Has anyone come up with a comparison of the two?
]]>If I delete the apostrophe, the scribe works fine and the note goes to the EMR.
Anybody else having a similar problem?
Any fix?
]]>