US 11,810,203 B1 | ||
Computer architectures and associated methods for enabling real-time data determinations and distribution | ||
Eugene Kakaulin, New York, NY (US); Michael Tanenbaum, New York, NY (US); Andrew Stead, New York, NY (US); Eric Young, New York, NY (US); and Charles A. Jacoby, New York, NY (US) | ||
Assigned to Hippo Technologies LLC, New York, NY (US) | ||
Filed by Hippo Technologies LLC, New York, NY (US) | ||
Filed on Aug. 15, 2019, as Appl. No. 16/541,747. | ||
Application 16/541,747 is a continuation of application No. 15/897,083, filed on Feb. 14, 2018, granted, now 10,417,715, issued on Sep. 17, 2019. | ||
Int. Cl. G06Q 20/40 (2012.01); G06Q 40/08 (2012.01); G06F 16/29 (2019.01); G16H 20/10 (2018.01); G06F 3/0482 (2013.01) |
CPC G06Q 40/08 (2013.01) [G06F 3/0482 (2013.01); G06F 16/29 (2019.01); G06Q 20/40 (2013.01); G16H 20/10 (2018.01)] | 16 Claims |
1. A method for data processing comprising:
receiving, by at least a first server, patient data from a patient’s computer device, the patient data including prescription data and location data, wherein the prescription data corresponds to a prescribed medication, wherein the prescription data comprises prescriber information including at least a national provider identifier, and wherein the location data includes global positioning system coordinate data corresponding to a location of the patient’s computer device; receiving, by at least the first server, prescriber data from a second server, wherein the second server determines whether the national provider identifier in the prescriber information corresponds to a verified national provider identifier and the prescriber data indicates whether the prescriber information corresponds to an authorized prescriber; receiving, by at least the first server, medication data from a third server, wherein the medication data corresponds to the prescribed medication; receiving, by at least the first server, pharmacy data from a fourth server, wherein the pharmacy data includes first location data for a first pharmacy and second location data for a second pharmacy, wherein the first location data includes global positioning system coordinate data corresponding to a first location and the second location data includes global positioning system coordinate data corresponding to a second location, and wherein the first location and the second location are each within a predetermined distance from the location data of the patient’s computer device; sending, by at least the first server, an adjudication request associated with the prescribed medication to a fifth server, wherein the adjudication request is generated using the received patient data and the received medication data; receiving, by at least the first server, co-pay data from the fifth server in response to the adjudication request, wherein the co-pay data corresponds to a failed adjudication request, wherein the failed adjudication request is recorded in a decentralized ledger, and wherein the co-pay data includes co-pay data corresponding to the first pharmacy and co-pay data corresponding to the second pharmacy; and transmitting, by at least the first server, the co-pay data to the patient’s computer device, wherein the co-pay data is configured for display on a graphical user interface of the patient’s computer device, wherein the co-pay data corresponding to the first pharmacy is configured for display with the first location data and the co-pay data corresponding to the second pharmacy is configured for display with the second location data, and wherein the display of the co-pay data is continually refreshed so that the co-pay data may change if the adjudication request results in revised co-pay data. |