MunitasFeature tourAll walkthroughs

All walkthroughs / Health organisation

Health organisation · Roles and approvers

Ask for a role, and see who may grant it

A researcher asks to hold a role and cannot decide the request alone. The platform administrator, who runs Munitas itself, is refused when trying to grant it. The data custodian of a department grants it instead, and the grant starts out marked as never checked, which means that nobody has yet confirmed that the researcher still needs it.

9Steps
3People
about 7Minutes to read
Who is involved
Sam
Researcher in the Health organisation, asks for the role
Priya
Platform administrator, who runs Munitas itself
Hartley
Data custodian for the Cardiology department

How to read this page

Words used on this page

Organisation
A company or hospital group that uses Munitas. Each organisation sees only its own data.
Department
A team inside an organisation that owns some of its data, such as Cardiology.
Custodian
A person who holds the data custodian role, which allows deciding who may read data. A custodian decides for the departments they are an approver for.
Role
A named set of permissions that a person can hold, such as the permission to decide who may read a department’s data.
Platform administrator
The person who runs Munitas itself. The role gives no say over who may read any department’s data.
De-identification reviewer
A role that allows a person to review data from which identifying details have been removed, and to decide whether it may be released.
PART ONE

Sam asks for a role

A role is a named set of permissions that a person can hold, such as the permission to review data from which identifying details have been removed. Anybody in an organisation may ask to hold a role. Nobody may decide their own request, so asking and deciding are two separate steps done by two different people.

1
Sam
Sam opens the directory of people
Munitas console · People and roles

The directory lists every person the Health organisation has registered, the role each one holds, the department each one belongs to, and what each one may approve. Sam is a researcher and belongs to no department.

Screenshot: Sam opens the directory of people
Sam's own row reads Researcher, with none under Department and no under May approve. The custodians, such as Hartley for Cardiology, show a department and an approval scope, for example Cardiology only.
2
Sam
Sam asks to hold the role of de-identification reviewer
Munitas console · People and roles · the Ask for a role form at the bottom of the page

Sam fills in two fields. The first chooses the role, here de-identification reviewer, the role that allows a person to review data from which identifying details have been removed. The second is a written reason, which is stored with the request and read by whoever decides it.

Screenshot: Sam asks to hold the role of de-identification reviewer
The role field reads De-identification reviewer and the reason reads covering de-identification reviews while Imani is away. Imani is the person who holds the role today, as the directory above the form shows.
3
Sam
The request is waiting, and Sam cannot decide it
Munitas console · People and roles · Role requests waiting for a decision

Sam's request now appears under Role requests waiting for a decision. It has no buttons next to it, and the page says in words why there are none. Sam does not hold the role yet, because a request records a wish and changes no permission.

Screenshot: The request is waiting, and Sam cannot decide it
The request reads Sam asks to hold De-identification reviewer for 90 days, and under it, This is your own ask, so somebody else decides it. The Roles held list below still reads No roles.
PART TWO

The platform administrator is refused

Priya is the platform administrator, the person responsible for running Munitas itself and not for any one department's data. This part shows the platform administrator being refused. Somebody who could both run the platform and decide who holds a role on it could grant themselves anything, so the platform does not allow it.

4
Priya
Priya, the platform administrator, opens the same page
Munitas console · People and roles

Priya sees the same waiting request that Sam made. The page shows Priya the reason box and the two buttons, Grant it and Refuse, because the page does not decide in advance who may click. The platform decides when a button is pressed.

Screenshot: Priya, the platform administrator, opens the same page
The panel at the bottom left of the menu reads Priya and, under the name, Platform administrator, Support and reliability. Grant it is pale because no reason has been written yet, and it becomes usable once one is.
5
Priya
Priya tries to grant the role and is refused
Munitas console · People and roles · after pressing Grant it

Priya types the reason seems reasonable and presses Grant it. The platform checks the request against its access rules and answers with the reason it was refused, written as a sentence a person can read.

Screenshot: Priya tries to grant the role and is refused
The red panel reads Could not record this decision, then It was refused, for these reasons, and under it This person holds no role that may decide who holds a role. The reason is named, not a bare not allowed.
PART THREE

A custodian grants the role, and the grant starts as never checked

Granting a role is the job of a data custodian, the kind of person who already decides who may read a department's data. Here that is Hartley, the data custodian of the Cardiology department.

6
Hartley
Hartley, the data custodian for Cardiology, writes down why
Munitas console · People and roles

Hartley opens the same page and writes a reason before deciding. The platform stores the reason together with the decision, on the same request that Sam made.

Screenshot: Hartley, the data custodian for Cardiology, writes down why
The panel at the bottom left of the menu reads Hartley and, under the name, Data custodian for Cardiology. The reason reads Imani is away and reviews cannot wait, and Grant it is now fully coloured.
7
Hartley
The role is granted, and marked as never checked
Munitas console · People and roles · Roles held

Sam now holds the role. The row in Roles held shows who granted it, the date on which it lapses by itself, and when somebody last checked that it is still needed. Being granted a role and having that grant checked are two separate facts, and the page keeps them apart.

Screenshot: The role is granted, and marked as never checked
The row names Sam, the role De-identification reviewer and Hartley under Granted by, with a lapse date in Lapses and never checked under Last checked. A notice at the bottom right reads De-identification reviewer granted.
8
Hartley
Hartley confirms the grant is still needed
Munitas console · People and roles · Roles held

Pressing Still needed records that a named person looked at the grant on a named day. It does not extend the grant or change what it covers.

Screenshot: Hartley confirms the grant is still needed
The words never checked have been replaced by checked followed by the date. Lapses still shows the same date as in the previous step.
9
Hartley
Withdrawing the role ends it at once
Munitas console · People and roles · Roles held

Pressing Withdraw ends the grant immediately. Sam no longer holds the role, and the Roles held list shows what is true now.

Screenshot: Withdrawing the role ends it at once
Roles held reads No roles again, and the notices at the bottom right list the three things Hartley did: granted, Marked still needed and Withdrawn.