Workflow Kontrolle/en: Unterschied zwischen den Versionen
Weitere Optionen
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
Isan (Diskussion | Beiträge) Die Seite wurde neu angelegt: „====Who receives an e-mail when?====<b>Umsetzer:</b> <b>Implementer:</b> * Receives an e-mail when a control triggers on the basis of a control definition and is to be executed by them. * Receives an e-mail when their processing is no longer necessary (e.g., another implementer has executed the control). * Receives an e-mail when their processing is needed anew (e.g., an examiner has requested a reworking). * Receives an e-mail when a reminder was configu…“ |
||
Zeile 12: | Zeile 12: | ||
If one of more examiner are configured in the control, they receive an e-mail when the control is ready for review. They inspect the execution description and any evidences and decide whether they are in order. If so, they accept the control. If not, they can request a reworking or reject the control. | If one of more examiner are configured in the control, they receive an e-mail when the control is ready for review. They inspect the execution description and any evidences and decide whether they are in order. If so, they accept the control. If not, they can request a reworking or reject the control. | ||
====Who receives an e-mail when?====<b>Umsetzer:</b> | |||
= | <b>Implementer:</b> | ||
<b> | * Receives an e-mail when a control triggers on the basis of a control definition and is to be executed by them. | ||
* | * Receives an e-mail when their processing is no longer necessary (e.g., another implementer has executed the control). | ||
* | * Receives an e-mail when their processing is needed anew (e.g., an examiner has requested a reworking). | ||
* | * Receives an e-mail when a reminder was configured and is sent. | ||
* | * Receives an e-mail when the control has failed. | ||
* | <b>Examiner:</b> | ||
<b> | * Receives an e-mail when the implementer forwards the control for examination. | ||
* | * Receives an e-mail when their processing is not longer necessary (e.g., another examiner has reviewed). | ||
* | * Receives an e-mail when a reminder was configured and is sent to the examiner as well. | ||
* | * Receives an e-mail when the control has failed. | ||
* | <b>Functional esalation:</b> | ||
<b> | * Receives an e-mail when a threshold was configured and met. | ||
* | * Receives an e-mail when the deadline of the control is exceeded. | ||
* | <b>Management system responsible:</b> | ||
<b> | * Receives an e-mail when a threshold was configured and met. | ||
* | |||
====Additional links==== | ====Additional links==== |
Aktuelle Version vom 3. Februar 2025, 11:52 Uhr

What is a control?
A control definition is the basis of a usually repeating task, which is created in HITGuard and assigned an implementer for execution and an examiner for review. A control is the task that triggers based on the repetition rhythm and that is executed and reviewed.
How can a control definition be created?
Experts and Professionals can freely create control definitions, create them in the course of interviews for reviews, create them directly out of a risk or opportunity for its treatment, or create them in the context of a case management dossier. Experts and Professionals can decide between freely creating a control definition or creating it from a knowledge base template.
It is determined for each control, in which rhythm it repeats.
How are controls executed?
Implementers receive an e-mail when the control triggers. They execute the control measure and fill in the execution description. Optionally, they can leave a remark and upload evidences. Then the control is forwarded to the examiners for review or closed, if no examiner was configured.
How are controls examined?
If one of more examiner are configured in the control, they receive an e-mail when the control is ready for review. They inspect the execution description and any evidences and decide whether they are in order. If so, they accept the control. If not, they can request a reworking or reject the control.
====Who receives an e-mail when?====Umsetzer: Implementer:
- Receives an e-mail when a control triggers on the basis of a control definition and is to be executed by them.
- Receives an e-mail when their processing is no longer necessary (e.g., another implementer has executed the control).
- Receives an e-mail when their processing is needed anew (e.g., an examiner has requested a reworking).
- Receives an e-mail when a reminder was configured and is sent.
- Receives an e-mail when the control has failed.
Examiner:
- Receives an e-mail when the implementer forwards the control for examination.
- Receives an e-mail when their processing is not longer necessary (e.g., another examiner has reviewed).
- Receives an e-mail when a reminder was configured and is sent to the examiner as well.
- Receives an e-mail when the control has failed.
Functional esalation:
- Receives an e-mail when a threshold was configured and met.
- Receives an e-mail when the deadline of the control is exceeded.
Management system responsible:
- Receives an e-mail when a threshold was configured and met.
Additional links
Find more on the creation of control definitions for Experts and Practitioners here.
Find more on the execution of controls for Practitioners here.
Find more on the review of controls for Practitioners here.