Healthcare · Managed platform (Nuance Dragon)

Virtual Scribe

Nuance Dragon clinical speech recognition, configured for your EHR and run for you

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs Nuance Dragon clinical documentation for hospitals, health systems and medical groups. We set up Dragon Medical One speech recognition, and ambient documentation where you license it, so clinicians can dictate or have their notes drafted inside the EHR, then operate the service day to day: user setup, shared templates and vocabulary, support, monitoring and change. Clinicians review and sign every note, and your organization keeps the decisions on privacy, consent and documentation policy.

The problem it solves

Clinicians spend a large share of their day typing notes into the EHR, often after clinic hours. Many organizations already own speech recognition licences but use them unevenly: profiles are set up once and never tuned, shared templates drift from documentation policy, new clinicians wait for accounts, and nobody owns the problems that make dictation feel unreliable. When ambient documentation is introduced, questions about patient consent, recording and who checks the draft note are left to each clinic to answer.

  • Licences are bought but adoption and usage are not tracked or supported
  • Shared templates and auto-texts drift from documentation and coding policy
  • Microphone, EHR and recognition problems have no clear owner
  • Consent and review rules for ambient documentation are unclear or inconsistent

Who uses it

  • Chief medical information officers and physician documentation leads
  • Physicians, advanced practice providers and other clinicians who document in the EHR
  • Health information management and clinical documentation integrity teams
  • EHR and clinical applications teams who support clinicians at the workstation
  • Privacy and compliance officers responsible for patient information and consent

Requirements it supports

HIPAA Privacy Rule (45 CFR Part 160 and Part 164, Subparts A and E)HIPAA Security Rule (45 CFR Part 164, Subpart C)HIPAA Breach Notification Rule (45 CFR 164.400 to 164.414)CMS Conditions of Participation for medical record services (42 CFR 482.24)Medicare Program Integrity Manual, Chapter 3, signature and documentation requirementsState laws on consent to record conversations, where ambient documentation is used

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Nuance runs the Dragon platform, Moraph configures and operates your organization's use of it, and your organization owns clinical, privacy and documentation decisions.

AreaMoraphNuance (Microsoft)Your organization
LicensingResells Dragon subscriptions, or works with licences you already hold, and tracks use against themSets licence terms and what each licence includesAgrees to Nuance's terms and decides how many licences and which products to buy
Platform availabilityTracks Nuance service notices and tells you when an incident affects cliniciansRuns, hosts and maintains the Dragon cloud service and its availability commitmentsKeeps a downtime plan so clinicians can document if speech recognition is unavailable
ConfigurationDesigns the baseline and builds and maintains settings, templates and vocabularyProvides the configuration options the platform supportsApproves the baseline and every change to it
Users and accessCreates and removes users and assigns licences from your requestsAuthenticates users to the service as configuredTells Moraph about joiners and leavers and decides who should have a licence
EHR integrationConfigures Dragon for your EHR and applications and tests after EHR upgradesSupports the EHR integrations the platform providesOwns the EHR, its upgrades and workstation builds
MonitoringMonitors service notices, support trends and administrator activityMonitors its own platformMonitors your own network, devices and EHR
Incident responseTriages incidents affecting your users, contains them under the agreed procedure and supports your investigationResponds to incidents in the Dragon platform itselfLeads incident response and makes breach notification decisions
Platform updatesReviews Nuance release notes and plans any changes to your configurationReleases updates to the service on its own scheduleApproves configuration changes needed in response
Policy decisionsRecommends settings and consent rules with reference to HIPAA and your policiesNoneOwns documentation, consent and privacy policy and approves ambient documentation use
User supportSecond-line support for recognition, microphone, profile and integration issuesSupport to Moraph for platform defectsFirst-line support for clinicians, unless you hand it to Moraph

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of Nuance Dragon itself, which belongs to its vendor.

  1. Step 1

    The rollout tracker

    During implementation, every department has a row: the product, how clinicians will capture audio and where setup stands.

    DepartmentProductMicrophoneCliniciansLead sign-offStatus
    Hospital medicine (example)DictationHandheld microphone42Signed offLive
    Emergency department (example)DictationHandheld microphone35Signed offLive
    Primary care clinic A (example)AmbientMobile app18Signed offTesting
    Orthopedics clinic (example)AmbientMobile app9PendingConsent rule not approved
    Behavioral health (example)DictationHandheld microphone14Not startedPlanned
    During implementation, every department has a row: the product, how clinicians will capture audio and where setup stands.

  2. Step 2

    The configuration baseline

    Settings, shared content and ambient documentation rules are written down and approved by your documentation lead.

    Baseline v2 · Example Health System (fictional)

    Status
    Awaiting approval
    Prepared by
    Moraph speech platform engineer
    Approver
    Chief medical information officer
    Changes from v1
    5
    Ambient clinics proposed
    1 without privacy approval

    Key settings

    • Specialty vocabularies set for each department in scope
    • Shared auto-texts reviewed by health information management
    • Ambient capture only in clinics approved by the privacy officer
    • Mobile microphone app allowed only on managed devices
    Settings, shared content and ambient documentation rules are written down and approved by your documentation lead.

  3. Step 3

    A template change

    A new shared template goes from request to live with a review, an approval and a record of each step.

    Change CR-0418 · New cardiology follow-up auto-text

    1. Change requested for cardiology clinicsClinician
    2. Template checked against documentation policyHIM lead
    3. Change approvedDocumentation lead
    4. Auto-text built and testedMoraph engineer
    5. Change applied and clinicians toldMoraph engineer
    A new shared template goes from request to live with a review, an approval and a record of each step.

  4. Step 4

    A support ticket

    Second-line issues come to Moraph with what is known so far, and the record shows the cause and the fix.

    Ticket INC-20733 · Recognition errors after workstation update

    Reported by
    Service desk, Example Health System (fictional)
    Department
    Emergency department (example)
    Clinicians affected
    6
    Cause found
    Microphone driver missing from new workstation build
    Status
    Awaiting desktop team fix

    Actions so far

    • Profiles checked and found healthy
    • Issue reproduced on the new workstation build
    • Driver requirement sent to the desktop team
    • Interim workaround: affected clinicians using mobile app
    Second-line issues come to Moraph with what is known so far, and the record shows the cause and the fix.

  5. Step 5

    The licence review

    Each month, licences are checked against use so they go to clinicians who need them.

    DepartmentLicencesActive usersNot used in periodRecommendation
    Hospital medicine (example)45423Reclaim 3
    Emergency department (example)38353Offer refresher training
    Primary care clinic A (example)20182No change
    Surgery (example)301713Review with department lead
    Each month, licences are checked against use so they go to clinicians who need them.

  6. Step 6

    The monthly service review

    Usage, support, changes and incidents for the month, reviewed with your leads and turned into actions.

    Monthly service review · Example Health System (fictional)

    Period
    Sample month
    Tickets opened
    27
    Tickets resolved
    25
    Changes applied
    4
    Platform incidents
    1, notified the same day

    Actions agreed

    • Reclaim unused licences in hospital medicine
    • Refresher sessions for the emergency department
    • Finish privacy approval for the orthopedics clinic
    • Test after the planned EHR upgrade
    Usage, support, changes and incidents for the month, reviewed with your leads and turned into actions.

Workflows

The principal workflows

  1. Onboard

    Clinicians are given a Dragon licence and profile, a microphone or mobile microphone app, and the shared vocabulary and templates for their specialty, ready to use in the EHR.

    • New clinician request received from medical staff office or IT
    • Licence assigned and user created under the agreed naming rules
    • Specialty vocabulary and shared auto-texts applied to the profile
    • Microphone or mobile microphone app set up and tested in the EHR
    • Short orientation session and quick reference guide provided

  2. Document

    Clinicians dictate directly into the EHR, use voice commands and auto-texts to insert standard text, or, where ambient documentation is licensed, have a draft note produced from the visit conversation for them to edit.

    • Clinician signs in to the EHR and Dragon with their own account
    • Dictation or ambient capture used according to clinic policy
    • Patient told about and agrees to ambient capture where policy requires
    • Clinician reviews, corrects and completes the draft text
    • Clinician signs the note in the EHR

  3. Support and tune

    Moraph handles recognition, microphone and integration issues as second-line support, and maintains shared vocabulary and templates through approved changes.

    • Issue raised by the clinician, your service desk or Moraph monitoring
    • Moraph reproduces the issue and checks profile, device and EHR settings
    • Fix applied, or escalated to Nuance for platform defects
    • Vocabulary or template change requested where the issue is recurring
    • Change approved by the documentation lead and applied by Moraph

  4. Review

    Each month Moraph reports usage, support and change activity, and reviews it with your documentation lead to target training and licences where they are needed.

    • Licence and usage data gathered by department and user
    • Support tickets and recurring issues summarized
    • Template and vocabulary changes listed with their approvers
    • Inactive licences and users with low use identified
    • Actions agreed and tracked to the next review

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Documentation lead

Chief medical information officer, physician informatics lead, clinical documentation director

Owns how speech recognition and ambient documentation are used across the organization and approves what clinicians share.

Sees

  • The configuration baseline and every change made to it
  • Shared templates, auto-texts and local vocabulary
  • Usage, adoption and support reporting by department

Does

  • Approves the configuration baseline and changes to it
  • Approves shared templates and vocabulary additions
  • Decides which clinics use ambient documentation, with the privacy officer
  • Chairs the monthly service review with Moraph
  • Sets priorities for training and licence allocation

Cannot

  • Apply configuration changes in the platform directly
  • Approve a change they requested themselves when a second approver is named
Approvals
Approves the baseline, shared content changes and ambient documentation rollout; their own requests go to a named second approver.
Notified about
Changes awaiting approval, the monthly service report, and platform incidents that affect clinicians.

Clinician

Physician, advanced practice provider, nurse or therapist who documents in the EHR

Uses dictation or ambient documentation to produce notes, and stays responsible for every note they sign.

Sees

  • Their own profile, personal auto-texts and vocabulary
  • Shared templates for their specialty
  • Ambient draft notes for their own visits, where enabled

Does

  • Dictates into the EHR and uses voice commands and auto-texts
  • Uses ambient capture where the clinic allows it and the patient agrees
  • Reviews, corrects and signs each note
  • Keeps their own personal auto-texts and words
  • Reports recognition or device problems to the service desk

Cannot

  • Change shared templates or vocabulary
  • Use ambient capture in a clinic where it has not been enabled
  • See other clinicians' profiles or draft notes
Approvals
Requests for shared templates and new local terms go to the documentation lead.
Notified about
Their account being ready, planned changes that affect their specialty, and resolution of the issues they reported.

Health information management lead

HIM director, clinical documentation integrity manager, coding manager

Keeps shared templates and documentation practice consistent with documentation, coding and signature policy.

Sees

  • Shared templates and auto-texts with their change history
  • Documentation quality findings
  • Usage reporting by department

Does

  • Reviews proposed templates against documentation and coding policy
  • Records documentation quality findings linked to dictated or ambient notes
  • Requests template changes when findings recur
  • Takes part in the monthly service review

Cannot

  • Approve the configuration baseline
  • Change a clinician's profile or apply changes in the platform
Approvals
Their template reviews feed the documentation lead's approval.
Notified about
New template proposals and template changes that have gone live.

Privacy officer

Privacy officer, compliance officer, HIPAA privacy lead

Sets the rules for patient information and consent in ambient documentation and decides on privacy events.

Sees

  • Consent and use rules by clinic
  • Privacy events Moraph escalates
  • Business associate and vendor terms for the service

Does

  • Approves consent and notice rules for ambient capture
  • Approves enabling ambient documentation for each clinic
  • Decides on privacy events and whether notification is needed
  • Reviews Moraph staff access to the service

Cannot

  • Change configuration or templates
  • Delegate a breach notification decision to Moraph
Approvals
Approves ambient documentation rollout with the documentation lead, and decides every escalated privacy event.
Notified about
Privacy events, requests to enable ambient capture in a new clinic, and changes to Moraph staff access.

EHR or IT analyst

Clinical applications analyst, EHR analyst, service desk lead

Supports clinicians at the workstation and works with Moraph on EHR integration, devices and accounts.

Sees

  • Open support tickets and their status
  • Workstation, microphone and EHR integration settings
  • Licence and user lists

Does

  • Raises new user, leaver and change requests
  • Handles first-line issues and passes others to Moraph
  • Coordinates EHR upgrades and testing with Moraph
  • Approves Moraph administrator access to the service
  • Manages workstations and mobile devices under your policies

Cannot

  • Approve shared templates or the configuration baseline
  • Enable ambient documentation for a clinic
Approvals
Changes to EHR integration settings are approved by the documentation lead; access to devices follows your IT policies.
Notified about
Tickets escalated or resolved, planned changes, and Nuance service notices that affect workstations.

Moraph speech platform engineer

Moraph speech recognition engineer, clinical applications engineer

Configures and supports the Dragon service under change requests your organization has approved.

Sees

  • The platform administration console within the service's scope
  • Support tickets and the change record
  • Usage data needed to support users

Does

  • Creates and removes users and assigns licences
  • Maintains shared templates and local vocabulary under approved changes
  • Configures EHR and application integration with your analysts
  • Investigates second-line issues and escalates platform defects to Nuance
  • Tests changes before they go live where testing is possible

Cannot

  • Approve a change they will apply
  • Listen to recordings or read draft notes except where needed to resolve a ticket and your organization has agreed
  • Grant themselves additional administrator rights
Approvals
Every change they apply has an approved request; emergency actions follow the agreed procedure and are reported straight away.
Notified about
New tickets and requests, approvals granted, and Nuance service notices.

Moraph service manager

Moraph service delivery manager

Runs the service, reports on it and makes sure requests, changes and escalations reach the right people.

Sees

  • Service reporting, tickets, changes and escalations
  • Licence usage and renewal dates
  • Open actions from service reviews

Does

  • Prepares and runs the monthly service review
  • Tracks requests, changes and escalations to closure
  • Reports licence use and recommends reclaiming unused licences
  • Coordinates with Nuance on platform incidents and service notices

Cannot

  • Apply configuration changes
  • Make policy or privacy decisions for your organization
Approvals
Recommendations on licences and training go to the documentation lead for a decision.
Notified about
Escalations, overdue requests, and platform incidents.

Permissions at a glance

ActionDoc leadClinicianHIM leadPrivacyIT analystMoraph eng.Moraph service
Approve the configuration baselineApprovesNo accessView onlyView onlyView onlyNo accessView only
Request a configuration changeFullOwn work onlyFullFullFullNo accessNo access
Apply a configuration changeApprovesNo accessNo accessNo accessNo accessFullNo access
Change shared templates and auto-textsApprovesNo accessView onlyNo accessNo accessFullNo access
Keep personal auto-texts and wordsOwn work onlyOwn work onlyNo accessNo accessNo accessNo accessNo access
Enable ambient documentation for a clinicApprovesNo accessNo accessApprovesNo accessFullView only
Create users and assign licencesView onlyNo accessNo accessNo accessApprovesFullView only
Reset a profile or device settingNo accessOwn work onlyNo accessNo accessFullFullNo access
Decide on a privacy eventView onlyNo accessNo accessFullNo accessView onlyView only
Grant Moraph administrator accessView onlyNo accessNo accessView onlyApprovesNo accessView only
View change history and usage reportsView onlyNo accessView onlyView onlyView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Clinicians remain responsible for every note. Dragon and ambient documentation produce text; the clinician reviews, corrects and signs it, and nothing is signed on their behalf.
  • Moraph engineers apply changes; your organization approves them. Nobody approves a change they requested themselves when a second approver is named.
  • Moraph staff use named, individual administrator accounts with only the rights the service needs. Access to recordings or draft notes for support is limited to what a ticket needs and to what your organization has agreed.
  • Roles are agreed during implementation. Your IT team can keep first-line support and user setup, or hand them to Moraph, and the split is written into the responsibilities for the service.

Features

What it does

Speech recognition in the EHR

Dragon Medical One turns clinicians' dictation into text directly in the EHR and other clinical applications, configured for the applications you use.

Profiles that follow the clinician

Each clinician's speech profile and personal settings are held in the cloud, so they work on any configured workstation.

Specialty vocabularies

Dragon's medical vocabularies are set by specialty, and Moraph adds approved local terms such as clinic names and local drug formulary entries.

Shared auto-texts

Standard text such as exam templates and patient instructions is inserted by voice, maintained by Moraph and approved by your documentation lead.

Ambient documentation, where licensed

Where you license Nuance's ambient capability, a draft note is produced from the visit conversation for the clinician to review, edit and sign.

Mobile microphone

Clinicians can use a smartphone as a secure microphone through Nuance's mobile app where you allow it, configured with your device policy.

Consent and use rules

Clinic-level rules for when ambient capture may be used, how patients are told and how agreement is recorded, written with your privacy officer.

Licence management

Licences assigned, reclaimed and reported by department, so they go to clinicians who use them.

Second-line support

Moraph takes recognition, microphone, profile and EHR integration issues from your service desk and escalates platform defects to Nuance.

Controlled changes

Every change to shared templates, vocabulary or settings has a request, an approver and a record.

Usage and adoption reporting

Use by department and clinician, licences not used, and recurring support issues, reviewed monthly.

Onboarding and offboarding

New clinicians are set up from your requests, and departing clinicians' access is removed when your leaver process tells Moraph.

Integrations

How it connects to your systems

Connects toHowWhat flows
Electronic health recordDragon is configured to insert text into your EHR's note fields, and ambient draft notes are placed where your EHR integration supports it.Out: dictated text and draft notes into the EHR. Signing happens in the EHR.
Single sign-onStaff administrator access, and clinician sign-in where the platform supports it, go through your identity provider.In: user identity and group membership.
Virtual desktop and workstationsDragon is set up for the virtual desktop or workstation build your clinicians use, tested with your desktop team.Configuration only; no patient data exchanged.
Microphones and mobile devicesSupported handheld microphones and Nuance's mobile microphone app, deployed under your device management policies.Audio from the device to the Dragon service.
Your service deskTickets pass between your IT service management tool and Moraph's, so clinicians report problems in the usual place.In and out: ticket details and status, without patient information.
HR and medical staff recordsJoiner and leaver requests from your HR or medical staff office drive account creation and removal.In: name, role, department and start or end date.
Usage reportingUsage and licence data from the platform is combined with Moraph's ticket and change records for monthly reporting.Out: usage, licence and service reports to your documentation lead.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Business associate agreement

Moraph signs a business associate agreement with your organization because the service involves PHI, and Nuance's own agreement covers the platform.

Named Moraph administrators

Moraph staff work with individual accounts, the least administrator rights the service needs and multi-factor authentication; there are no shared accounts.

Role-based access

What each person at your organization and at Moraph can see and do follows their role; requesting a change is separate from approving it.

Complete audit trail

Moraph's change and ticket records show who did what and when, alongside the platform's own administration logs.

Encryption and keys

Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Audited company-wide

Moraph is audited to SOC 2 Type II and ISO/IEC 27001 across the company, including the teams that run this service. Nuance's own attestations cover the platform.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Open tickets and requests

For iT analysts and the Moraph service manager

Every open support ticket and service request with its age, category, department and status.

Break down by
Category, Department, Age band, Status
Delivered as
Live view; CSV export
Used for
Making sure clinician issues are followed up and none sit unresolved.

Joiners and leavers

For iT analysts and the documentation lead

Accounts created and removed in the period, with the request behind each and any leaver requests still open.

Break down by
Request type, Department, Status, Period
Delivered as
Live view; scheduled email
Used for
Confirming that new clinicians are ready to start and leavers lose access.

Recurring issues

For iT analysts, Moraph engineers

Support issues that keep coming back, grouped by cause such as microphone, profile, network or EHR integration.

Break down by
Cause, Department, Workstation type, Period
Delivered as
Monthly report; CSV export
Used for
Fixing causes rather than individual tickets.

Adoption and licences

Usage by department

For documentation lead and department heads

Active users and amount of dictation or ambient use by department and over time.

Break down by
Department, Specialty, Period, Product
Delivered as
Monthly report; CSV export
Used for
Seeing where clinicians use the service and where training would help.

Unused licences

For documentation lead and the Moraph service manager

Licences assigned to users who have not used the service in a period you set, with the user's department.

Break down by
Department, Product, Last used band
Delivered as
Monthly report
Used for
Reclaiming licences and offering help to clinicians who stopped using the service.

Ambient documentation rollout

For documentation lead and privacy officer

Clinics where ambient documentation is enabled, the date each was approved and by whom, and active users in each.

Break down by
Clinic, Approval date, Approver, Active users
Delivered as
Live view; PDF export
Used for
Keeping rollout to the clinics the organization approved.

Change and configuration

Change history

For documentation lead, HIM lead, auditors

Every change to settings, shared templates and vocabulary, with the request, approver and date applied.

Break down by
Change type, Approver, Date, Specialty
Delivered as
Live view; PDF and CSV export
Used for
Evidencing that shared content changes were reviewed and approved.

Shared template register

For hIM lead and documentation lead

Every shared template and auto-text in use, its specialty, owner and the date it was last reviewed.

Break down by
Specialty, Owner, Last review date
Delivered as
Live view; CSV export
Used for
Keeping shared text consistent with current documentation and coding policy.

Moraph administrator access

For privacy officer and IT analysts

Moraph staff with administrator access, their rights and when access was granted or last reviewed.

Break down by
Person, Rights, Granted date, Review date
Delivered as
Quarterly report; PDF export
Used for
Periodic review of who at Moraph can administer the service.

Service

Monthly service review

For documentation lead, IT lead and privacy officer

Tickets, changes, incidents, usage and licence position for the month, with open actions and recommendations.

Break down by
Month, Topic, Action owner
Delivered as
PDF; presented in the review meeting
Used for
Running the service with your organization and agreeing what to do next.

Platform incidents

For iT lead and documentation lead

Nuance service incidents in the period, when Moraph told you, the effect on clinicians and the follow-up.

Break down by
Incident, Date, Effect, Follow-up status
Delivered as
Monthly report; email at the time of the incident
Used for
Understanding how platform availability affected clinicians.

Exports, access and evidence

  • Reports are produced by Moraph from the platform's usage data and from Moraph's ticket and change records, and reviewed with you each month.
  • Usage reports show use of the service, not the content of notes. Moraph does not report on what clinicians wrote.
  • Reports can be exported to CSV, and summary reports to PDF, for your committees and for internal audit.
  • Report contents and frequency are agreed during implementation; additional views can be requested through the service review.
  • Change history and administrator access reports can be produced for a past period to answer audit and privacy questions.

Deployment

Where and how it runs

Licences through Moraph

Moraph resells the Dragon subscription and runs it as one service, subject to Nuance's terms.

Your existing Dragon licences

If you already license Dragon, Moraph reviews the current setup against a new baseline and takes over its operation.

Co-managed

Your team keeps some tasks, such as first-line support or user setup, and Moraph runs the rest; the split is written into the responsibilities for the service.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We review your EHR, workstation and virtual desktop builds, existing licences, departments in scope and current documentation policies with your IT and clinical leads.

Baseline design

We propose settings, specialty vocabularies, shared templates and support arrangements, and agree the baseline with your documentation lead.

Consent and use rules

Where ambient documentation is in scope, we draft clinic-level rules for patient notice, agreement and clinician review with your privacy officer.

Build and integration

The service is configured to the baseline and tested in your EHR and on your workstation builds and mobile devices.

Rollout by department

Clinicians are set up in waves with orientation, quick reference guides and extra support in the first weeks of each wave.

Handover to operations

Change process, approvers, support routes, escalation contacts and reporting are agreed, and the service moves into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Nuance. Nuance operates the Dragon platform, and Nuance's own service commitments, roadmap, maintenance and outages apply.
  • Dragon licences are subject to Nuance's terms. Ambient documentation and some other capabilities need their own licences.
  • Speech recognition and ambient documentation produce text that can contain errors. The clinician must review, correct and sign every note.
  • Moraph does not provide clinical documentation, coding or medical advice, and does not edit or sign notes on anyone's behalf.
  • Consent rules for recording patient conversations vary by state. Your organization decides its consent and notice policy; Moraph helps document and apply it.
  • EHR integration depends on what your EHR and Nuance support together. Some note fields or workflows may need manual steps.
  • Recognition quality depends on microphones, network and workstation builds that your organization manages.
  • Moraph does not make privacy or breach notification decisions; your privacy officer does.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. List your current licences and compare them with who actually uses the service
  2. Ask a few clinicians where dictation fails them today and check whether the proposed baseline addresses it
  3. Review the shared template process and confirm who approves shared text
  4. Walk through a support ticket from your service desk to Moraph and back
  5. If ambient documentation is in scope, review the draft consent and notice rules with your privacy officer
  6. Confirm the split of responsibilities between your IT team, Moraph and Nuance

Questions

Frequently asked questions

Do we buy Dragon from Moraph or from Nuance?

Either. Moraph can resell the subscription, or run licences you already hold. In both cases Nuance's terms apply to the licence.

Does Moraph sign a business associate agreement?

Yes. The service involves PHI, so Moraph signs a business associate agreement with your organization. Nuance's own terms and agreement cover the platform.

Who checks the notes?

The clinician. Dictated text and ambient draft notes are reviewed, corrected and signed by the clinician in the EHR. Moraph does not edit or sign notes.

What happens if the Dragon service is down?

Nuance's own service commitments and incident process apply. Moraph tells you when an incident affects clinicians, and your downtime plan, agreed during implementation, covers how they document in the meantime.

How is it priced?

Dragon licences are priced under Nuance's terms, and the managed service and implementation are quoted separately. See Working with Moraph for what drives a quotation.

Can we take the service back in-house?

Yes. At the end of the agreement Moraph hands over the configuration, shared templates, documentation and change history, and removes its administrator access.

Next steps

Evaluate Virtual Scribe

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Virtual Scribe guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Virtual Scribe support guide.

Related products