1. GRC for Healthcare and Hospitals
  2. Features
  3. Risks and controls
Feature · Risks and controls

Risks and controls

Keep the risk and its assigned control together.

OverviewMy risks
GRC for Healthcare and Hospitals · Risks and controls

My risks

Risks

New
IdTitleBusiness unitOwnerLikelihoodImpact
IDD-235Risk 1BU-8627330200
IDD-424Risk 2BU-4134550730
IDD-567Risk 3BU-9144390160
IDD-755Risk 4BU-9142860640
IDD-130Risk 5BU-2701560870
6 of 6 records
IDD-235Risks · RSK-59821
TitleRisk 1
Business unitBU-8627
Likelihood330
Impact200
Scale versionRev A
Example screen with sample data

What you can do

Work from the actual assessment

A risk belongs to a business unit and has a named owner, likelihood, impact and scale version. The scale version matters because a score is hard to interpret without knowing which scale the organization used. A control has its own code, description, effective date, status and owner. Linking it to the risk makes the reason for the control explicit.

A facility access risk can have a control requiring periodic access review. The control owner maintains the wording and effective date; the assessment owner selects it for a period and tests it through the assessment record. Retired controls remain understandable in historical work, while new plans should select controls appropriate to the period.

How the work is organized

  • One accountable parent. Keep each activity linked to the relevant assessment, risk, control or finding so the next person can follow the same case.
  • Named responsibility. Assign the record to the person who prepares the work and keep independent judgement with a separate reviewer where a decision is required.
  • Visible outcome. Use the recorded state, result, date and evidence to explain what happened before moving the case forward.

What to agree during setup

Agree the likelihood and impact scales before entering scores. Decide who may change a risk owner and who maintains a control description or effective date. Review business-unit ownership when the organization structure changes. A control code should remain stable enough for earlier test results to be traced to the control tested at the time.

Rehearse an active control whose owner belongs to the correct organization. Then inspect an old test after changing the control’s current status. The earlier result should still be explainable from its parent assessment, control link and recorded evidence reference.

Check the handoff on an actual case

Take a facility access risk owned by a team member in the business unit under review. The control owner checks the control code, effective date and active status before the assessment owner selects it for testing. Once a test is recorded, its link to that control and its own evidence reference explain what was tested at the time. If the control is later retired, keep the earlier test and risk context available for review.

What your team sees

  • My risks — Business-unit risks assigned to the current owner, with likelihood, impact and scale version.
  • Tests needing results — Planned tests that need a result from the selected control.

What it keeps track of

Data model
Risks
Risks held against a business unit on an explicit likelihood and impact scale.
Controls
Controls that mitigate a risk and are executed by a named owner.
Business units
Operating units and counterparties that assessments and risks attach to.
Team members
Named people who own, prepare and independently review work.

Who uses it

Permissions
Control Owner
, Assessment Owner, Admin

Set up GRC for Healthcare and Hospitals your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started