Incidents and validations

Common administrative incidents

Situation	What to check
A user cannot log in	Verify email, registration status, permissions, and whether access needs to be resent
A module does not appear	Check the assigned role and permission group
A professional does not see expected patients	Check locations, permissions, and configured relationships
A follow-up does not work as expected	Review the tracking type, its components, and whether there are associated alerts or forms
An alert does not arrive	Review the template, group, subscribers, and notification channel

Minimum validations after each change

• The change has been saved correctly.
• The user or element appears in the correct list.
• The visibility matches the expected permission.
• No other related module has been affected.

Module-specific validations

• Equipo: the user appears in the correct list with the expected permission.
• Localizaciones: the location appears in the hierarchy and does not break the existing organization.
• Tipos de seguimiento: the tracking can be reused and its components are as expected.
• Plantillas Alertas: the rule is in the correct tab with the appropriate criteria.
• Grupos de alertas: patients, templates, and subscribers match the actual intent.
• Formularios: the form displays correctly and has text that is understandable for the patient.
• Referencias externas: the linkage points to the correct user.

Temporary example for a visual validation after administrative changes.

Pending screenshot: show an actual list or detail screen after saving a change, where it is clearly visible that the result has been correctly applied.

When to escalate

It is advisable to escalate the incident when:

• the problem appears to be technical and not configuration-related
• an action affects sensitive data or multiple users
• the business rule is not clear
• the impact is clinical and requires care validation

Task closure

Before considering an administrative task as resolved, always verify the result from the perspective of the affected user or module.