Access & roles

Resolve missing buttons and read-only encounter views

Check context, active record state and assigned permissions before escalating a missing clinical action.

Current source · source reviewed · 3 min read

Before you begin

Know the patient, facility, encounter and action you are trying to use.
Use your own assigned account.

1. Confirm the facility and selected encounter

Read the sidebar header and encounter details. The selected encounter can differ from the primary encounter currently open. The source permits writing to the selected encounter only from facility scope, when it matches the primary encounter and has an active status.

2. Check whether the episode is inactive

Completed, Cancelled, Discontinued and Entered in Error encounters are treated as inactive in the documented clinical workflows. Actions such as new notes, service requests and medication administration may be hidden or disabled. Use the approved completion or correction workflow rather than creating a duplicate episode to regain a button.

3. Distinguish basic encounter access from clinical access

Reading the encounter and reading clinical data are separate checks. The current provider permits clinical reading through the relevant patient-level or encounter clinical permission. The Overview displays a no-permission state when clinical-data reading is unavailable.

4. Review department and care-team access

Linked encounter departments, the department owning the current bed and care-team membership can affect who may open the encounter. Ask an authorized administrator to inspect the actual group and encounter relationships.

5. Give the administrator a precise issue

State the action label, patient-safe record reference, facility, encounter status and the observed message. The administrator can compare the intended role with the permissions matrix and scope of the user link. Keep patient data out of public support channels.

Roles and scope

A role assignment belongs to a group such as an organization, facility or department. Possessing a similarly named role elsewhere does not establish access to this encounter. The documented role-link workflow allows users to grant only permissions they themselves hold.

Restart is separately controlled

A completed encounter can be eligible for a Restart action in the interface, while the backend still enforces the configured time limit. The audited default restart limit is zero hours.

Troubleshooting

The Overview is visible but clinical panels are missing

Check clinical-data permission on the patient or encounter. Viewing basic encounter information does not automatically permit clinical data.

An earlier encounter is read-only while the current one is editable

Check whether the selected encounter differs from the primary encounter and whether it is inactive. The provider deliberately limits edits to the active primary encounter in facility scope.

The role name looks correct but the action is still unavailable

Check the role’s actual permissions and group scope, plus the record state and feature configuration. A role name alone is insufficient evidence.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.