The scenarios demonstrate the basics of the various data integration features. The corresponding Corticon Studio sample projects are very complete, requiring only minimal adjustments if you are using Microsoft SQL Server as the database installed locally. While the samples are loaded separately, there are very few dependencies -- the only considerable one is the Batch Rules Processing sample which requires that the ADC Database Connectivity has been loaded and setup.
The sample files as well as this document's discussion of samples and related database operations describe its use with Microsoft SQL Server 2014. For several other databases, SQL is supplied for the schema and data loading operations.
This guide refers to a script by its essential name. For example, the SQL script that sets up the patient schema and data on SQL Server is the sample's sql/sqlserver/patient_sqlserver.sql file. This guide refers to that as simply patient. Once a script has been run in the database, it does need to run again for another sample as the script is the same. The exception is the Batch sample's scripts as they are simply utilities.
Each sample section starts with advice about advancing from the previous section. Each topic within a Getting Started section indicates how hands-on users can just read through the steps that are pre-defined in the sample project assets.
If you choose, you could start at Multiple Database Connectivity, and work backwards to the ADC and then the EDC sample. You might see some unneeded data and tables yet all the required metadata and SQL Queries will process the samples as expected.
There are four Corticon samples that relate to data integration:
1. EDC Database Connectivity - The classic database connectivity in Corticon is EDC. Using Hibernate, the richness of database interaction is defined within Rulesheets. While this can be constraining, its simplicity is appropriate for many applications, as illustrated:
The EDC sample can be used as the basis for the ADC sample. It is a good idea though to close the EDC asset files to ensure that you keep the samples distinguished. SQL script: patient.
2. ADC Database Connectivity - Corticon Extensions are the foundation of the ADC functionality. The defined functions enable read and write functionality that are implemented in the sample's Ruleflow as Service Call-outs, where one call-out is enabling read functions while the other enables write functions, as illustrated:
The ADC sample can be used as the basis for the Multiple Database sample and is needed by the Batch Rule Processing sample. SQL scripts: patient and adc.
3. Multiple Database Connectivity - When database requirements expand across databases, ADC lets you define mappings to one database and then appropriate mappings to another database. This sample will demonstrate this implementation, where the first call-out reads patient data that it can use to then read more information about each patient's treatments from another database. Then the rules process the composite information and the status of certain treatments, before writing the results to the database, as illustrated:
SQL scripts: patient, adc and cms.
4. Batch Rule Processing - The batch sample compiles and deploys the ADC sample's Ruleflow to Corticon Server so that it can be defined in the Web Console as a batch process that will iterate a single query through large volumes of source input.
SQL utility scripts: clear_approved, and generate_patients. Requires that the ADC or MultiDatabase scripts have run.
