The .Net CDM Builder was developed by Janssen Research & Development as a tool to transform its observational databases into the OMOP Common Data Model. The tool was specifically developed for the Janssen environment: SQL Server/Amazon Redshift/Amazon S3 as database and data storage platforms and Windows Servers and Microsoft.Net for running the application itself. Additionally, the builder logic designed is based on the input format of the source data that are loaded in our local environment. We have made the tool open-source as a reference for other researchers in the OHDSI community who may be looking ETL their observational data, but we do not expect the tool would execute successfully for others unless they have similar infrastructure and similar source datasets. The tool was not originally designed to support general purpose ETLs across different platforms, and modifications would be required to apply to other systems. Contributions from the community to advance the tool in that direction are welcome and encouraged, as our team cannot support and test the tool in other environments.

• The CDM Builder was created using the Microsoft .NET framework (version 4.6+) and is meant to be executed against Microsoft SQL Server 2012+ databases and Amazon Redshift databases.
• The CDM Builder is only intended to run in a Windows environment.

• .NET version 4.6+
• Visual Studio 2011+ is only required if you're looking to re-build the solution from source code
• SQL Server builds: SQL Server Native Client ODBC Driver (https://www.microsoft.com/en-us/download/details.aspx?id=36434)
• Amazon Redshift builds: Amazon Redshift (x64) ODBC Driver (http://docs.aws.amazon.com/redshift/latest/mgmt/install-odbc-driver-windows.html)

• A SQL Server or Amazon Redshift database of the OMOP Vocabulary must be accessible within your network. This will be used to map source concepts into CDM concepts.
• For SQL Server, SQL-based accounts are needed, as Trusted Connections via Windows Authentication are not supported.
• In the MAN\VOCAB_ADDITIONS folder, you will need to append these files to the OMOP Vocabulary (i.e. add the JNJ_TRU_P_SPCLTY file to the records already in SOURCE_TO_CONCEPT_MAP and do the same for the VOCABULARY table with JNJ_VOCABULARY).

• Download from the GitHub CDM Builder https://github.com/OHDSI/ETL-CDMBuilder/tree/master/source.
• The application requires the configuration of three databases: Source of non-CDM data, Destination (where to build the CDM data), and Vocabulary (the OMOP Vocabulary)
  • Connection strings and credentials for CDM Builder database can be configured either in the config file (org.ohdsi.cdm.presentation.buildingmanager.exe.config) or within the actual CDM Builder application (org.ohdsi.cdm.presentation.buildingmanager.exe)
  • Connection string examples (fill in the bolded values with your environment's values)
    • SQL Server (SQL-based accounts only)
      • Driver={SQL Server Native Client 11.0};Server=HOST_NAME;Database=VOCAB_DB_NAME;Uid=USER_NAME;Pwd=PASSWORD
    • Amazon Redshift
      • Driver={Amazon Redshift (x64)};Server=HOST_NAME;Database=CDM_DB_NAME;Sc=SCHEMA_NAME;Uid=USER_NAME;Pwd=PASSWORD;Port=PORT;SSL=USE_SSL;Sslmode=SSL_MODE
• As the Build process can be time- and resource-intensive, CDM Builder can be executed using multiple Windows servers. This is optional, but recommended, especially for larger databases.

• The CDM Builder comes with several pre-written ETLs, each of which corresponds to a specific data vendor and data product. Select the appropriate vendor from the "Vendor" dropdown
  • The vendors and products can be found here: https://github.com/OHDSI/ETL-CDMBuilder/tree/master/man
• Builder Settings
  • The “Number of batches” field can be used to specify if you want to convert the entire source database (0) or a sample size for testing purposes.
  • The “Batch size” refers to the number of person(s) that should be part of each those batches.
  • The “MaxDegreeofParallelism” establishes the number of processes to start on this particular machine. This value should be based on the hardware resources at your disposal.
  • It has been observed that a server with a 24-core CPU and 256 GB RAM should invoke 10 processes for optimal performance. Similarly, for a workstation with a 2-core CPU and 12 GB RAM, 3-4 processes was the best choice. Using these examples, you should determine the number of processes that fit best with your hardware configuration.

• User Guide: ETL-CDMBuilder
• Developer questions/comments/feedback: OHDSI Forum
• We use the GitHub issue tracker for all bugs/issues/enhancements

ETL-CDMBuilder is licensed under Apache License 2.0

###Development status Beta testing, source is not set up properly to deploy an executable this release.

Janssen Pharmaceutical Research & Development, LLC