Administration
Roles and permissions in Patient Privacy Monitoring
Each role in Patient Privacy Monitoring: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Patient Privacy Monitoring 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 Patient Privacy Monitoring. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Imprivata Patient Privacy Intelligence as part of the managed service.
Roles
Privacy officer
Chief privacy officer, HIPAA privacy officer, privacy and compliance director. Owns the privacy monitoring program: what is monitored, how strictly, and the decisions that follow a finding.
- Sees: All rules, protected-patient groups and their versions; Alert volumes, escalations, findings and sanctions; Every case and its evidence; Monthly service reports
- Does: Approves rules, thresholds and protected-patient groups; Agrees the triage runbook and what counts as a legitimate reason; Reviews findings and decides whether a breach occurred; Records notifications to patients, HHS, state agencies or the media; Samples alerts Moraph has closed for quality review; Reviews the monthly service report with Moraph
- Cannot: Apply rule changes directly; Moraph applies approved changes; Edit or delete case history or the audit trail; Investigate a case in which they are the employee or the patient
- Approvals: Approves every rule change, protected-patient group and runbook change, and every breach determination; changes they propose themselves need a second approver your organization names.
- Notified about: Escalated cases involving protected patients, findings ready for decision, feed failures and changes waiting for approval.
Privacy investigator
Privacy analyst, privacy investigator, compliance specialist. Investigates escalated alerts and records a finding with its rationale.
- Sees: Cases assigned to them and the evidence Moraph attached; The user's access history and the patient's encounters relevant to the case; Earlier cases for the same employee, where their role allows
- Does: Reviews evidence and requests further access history; Contacts managers and interviews employees under your procedures; Records the finding and its rationale; Refers substantiated findings to HR; Prepares patient access reports for complaints
- Cannot: Change rules or protected-patient groups; Work a case involving themselves, a relative or a direct colleague; Decide sanctions or breach determinations
- Approvals: Findings are reviewed by the privacy officer before referral to HR or any breach assessment.
- Notified about: Cases assigned to them, evidence requests completed and cases returned with comments.
HR partner
HR business partner, employee relations specialist. Decides, with the employee's manager, the sanction that follows a substantiated finding, under your sanctions policy.
- Sees: Findings referred to HR and the evidence summary; The employee's earlier findings and sanctions; Sanctions recorded across the organization by category
- Does: Reviews referred findings with the employee's manager; Decides and records the sanction; Records retraining or other follow-up; Closes the referral when actions are complete
- Cannot: See alerts or cases not referred to HR; Change a finding; Change rules or configuration
- Approvals: Sanctions follow your HR policy and approval process; the service records the outcome.
- Notified about: New referrals and referrals approaching the follow-up date your policy sets.
EHR and data administrator
EHR analyst, integration analyst, HRIS analyst. Keeps the access log, HR and registration extracts flowing to Patient Privacy Intelligence and fixes problems at the source.
- Sees: Feed specifications and schedules; Feed health results and failure tickets; Data quality issues found in their extracts
- Does: Builds and maintains extracts from the EHR, HR and registration systems; Fixes extract failures and data quality problems; Tells Moraph before EHR upgrades or changes that affect logs; Maintains the mapping of system accounts to employees
- Cannot: See alerts, cases or findings; Change rules
- Approvals: Extract changes follow your organization's change process.
- Notified about: Feed failures, late files and data quality issues in their extracts.
Moraph privacy analyst
Moraph privacy analyst, healthcare compliance analyst. Works the alert queue under your runbook so your team handles only the alerts that need a decision.
- Sees: Alerts and the access details behind them; The user's role and department and the patient's encounters relevant to the alert; Earlier alerts for the same user
- Does: Reviews each alert for a documented legitimate reason; Closes alerts with a reason code and note under the runbook; Escalates alerts without a clear reason, with evidence attached; Prepares patient access reports when your privacy team asks; Flags rules that produce many alerts with legitimate reasons for tuning
- Cannot: Contact employees, managers or patients; Record findings, sanctions or breach determinations; Close alerts on protected patients without your privacy team's review, unless the runbook allows it
- Approvals: Their closures are sampled by your privacy officer, and alerts the runbook reserves are escalated rather than closed.
- Notified about: New alerts, alerts approaching the age the runbook sets, and closures returned after quality review.
Moraph platform engineer
Moraph platform engineer, healthcare integration engineer. Configures Patient Privacy Intelligence and its data feeds so detection reflects your decisions and your data.
- Sees: Rule configuration and its version history; Feed health and data quality results; Imprivata release notes and service notices
- Does: Configures relationship, protected-patient and other rules; Tests rule changes against recent activity and reports the result; Applies approved changes and records each version; Connects and monitors data feeds; Raises platform issues with Imprivata support
- Cannot: Apply a rule change without your approval; Work alerts or cases; Change source systems or extracts
- Approvals: Every rule and protected-patient change is approved by your privacy officer first.
- Notified about: Feed failures, approved changes ready to apply and Imprivata service notices.
Auditor (read-only)
Internal auditor, external auditor, compliance reviewer. Reviews the program's rules, decisions and evidence without being able to change anything.
- Sees: Rule versions and approval records; Cases, findings and sanctions within the scope granted; Monthly service reports and the audit trail
- Does: Searches and reads records within their scope; Exports reports they have been given access to, with each export logged
- Cannot: Change, approve or delete anything
- Approvals: Their access is approved by the privacy officer, with a scope and an end date.
- Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.
Permissions at a glance
| Action | Privacy officer | Investigator | HR partner | EHR admin | Moraph analyst | Moraph engineer | Auditor |
|---|---|---|---|---|---|---|---|
| Approve rules and thresholds | Approves | – | – | – | – | – | – |
| Configure rules and data feeds | – | – | – | – | – | Full | – |
| Maintain protected-patient groups | Approves | – | – | – | – | Full | – |
| Provide access log and HR extracts | – | – | – | Full | – | View | – |
| Triage and close alerts | Full | View | – | – | Full | – | – |
| Work investigations | Full | Own work | – | – | – | – | – |
| View patient and employee details | Full | Own work | Own work | – | Own work | – | View |
| Record a finding | Approves | Own work | – | – | – | – | – |
| Record a sanction | View | – | Full | – | – | – | – |
| Record a breach determination | Full | – | – | – | – | – | – |
| View reports | View | View | Own work | Own work | View | View | View |
| View audit trail | 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
- Nobody investigates themselves or people close to them: investigators and analysts are kept off cases involving their own records, relatives or direct colleagues, and such cases go to the privacy officer or a designee.
- The triage runbook sets what Moraph analysts may close without asking, what counts as a documented legitimate reason, and which alerts, such as those on protected patients, always go to your privacy team.
- Moraph identifies and documents; your organization decides. Findings, sanctions and breach determinations are recorded only by your staff.
- Every view of a case or of patient and employee details is logged, including views by your privacy team and by Moraph. Auditors get temporary read-only access with a scope and an end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.