eTIPS
Did you know the “Accuracy Center” gives access to tools you can use to improve recognition accuracy?
The “Accuracy Center" gives access to all the tools you can use to improve your recognition accuracy including; personalizing Dragon’s vocabulary by letting Dragon analyze text, or importing lists of custom entries. Say “Start Accuracy Center” or use the DragonBar’s Tools.
Alternatively, if you are unsure of which Dragon tool to use, let the Accuracy Center help you by saying, “open Accuracy Center,” then click or say, “which tool should I use?” to start the accuracy assistant.
_______________back to top_______________
Did you know you could optimize recognition accuracy by speaking in complete phrases or sentences?
You can optimize recognition accuracy by speaking in complete phrases or sentences. Speaking too slowly, in short phrases or single words, makes recognition more difficult for Dragon, since longer phrases provide context which Dragon uses to guess what it should write; this is especially important for sounds that could be spelled different ways.
_______________back to top_______________
Did you know why Dragon might spell out dictated symbol names rather than recognize the symbol's character?
When dictating into a target application, Dragon might recognize symbol names by spelling them out instead of using their single character representation. Here are two examples:
-
When dictating "seven point six", the recognized text is 7 point 6 instead of 7.6
- When dictating "seven plus six", the recognized text is 7 plus 6 instead of 7+6
If the Dragon user's workflow requires character representation for symbols instead of the complete spelling, confirm the following Formatting setting within Dragon.
- Under DragonBar, click Tools > Formatting.
- On the General tab, click the Format Other Numbers checkbox to enable it.
- Click Apply, and then OK.
Re-launching the Dragon application or re-opening the User Profile should not be necessary.
_______________back to top_______________
Did you know what is required for MEDITECH EHR compatibility with the Dragon Medical 360 | Network Edition vSync feature?
The MEDITECH EHR (Electronic Health Record) system when interfacing with DM360|NE (Dragon Medical 360 | Network Edition) must adhere to minimum requirements in order to be compatible with the DM360|NE vSync feature.
Note: MEDITECH upgrades can require months of planning and testing to migrate from one release to another. The MEDITECH customer should always consult with their MEDITECH vendor for the most recent information related to Dragon usage with MEDITECH.
vSync Overview
The DM360|NE vSync feature allows Full Text Control (Dragon Select-and-Say support) within Citrix-published applications across a Citrix environment exclusively. The vSync feature is comprised of both a DM360|NE Client component as well as a Citrix server component. The vSync feature is enabled in both the NMC (Nuance Management Console) and at the DM360|NE Client.
In general, the DM360|NE Full Text Control (Dragon Select-and-Say support) capability requires constant, real-time monitoring of the data for the target application's (EHR) screen content. This would include aspects such as: utterance mapping, correction support, cursor location, audio preservation, element tracking, navigation command and control, and formatting support.
A simplistic view of how the vSync feature works is that vSync mirrors the data from the screen content of the Citrix-published EHR application and provides that data to the DM360|NE Client application running at the local workstation.
Prerequisites for DM360|NE vSync compatibility with MEDITECH
There are three (3) separate MEDITECH platforms with numerous versions and priority pack levels within each platform. Please see the prerequisites below.
Note: vSync is currently compatible with the MEDITECH Client Server product.
- The MEDITECH Text Editor (MEditor) must be at version 2.6. The current availability of MEditor 2.6 is listed below:
- Client Server 5.65, Priority Pack 15 and higher - available now
- Client Server 6.x - availability is pending
- Magic (all releases) - availability to be evaluated by MEDITECH
- DM360|NE Service Pack 3 or higher is required.
In general, EHR vendors can certify their EHR applications with Dragon by working with the Nuance Engineering Team to develop fully-compatible versions. MEDITECH is actively pursuing this now. For information on enrolling in the Nuance EHR certification program, refer to Nuance's Dragon EHR Certification web site.
Implementation Architecture
The following terms are used when describing how Dragon and MEDITECH applications can be implemented in different scenarios:
- Fat / Thick / Local - describes an application that is installed "locally" on the workstation
- Thin / Remote / Virtualized / Web-based - describes an application that is installed on a remote server where the client workstation accesses the provided application through host software like Citrix, or Terminal Services, or Internet Explorer.
There are three (3) potential scenarios for how Dragon is implemented with MEDITECH or any EHR application.
Note: Currently, a majority of MEDITECH customers are configured for scenario 1. However, more customers are beginning to adopt scenario 2 as their configuration.
Scenario 2
Under this scenario, MEDITECH users are normally trained to use the Dragon Dictation Box feature and transfer text into the MEditor window. Alternatively, when dictating directly into MEDITECH comment boxes (i.e., after clicking a check box or radio button), MEDITECH users are instructed that any corrections will likely need to be performed manually.
When MEDITECH is a Citrix-published application, the DM360|NE vSync feature can provide Full Text Control support, provided the aforementioned prerequisites are met.
Scenario 3
This scenario, where both applications (Dragon and MEDITECH) are published by Citrix in the same Citrix session and from the same Citrix server, is ultimately dismissed by most customers for two technical challenges:
- The network bandwidth required to move the dictated audio from the local workstation to the Citrix server can be too large.
- The number of simultaneous active users per Citrix server that can be supported is small, requiring additional Citrix server resources.
DM360|NE vSync is not required for scenario 3.
Citrix Smooth Roaming
Also, if the Citrix Smooth Roaming feature is being used, please login to iSupport and search for solution 14898: Configuring Citrix Smooth Roaming in a DM360|NE (vSync) Environment. If you are not an iSupport subscriber, click iSupport Timesaver for information about how to get stated.
back to top
|