Skip to main content
GullySystem
Healthcare

Roles and Permissions for Eye hospitals

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

An optometrist, ophthalmologist, optical-counter user and billing clerk need different parts of the eye-care record. Design permissions around those tasks and the hospital's policy. Access to a spectacle prescription does not require access to surgical notes, and the ability to prepare an invoice does not confer authority to amend a clinical finding.

Bring the records the workflow depends on.

  • Named hospital users, assigned locations and responsibilities across clinical, optical and billing work.
  • Record and action matrix for refraction, examination, surgery plans, prescriptions and charges.
  • Approval owners for temporary access, account closure and review of sensitive-record exports.

Outputs to check

  • Permission matrix showing each role's authorised view, entry, amendment and export actions.
  • Access-change history recording who approved an exception and when it expires or is withdrawn.

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Clinical information owner

Defines the clinical records each profession needs and approves changes to access boundaries.

System administrator

Applies the approved permissions and tests them with representative accounts without deciding clinical authority.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Optical user requests surgical notes

Reject the request unless a specific approved need changes the role; prescription visibility must not expose the complete encounter.

Temporary cover account

Set the authorised scope and end condition, keeping the covering person's own identity instead of borrowing a doctor's login.

Staff member leaves

Withdraw access through the offboarding process and retain attributed historical entries rather than deleting their authorship.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • An optical-counter test user can access the required spectacle details but cannot open or export surgical notes.
  • Billing permissions allow authorised charge work while preventing amendment of clinical examination fields.
  • Temporary access expires or is removed as approved, with the original author retained on existing patient records.
Eye hospitals

How the business operates.

An outpatient eye clinic moves in stages: registration, vision and refraction, a pressure check, the doctor’s exam, then dilation and a second look once the drops have acted.

Eye clinic queue with dilation status

Track each patient through registration, optometry, the doctor and dilation, with a status that shows who is waiting for drops and who is ready to be seen again.

Optometry and examination record

Record vision, refraction, pressure, slit-lamp and fundus findings in set fields for each eye, so the doctor, the optical counter and the next visit all read the same values.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Patient, visit and eye-specific examination record
  • Queue position and clinician-directed dilation status
  • Approved surgery plan, lens model and power
  • Lens serial or lot, consignment and patient-use record

Operational bottlenecks to check

Refraction is written twice

The optometrist’s readings are copied into the doctor’s notes and again at the optical counter. Each copy invites a mistake.

Dilated patients lose their place

Patients sent for drops rejoin the queue on someone’s memory, and the token order breaks down. Nobody knows who is ready.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Identify the patient and visit

    Create or locate the patient record and record the visit reason. Urgent needs follow the hospital’s clinical triage process rather than booking order.

  2. 2. Record the workup and examination

    Keep optometry measurements and clinician findings against the correct eye and visit. Record any clinician-directed change in queue status.

  3. 3. Prepare an approved procedure

    Where surgery is advised, organise the approved case, consent record, theatre slot and selected lens. Staff verify identity and laterality through the hospital’s own checks.

  4. 4. Record use and charges

    Record the lens and consumables actually used. Billing applies the approved package and separately authorised charges.

  5. 5. Coordinate follow-up and optical orders

    Use dates and prescriptions recorded by the clinical team for follow-up and spectacle orders. Keep the laboratory order and collection record separate from clinical findings.

Industry reports to connect with

  • Visit and queue status by work area
  • Approved theatre list and outstanding preparation items
  • Lens stock, consignment and patient-use reconciliation
  • Optical orders and insurer balances awaiting action

Questions before implementation.

When should eye hospitals consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of Named hospital users, assigned locations and responsibilities across clinical, optical and billing work.; Record and action matrix for refraction, examination, surgery plans, prescriptions and charges.; Approval owners for temporary access, account closure and review of sensitive-record exports. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. An optical-counter test user can access the required spectacle details but cannot open or export surgical notes. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements