Automation library
>
Healthcare Administration
>
Notifications for confidential documents

Notifications for confidential documents

Emails the right people about confidential documents from a daily file and archives the file and the log.

Overview

Confidential documents must be reported to the right people. This automation reads the daily file, sends up to three notifications per record to the creator, the case manager, and a central mailbox, logs every result, and archives the file and the log.

What has changed

  • Less manual handling of sensitive documents
  • Notifications are faster and standardized
  • File handling is controlled and traceable

At a glance

SECTOR:
Disability care
System:
OneDrive, email
RUNS:
Daily
Technique:
Rule-based

In één oogopslag

SECTOR:
Disability care
Systeem:
OneDrive, email
RUNS:
Daily
Techniek:
Rule-based

Overzicht

Confidential documents must be reported to the right people. This automation reads the daily file, sends up to three notifications per record to the creator, the case manager, and a central mailbox, logs every result, and archives the file and the log.

Wat er verandert

  • Less manual handling of sensitive documents
  • Notifications are faster and standardized
  • File handling is controlled and traceable

How it works.

Daily file in progress
Record 1done
Record 2done
Record 3running
Email fields checked
Daily
Y
Yara notifies
the right people
Notifications up to 3 per record
Record 12 sent
Record 23 sent
Record 31 sent
File and log archived
The log is emailed and archived too.

What it does per record

  1. Loads the daily CSV file and moves it to 'in progress'
  2. Checks which email fields are populated for each record
  3. Sends up to three notifications per record
  4. Adds the outcome to a log
  5. Archives the CSV file
  6. Emails the log and archives it

Rules

A notification is sent to every recipient whose email address is provided, and records with missing recipient details are logged separately. Because the logic is fixed, the same input always produces the same result, and every run is logged.

Frequently asked questions.

Do we need to change our system?

No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.

Who builds and maintains the automation?

Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.

Can we see what it did?

Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.

What happens if something goes wrong?

Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.

Can it work for our process, even if it differs from this example?

Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.

Process not found?

Don't see your process listed? Let us know. We'll start with an automation scan to see what can be automated.