# US 2017/0255599 A1 · Anonymous reporting system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0255599 A1
- Document ID: US20170255599A1
- Status: Published application
- Kind: A1
- Application number: 15/443,917
- Filed: 2017-02-27
- Published: 2017-09-07
- Earliest claimed: 2002-11-05
- Assignees: Convercent, Inc.
- Applicants: Convercent, Inc.
- Inventors: Eugene F. Ferraro; Steven Foster; Kimberly L. Pfaff; Mary Eileen Persichetti; Briggin A. Palmer
- Web page: https://patentgrep.com/patent/US20170255599A1

## CPC

- G06F 16/335: Filtering based on additional data, e.g. user or group profiles (filtering in web context G06F16/9535, G06F16/9536)
- G06F 40/14: Tree-structured documents (parsing G06F40/205; validation G06F40/226)
- G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification}
- G06Q 10/00: Administration; Management
- G06Q 10/10: Office automation; Time management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

An anonymous reporting system for use in reporting and following up on incidents, accidents, and the like. The system may be accessed via an Internet website. A reporting individual may select a type of incident to report. In one example, the reporting individual may select a level on anonymity and some, none or all of the individual's personal identification is displayed to the organization according to the selected level.

## Claims

### Claim at position 1

-19. (canceled)

### Claim 20

A computer-implemented method of providing a reporting system for an exchange of incident information between a reporting party and an organization, comprising:
receiving, via an administration computing device, a designation of authorized users;
receiving, via the administration computing device, an assignment of a first set of authorized users to a first notification level and a second set of authorized users to a second notification level;
receiving, via a reporting party computing device, an incident report comprising: a type of report, an anonymity level, and incident information;
storing the incident report in a database;
assigning the incident report to the first notification level or the second notification level based on the type of report and the anonymity level;
in accordance with the incident report being assigned to the first notification level, transmitting a notification of the incident report to the first set of authorized users; and
in accordance with the incident report being assigned to the second notification level, transmitting the notification of the incident report to the second set of authorized users.

### Claim 21 (depends on 20)

The computer-implemented method of claim 20, wherein:
the incident report identifies the reporting party that initiated the incident report; and
a status is transmitted to the reporting party in response to the notification of the incident report being transmitted to either the first or second set of authorized users.

### Claim 22 (depends on 20)

The computer-implemented method of claim 20, wherein:
the incident report identifies a subject person that is a subject of the incident report; and
the notification of the incident report is not transmitted to the subject person.

### Claim 23 (depends on 22)

The computer-implemented method of claim 22, further comprising
if the incident report is assigned to the first notification level:
providing authorized access to the incident report to the first set of authorized users; and
denying authorized access to the incident report to the subject person.

### Claim 24 (depends on 20)

The computer-implemented method of claim 20, wherein the transmitting the notification comprises transmitting an email message having a link to the incident report.

### Claim 25 (depends on 20)

The computer-implemented method of claim 20, further comprising storing in the database a log of the notification.

### Claim 26 (depends on 20)

The computer-implemented method of claim 20, wherein the anonymity level comprises one of:
remain completely anonymous;
remain anonymous to the organization; and
do not care about anonymity.

### Claim 27 (depends on 26)

The computer-implemented method of claim 26, wherein if the anonymity level is do not care about anonymity, the incident report includes a name of the reporting party and contact information for the reporting party.

### Claim 28 (depends on 26)

The computer-implemented method of claim 26, wherein if the anonymity level is remain completely anonymous, information regarding the reporting party is not stored in the database.

### Claim 29 (depends on 20)

The computer-implemented method of claim 20, wherein the database is a relational database.

### Claim 30 (depends on 20)

The computer-implemented method of claim 20, further comprising:
in accordance with the incident report being assigned to the first notification level:
providing authorized access to the incident report to the first set of authorized users; and
denying authorized access to the incident report to the second set of authorized users.

### Claim 31

An incident reporting and management system, comprising
a database;
a device operating a report intake portal;
an organization portal; and
an application server configured to:
store, on the database, a list of authorized users, wherein each authorized user is assigned a notification level and a role;
receive, from the report intake portal, an incident report comprising: a type of report, an identification of a subject person, and incident information;
store the incident report in the database;
query the list of authorized users to generate a list of report recipients based on the type of report, the notification level of each authorized user, and the role of each authorized user;
exclude the subject person from the list of report recipients; and
transmit a notification of the incident report to users associated with the list of report recipients.

### Claim 32 (depends on 31)

The system of claim 31, wherein the application server is further configured to receive, from the report intake portal, a level of anonymity associated with the incident report.

### Claim 33 (depends on 32)

The system of claim 32, wherein the level of anonymity comprises one of:
remain completely anonymous;
remain anonymous to an organization; and
do not care about anonymity.

### Claim 34 (depends on 31)

The system of claim 31, wherein the report intake portal is configured for use with an Internet browser.

### Claim 35 (depends on 34)

The system of claim 34, wherein the Internet browser is facilitated using a secure website having data encryption configured for encrypting confidential data transmitted using the Internet browser.

### Claim 36 (depends on 31)

The system of claim 31, wherein the incident information includes confidential data.

### Claim 37 (depends on 32)

The system of claim 32, wherein the application server is further configured to, in response to receiving the level of anonymity of remain anonymous to the organization:
store contact information of a reporting party in the database; and
deny access to the contact information to the list of authorized users.

### Claim 38 (depends on 37)

The system of claim 37, wherein the application server is further configured to, in response to receiving the level of anonymity of do not care about anonymity, store contact information of a reporting party in the incident report.

### Claim 39 (depends on 31)

The system of claim 31, wherein the application server is further configured to grant access to the incident report to the users associated with the list of report recipients.
