US 12,094,588 B1
Rules-based processing of structured data
Thomas J. Hermey, Boonton, NJ (US); Tillman E. Johnson, Chapin, SC (US); Jhanvika Thakkar, Bridgewater, NJ (US); Timothy R. Tannert, Gibsonia, PA (US); Shantanu V. Bhide, Sewickley, PA (US); Shirin Vinayak, Short Hills, NJ (US); Glen R. McCloskey, Springfield Township, NJ (US); Neelanjana Panda, Jersey City, NJ (US); Milind Deodhar, Parsippany, NJ (US); and Rene' Charlene Bloemke, Woodland, WA (US)
Assigned to MANAGED HEALTH CARE ASSOCIATES, INC., Florham Park, NJ (US)
Filed by MANAGED HEALTH CARE ASSOCIATES, INC., Florham Park, NJ (US)
Filed on Oct. 30, 2020, as Appl. No. 17/085,631.
Claims priority of provisional application 62/929,231, filed on Nov. 1, 2019.
Int. Cl. G16H 20/10 (2018.01); G06F 9/54 (2006.01); G06F 16/25 (2019.01); G06N 20/00 (2019.01)
CPC G16H 20/10 (2018.01) [G06F 9/547 (2013.01); G06F 16/258 (2019.01); G06N 20/00 (2019.01)] 20 Claims
OG exemplary drawing
 
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, wherein the supplementary data comprises at least one of
a comment or instruction for a pharmacy worker, or
a notification relating to a future clinical intervention or future evaluation of a patient associated with the transaction,
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.