The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Apr. 01, 2025
Filed:
Jul. 11, 2022
Bind Benefits, Inc., Minneapolis, MN (US);
Anthony Miller, Minneapolis, MN (US);
David Dickey, Minneapolis, MN (US);
Henning Chiv, Castro Valley, CA (US);
Matthew Chock, Eagan, MN (US);
Glen Eiden, Forest Lake, MN (US);
Trevor Fast, San Francisco, CA (US);
Shawn Wagoner, Minneapolis, MN (US);
Matthew Wiandt, Bloomington, MN (US);
Jessica Zeaske, Minneapolis, MN (US);
Nels Marcus Thygeson, San Rafael, CA (US);
Charley Hastings, Cape Coral, FL (US);
Jason Haupt, Maple Grove, MN (US);
Mark Peterson, Eagan, MN (US);
Maxwell L. Peterson, Minneapolis, MN (US);
Benjamin Kowitt, Philadelphia, PA (US);
Thomas Anton Klun, Minneapolis, MN (US);
Bind Benefits, Inc., Minneapolis, MN (US);
Abstract
The Use Determination Risk Coverage Datastructure for On-Demand and Increased Efficiency Coverage Detection and Rebalancing Apparatuses, Processes and Systems ('UDRCD') transforms coverage enrollment request, event signal, ACGG request, search request, props ratios calculation request, encounters build request, episodes build request, price calculation request, price range generation request, price range lookup request inputs via UDRCD components into coverage enrollment response, add-in recommendation, ACGG response, search response, props ratios calculation response, encounters build response, episodes build response, price calculation response, price range generation resp., price range lookup resp. outputs. An episodes build request datastructure identifying an encounter type is obtained. An anchor encounter datastructure is selected. A set of other encounter datastructures for the anchor encounter datastructure is determined. A props ratio relevance function associated with the encounter type is determined, and used to determine a set of accessory encounter datastructures for the anchor encounter datastructure. An episode datastructure is generated.