Compliance

Pharmacy user access review beyond staff departures

Run a pharmacy user access review that checks current roles, administrator rights, vendor accounts and evidence, with separate My Health Record obligations.

Krepko Team
30 October 2026·7 min read
A pharmacy staff member holds an identity badge beside a desktop monitor showing an abstract permissions grid.
Need to know

Limit internal access to personal information to staff who need it for their work

Source: OAIC
Separate privileges

ASD guidance distinguishes privileged access from ordinary work

Source: Australian Signals Directorate
Keep evidence

My Health Record participants must retain records of account authorisation and changes

Source: Australian Digital Health Agency
In this article
  1. 01What should the review cover?
  2. 02Does each permission still fit the person's role?
  3. 03Review administrator and supplier access separately
  4. 04What changes for My Health Record participants?
  5. 05How do you verify changes without losing accountability?
  6. 06Make the next review easier to complete

A pharmacy user access review asks whether today’s permissions still match today’s work. It covers continuing staff and support providers, not just people who left.

A technician may have moved roles. A locum account may remain active between engagements. A supplier may retain access granted during an earlier repair.

Our staff offboarding checklist addresses departure events. This guide adds a repeatable review of the accounts that remain, including permission changes and unresolved exceptions.

Key facts

  • OAIC guidance supports limiting access to people who need it for their work and reviewing security controls as circumstances change.
  • Review actual permissions, including administrator rights and support accounts, rather than accepting an old staff list.
  • Record decisions, verify changes and check My Health Record obligations separately for participating organisations.

What should the review cover?

Start with the systems holding patient, staff, financial and operational information. Ask each system owner for an account list and the permissions currently attached to it.

Include dispensing software, email, shared documents, ordering, rostering, payments and remote support. Check account recovery routes and connected applications as well as ordinary logins.

The OAIC APP 11 guidance describes reasonable protection against unauthorised access, modification and disclosure. A review helps examine those controls; it does not certify compliance.

Choose an accountable pharmacy owner and an authorised technical contact. The pharmacy explains who needs to do what; the administrator confirms what each permission permits.

Keep the review register in an approved restricted location. It can contain account identifiers and decisions without storing passwords, recovery codes or copied patient records.

Record the system, account holder, role, permissions, approver and decision date. Add a clear next action for any account whose purpose remains uncertain.

Does each permission still fit the person’s role?

Review the task behind each entitlement. A familiar name or current employment relationship does not explain why someone needs export, deletion or configuration rights.

Compare the approved role with actual system permissions. Ask whether the person needs to view records, edit them, approve transactions, manage users or administer the service.

Account or permissionQuestion to answerUseful decision evidence
Continuing employeeDoes this access match current duties?Role confirmation and permission report
Locum or contractorIs the current engagement still authorised?Named sponsor and agreed access period
AdministratorWhich privileged task requires these rights?Technical justification and separate ordinary account
Vendor supportWho can connect, and under what conditions?Support owner, agreed method and access record
Unidentified accountCan anyone establish ownership and purpose?Investigation outcome and approved restriction

Do not guess. A generic account may belong to a person, integration or service, so establish its purpose before making changes.

Our locum induction guide covers access before a shift. Carry any approved expiry or renewal decision into this continuing review.

Record both the permission and the job it enables. That pairing makes a later role change easier to assess than a list of account names alone.

Review administrator and supplier access separately

Examine privileged access separately because it can change how other people use a system. Ask the provider to explain the available controls in plain language.

ASD’s Restrict administrative privileges guidance distinguishes privileged from unprivileged environments and validates privileged-access requests. It is an implementation framework, not a universal pharmacy legal checklist.

Use it to question whether ordinary tasks need administrator rights. Confirm which account performs routine work and which account performs authorised administration.

For supplier support, identify the pharmacy contact who approves access. Ask whether access can be limited to the relevant system, purpose and support window.

Agree how support activity is recorded and how continuing access is reviewed. A closed helpdesk ticket does not, by itself, establish that remote access ended.

Where the system cannot offer narrower permissions, document the limitation. Ask the responsible administrator for proportionate controls and an agreed review date.

Avoid live experiments with patient records to discover what a permission allows. Use provider documentation, administrator reports or an authorised test environment instead.

What changes for My Health Record participants?

Treat My Health Record access as a specific participation obligation. Do not assume that a general pharmacy account audit fulfils its policy, training or record requirements.

As of October 2026, ADHA participation guidance refers to the My Health Records Rules 2026. Its security and access policy requirements now refer to Rule 21.

The guidance covers creating, modifying, suspending and deactivating user accounts. It also describes identifying individual users and keeping records of authorisation and account changes.

ADHA states that participating organisations must review the policy at least annually, when material risks change, and when requested by the System Operator. Its user-account management guidance also requires practices to be reviewed at least annually.

Have the responsible officer or organisation maintenance officer confirm the applicable process. Match the pharmacy’s review evidence to its current policy and the Agency’s guidance.

These specific annual requirements are not a claim that every pharmacy application has the same review interval. Check other obligations on their own terms.

How do you verify changes without losing accountability?

Approval is not removal. Separate the access decision from the technical change and its verification. An owner can approve removal while the account still remains active awaiting provider action.

Use clear states such as keep, narrow, suspend, investigate and completed. Record who authorised the decision and who will confirm the result.

Retain an administrator report or provider confirmation that identifies the permission removed, completion time and any dependency still needing attention.

Preserve required records and audit history through the authorised process. Do not delete an account merely to make the register look tidy without considering those records.

If the review reveals possible unauthorised use, preserve relevant evidence and involve the privacy or security lead. Follow the data breach response process where appropriate.

Do not borrow credentials. Ask the administrator to verify account status and arrange any necessary authorised testing.

An exception should name its owner, interim restriction and next decision date. Keep it visible until the change is verified or a justified continuing arrangement is approved.

Make the next review easier to complete

Choose a review cadence that reflects the systems, information and risks involved. Add event-triggered checks for role changes, new providers, suspected compromise and changes in system ownership.

The most useful review record is a decision history. It shows what changed since the last check and why remaining access still makes sense.

As an illustrative exercise, take a current employee with changed duties and a vendor account from an old support job. Ask who can approve their permissions.

Then ask the administrator to show how the decision would be implemented and evidenced. If nobody can demonstrate that path, assign the missing action before closing the review.

Finish with verified changes, a current permission register and an owned exception list. A spreadsheet marked reviewed is only useful when its decisions match the systems.

Frequently asked questions

How is a pharmacy user access review different from offboarding?
Offboarding closes access after a departure; a periodic review checks whether every current user, vendor and account still has justified permissions.
Is there one mandatory review interval for every pharmacy system?
No single interval is established here for all systems; set risk-based reviews and check any specific legal, contractual and system requirements separately.
Should an owner approve every existing administrator account automatically?
No. Ask what privileged task requires it, who controls the account, how its use is recorded and whether narrower access would meet the need.
Does the review replace My Health Record participation requirements?
No. Participating organisations must separately follow current My Health Record policy, user-account, training, review and record-keeping requirements.

Preparation note

Prepared with AI-assisted drafting and primary-source research. Examples and generated imagery are illustrative. Independent editorial and source reviews form part of publication checks.

Publisher: Krepko.

Sources

  1. Guide to securing personal information · Office of the Australian Information Commissioner · Retrieved
  2. Chapter 11: APP 11 Security of personal information · Office of the Australian Information Commissioner · Retrieved
  3. Restrict administrative privileges · Australian Signals Directorate · Retrieved
  4. My Health Record participation obligations · Australian Digital Health Agency · Retrieved

Keep reading

Join the Krepko waitlist

Follow the KSuite pilot and receive occasional practical guides on pharmacy operations and automation. No spam, unsubscribe any time.