Administration
Roles and permissions in Virtual Scribe
Each role in Virtual Scribe: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Virtual Scribe as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Virtual Scribe. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Microsoft Dragon as part of the managed service.
Roles
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 Microsoft 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 Microsoft; 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 Microsoft 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 Microsoft 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
| Action | Doc lead | Clinician | HIM lead | Privacy | IT analyst | Moraph eng. | Moraph service |
|---|---|---|---|---|---|---|---|
| Approve the configuration baseline | Approves | – | View | View | View | – | View |
| Request a configuration change | Full | Own work | Full | Full | Full | – | – |
| Apply a configuration change | Approves | – | – | – | – | Full | – |
| Change shared templates and auto-texts | Approves | – | View | – | – | Full | – |
| Keep personal auto-texts and words | Own work | Own work | – | – | – | – | – |
| Enable ambient documentation for a clinic | Approves | – | – | Approves | – | Full | View |
| Create users and assign licences | View | – | – | – | Approves | Full | View |
| Reset a profile or device setting | – | Own work | – | – | Full | Full | – |
| Decide on a privacy event | View | – | – | Full | – | View | View |
| Grant Moraph administrator access | View | – | – | View | Approves | – | View |
| View change history and usage reports | View | – | View | View | View | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
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.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.