Trust me I tried. RC is difficult to setup and activate where when I tried to get them to certify openemr interface, they bulked. Poor business decision imo. Most these companies get overly concerned with points of responsibility. EFax shut me down as well. Twilio is better in many ways but fax does not seem to be a priority for them.
Any of these features that require outside resource vendors setup does prove to be difficult to implement by day to day users. This is why getting openemr pre certified so user doesnāt have to certify their instance is important. Not so easy iāve found however, now that iām an Administrator, perhaps they will take me more serious. So, iāll try again.
The reason I am interested in WebRTC is the fact that we can host the required services.
WebRTC has the capability to conference and implementing a TURN is fairly straight forward.
Along with video we also create a command driven message server that allows intra app communications as well as off loading reminders and messages as part of its responsibilities. eg get rid of reminder polling in openemr proper.
This doesnāt mean the other solutions arenāt viable, itās that I prefer to keep as much as we can close to home so to say. Especially concerning any fee requirements.
Regarding NodeJs. Unsure why the misgivings as Node is a terrific tool.
Hi @itsaboutcode and @gutiersa,
First, any implementation should include the ability to conference video and voip.
In practice, the ability to include care team members or groups would be of great benefit.
Consider a mental health practice that may which to consult other providers or even hold group meetings and so forth.
Last time I checked into WebRTC it had ability to do video conference. Did something change?
Also, my preference is to host the TURN and Signalling and looks like coturn could work for TURN.
May be of interest:
@pithonsoft submitted this PR last month. Problem with his implementation is the limited O.S support.
Keeping in mind Hipaa, what do you want to work with?
@gutiersa - I have recently checked https://doxy.me/ from the link you shared. It has a very generous free tier. To integrate it with any EHR, I did not see any API though.
Well, is an iFrame not enough?
We need not record the visit really. We just need to document a consent for seeing the patient via a video and document the actual visit exchange. In other words. The clinic note which we do anyway.
If We could integrage doxyme into openemr with something like greasemonkey or tampermonkey, just for ease of use. Then, the documentation regarding the timestamp, browser id, duration of the visit, and the session data, hardware used, can get transferred into the openemer database via an SSL encrypted HL7 transfer, into openemr, wouldnāt that be valid?
It is opensource and distributed via the GNU licence. (I think)
I signed up for a doxy me account today. I was not able to use it as I only had one patient and for some reason my chrome browser was not compatible. It looks like what Doxy me uses is an implematation of webRTC. It requires chrome or firefox to run.
I canāt contribute much more as I am not a programmer.
But I am here for testing.
My suggestion would be to start with one-to-one calling (on browsers to start with - can build native applications for iOS and Android too) because for that we donāt need media server e.g; Kurento.
I use bigbluebutton with my Moodle server and with Tikiwiki. It has a straightforward api and can be made secure. I currently run it on a digital ocean server with 4 cores @ 2.30 GHz and 8 Gb of ram. I use it for regular virtual meetings of 4 or more people with little to no issues. Installation is easy and steps can be taken to harden the server it is running on for security.