Please note: The algorithm descriptions in English have been automatically translated. Errors may have been introduced in this process. For the original descriptions, go to the Dutch version of the Algorithm Register.

Common topics in case system

To see if questions can be handled easily based on web forms, all case descriptions are collected and see which questions are asked most frequently.

Last change on 21st of June 2024, at 7:52 (CET) | Publication Standard 1.0
Publication category
Impactful algorithms
Impact assessment
Field not filled in.
Status
Out of use

General information

Theme

Organisation and business operations

Begin date

7-2022

End date

12-2022

Contact information

algoritmeregister@stichtsevecht.nl

Responsible use

Goal and impact

Field not filled in.

Considerations

Few drawbacks because personal data is reduced to a minimum, while residents are facilitated in terms of information.

Human intervention

The outcome of the algorithm is processed manually. Of the frequently occurring topics, an employee checks whether these include topics that are interesting for follow-up steps (creating web forms or providing more information on the website).

Risk management

Before processing the data, all privacy-sensitive data are removed from the descriptions. This is done on the basis of automatic recognition of names and other personal data.

Operations

Data

Case data

Technical design

Before the data is processed, the descriptions are first anonymised. All personal data, such as names, addresses and other details are removed from the description. After this, a thesaurus (synonym list) is used to determine which words have the same meaning (as far as possible, within the context of the topic). A list is then generated of the topics that occur most frequently. This list is checked by a staff member to see if web forms are already present here. If this is not the case, it is considered whether it makes sense to make a web form for this available on the website or whether other provisions can be taken for this.

External provider

internally developed

Similar algorithm descriptions

  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 27th of August 2024, at 9:28 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 12th of September 2024, at 7:35 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 12th of September 2024, at 7:34 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 7th of August 2024, at 9:43 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 19th of September 2024, at 10:33 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use