Skip to main content

Data model configuration

Data Exploration lets researchers build cohorts with filter cards and look at them in charts and in the Person List. Two configurations control what it offers for a dataset:

  • Data model configuration: describes the underlying data model. It maps the tables and columns of a dataset, for example an OMOP CDM schema, to the person attributes, interactions and attributes Data Exploration can query.
  • Data Exploration configuration: describes what researchers see. It selects which filter cards and attributes are available, which charts are offered, and how the Person List looks.

The two build on each other:

Data model configuration (with versions)
▲ is based on one version of
Data Exploration configuration
▲ is assigned to
Dataset

Each Data Exploration configuration is based on exactly one version of a data model configuration. Each dataset uses exactly one Data Exploration configuration, which you choose when you create or update the dataset.

Where to find the configurations​

Both editors are in the Admin Portal under Setup:

ConfigurationCard in Setup
Data model configurationCDM configuration
Data Exploration configurationCohort builder config

You need the System admin role to open and change them.

Configurations that ship with Data2Evidence​

Data2Evidence ships a ready-to-use pair of configurations for each supported data model:

Data Exploration configurationData model configurationUse for
OMOPOMOP_DMOMOP CDM datasets
OMOP_HANAOMOP_HANA_DMOMOP CDM datasets on SAP HANA
OMOP_HANA_LEANOMOP_HANA_LEAN_DMOMOP CDM datasets on SAP HANA, reduced set of attributes
FHIR_ALLFHIR_DM_ALLFHIR datasets
FHIR_QRFHIR_QR_DMFHIR questionnaire responses
WAVEFORMWAVEFORM_DMWaveform data

For most deployments the shipped configurations are enough. Change them, or create your own, when you want to show additional attributes, hide attributes researchers do not need, or support a custom data model.

tip

Instead of editing a shipped configuration, duplicate it and change the copy. You keep the original as a fallback, and you can switch a dataset back to it at any time.

The shipped configurations are created on first start only. If you change them, your changes are kept across restarts and upgrades.