The Getting Started techniques for data
integration are presented in this guide using a sample of medical patient records and
treatments that have been performed on the patient. The samples provide the SQL
statements that setup the table and sample data for many supported databases. All the
samples build on each other so that you understand that what is under discussion is
evolution of functionality in Corticon
data integration.
The scenarios demonstrate the essential concepts of the various data
integration options. The corresponding Corticon Studio sample projects use one or more databases or REST
services. Where a database is needed, the samples include SQL scripts to define the
schema and load sample data for many supported databases. Where REST is needed, the
samples use a test REST service hosted by Progress on AWS. With the exception of the
Batch Rule Process sample, the samples are independent. The Batch Rule Processing sample
requires the ADC Database Connectivity sample's database configuration to have been
performed and the decision service deployed to Corticon Server.
For database samples, this guide demonstrates usage with Microsoft SQL
Server. The techniques can be applied to other supported databases.
This guide refers to the included SQL scripts by their logical name.
For example, the SQL script that sets up the patient schema and data on SQL Server is
the file sql/sqlserver/patient_sqlserver.sql. 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.
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 Mixed Connectivity, and work
backwards to the other samples. You might see some unneeded data and tables yet all the
required metadata and SQL Queries will process the samples as expected.
There are six Corticon
samples that relate to data integration:
EDC Database Connectivity - The classic
database connectivity in Corticon is EDC. 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.
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.
Multiple Database Connectivity - With ADC you
can access multiple databases. The data read in from one database can even be used
when querying data from another database. This sample will demonstrate the use of ADC
to read patient and treatment data from one database and then access a second
database to retrieve detailed information about a type of treatment. The rules
determine if a treatment is approved and the results are saved to the patient and
treatment database, as illustrated:
REST Connectivity - The REST sample
demonstrates the use of Corticon's REST Connectivity for accessing REST services from
rules. The sample calls a REST service to retrieve the reimbursement rates for a
medical procedure given a procedure code. There may be multiple rates for a procedure
with different effective date ranges.
Mixed Connectivity - This sample mixes ADC
and REST datasources to demonstrate the flexibility of Corticon's data access
capabilities. The sample builds on the Multi Database Sample, adding to it the
retrieval of reimbursement rate data as is done in the REST connectivity sample.
.
Batch Rule Processing - The batch sample
does not include any rule assets. It contains SQL scripts to populate a test database
with additional records to better explore the batch rule processing concepts. This
guide will show how to use the Web Console perform batch rule processing.
