As an individual user dictating into applications on your Windows 10 computer: Download the Dragon Medical One Installer.
If you are deploying Dragon Medical One in a larger system or as a virtualized application/virtual desktop: Download the XCOPY package or MSI package below.
Use this installer to get started quickly on a single computer and dictate into applications that are running on the same computer. Download the installer, double-click it and follow the installation instructions. Windows 10 is required and you will need the organization token that you received in your Welcome Kit email. Once Dragon Medical One is installed, it will notify you when new versions are available.
Download Dragon Medical One Installer
Note: Depending on your security settings, Windows might mark downloaded files as unsafe and prevent the installer from running. To unblock the installer, right-click the .exe file and select Properties; on the General tab, click Unblock and Apply. You might also need to add the Dragon Medical One Installer to the list of allowed apps in your antivirus program.
In larger systems and virtual deployments, the XCOPY installation package enables you to deploy Dragon Medical One using simple file copy operations. You can customize the application flexibly by editing the application configuration file; for more information, see the Dragon Medical One Installation and Administration Guide.
Dragon Medical One needs to run in the same process space as the target application. If the target application is installed locally, Dragon Medical One should also be installed locally. Likewise, if the target application is deployed virtually, Dragon Medical One needs to be deployed virtually as well.
For more information on how to deploy your application in a virtual environment see: Virtual environment support.
Note: Depending on your Group Policy security settings, Windows might mark downloaded files as unsafe. Unblock the .zip file, if necessary, to allow proper execution of Dragon Medical One when started: Right-click the .zip file and select Properties; on the General tab, click Unblock and Apply.
The Windows Installer package is MSI command line-only; no installation wizard is available. For information on mandatory and optional parameters, see the Dragon Medical One Installation and Administration Guide. To control deployment to users' local workstations across your system, you can use the MSI package to perform an SMS push installation.
PowerMic Mobile gives clinicians the freedom to roam from workstation-to-workstation, room-to-room and location-to-location to complete clinical documentation using their smartphone as a microphone at the desktop.
The following license types are available:
By default, when a user logs on to PowerMic Mobile with a new user name, the user is automatically added to your organization and a PowerMic Mobile license is assigned. You can turn this off at the organization level via the Nuance Management Center (NMC). Proceed as follows:
Nuance provides two methods for software distribution. Both methods require configuration URLs that are specific to your organization. See the 'Getting Started' section of the Welcome Kit that was sent to your organization's point-of-contact or system administrator.
Your organization can use either method or both, depending on your environment and usage policies.
PowerMic Mobile uses WiFi or cellular data. It is recommended that users connect primarily via a reliable WiFi network with the following characteristics:
If you have additional questions or need support, please contact Nuance technical support
Using an MDM to deploy and configure PowerMic Mobile provides the following solutions:
PowerMic Mobile supports MDM configuration via the AppConfig standard (appconfig.org). Most major MDM vendors have adopted the AppConfig standard, including VMware AirWatch, MobileIron, Cisco Meraki and Sophos. If your MDM does not belong to AppConfig, it might still be possible to use the PowerMic Mobile MDM configuration file with your MDM or to extract the configuration elements from the XML file and load them into your MDM. For more information, see the documentation provided by your MDM vendor.
PowerMic Mobile
Version 4.0 and higher.
You will need access to the PowerMic Mobile apps available in the App Store and Google Play. Search for these apps from your MDM solution:
iOS: https://apps.apple.com/us/app/powermic-mobile/id983002170?ls=1
Android: https://play.google.com/store/apps/details?id=com.Nuance.Mobility.DMic.Live&hl=en
iOS
iOS version 9.3.5 or higher.
The device must be enrolled with Apple's MDM protocol.
PowerMic Mobile must be provisioned and installed via Enterprise Mobile Management for the PowerMic Mobile configuration values to take effect.
For more information, see: https://www.appconfig.org/ios/
Android
Android version 6.0 or higher.
Devices must be enrolled in Android for Work.
The PMM app must be provisioned and installed via Enterprise Mobile Management for the PowerMic Mobile configuration values to be applied. Use an MDM solution to push Android for Work public applications to devices. This process includes adding and approving applications for integration between your MDM solution and Android for Work from the Google Play Store which can be accessed from your MDM solution.
For more information, see: https://www.appconfig.org/android/
You will need an edited version of the MDM configuration file. Copy the sample XML at the end of this page to a text editor, modify the values for the PMMConfigurationName and PMMConfigurationURL parameters within the <dict> element and save the file with a .XML file extension.
This parameter is optional. If you do not specify a value for the parameter, PowerMic Mobile will generate a profile name; for example, "Profile 1."
Note: You can define a single profile in the MDM configuration file. If your users need multiple profiles because they work with multiple NMS organizations, use the MDM file to define the profile that will be used by the majority of your users. Users who need access to additional organizations will need to add additional profiles in PowerMic Mobile via the corresponding configuration URLs. Gather the required configuration URLs from the Nuance welcome letters and then distribute them to your users via the Nuance-hosted web page or via email.
It might be necessary to validate your configuration URL; for example, if the URL has been edited for an on-premise deployment. Proceed as follows:
If the URL is valid, the Valid URL message is displayed.
We use VMware AirWatch as an example MDM solution. The procedure is similar for other MDM solutions that support the AppConfig standard.
Proceed as follows:
Complete the following fields in the Add Assignment dialog box:
Assignment Groups: Select the distribution groups to which you want to assign PowerMic Mobile.
App Delivery Method: Select Auto.
Deployment Begins On: Select a date to start installing PowerMic Mobile.
Managed Access: Select Enabled.
Application Configuration: Select Enabled.
PowerMic Mobile will be installed on managed devices, starting on the date you specified. When your users launch PowerMic Mobile, it will already be configured with the profile defined in your MDM configuration file. To begin using PowerMic Mobile, users enter their user name and tap Log In.
<managedAppConfiguration> <version>1.4</version> <bundleId>com.nuance.mobility.dMIC</bundleId> <dict> <string keyName="PMMConfigurationName"> <defaultValue> <value>Enter the profile name here</value> </defaultValue> </string> <string keyName="PMMConfigurationURL"> <defaultValue> <value>Enter your configuration URL here</value> </defaultValue> </string> </dict> <presentation defaultLocale="en-US"> <field keyName="PMMConfigurationName" type="input"> <label> <language value="en-US">Configuration Name</language> </label> <description> <language value="en-US">This is the default profile name for your organization in PowerMic Mobile.</language> </description> </field> <field keyName="PMMConfigurationURL" type="input"> <label> <language value="en-US">Configuration URL</language> </label> <description> <language value="en-US">This is the configuration URL to set up the profile for your organization in PowerMic Mobile.</language> </description> </field> </presentation> </managedAppConfiguration>
Dragon Medical One was built from the ground up as a pure virtual application to allow for rapid deployment and help ease the burden on overworked IT staff. For doctors to dictate from an endpoint, you may need to install vendor-specific microphone and audio compression extensions.
The Nuance custom audio channel significantly reduces the bandwidth requirements for audio transmission from the client end point to the virtual application. Nuance provides custom audio channel implementations for Citrix, VMware and RDS.
These custom audio channels are automatically installed on the server when you deploy the main Dragon Medical One application. The client components of the extensions still need to be installed on the client PC using the installation packages below.
For more information on the available audio solutions for your configuration, see Dragon Medical One Audio Routing Solutions in Virtualized Environments.
The Nuance virtual extensions are designed to be backward compatible from Dragon Medical One to the client end point. This means you can run newer versions of Dragon Medical One in your virtual environment and they will be compatible with older versions of their corresponding client end point extension. The following recommendations and restrictions apply:
Nuance Citrix extensions v121.4.136.2138: The Nuance Citrix extensions package includes a custom audio channel to increase audio quality and reduce bandwidth requirements for audio transmission from the end point to the virtual application on the Citrix server or virtual desktop. This package also includes a custom channel to enable Nuance PowerMic and Philips SpeechMike buttons in Dragon Medical One.
Note: Starting with Citrix Virtual Apps and Desktops 7 2109, the Virtual channel allow list policy setting will be enabled by default. This means that Nuance virtual extensions will no longer work with the default configuration. For more information, contact Nuance technical support.
Nuance VMware extensions v121.4.136.2138: The Nuance VMware extensions package includes a custom audio channel to increase audio quality and reduce bandwidth requirements for audio transmission from the end point to the virtual application on the Citrix server or virtual desktop. This package also includes a custom channel to enable Nuance PowerMic and Philips SpeechMike buttons in Dragon Medical One.
Nuance RDS extensions v121.4.136.2138: The Nuance RDS extensions package includes a custom audio channel to increase audio quality and reduce bandwidth requirements for audio transmission from the end point to the virtual application on the Terminal Server. This package also includes a custom channel to enable Nuance PowerMic and Philips SpeechMike buttons in Dragon Medical One.
Optional third-party microphone extensions v121.4.136.2138: The optional third-party microphone extensions package includes a collection of virtualization add-ons provided by third-party device suppliers (for example, Grundig or Olympus). Virtualization technology support varies by microphone supplier.
The following guides are available for download.
The rapid rise of the cloud computing model has fundamentally reshaped the software industry and the way software is delivered. Gone are the days of biannual software releases shipped on a DVD, replaced with a cloud distribution model that allows software manufacturers to rapidly innovate and easily distribute their solutions to cloud connected customers. Nuance is no exception, and we have used the cloud model to radically accelerate our ability to deliver new solutions, capabilities and features into the market and respond to our customers' needs.
Supported. A given major release or point release is supported for 12 months after the initial release date. During this period, Nuance will investigate any reported issues and make best efforts to address any confirmed defects in a future major, point or service release.
End of Support (EOS). If a major release or point release is more than 12 months old, it will still interoperate with our Nuance cloud, but it is no longer officially supported. Any issues reported against an unsupported release will not be analyzed or investigated.
End of Life (EOL). A major release or point release that is more than 15 months old will no longer function due to advances in the Nuance cloud infrastructure.
Dragon Medical One relies on a modern software infrastructure in order to be able to provide frontend speech recognition in a highly secure manner. Key components include modern operating systems from Microsoft, the latest and most secure versions of the Microsoft .NET Framework, as well as solutions from virtualization vendors such as Citrix and VMware. In keeping with standard industry practices, these vendors routinely discontinue support for older products. By default, when a third-party vendor such as Microsoft or Citrix no longer supports an existing product, Nuance also officially ends support of Dragon Medical One running in that environment. Although the product may continue to function, Nuance will not be able to address any performance, security or functional issues that may arise from using unsupported third-party software.
Dragon Medical cloud services provide real-time speech recognition for Dragon Medical One as well as hundreds of partner applications. At Nuance, we recognize the critical role of real-time speech recognition in creating robust clinical documentation and delivering timely, personalized patient care. In order to provide complete transparency, this status page provides historical insight into the overall uptime and SLA compliance of our Dragon Medical cloud services.
In addition to the SLA history page, Nuance also provides a service status page that provides a real time health check of our cloud services. If your users are experiencing any issues you can use this status dashboard to determine the health of our cloud services.
Technical support from the Nuance Healthcare Solutions Support Center is provided during the term of the Service Agreement. An authorized contact (registration required) should submit an online support case from our Nuance Healthcare Support Platform web page.
Telephone support is recommended for emergency assistance (24x7) and follow-up or escalation of existing support cases created through our Nuance Healthcare Support Platform web page.
No on-site service is available for this product.
Registered Nuance Healthcare Support Platform customers have access to Knowledge Base solutions, plus the ability to submit support cases online. The average response time for web-based support cases is four (4) hours during normal business hours, 8:00 AM to 8:00 PM EST, Monday through Friday.
Telephone support is recommended for emergency assistance (24x7) and follow-up or escalation of existing support cases created through our Nuance Healthcare Support Platform web page.
The Nuance Healthcare Solutions Support Center will provide product support to authorized contacts of Dragon Medical One customers during the term of the Service Agreement. The customer is responsible for registering, through our Nuance Healthcare Support Platform web page, two (2) trained authorized contacts per customer site, who may contact the Nuance Healthcare Solutions Support Center for technical support on Dragon Medical One.
The trained authorized contacts are defined as customer personnel possessing a reasonable level of operational competency with Dragon Medical One. This can be accomplished through a review of Dragon Medical One product documentation or hands-on product experience. A customer site is defined as any physical location or organizational entity that requires separate administration within the customer's environment.
Registered Nuance Healthcare Support Platform customers have access to Knowledge Base solutions, plus the ability to submit support cases online.
To register an authorized contact please email hc.support@nuance.com to have your Nuance Healthcare Support Platform account activated.
You will need to provide the following information in the email request:
When your account is activated, you will receive an email containing your Nuance Healthcare Support Platform account credentials. You can then log on to your account and take advantage of the site features. Approvals may require up to one (1) business day to process. If immediate support is needed during the approval process, please use the telephone support procedure.