Introducing LIVERULES

LiveRules – The Modern Business Rules Engine

LiveRules is a simple, yet very powerful rules processor for the modern business demand for both traditional and big data systems. 

What is LiveRules?

LiveRules suite has LiveRules Editor (LRE), LiveRules Processor (LRP) and LiveRules Administrator (LRA). LRE is a web based interface to create and author the business Rules which can then be processed by the LiveRules Processor (LRP). LiveRules Administrator (LRA) is the administrative component which allows to manage and administrate the entire LiveRules suite of components. LiveRules supports various features which are really needed for the fast paced development and deployment needs.

LiveRules employs a unique design which supports not just one specific database or a particular data model.

LiveRules is designed to support any Java supported RDBMS database and building your own business dictionary out of any Database through our user-friendly web based system. LiveRules also supports the big data right out of the box. LiveRules has evolved to support the NoSQL big data systems like MongoDB. The business dictionary can be now mapped for the MongoDB right out of the box.

LiveRules allows the users to map JSON and XML documents as input data elements. LiveRules supports JSON document mapping and the XML document mapping right out of the box.

Once the business dictionary is built, you can use our web- based LRE system to create the rules. LiveRules processor then knows how to load various values from your database based on your own business dictionary for processing your rules. This is where the LiveRules brings in the real value addition of developing at a great pace and also supporting various systems for their native RDBMS database / MongoDB rather than going with a specific vendor’s database and their data model to be used for their rules engine support.

Introducing liveclaims


A revolutionary big data healthcare adjudication system. 

LiveClaims is based on micro-services based architecture using Docker containers and Kubernetes which scales horizontally using the cloud native methodologies.  The claims adjudication has been a very slow process traditionally and LiveClaims breaks that using horizontally scaling NoSQL and Clustering RDBMS technologies to reach multi-million claims in an hour instead of days.

What is LiveClaims?

Unique healthcare design has evolved from early concepts such as “do the sick no harm” from Florence Nightingale, Hospitals and healthcare facilities are continually changing to meet new regulatory requirements, introduce new technologies and continue providing a healing environment for patient care. LiveClaims provides a fully Web based application that adapts to continuous changes through its unique design and technologies by reducing the investment in system changes and shortening the Return On Investment (ROI) time frame and ensure efficient, economical management with effective health care outcome.

LiveClaims is designed to provide a cohesive management for providers to enroll in the program, update enrollment information, verifying patient eligibility, submit a claim online and know instantly if it is approved for payment. Additionally, providers can request service authorization. Beneficiary can inquire for their own coverage, eligibility status and service authorizations. At the core LiveClaims provides claim, member and provider management.

LiveClaims architecture illustrates the modern micro-services using containers. Developing a Modular system brings about separating out common activities, tasks and business events into common reusable components/services. The API Gateway is the core service mediator for a successful MITA architecture implementation. API Gateway is flexible in integrating the system with external sources or COTS product coupled with security management. Each component interacts through API Gateway and all the interfaces follow the standards (X12). Application is engineered to interact to legacy or public administrative sources to facilitate data migration and with other necessary data sources