Computer architectures and associated methods for enabling real-time data determinations and distribution
Computer architectures and associated methods for real-time data processing are disclosed. In some embodiments, a trial adjudication request for a cost determination can be received by a first server and verified using a security protocol, wherein a password token of the trial adjudication request can be matched to a stored password token. The first server can transmit an adjudication command packet to a second server that includes at least one data set of a plurality of data sets and a command for a claim determination, and can receive a response packet from the second server. The first server can determine that a successful claim determination was performed by the second server from the response packet, and can transmit a reversal request packet to the second server which can cancel the successful claim determination. The first server can perform the electronic calculation using the claim data.
1. A method for data processing comprising:
receiving patient data from a first server based upon input from a patient's computer device, wherein the patient data comprises prescription data and location data, wherein the prescription data corresponds to a prescribed medication;
sending a derived data request associated with the prescribed medication to a second server, wherein the derived data request is generated using the received patient data and comprises a first encrypted password token for verifying the derived data request;
receiving medication data from the second server in response to the derived data request after the second server verifies the derived data request using the first encrypted password token, wherein the medication data corresponds to the prescribed medication;
sending an adjudication request associated with the prescribed medication to a third server, wherein the adjudication request is generated using the received patient data and the received medication data and comprises a second encrypted password token for verifying the adjudication request; and
receiving co-pay data from the third server in response to the adjudication request after the third server verifies the adjudication request using the second encrypted password token;
wherein the co-pay data is transmitted 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, and wherein the co-pay data is continually refreshed and new co-pay data is transmitted to the patient's computer device in real time if the adjudication request results in revised co-pay data.
2. The method of claim 1 , wherein the medication data further corresponds to alternatives to the prescribed medication.
3. The method of claim 1 , wherein the patient data includes insurance data.
4. The method of claim 1 , wherein a co-pay adjudication is generated in response to the adjudication request, and the co-pay adjudication generates the co-pay data.
5. The method of claim 4 , wherein the co-pay adjudication is reversed based upon a reversal request to cancel the co-pay adjudication.
6. The method of claim 4 , wherein the co-pay adjudication uses a masked data structure that corresponds to a national provider identifier (NPI) of a pharmacy.
7. The method of claim 1 , wherein the co-pay data corresponds to at least a co-pay associated with the prescribed medication.
8. The method of claim 1 , wherein the co-pay data corresponds to a failed adjudication request.
9. The method of claim 8 , wherein the failed adjudication request is recorded in a decentralized ledger.
10. A data processing system comprising:
a first receiver configured to receive patient data from a first server based upon input from a patient's computer device, wherein the patient data comprises prescription data and location data, wherein the prescription data corresponds to a prescribed medication;
a first transmitter for sending a derived data request associated with the prescribed medication to a second server, wherein the derived data request is generated using the received patient data and comprises a first encrypted password token for verifying the derived data request;
a second receiver configured to receive medication data from the second server in response to the derived data request after the second server verifies the derived data request using the first encrypted password token, wherein the medication data corresponds to the prescribed medication;
a second transmitter configured to send an adjudication request associated with the prescribed medication to a third server, wherein the adjudication request is generated using the received patient data and the received medication data and comprises a second encrypted password token for verifying the adjudication request; and
a third receiver configured to receive co-pay data from the third server in response to the adjudication request after the third server verifies the adjudication request using the second encrypted password token;
wherein the co-pay data is transmitted 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, and wherein the co-pay data is continually refreshed and new co-pay data is transmitted to the patient's computer device in real time if the adjudication request results in revised co-pay data.
11. The data processing system of claim 10 , wherein the medication data further corresponds to alternatives to the prescribed medication.
12. The data processing system of claim 10 , wherein the patient data includes insurance data.
13. The data processing system of claim 10 , wherein a co-pay adjudication is generated in response to the adjudication request, and the co-pay adjudication generates the co-pay data.
14. The data processing system of claim 13 , wherein the co-pay adjudication is reversed based upon a reversal request to cancel the co-pay adjudication.
15. The data processing system of claim 13 , wherein the co-pay adjudication uses a masked data structure that corresponds to a national provider identifier (NPI) of a pharmacy.
16. The data processing system of claim 10 , wherein the co-pay data corresponds to at least a co-pay associated with the prescribed medication.
17. The data processing system of claim 10 , wherein the co-pay data corresponds to a failed adjudication request.
18. The data processing system of claim 17 , wherein the failed adjudication request is recorded in a decentralized ledger.