Risk UI components - Risk of Serious Harm (RoSH) widget #280
Replies: 5 comments 1 reply
-
|
UPDATE: When UNKNOWN LEVEL is because no RoSH summary has been completed we use a yellow outline along with "A RoSH summary has not been completed for this individual. Check OASys for this persons current assessment status." When UNKNOWN LEVEL is shown due to the system not being able to obtain the RoSH (whether it's there or not) We use the Grey outline along with the text "Something went wrong. We are unable to show RoSH information at this time. Try again later."
The use of UNKNOWN LEVEL rather than NO RoSH creates a little more uncertainty over RoSH and should encourage a user to double check OASys to understand the person on probations risk of serious harm. |
Beta Was this translation helpful? Give feedback.
-
ACCESSIBILITY UPDATES:Unpaid work DAC audit: Screen Magnification(Usability) |
Beta Was this translation helpful? Give feedback.
-
RoSH Component being is being used in the following services:
|
Beta Was this translation helpful? Give feedback.
-
|
This feels like we can answer "Does the design work across all probation services, or do we need variations" |
Beta Was this translation helpful? Give feedback.
-
Deciding if someone should be recalled or not - Accessibility issue |
Beta Was this translation helpful? Give feedback.
-
The Grand High Council of Risk UI - December 2022https://miro.com/app/board/uXjVPH939-Y=/?share_link_id=481664550142 |
Beta Was this translation helpful? Give feedback.
-
Background information
Do you think this component or pattern would be useful for other teams and services in MOJ?
Yes, for probation and prison teams needing to display risk information.
Name of product(s) this component or pattern relates to:
All HMPPS digital products and services that include risk information
What the product(s) do:
The widget shows a summary of the Risk of Serious Harm (RoSH) level for an individual.
The widget uses information from the legacy OASys risk assessment system to populate a mini-table showing:
Who the users are:
What the user need is for this component/pattern:
What already exists
Similar published components or patterns
N/A
GitHub discussions on similar topics
N/A
Have you tried using what already exists?
There is currently no single consistent HMPPS visual language for communicating risk in digital services.
When to use
Use this component/pattern to help users…
quickly absorb and interpret the risk of serious harm posed by an individual
develop a picture of the individual and their risks and needs
share and reuse risk information in a standard way with consistent meaning
Types of scale and call-out for each risk tool:
The information is presented in table form. The RoSH level is set by the probation practitioner based on a clinical assessment and the application of their professional judgement. It uses words rather than numbers. The words used are ‘low’, ‘medium’, ‘high’ and ‘very high’ and these are given unique and consistent colours.
How to use
When using this component or pattern, what should be considered when it comes to:
Establishing the potential victims
Based on OASys data, the categories of potential victims are:
The potential contexts are:
In any given case, one or more classes of potential victims may be excluded and not all risks will be present across both community and custody. Use N/A for any empty values.
Making sure it’s accessible?
Implementing in Figma?
A library of Risk components is available in the MoJ Figma account called Risk Components
It can also be viewed here
Implementing the code?
TBC
Using it in context with other components and as part of a service?
Side bar
In a document e.g. Community Payback Assessment PDF
when to use variations? (if applicable)
Things we don’t know enough about
Beta Was this translation helpful? Give feedback.
All reactions