IP Library › Granted Patent US 12,748,728
Granted Patent B2
US 12,748,728 · App. 18/802,926 · Granted Sep 29, 2026

Fault tolerant method for processing data with human intervention

Inventors: Carlos Vera-Ciro (Madison, WI); Robert Raymond Lindner (Fitchburg, WI)
Assignee: H1 insights, Inc.
G06F16/164
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,748,728
App. No.
18/802,926
Granted
Sep 29, 2026
Kind
B2
Abstract

The present disclosure is directed to methods and non-transitory program storage devices for identifying demographic information in an input data file even in the face of known errors that would otherwise prevent the method from operating. When a fault condition is detected, a fault handler may attempt to fix the faulty data, remove the faulty data from the input data file being processed, or provide the faulty data at a user interface so a human user can intervene. The method and storage devices may continue processing the data regardless of whether human input has been received because the system can bypass or remove the data, thereby keeping the method fault tolerant.

Claims (58)

1 . A computer-implemented method, comprising:

detecting, by one or more computing devices, a data type of one or more of a plurality of fields of demographic information associated with a data file from a third-party;

assigning, by the one or more computing devices, a naive label to the data type of the data file, wherein the data file comprises a mislabeled data type of the one or more of the plurality of fields of demographic information;

generating, by the one or more computing devices, a request for human intervention based on an identified exception condition associated with the mislabeled data type, further comprising:

providing, by the one or more computing devices via a user interface, a notification to notify a user device that the request for human intervention has been generated,

prior to receiving a user input at the user interface from the user device, bypassing, by the one or more computing devices, the mislabeled data type of the one or more of the plurality of fields of demographic information without interrupting an ongoing processing of the data file,

in response to the notification and receiving the user input, assigning, by the one or more computing devices, an active label to the mislabeled data type based on the received user input at the user interface, and

storing, by the one or more computing devices, one or more of the received user input and the assigned active label in a memory;

normalizing, by the one or more computing devices, naive labeled data and active labeled data; and

outputting, by the one or more computing devices, the normalized data using a format.

2 . The computer-implemented method of claim 1 , wherein:

the third-party is a healthcare provider;

the data file is a medical roster; and

the format is pre-specified by the healthcare provider.

3 . The computer-implemented method of claim 1 , the detecting of the data type is based on analyzing at least one of a semantic content, a data shape, a style, a name, or a phrase; and further comprising:

determining, by the one or more computing devices, the data type as at least one of an address or a phone number, based on analyzing at least one of a column type, a column title, a neighboring data type, or the active label stored in the memory.

4 . The computer-implemented method of claim 1 , further comprising suggesting, by the one or more computing devices, a possible data type for human confirmation based on determining a probability that the data type was identified correctly.

5 . The computer-implemented method of claim 1 , wherein the mislabeled data type with the active label is used as training data for at least one machine learning model.

6 . The computer-implemented method of claim 1 , wherein the one or more of the received user input and the assigned active label are used to determine an additional data type without being used as training data for a machine learning model.

7 . The computer-implemented method of claim 1 , further comprising validating, by the one or more computing devices, the normalized data.

8 . A non-transitory program storage device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

detecting a data type of one or more of a plurality of fields of demographic information associated with a data file from a third-party;

assigning a naive label to the data type of the data file, wherein the data file comprises a mislabeled data type of the one or more of the plurality of fields of demographic information;

generating a request for human intervention based on an identified exception condition associated with the mislabeled data type, further comprising:

providing, via a user interface, a notification to notify a user device that the request for human intervention has been generated,

prior to receiving a user input at the user interface from the user device, bypassing the mislabeled data type of the one or more of the plurality of fields of demographic information without interrupting an ongoing processing of the data file,

in response to the notification and receiving the user input, assigning an active label to the mislabeled data type based on the received user input at the user interface, and

storing one or more of the received user input and the assigned active label in a memory;

normalizing naive labeled data and active labeled data; and

outputting the normalized data using a format.

9 . The non-transitory program storage device of claim 8 , wherein:

the third-party is a healthcare provider;

the data file is a medical roster; and

the format is pre-specified by the healthcare provider.

10 . The non-transitory program storage device of claim 8 , the detecting of the data type is based on analyzing at least one of a semantic content, a data shape, a style, a name, or a phrase; and further comprising:

determining the data type as at least one of an address or a phone number, based on analyzing at least one of a column type, a column title, a neighboring data type, or the active label stored in the memory.

11 . The non-transitory program storage device of claim 8 , wherein the operations further comprise suggesting a possible data type for human confirmation based on determining a probability that the data type was identified correctly.

12 . The non-transitory program storage device of claim 8 , wherein the mislabeled data type with the active label is used as training data for at least one machine learning model.

13 . The non-transitory program storage device of claim 8 , wherein the one or more of the received user input and the assigned active label are used to determine an additional data type without being used as training data for a machine learning model.

14 . The non-transitory program storage device of claim 8 , wherein the operations further comprise validating the normalized data.

15 . A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to perform operations comprising:

detecting a data type of one or more of a plurality of fields of demographic information associated with a data file from a third-party;

assigning a naive label to the data type of the data file, wherein the data file comprises a mislabeled data type of the one or more of the plurality of fields of demographic information;

generating a request for human intervention based on an identified exception condition associated with the mislabeled data type, further comprising:

providing, via a user interface, a notification to notify a user device that the request for human intervention has been generated,

prior to receiving a user input at the user interface from the user device, bypassing the mislabeled data type of the one or more of the plurality of fields of demographic information without interrupting an ongoing processing of the data file,

in response to the notification and receiving the user input, assigning an active label to the mislabeled data type based on the received user input at the user interface, and

storing one or more of the received user input and the assigned active label in the memory;

normalizing naive labeled data and active labeled data; and

outputting the normalized data using a format.

16 . The system of claim 15 , the detecting of the data type is based on analyzing at least one of a semantic content, a data shape, a style, a name, or a phrase; and further comprising:

determining the data type as at least one of an address or a phone number, based on analyzing at least one of a column type, a column title, a neighboring data type, or the active label stored in the memory.

17 . The system of claim 15 , wherein the operations further comprise suggesting a possible data type for human confirmation based on determining a probability that the data type was identified correctly.

18 . The system of claim 15 , wherein the mislabeled data type with the active label is used as training data for at least one machine learning model.

19 . The system of claim 15 , wherein the one or more of the received user input and the assigned active label are used to determine an additional data type without being used as training data for a machine learning model.

20 . The system of claim 15 , wherein the operations further comprise validating the normalized data.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 29, 2026
From: VEDA DATA SOLUTIONS, INC
To: H1 INSIGHTS, INC.
Reel/Frame 073623/0895 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 11, 2025
From: VERA-CIRO, CARLOS; LINDNER, ROBERT RAYMOND
To: VEDA DATA SOLUTIONS, INC.
Reel/Frame 071681/0460 →
Continuity (3)
Continuation 18114002 · Feb 24, 2023
Provisional Application 63268534 · Feb 25, 2022
Related Publication 20240403267A1 · Dec 5, 2024
References Cited (18)
US 10521456B2 · Lindner · 2019 [cited by examiner]
US 10878334B2 · Lindner · 2020 [cited by examiner]
US 12105674B2 · Vera-Ciro et al. · 2024 [cited by applicant]
US 20130103637A1 · Dror · 2013 [cited by examiner]
US 20140149837A1 · Bedard · 2014 [cited by examiner]
US 20180060418A1 · Robichaud · 2018 [cited by applicant]
US 20190311299A1 · Lindner · 2019 [cited by examiner]
US 20190392075A1 · Han et al. · 2019 [cited by applicant]
US 20200409919A1 · Zhang · 2020 [cited by examiner]
US 20210174380A1 · Vera-Ciro et al. · 2021 [cited by applicant]
US 20210326519A1 · Lin · 2021 [cited by examiner]
US 20220309390A1 · Arnautov · 2022 [cited by examiner]
CN 112817847A · 2021 [cited by applicant]
Web Archive Screenshot of “Veda”, by Veda, Collectively Dated Jan. 26, 2021 (Year: 2021). [cited by examiner]
International Search Report and Written Opinion for Application No. PCT/US2023/063197, mailed on Jun. 2, 2023, 9 pages. [cited by applicant]
Web Archive Screenshot of “Veda,” by Veda, dated Jan. 26, 2021, 7 pages, (Available at https://web.archive.org/web/20210126055257/https://vedadata.com/) (Year: 2021). [cited by applicant]
Web Archive Screenshot of “Veda Data Alchemy,” by Veda, dated Dec. 1, 2020, 4 pages, (Available at https://web.archive.org/web/20201201210531/https://vedadata.com/products/alchemy/), (Year: 2020). [cited by applicant]
Web Archive Screenshot of “Veda Data Sentinel,” by Veda, dated Dec. 1, 2020, 4 pages, (Available at https://web.archive.org/web/20201201205737/https://vedadata.com/products/providersync/), (Year: 2020). [cited by applicant]