Over the last months we’ve been making some considerable updates to the product as well as bugfixes as they come up. We’ve been updating the product on the Google Play store and some updates and troubleshooting tips on the Forums but nothing really in depth and I thought it would be a good time considering the progress we’ve made on the extension. Apart from stability and user interface enhancements, the most prominent feature we’ve added to our Medical Voice Recognition Chrome Extension has been the addition of compatibility mode.

Compatibility Mode?

The main reason for this is there are so many web based EMRs out there that are all coded somewhat differently we were finding that its much more difficult than we thought to have a sort of standard operating method. Some EMRs use plugins for documentation, others have keyboard hooks, custom field classes etc… We found that we were making enhancements to accomodate various EMRs (which we will continue to do) to keep up. However, we quickly realized that we need to make sure that if an EMR vendor makes a change that possibly causes an issue with our extension or Chrome makes some change that affects the way the extension is used (ie: either prompting for mic access or blocking. No more allowing all) that the users won’t be stuck which we race to get it fixed.

What is our solution?

The solution to this was to add a compatibility mode to the extension. What this does is opens up a separate text window where all of the voice recognized test will go into. The user can choose to paste that text into the browser window field whenever they are ready.

This essentially confirms that ANY EMR will work with vScription VR. If it won’t work natively, compatibility mode will ensure that you can use Medical Voice Recognition with any web based EMR. With compatibility mode, you could also use vScription VR for medical speech to text on Linux for any application provided you create the content in the Chrome Browser. The workflow may not be the best but if you are running in a Linux Environment, this can be a viable option for you.

Please stay tuned and if you have any suggestions for functionality, please post in our forums and we’ll do our best add to our product roadmap.

We are very proud to announce the first release of our new vScription VR Chrome Extension!

Medical Speech Recognition is not new. We’ve been selling it for almost 10 years and have sold hundreds of copies to hospitals and clinics throughout Canada however we have had clients running open source environments using Linux which we have not been able to find a practical medical voice recognition solution for them.

The vScription VR Chrome Extension has been tested using the most common open source platforms in OpenEMR and LibreEHR on OS X and Linux (Fedora Linux and Ubuntu Linux).

The initial release is pretty bare bones but includes the ability for front end voice recognition, substitutions, custom vocabularies and text shortcuts. Based on our experience, this is the bread and butter of what most physicians need to generate their medical documentation. We are currently planning on adding other features in the upcoming months based on user feedback and our vision. If you have any suggestions, please be sure to let us know.