Managing data objects for graph-based data structures
AssigneeUnitedHealth Group Incorporated
InventorsRalph A. Korpman, Rudy R. Hilado, W. Randal Clegg, Cindy A. Post
Life of this patent
Estimating the term…
Abstract
Various embodiments provide methods, systems, apparatus, computer program products, and/or the like for managing, ingesting, monitoring, updating, and/or extracting/retrieving information/data associated with an electronic record (ER) stored in an ER data store and/or accessing information/data from the ER data store, wherein the ERs are generated, updated/modified, and/or accessed via a graph-based domain ontology.
Claims24
A method for executing an XML rule document via a rules engine, the method comprising:
- automatically identifying, by one or more processors, an XML, rule document comprising a rule to be applied to data stored in a plurality of database objects, wherein the XML rule document (a) is identified based at least in part on a rule identifier, (b) defines one or more of (1) selection criteria for the rule or (2) condition criteria for the rule, (c) identifies an action to be performed, and (d) identifies an observable packet data object based at least in part on an observable packet data object identifier;
- responsive to receiving the data stored in the plurality of database objects, programmatically evaluating, by the one or more processors, the data of each of the plurality of database objects using one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule;
- responsive to data of a first database object of the plurality of database objects satisfying one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule:
- identifying, by the one or more processors, the observable packet data object for the rule based at least in part on the observable packet data object identifier,
- automatically populating, by the one or more processors, one or more fields in the observable packet data object with data from an electronic record corresponding to the first database object,
- providing, by the one or more processors, the populated observable packet data object for ingestion processing, wherein the populated observable packet data object comprises the action to be performed for the electronic record corresponding to the first database object, and
- generating, by the one or more processors, a data artifact packet based at least in part on the populated observable packet data object.
A system comprising one or more processors, one or more memory storage areas comprising program code, the one or more memory storage areas and the program code configured to, with the one or more processors, cause the system to at least:
- automatically identify an XML rule document comprising a rule to be applied to data stored in a plurality of database objects, wherein the XML rule document (a) is identified based at least in part on a rule identifier, (b) defines one or more of (1) selection criteria for the rule or (2) condition criteria for the rule, (c) identifies an action to be performed, and (d) identifies an observable packet data object based at least in part on an observable packet data object identifier;
- responsive to receiving the data stored in the plurality of database objects, programmatically evaluate the data of each of the plurality of database objects using one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule;
- responsive to data of a first database object of the plurality of database objects satisfying one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule:
- identify the observable packet data object for the rule based at least in part on the observable packet data object identifier,
- automatically populate one or more fields in the observable packet data object with data from an electronic record corresponding to the first database object,
- provide the populated observable packet data object for ingestion processing, wherein the populated observable packet data object comprises the action to be performed for the electronic record corresponding to the first database object, and
- generate a data artifact packet based at least in part on the populated observable packet data object.
A computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code stored therein, the computer-readable program code is, when executed by one or more processors, configured to at least:
- automatically identify an XML rule document comprising a rule to be applied to data stored in a plurality of database objects, wherein the XML rule document (a) is identified based at least in part on a rule identifier, (b) defines one or more of (1) selection criteria for the rule or (2) condition criteria for the rule, (c) identifies an action to be performed, and (d) identifies an observable packet data object based at least in part on an observable packet data object identifier;
- responsive to receiving the data stored in the plurality of database objects, programmatically evaluate the data of each of the plurality of database objects using one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule;
- responsive to data of a first database object of the plurality of database objects satisfying one or more of (a) the selection criteria for the rule or (b) the condition criteria for the rule:
- identify the observable packet data object for the rule based at least in part on the observable packet data object identifier,
- automatically populate one or more fields in the observable packet data object with data from an electronic record corresponding to the first database object,
- provide the populated observable packet data object for ingestion processing, wherein the populated observable packet data object comprises the action to be performed for the electronic record corresponding to the first database object, and
- generate a data artifact packet based at least in part on the populated observable packet data object.
Dependencies are inferred from the claim text.