Context
Access to medical data must take account of duties and the work context
In healthcare facilities, permissions cover HIS, EDM, laboratory, diagnostics, pharmacy, billing and administrative systems. Staff work in shifts, across many wards and under different forms of contract. At the same time some access concerns particularly sensitive personal data.
sara.next can act as the layer for managing requests and the periodic assessment of permissions, taking into account role, ward, organisational unit or functional scope. It does not replace the access control performed directly in the medical system.
Use cases
Sample use cases
New staff
Granting roles to newly hired or contract staff.
Change of ward
Modifying the access scope when someone changes ward.
External suppliers
Controlled provision of systems to external suppliers.
Medical records
Reviewing permissions to applications that process medical records.
End of collaboration
Documenting approvals and the removal of permissions after collaboration ends.
Scenario
A doctor working on two wards
The request specifies the doctor role and the wards where access is needed. An authorised process owner approves the scope. When the doctor stops working on one ward, the relevant access dimension is modified. A review makes it possible to confirm whether the remaining assignments are justified.
01 · Request
- Roledoctor
- Role dimensionthe wards where access is needed
02 · Decisions
- Approving the scopeauthorised process owner
- Stopping work on one wardmodifying the access dimension
- Reviewjustification of the remaining assignments
03 · Effect
- Access on the wardsin line with the role and dimension
- Historyapprovals and changes
emergency access — a separate project
An implementation expert's view
Governance must not get in the way of providing care
In healthcare you have to be particularly careful that governance does not get in the way of providing care. Emergency ("break glass") access, cover arrangements and on-call duty require a separate design, clear rules and follow-up control.
You should not present a standard IGA workflow as a substitute for emergency access mechanisms in the HIS.
Scope
Limits and risks
Implementation requires verification of:
- integration with the specific HIS/EDM,
- regulations on medical records,
- emergency access rules,
- data protection,
- continuity of care.
NoteWhether automatic implementation is possible depends on the target system's interfaces and its permission model.
Map staff roles and permissions in a selected medical system
During a technical consultation we will go through your applications, roles and the scope of the first implementation stage.