Rules-based processing of structured data
A rules processing system includes one or more processors and one or more memory devices storing non-transitory, computer-readable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations. The operations include receiving, by an API gateway, a transaction from a pharmacy, the transaction having a first data format; reformatting, by a translation component, the transaction received by the API gateway into a structured data format used by a rules engine included in the rules processing system; evaluating, by the rules engine, one or more of fields of the transaction according to a configurable set of logic rules; inserting, into a wrapper of the transaction, supplementary data based on the evaluation of the one or more fields; reformatting, by the translation component, the transaction into the first data format; and transmitting, by the API gateway, the transaction to the pharmacy.
1 . A rules processing system comprising:
one or more processors, and
one or more memory devices storing non-transitory, computer-readable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving, by an application program interface (API) gateway, a transaction from a pharmacy, the transaction having a first data format,
validating, by the API gateway, that the pharmacy is authorized to access the rules processing system,
reformatting, by a translation component, the transaction received by the API gateway into a structured data format used by a rules engine included in the rules processing system,
evaluating, by the rules engine, one or more fields of the transaction according to a configurable set of logic rules, comprising at least one of
modifying values of the one or more fields, generating a rejection of the transaction, or generating an indication that at least some of the one or more fields do not violate the set of logic rules,
inserting, into a wrapper of the transaction, supplementary data based on the evaluation of the one or more fields,
reformatting, by the translation component, the transaction into the first data format, and
transmitting, by the API gateway, the transaction to the pharmacy,
wherein the wrapper comprises an extensible data structure having a plurality of fields, the plurality of fields including metadata of the transaction,
wherein the extensible data structure of the wrapper has a second data format different from the first data format,
wherein the first data format is incompatible with storage of the supplementary data, and
wherein the second data format is compatible with storage of the supplementary data, and
wherein reformatting the transaction into the first data format comprises retaining the wrapper in the second data format.
2 . The rules processing system of claim 1 , wherein evaluating the one or more fields comprises:
comparing a value in a first field of the one or more fields to a predetermined comparison value;
determining, based on a result of comparing the value to the predetermined comparison value, that a logic rule in the set of logic rules dictates a change to the value; and
changing the value in the first field to a modified value according to the logic rule.
3 . The rules processing system of claim 1 , wherein the supplementary data comprises an indication of at least one on-the-fly update performed on the transaction by the rules processing system.
4 . The rules processing system of claim 1 , wherein the supplementary data comprises an encoded instruction indicating one or more other operations to be performed by the pharmacy.
5 . The rules processing system of claim 4 , wherein the operations comprise:
accessing stored data indicating a format for the encoded instruction based on the pharmacy from which the transaction is received; and
generating the encoded instruction in the indicated format.
6 . The rules processing system of claim 4 , wherein the encoded instruction comprises a scripted command corresponding to executable code that, when executed, causes the one or more other operations to be performed.
7 . The rules processing system of claim 4 , wherein the wrapper comprises an indication of a format of the encoded instruction.
8 . The rules processing system of claim 1 , wherein inserting the supplementary data into the wrapper comprises:
adding a new field to the wrapper; and
inserting the supplementary data into the new field.
9 . The rules processing system of claim 1 , wherein the logic rules depend upon a set of pharmacy-specific parameters.
10 . The rules processing system of claim 1 , wherein the rules processing system comprises a cloud-based system remote from the pharmacy, and wherein the API gateway comprises an internet-accessible API gateway.
11 . The rules processing system of claim 1 , wherein the operations comprise:
comparing data in the transaction to stored data from one or more other transactions;
based on the comparison, generating an indication that a clinical intervention is needed for a patient associated with the transaction; and
including the indication in the supplementary data.
12 . The rules processing system of claim 1 , wherein the operations comprise:
applying a machine learning model to data in the transaction and to data included in one or more other transactions from one or more other pharmacies, to generate an outbreak prediction indicating a predicted disease outbreak; and
including the outbreak prediction in the supplementary data.
13 . A computer-implemented method for transaction processing by a rules processing system, the method comprising:
receiving, by an application program interface (API) gateway, a transaction from a pharmacy, the transaction having a first data format,
validating, by the API gateway, that the pharmacy is authorized to access the rules processing system,
reformatting, by a translation component, the transaction received by the API gateway into a structured data format used by a rules engine included in the rules processing system,
evaluating, by the rules engine, one or more fields of the transaction according to a configurable set of logic rules, comprising at least one of
modifying values of the one or more fields, generating a rejection of the transaction, or generating an indication that at least some of the one or more fields do not violate the set of logic rules,
inserting, into a wrapper of the transaction, supplementary data based on the evaluation of the one or more fields,
reformatting, by the translation component, the transaction into the first data format, and
transmitting, by the API gateway, the transaction to the pharmacy,
wherein the wrapper comprises an extensible data structure having a plurality of fields, the plurality of fields including metadata of the transaction,
wherein the extensible data structure of the wrapper has a second data format different from the first data format,
wherein the first data format is incompatible with storage of the supplementary data, and wherein the second data format is compatible with storage of the supplementary data, and
wherein reformatting the transaction into the first data format comprises retaining the wrapper in the second data format.
14 . The computer-implemented method of claim 13 , wherein the supplementary data comprises an encoded instruction indicating one or more operations to be performed by the pharmacy.
15 . The computer-implemented method of claim 14 , comprising:
accessing stored data indicating a format for the encoded instruction based on the pharmacy from which the transaction is received; and
generating the encoded instruction in the indicated format.
16 . The computer-implemented method of claim 13 , wherein inserting the supplementary data into the wrapper comprises:
adding a new field to the wrapper; and
inserting the supplementary data into the new field.
17 . A non-transitory, computer-readable medium storing instructions that, when executed by a computer system, cause the computer system to perform operations for transaction processing by a rules processing system, the operations comprising:
receiving, by an application program interface (API) gateway, a transaction from a pharmacy, the transaction having a first data format,
validating, by the API gateway, that the pharmacy is authorized to access the rules processing system,
reformatting, by a translation component, the transaction received by the API gateway into a structured data format used by a rules engine included in the rules processing system,
evaluating, by the rules engine, one or more fields of the transaction according to a configurable set of logic rules, comprising at least one of
modifying values of the one or more fields, generating a rejection of the transaction, or generating an indication that at least some of the one or more fields do not violate the set of logic rules,
inserting, into a wrapper of the transaction, supplementary data based on the evaluation of the one or more fields,
reformatting, by the translation component, the transaction into the first data format, and
transmitting, by the API gateway, the transaction to the pharmacy,
wherein the wrapper comprises an extensible data structure having a plurality of fields, the plurality of fields including metadata of the transaction,
wherein the extensible data structure of the wrapper has a second data format different from the first data format,
wherein the first data format is incompatible with storage of the supplementary data, and wherein the second data format is compatible with storage of the supplementary data, and
wherein reformatting the transaction into the first data format comprises retaining the wrapper in the second data format.
18 . The computer-readable medium of claim 17 , wherein the supplementary data comprises an encoded instruction indicating one or more other operations to be performed by the pharmacy.
19 . The computer-readable medium of claim 18 , wherein the operations comprise:
accessing stored data indicating a format for the encoded instruction based on the pharmacy from which the transaction is received; and
generating the encoded instruction in the indicated format.
20 . The computer-readable medium of claim 17 , wherein inserting the supplementary data into the wrapper comprises:
adding a new field to the wrapper; and
inserting the supplementary data into the new field.