Staff role changes: update connected permissions

The decision

Treat a role change as a review of existing access as well as a request for new access. Identify systems that need separate handling when automatic updates are unavailable.

Rehearse this before accepting the change

Change a fictional staff role and inspect access across each connected tool.

Use fictional examples and an authorised test environment. Record what happened, the evidence you inspected and any issue that still needs a responsible owner.

Choose a useful measure

Count residual permissions awaiting review.

Agree the definition and baseline with the team doing the work. Review the result over a comparable period and note other changes that could affect it.

Healthcare data integration connecting two applications through a field-mapping board. — Agree what each field means and which system owns it.

Healthcare data validation separating matched records from an exception tray. — Make rejected or uncertain records visible for review.

Healthcare integration recovery with queued records, a retry route and a receipt check. — Plan recovery and confirm the receiving result.

Your planning worksheet

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordList all connected systems affected by the roleDefine access to add, retain or removeAssign ownership of manual exceptions

Evidence, open questions and decisionsNext action, responsible role and review date

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.

Related decisions

Turn the brief into a working service

Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.

Explore integrations & data services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.