Workflow Kontrolle/en: Unterschied zwischen den Versionen
Aus HITGuard User Guide
Weitere Optionen
Isan (Diskussion | Beiträge) Die Seite wurde neu angelegt: „|center|thumb|900px|Rough overview of the general control workflow<br clear=all> ====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.“ |
Isan (Diskussion | Beiträge) Die Seite wurde neu angelegt: „Workflow control“ |
||
| Zeile 3: | Zeile 3: | ||
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. | 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. | ||
<div class="mw-translate-fuzzy"> | |||
====How can a control definition be created?==== | ====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.<p>It is determined for each control, in which rhythm it repeats. | 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.<p>It is determined for each control, in which rhythm it repeats. | ||
</div> | |||
====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. | ||
====Additional links==== | |||
== | Find more on the creation of control definitions for Experts and Practitioners [[Special:MyLanguage/Kontrolldefinitionen|here]].<br> | ||
Find more on the execution of controls for Practitioners [[Special:MyLanguage/Kontrollen#Ausstehend|here]].<br> | |||
Find more on the review of controls for Practitioners [[Special:MyLanguage/Kontrollen#Prüfung_ausstehend|here]]. | |||
Version vom 31. Januar 2025, 11:02 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?
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.
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.