Workflow Kontrolle/en: Unterschied zwischen den Versionen

Aktuelle Version vom 3. Februar 2025, 11:52 Uhr

Rough overview of the general control workflow

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.

@@ Zeile 6: / Zeile 6: @@
 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 lang="de" dir="ltr" class="mw-content-ltr">
+====How are controls executed?====
-====Wie werden Kontrollen durchgeführt?====
+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.
-Umsetzer erhalten ein E-Mail, wenn die Kontrolle auslöst. Sie führen die Kontrollmaßnahme durch und füllen dann die Durchführungsbeschreibung aus. Optional kann eine Anmerkung hinzugefügt und Evidenzen hochgeladen werden. Dann wird die Kontrolle entweder den Prüfern zur Prüfung weitergegeben oder abgeschlossen, wenn keine Prüfer hinterlegt sind.
-</div>
-<div lang="de" dir="ltr" class="mw-content-ltr">
+====How are controls examined?====
-====Wie werden Kontrollen geprüft?====
+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.
-Wenn ein oder mehrere Prüfer hinterlegt sind, erhalten diese ein E-Mail, wenn die Kontrolle zur Prüfung bereitsteht. Sie überprüfen die Durchführungsbeschreibung und etwaige Evidenzen und entscheiden, ob diese in Ordnung sind. Wenn ja, akzeptieren sie die Kontrolle. Wenn nein, können sie eine Überarbeitung anfordern oder die Kontrolle ablehnen.
-</div>
-<div lang="de" dir="ltr" class="mw-content-ltr">
+====Who receives an e-mail when?====<b>Umsetzer:</b>
-====Weiterführende Links====
+<b>Implementer:</b>
-Mehr zum Erstellen von Kontrolldefinitionen für Experts und Professionals finden Sie [[Special:MyLanguage/Kontrolldefinitionen|hier]].<br>
+* Receives an e-mail when a control triggers on the basis of a control definition and is to be executed by them.
-Mehr zum Durchführen von Kontrollen für Practitioner finden Sie [[Special:MyLanguage/Kontrollen#Ausstehend|hier]].<br>
+* Receives an e-mail when their processing is no longer necessary (e.g., another implementer has executed the control).
-Mehr zum Prüfen von Kontrollen für Practitioner finden Sie [[Special:MyLanguage/Kontrollen#Prüfung_ausstehend|hier]].
+* Receives an e-mail when their processing is needed anew (e.g., an examiner has requested a reworking).
-</div>
+* Receives an e-mail when a reminder was configured and is sent.
+* Receives an e-mail when the control has failed.
+<b>Examiner:</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>
+* 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>
+* 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 [[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]].