Skip to main content
GullySystem
Healthcare

Roles and Permissions for Paediatric clinics

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.

The front desk sees bookings and fees, nurses see measurements and vaccines, and the paediatrician sees the full record. Locum doctors get access for their sessions. Parents see only their own child.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

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.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

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.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

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.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Paediatric clinics

How the business operates.

A paediatric clinic sees the same child visit after visit, year after year. A newborn check at one week, a vaccine at six, a fever at two years and a school form at five. The record has to follow the child, not the visit.

Child record with guardians

Hold each child’s date of birth, birth weight, allergies and guardians, with siblings linked under one family and separate files for each child.

Growth chart and measurements

Record weight, length or height and head circumference at every visit, and plot them against the growth reference your paediatrician chooses.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Child and family records. Hold date of birth, birth weight, allergies, guardians and contact numbers, with siblings linked to a family and a file for each child.
  • Growth chart and measurements. Record weight, height or length and head circumference at each visit and plot them on the reference chart your paediatrician selects.
  • Developmental milestone notes. Note when a child sat, walked and spoke, with screening questionnaires attached to the visit and the doctor’s remark beside each answer.
  • Vaccine schedule and dose log. Build a child’s schedule from the date of birth, log brand, batch and site for each dose, and list every dose that is overdue.

Operational bottlenecks to check

Vaccine schedules are tracked on a card

A missed rotavirus or measles dose is not noticed until the parent returns for a cough. The clinic’s register and the parent’s card each hold half the dates. Parents trust the card.

Weight-based dosing is worked out by eye

A syrup dose for a twelve-kilogram child is worked out in the doctor’s head. The weight is on the nurse’s slip and the dose is on the prescription. Neither is checked. A wrong figure is easy to miss.

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. Registration

    The desk opens a child record with date of birth, birth weight, allergies and guardians, and siblings are linked as one family. Nothing is typed twice.

  2. 2. Nurse check

    The nurse records weight, length or height, head circumference for infants, temperature and any oxygen saturation, and the numbers plot straight onto the growth chart.

  3. 3. Consultation

    The paediatrician reads the history and chart, examines the child, and writes the diagnosis and advice for the parent. Notes stay with the visit.

  4. 4. Prescription

    Syrups, drops and tablets are written as a dose per kilogram against the latest weight. The doctor confirms the volume before the slip prints.

  5. 5. Vaccination

    Doses due for the child’s age appear on the visit. The nurse logs brand, batch and injection site, and the schedule sets the next date for the booster.

  6. 6. Billing and recall

    The visit, any vaccine package and procedures are billed. Children with a dose or review coming up join the recall list, which the desk works through by phone.

Industry reports to connect with

  • Missed doses listed per vaccine, with the child’s age band beside each
  • Boosters falling due before month end, grouped by vaccine
  • Consultations split by doctor and the diagnosis recorded
  • Vials on the shelf by brand, batch number and expiry date

Questions before implementation.

When should paediatric clinics 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 User list; Role responsibilities; Record-level access rules. 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. Restricted records are inaccessible to unauthorised users. 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