Chapter 5 The Common Data Model

Chapter lead: Clair Blacketer

Observational data provides a view of what happens to a patient while receiving healthcare. Data are collected and stored for increasingly large numbers of patients all over the world creating what is often called Big Health Data. The purpose of these collections are threefold: (i) directly to facilitate research (often in the form of survey or registry data), or (ii) to support the conduct of healthcare (usually called EHR - Electronic Health Records) or (iii) to manage the payment for healthcare (usually called claims data). All three are routinely used for clinical research, the latter two as secondary use data, and all three typically have their unique formating and encoding of the content.

Why do we need a Common Data Model for observational healthcare data?

Depending on their primary needs none of the observational databases capture all clinical events equally well. Therefore, research results must be drawn from many disparate data sources and compared and contrasted to understand the effect of potential capture bias. In addition, in order to draw conclusions with statistical power we need large numbers of observed patients. That explains the need for assessing and analyzing multiple data sources concurrently. In order to do that, data need to be harmonized into a common data standard. In addition, patient data require a high level of protection. To extract data for analysis purposes as it is done traditionally requires strict data use agreements and complex access control. A common data standard can eleviate this need by omitting the extraction step and allowing a standardized analytic to be executed on the data in it’s native environment - the analytic comes to the data instead of the data to the analytic.

This standard is provided by the OMOP Common Data Model (CDM). The CDM, combined with its standardized content (see chapter 6), will ensure that research methods can be systematically applied to produce meaningfully comparable and reproducible results. In this chapter we provide an overview of the data model itself, design, conventions, and discussion of select tables.

An overview of all the tables in the CDM is provided in Figure 5.1.

Overview of all tables in the CDM version 6.0. Note that not all relationships between tables are shown.

Figure 5.1: Overview of all tables in the CDM version 6.0. Note that not all relationships between tables are shown.

5.1 Design Principles

The CDM is optimized for typical observational research purposes of

  • Identifying patient populations with certain healthcare interventions (drug exposure, procedures, healthcare policy changes etc.) and outcomes (conditions, procedures, other drug exposures etc.),
  • Characterization of these patient populations for various parameters like demographic information, disease natural history, healthcare delivery, utilization and cost, morbidities, treatments and sequence of treatment etc.,
  • Predicting the occurrence of these outcomes in individual patients - see chapter 14,
  • Estimating the effect these interventions have a population - see chapter 13,

To achieve this goal, the development of the CDM follows the following design elements:

  • Suitability for purpose: The CDM aims to provide data organized in a way optimal for analysis, rather than for the purpose of addressing the operational needs of health care providers or payers.
  • Data protection: All data that might jeopardize the identity and protection of patients, such as names, precise birthdays etc. are limited. Exceptions are possible when the research expressly requires more detailed information, such as precise birth dates for the study of infants.
  • Design of domains: The domains are modeled in a person-centric relational data model, where for each record the identity of the person and a date is captured as a minimum. Here, a relational data model is one where the data is represented as a collection of tables linked by primary and foreign keys.
  • Rationale for domains: Domains are identified and separately defined in an entity-relationship model if they have an analysis use case (conditions, for example) and the domain has specific attributes that are not otherwise applicable. All other data can be preserved as an observation in the observation table in an entity-attribute-value structure.
  • Standardized Vocabularies: To standardize the content of those records, the CDM relies on the Standardized Vocabularies containing all necessary and appropriate corresponding standard healthcare concepts.
  • Reuse of existing vocabularies: If possible, these concepts are leveraged from national or industry standardization or vocabulary definition organizations or initiatives, such as the National Library of Medicine, the Department of Veterans’ Affairs, the Center of Disease Control and Prevention, etc.
  • Maintaining source codes: Even though all codes are mapped to the Standardized Vocabularies, the model also stores the original source code to ensure no information is lost.
  • Technology neutrality: The CDM does not require a specific technology. It can be realized in any relational database, such as Oracle, SQL Server etc., or as SAS analytical datasets.
  • Scalability: The CDM is optimized for data processing and computational analysis to accommodate data sources that vary in size, including databases with up to hundreds of millions of persons and billions of clinical observations.
  • Backwards compatibility: All changes from previous CDMs are clearly delineated in the github repository (https://github.com/OHDSI/CommonDataModel). Older versions of the CDM can be easily created from the current version, and no information is lost that was present previously.

5.2 Data Model Conventions

There are a number of implicit and explicit conventions that have been adopted in the CDM. Developers of methods that run against the CDM need to understand these conventions.

5.2.1 General conventions of the model

The OMOP CDM is considered a “person-centric” model, meaning that all clinical Event tables are linked to the PERSON table. Together with the date or start date this allows for a longitudinal view on all healthcare-relevant Events by person. The exceptions from this rule are the standardized health system data tables, which are linked directly to Events of the various domains.

5.2.2 General conventions of schemas

Schemas, or database users in some systems, allow for separation between read-only and read-write tables. The clinical Event and vocabulary tables are in the “CDM” schema and are considered read-only to the end user or analytic tool. Tables that need to be manipulated by web-based tools or end users are stored in the “Results” schema. The two tables in the “Results” schema are COHORT and COHORT_DEFINITON. These tables are meant to describe groups of interest that the user might define, as detailed in chapter 11. These tables can be written to, meaning that a cohort can be stored in the COHORT table at run time. Since there is only one read-write schema for all users it is up to the implementation of the CDM how multiple user access is organized and controlled.

5.2.3 General conventions of data tables

The CDM is platform-independent. Data types are defined generically using ANSI SQL data types (VARCHAR, INTEGER, FLOAT, DATE, DATETIME, CLOB). Precision is provided only for VARCHAR. It reflects the minimal required string length, but can be expanded within a concrete CDM instantiation. The CDM does not prescribe the date and datetime format. Standard queries against CDM may vary for local instances and date/datetime configurations.

Note: While the data model itself is platform-independent, many of the tools that have been built to work with it require certain specifications. For more about this please see chapter 9.

5.2.4 General conventions of Domains

Events of different nature are organized into Domains. These Events are stored in tables and fields which are Domain-specific, and represented by Standard Concepts that are also Domain-specific as defined in the Standardized Vocabularies (see section 5.2.7). Each Standard Concept has a unique Domain assignment, which defines which table they are recorded in. Even though the correct Domain assignment is subject for debate in the community, this strict Domain-table-field correspondence rule assures that there is always an unambiguous location for any code or concept. For example, signs, symptoms and diagnosis Concepts are of the Condition Domain, and are recorded in the CONDITION_CONCEPT_ID of the CONDITION_OCCURRENCE table. So-called Procedure Drugs are typically recorded as procedure codes in a procedure table in the source data. In an OMOP CDM, these records are found in the DRUG_EXPOSURE table because the mapped Standard Concepts have the Domain assignment Drug. There is a total of 30 Domains, as shown in table 5.1.

Table 5.1: Number of standard concepts belonging to each domain.
Concept Count DOMAIN_ID
1731378 Drug
477597 Device
257000 Procedure
163807 Condition
145898 Observation
89645 Measurement
33759 Spec Anatomic Site
17302 Meas Value
1799 Specimen
1215 Provider Specialty
1046 Unit
944 Metadata
538 Revenue Code
336 Type Concept
194 Relationship
183 Route
180 Currency
158 Payer
123 Visit
51 Cost
50 Race
13 Plan Stop Reason
11 Plan
6 Episode
6 Sponsor
5 Meas Value Operator
3 Spec Disease Status
2 Gender
2 Ethnicity
1 Observation Type

5.2.5 Representation of content through Concepts

In CDM data tables the content of each record is fully normalized and represented through Concepts. Concepts are stored in Event tables with their CONCEPT_ID values, which are foreign keys to the CONCEPT table, which serves as the general reference table. All OMOP CDM instances use the same CONCEPT table as a reference of the Concepts, which together with the Common Data Model is a key mechanism of interoperability and the foundation of the OHDSI research network. If a Standard Concept does not exist or cannot be identified, the value of the CONCEPT_ID is set to 0, representing a non-existing concept, an unknown or un-mappable value.

Records in the CONCEPT table contain detailed information about each concept (name, domain, class etc.). Concepts, Concept Relationships, Concept Ancestors and other information relating to Concepts is contained in the tables of the Standardized Vocabularies (see chapter 6).

5.2.6 General naming conventions of fields

Variable names across all tables follow one convention:

Table 5.2: Field name conventions.
Notation Description
[Event]_ID Unique identifier for each record, which serves as a foreign keys establishing relationships across Event tables. For example, PERSON_ID uniquely identifies each individual. VISIT_OCCURRENCE_ID uniquely identifies a Visit.
[Event]_CONCEPT_ID Foreign key to a Standard Concept record in the CONCEPT reference table. This is the main representation of the Event, serving as the primary basis for all standardized analytics. For example, CONDITION_CONCEPT_ID = 31967 contains the reference value for the SNOMED concept of “Nausea”.
[Event]_SOURCE_CONCEPT_ID Foreign key to a record in the CONCEPT reference table. This Concept is the equivalent of the Source Value (below), and it may happen to be a Standard Concept, at which point it would be identical to the [Event]_CONCEPT_ID, or another non-standard concept. For example, CONDITION_SOURCE_CONCEPT_ID = 45431665 denotes the concept of “Nausea” in the Read terminology, and the analogous CONDITION_CONCEPT_ID is the Standard SNOMED-CT Concept 31967. The use of Source Concepts for standard analytics applications is discouraged since only Standard Concepts represent the semantic content of an Event in a unambiguous way and therefore Source Concepts are not interoperable.
[Event]_TYPE_CONCEPT_ID Foreign key to a record in the CONCEPT reference table, representing the origin of the source information, standardized within the Standardized Vocabularies. Note that despite the field name this is not a type of an Event, or type of a Concept, but declares the capture mechanism that created this record. For example, DRUG_TYPE_CONCEPT_ID discriminates if a Drug record was derived from a dispensing Event in the pharmacy (“Pharmacy dispensing”) or from an e-prescribing application (“Prescription written”)
[Event]_SOURCE_VALUE Verbatim code or free text string reflecting how this Event was represented in the source data. Its use is discouraged for standard analytics applications, as these Source Values are not harmonized across data sources. For example, CONDITION_SOURCE_VALUE might contain a record of “78702”, corresponding to ICD-9 code 787.02 written in a notation omitting the dot.

5.2.7 Difference between Concepts and Source Values

Many tables contain equivalent information in multiple places: as a Source Value, a Source Concept and as a Standard Concept.

  • Source Values are the original representation of an Event record in the source data. They can be codes from widely used coding systems, which are often public domain, such as ICD9CM, NDC or Read, proprietary coding systems like CPT4, GPI or MedDRA, or controlled vocabularies used only in the source data, such as F for female and M for male. They can also be short free text phrases that are not standardized and cotrolled. Source Values are stored in the [Event]_SOURCE_VALUE fields in the data tables.
  • Concepts are CDM-specific entities that normalize the meaning of a clinical fact. Most Concepts are based on existing public or proprietary coding systems in healthcare, while others were created de-novo (CONCEPT_CODE starts with “OMOP”). Concepts have unique IDs across all domains.
  • Source Concepts are the Concepts that represent the code used in the source. Source Concepts are only used for existing public or proprietary coding systems, not for OMOP-generated Concepts. Source Concepts are stored in the [Event]_SOURCE_CONCEPT_ID field in the data tables.
  • Standard Concepts are those Concepts that are used to define the meaning of a clinical entity uniquely across all databases and independent from the codinng system used in the sources. Standard Concepts are typically drawn from existing public or proprietary vocabulary sources. Non-standard Concepts that have the equivalent meaning to a Standard Concept have a mapping to the Standard Concept in the Standardized Vocabularies. Standard Concepts are referred to in the [Event]_CONCEPT_ID field of the data tables.

Source Values are only provided for convenience and quality assurance (QA) purposes. They may contain information that is only meaningful in the context of a specific data source. The use of Source Values and Source Concepts is optional, even though strongly recommended if the source data make use of coding systems. Standard Concepts are mandatory however. This mandatory use of Standard Concepts is what allows all OMOP CDM instances to speak the same language. For example, the condition “Pulmonary Tuberculosis” (TB, Figure 5.2) shows that the ICD9CM code for TB is 011.

ICD9CM code for Pulmonary Tuberculosis

Figure 5.2: ICD9CM code for Pulmonary Tuberculosis

Without context, the code 011 could be interpreted as “Hospital Inpatient (Including Medicare Part A)” from the UB04 vocabulary, or as “Nervous System Neoplasms without Complications, Comorbidities” from the DRG vocabulary. This is where Concept IDs, both Source and Standard, are valuable. The CONCEPT_ID value that represents the 011 ICD9CM code is 44828631. This differentiates the ICD9CM from the UBO4 and DRG. The ICD9CM TB Source Concept maps to Standard Concept 253954 from the SNOMED vocabulary through the relationship “Non-standard to Standard map (OMOP)” as shown in figure 5.3. This same mapping relationships exists for Read, ICD10, CIEL, and MeSH codes, among others, so that any research that references the standard SNOMED concept is sure to include all supported source codes.

sNOMED code for Pulmonary Tuberculosis

Figure 5.3: sNOMED code for Pulmonary Tuberculosis

An example of how the Standard Concept to Source Concept relationship is depicted is shown in Table 5.7.

5.3 OMOP CDM Standardized Tables

The OMOP CDM contains 16 Clinical Event tables, 10 Vocabulary tables, 2 metadata tables, 4 health system data tables, 2 health economics data tables, 3 standardized derived elements, and 2 Results schema tables. These tables are fully specified in the CDM Wiki15.

To illustrate how these tables are used in practice, the data of one person will be used as a common thread throughout the rest of the chapter.

5.3.1 Running Example: Endometriosis

Endometriosis is a painful condition whereby cells normally found in the lining of a woman’s uterus occur elsewhere in the body. Severe cases can lead to infertility, bowel, and bladder problems. The following sections will detail one patient’s experience with this disease and how it might be represented in the Common Data Model.

Every step of this painful journey I had to convince everyone how much pain I was in.

Lauren had been experiencing endometriosis symptoms for many years; however, it took a ruptured cyst in her ovary before she was diagnosed. You can read more about Lauren at https://www.endometriosis-uk.org/laurens-story.

5.3.2 PERSON table

What do we know about Lauren?

  • She is a 36-year-old woman
  • Her birthday is 12-March-1982
  • She is white
  • She is English

With that in mind, her PERSON table might look something like this:

Table 5.3: The PERSON table.
Column name Value Explanation
PERSON_ID 1 The PERSON_ID should be an integer, either directly from the source or generated as part of the build process.
GENDER_CONCEPT_ID 8532 The concept ID referring to female gender is 8532.
YEAR_OF_BIRTH 1982
MONTH_OF_BIRTH 3
DAY_OF_BIRTH 12
BIRTH_DATETIME 1982-03-12 00:00:00 When the time is not known midnight is used.
DEATH_DATETIME
RACE_CONCEPT_ID 8527 The concept ID referring to white race is 8527. English ethnicity is 4093769. Either one is correct, the latter will roll up to the former. Notice that enthnicities are stored here as part of Races, not in the ETHNICITY_CONCEPT_ID
ETHNICITY_CONCEPT_ID 38003564 This is a US-typical notation to distingish Hispanics from the rest. Ethnicities, in this case English, is stored in the RACE_CONCEPT_ID. Outside the US this is not used. 38003564 refers to “Not hispanic”.
LOCATION_ID Her address is not known.
PROVIDER_ID Her primary care Provider is not known.
CARE_SITE Her primary Care Site is not known.
PERSON_SOURCE_VALUE 1 Typically this would be her identifier in the source data, though often it is the same as the PERSON_ID.
GENDER_SOURCE_VALUE F The gender value as it appears in the source is stored here.
GENDER_SOURCE_ CONCEPT_ID 0 If the gender value in the source was coded using a coding scheme supported by OHDSI that Concept would go here. For example, if her gender was “sex-F” in the source and it was stated to be in the PCORNet vocabulary concept 44814665 would go in this field.
RACE_SOURCE_VALUE white The race value as it appears in the source is stored here.
RACE_SOURCE_CONCEPT_ID 0 Same principle as GENDER_CONCEPT_ID.
ETHNICITY_SOURCE_VALUE english The ethnicity value as it appears in the source is stored here.
ETHNICITY_SOURCE_ CONCEPT_ID 0 Same principle as GENDER_SOURCE_CONCEPT_ID.

5.3.3 OBSERVATION_PERIOD table

The OBSERVATION_PERIOD table is designed to define the amount of time for which at least a patient’s demographics, conditions, procedures and drugs are recorded in the source system with the expection of a reasonable sensitivity and specificity. For insurance data this is typically the enrollment period of the patient. It’s trickier in electronic health records (EHR), as most healthcare systems do not determine which healthcare institution or provider is visited. As a next best solution, often the first record in the system is considered the Start Date of the Observation Period and the latest record is considered the End Date.

How is Lauren’s Observation Period defined?

Let’s say Lauren’s information as shown in Table 5.4 is recorded like in an EHR system. Her encounters from which the Observation Period was derived are:

Table 5.4: Lauren’s healthcare encounters.
Encounter ID Start date Stop date Type
70 2010-01-06 2010-01-06 outpatient
80 2011-01-06 2011-01-06 outpatient
90 2012-01-06 2012-01-06 outpatient
100 2013-01-07 2013-01-07 outpatient
101 2013-01-14 2013-01-14 ambulatory
102 2013-01-17 2013-01-24 inpatient

Based on the encounter records her OBSERVATION_PERIOD table might look something like this:

Table 5.5: The OBSERVATION_PERIOD table.
Column name Value Explanation
OBSERVATION_PERIOD_ID 1 This is typically an autogenerated value creating a unique identifier for each record in the table.
PERSON_ID 1 This is a foreign key to Laura’s record in the PERSON table and links PERSON to OBSERVATION_PERIOD table.
OBSERVATION_PERIOD_START_DATE 2010-01-06 This is the start date of her earliest encounter on record.
OBSERVATION_PERIOD_END_DATE 2013-01-24 This is the end date of her latest encounter on record.
PERIOD_TYPE_CONCEPT_ID 44814725 The best option in the Vocabulary with the concept class “Obs Period Type” is 44814724, which stands for “Period covering healthcare encounters”.

5.3.4 VISIT_OCCURRENCE

the VISIT_OCCURRENCE table houses information about a patient’s encounters with the health care system. Within the OHDSI vernacular these are referred to as Visits and are considered to be discreet events. There are 12 top categories of Visits with an extensive hierarchy, depicting the many different circumstances healthcare might be delivered. The most common Visits recorded are inpatient, outpatient, emergency department and non-medical institution Visits.

How are Lauren’s encounters represented as Visits?

As an example let’s represent the inpatient encounter in Table 5.4 in the VISIT_OCCURRENCE table.

Table 5.6: the VISIT_OCCURRENCE table.
Column name Value Explanation
VISIT_OCCURRENCE_ID 514 This is typically an autogenerated value creating a unique identifier for each record.
PERSON_ID 1 This is a foreign key to Laura’s record in the PERSON table and links PERSON to VISIT_OCCURRENCE.
VISIT_CONCEPT_ID 9201 A foreign key referring to an Inpatient Visit is 9201.
VISIT_START_DATE 2013-01-17 The start date of the Visit.
VISIT_START_DATETIME 2013-01-17 00:00:00 The date and time of the Visit. The time is unknown, so midnight is used.
VISIT_END_DATE 2013-01-24 The end date of the Visit. If this is a one-day Visit the end date should match the start date.
VISIT_END_DATETIME 2013-01-24 00:00:00 The date and time of the Visit end. The time is unknown, so midnight is used.
VISIT_TYPE_CONCEPT_ID 32034 This provides information about the provenance of the Visit record, i.e. does it come from an insurance claim, hospital billing, EHR record, etc. For this example the concept ID 32035 (“Visit derived from EHR encounter record”) is used as the encounters are similar to Electronic Health Records
PROVIDER_ID* NULL If the encounter record has a provider associated the ID for that provider goes into this field. This should be the content of the PROVIDER_ID field from the PROVIDER table.
CARE_SITE_ID NULL If the encounter record has a Care Site associated, the ID for that Care Site goes into this field. This should be the CARE_SITE_ID from the CARE_SITE table.
VISIT_SOURCE_ VALUE inpatient The Visit value as it appears in the source goes here. Lauren’s data do not have that.
VISIT_SOURCE_ CONCEPT_ID 0 If the Visit value from the source is coded using a vocabulary that is recognized by OHDSI the CONCEPT_ID value representing the source code would be found here. Lauren’s data do not have that.
ADMITTED_FROM_ CONCEPT_ID 0 If known, this is contains a Concept representing where the patient was admitted from. This concept should have the domain “Visit”. For example, if the patient were admitted to the hospital from home it would contain 8536 (“Home”).
ADMITTED_FROM_ SOURCE_CONCEPT_ID NULL This is the value from the source that represents where the patient was admitted from. Using the above example, this would be “home”.
DISCHARGE_TO_ CONCEPT_ID 0 If known, this refers to a Concept representing where the patient was discharged to. This concept should have domain “Visit”. For example, if a patient was released to an assisted living facility, the concept ID would be 8615 (“Assisted Living Facility”).
DISCHARGE_TO_ SOURCE_VALUE 0 This is the value from the source that represents where the patient was discharged to. Using the above example, this would be “Assisted living facility”.
PRECEDING_VISIT_ OCCURRENCE_ID NULL This denotes the Visit immediately preceding the current one. In contrast to ADMITTED_FROM_CONCEPT_ID this links to the actual Visit Occurrence record rather than a Visit Concept. Also, note there is no record for the following Visit Occurrence, Visit Occurrences are only linked through this field.
  • A patient may interact with multiple health care Providers during one visit, as is often the case with inpatient stays. These interactions can be recorded in the VISIT_DETAIL table. While not covered in depth in this chapter, you can read more about the VISIT_DETAIL table in the CDM wiki.

5.3.5 CONDITION_OCCURRENCE

Records in the CONDITION_OCCURRENCE table are diagnoses, signs, or symptoms of a condition either observed by a Provider or reported by the patient.

What are Lauren’s conditions?

Revisiting her account she says:

About 3 years ago I noticed my periods, which had also been painful, were getting increasingly more painful. I started becoming aware of a sharp jabbing pain right by my colon and feeling tender and bloated around my tailbone and lower pelvis area. My periods had become so painful that I was missing 1-2 days of work a month. Painkillers sometimes dulled the pain, but usually they didn’t do much.

The SNOMED code for painful menstruation cramps, otherwise known as dysmenorrhea, is 266599000. Table 5.7 shows how that would be represented in the CONDITION_OCCURRENCE table:

Table 5.7: The CONDITION_OCCURRENCE table.
Column name Value Explanation
CONDITION_OCCURRENCE_ID 964 This is typically an autogenerated value creating a unique identifier for each record.
PERSON_ID 1 This is a foreign key to Laura’s record in the PERSON table and links PERSON to CONDITION_OCCURRENCE.
CONDITION_CONCEPT_ID 194696 A foreign key referring to the SNOMED code 266599000: 194696.
CONDITION_START_DATE 2010-01-06 The date when the instance of the Condition is recorded.
CONDITION_START_ DATETIME 2010-01-06 00:00:00 The date and time when the instance of the Condition is recorded. Midnight is used since the time is unknown.
CONDITION_END_ DATE NULL This is the date when the instance of the Condition is considered to have ended, but this is rarely recorded.
CONDITION_END_ DATETIME NULL If known, this is the date and time when the instance of the Condition is considered to have ended.
CONDITION_TYPE_ CONCEPT_ID 32020 This column is intended to provide information about the provenance of the record, i.e. that it comes from an insurance claim, hospital billing record, EHR record, etc. For this example the concept 32020 (“EHR encounter diagnosis”) is used as the encounters are similar to electronic health records. Concepts in this field should be in the “Condition Type” vocabulary.
CONDITION_STATUS_ CONCEPT_ID 0 If known, the this tells the circumstance and . For example, a condition could be an admitting diagnosis, in which case the concept ID 4203942 was used.
STOP_REASON NULL If known, the reason that the Condition was no longer present, as indicated in the source data.
PROVIDER_ID NULL If the condition record has a diagnosing provider listed, the ID for that provider goes in this field. This should be the provider_id from the PROVIDER table that represents the provider on the encounter.
VISIT_OCCURRENCE_ID 509 The Visit (foreign key to the VISIT_OCCURRENCE_ID in the VISIT_OCCURRENCE table) during which the Condition was diagnosed.
CONDITION_SOURCE_VALUE 266599000 This is the original source value representing the Condition. In Lauren’s case of dysmenorrhea the SNOMED code for that Condition is stored here, while the Concept representing the code went to the CONDITION_SOURCE_CONCEPT_ID and the Standard Concept mapped from that is stored in the CONDITION_CONCEPT_ID field.
CONDITION_SOURCE_ CONCEPT_ID 194696 If the condition value from the source is coded using a vocabulary that is recognized by OHDSI, the concept ID that represents that value would go here. In the example of dysmennorhea the source value is a SNOMED code so the Concept representing that code is 194696. In this case it has the same value as the CONDITION_CONCEPT_ID field.
CONDITION_STATUS_ SOURCE_VALUE 0 If the Condition Status value from the source is coded using a coding scheme supported by OHDSI that concept would go here.

5.3.6 DRUG_EXPOSURE

The DRUG_EXPOSURE table captures records about the intent or actual introduction of a drug into the body of the patient. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Drug exposures are inferred from clinical events associated with orders, prescriptions written, pharmacy dispensings, procedural administrations, and other patient-reported information.

How are Lauren’s Drug Exposures represented?

To help with her dysmenorrhea pain, Lauren was given 60 oral tablets with 375 mg Acetaminophen (aka Paracetamol, e.g. sold in the US under NDC code 69842087651) each for 30 days at her Visit on 2010-01-06. Here’s how that might look in the DRUG_EXPOSURE table:

Table 5.8: The DRUG_EXPOSURE table.
Column name Value Explanation
DRUG_EXPOSURE_ID 1001 This is typically an autogenerated value creating a unique identifier for each record.
PERSON_ID 1 This is a foreign key to Laura’s record in the PERSON table and links PERSON to DRUG_EXPOSURE.
DRUG_CONCEPT_ID 1127433 The Concept for the Drug product. The NDC code for acetaminophen maps to the RxNorm code 313782 which is represented by the Concept 1127433.
DRUG_EXPOSURE_START_DATE 2010-01-06 The start date of the exposure to the Drug.
DRUG_EXPOSURE_ START_DATETIME 2010-01-06 00:00:00 The start date and time of the drug exposure. Midnight is used as the time is not known.
DRUG_EXPOSURE_END_DATE 2010-02-05 The end date of the Drug Exposure. Depending on different sources, it could be a known or an inferred date and denotes the last day at which the patient was still exposed to the drug. In this case this date is inferred since we know Lauren had a 30 days supply.
DRUG_EXPOSURE_ END_DATETIME 2010-02-05 00:00:00 The end date and time of the drug exposure. Similar rules apply as to DRUG_EXPOSURE_END_DATE. Midnight is used as time is unknown.
VERBATIM_END_DATE NULL If the source recorded an explicit actual end date. The inferred end date banks on the assumption that the full range of days supply was utilized by the patient.
DRUG_TYPE_CONCEPT_ID 38000177 This column is intended to provide information about the provenance of the record, i.e. does it come from an insurance claim, prescription record, etc. For this example the concept 38000177 (“Prescription written”) is used.
STOP_REASON NULL The reason the administration of the Drug was stopped. Reasons include regimen completed, changed, removed, etc. This information is very rarely captured.
REFILLS NULL The number of automatic refills after the initial prescription that are part of the prescripion system in many countries. The initial prescription is not counted, values start with NULL. In the case of Lauren’s acetaminophen she did not have any refills so the value is NULL.
QUANTITY 60 The quantity of drug as recorded in the original prescription or dispensing record.
DAYS_SUPPLY 30 The number of days of supply of the medication as prescribed.
SIG NULL The directions (“signetur”) on the Drug prescription as recorded in the original prescription or dispensing record (and printed on the container in the US drug prescription system). Signeturs are not yet standardized in the OMOP CDM, and provided verbatim.
ROUTE_CONCEPT_ID 4132161 This concept is meant to represent the route of administration of the Drug the patient was was exposed to. Lauren took her acetaminophen orally so the concept ID 4132161 (“Oral”) is used.
LOT_NUMBER NULL An identifier assigned to a particular quantity or lot of Drug product from the manufacturer. This information is rarely captured.
PROVIDER_ID NULL If the drug record has a prescribing Provider listed, the ID for that Provider goes in this field. In that case this contains the PROVIDER_ID from the PROVIDER table.
VISIT_OCCURRENCE_ID 509 A foreign key to the VISIT_OCCURRENCE table during which the Drug was prescribed.
VISIT_DETAIL_ID NULL A foreign key to the VISIT_DETAIL table during which the Drug was prescribed.
DRUG_SOURCE_VALUE 69842087651 This is the source code for the Drug as it appears in the source data. In Lauren’s case the NDC code is stored here.
DRUG_SOURCE_CONCEPT_ID 750264 This is the Concept that represents the drug source value. The Concept 750264 standing for the NDC code for “Acetaminophen 325 MG Oral Tablet”.
ROUTE_SOURCE_VALUE NULL The verbatim information about the route of administration as detailed in the source.

5.3.7 PROCEDURE_OCCURRENCE

The PROCEDURE_OCCURRENCE table contains records of activities or processes ordered or carried out by a healthcare Provider on the patient with a diagnostic or therapeutic purpose. Procedures are present in various data sources in different forms with varying levels of standardization. For example:

  • Medical Claims include procedure codes that are submitted as part of a claim for health services rendered, including procedures performed.
  • Electronic Health Records that capture procedures as orders.

What procedures did Lauren have?

From her description we know she had an ultrasound of her left ovary on 2013-01-14 that showed a 4x5cm cyst. Here’s how that would look in the PROCEDURE_OCCURRENCE table:

Table 5.9: The PROCEDURE_OCCURRENCE table.
Column name Value Explanation
PROCEDURE_OCCURRENCE_ID 1277 This is typically an autogenerated value creating a unique identifier for each record.
PERSON_ID 1 This is a foreign key to Laura’s record in the PERSON table and links PERSON to PROCEDURE_OCCURRENCE
PROCEDURE_CONCEPT_ID 4127451 The SNOMED procedure code for a pelvic ultrasound is 304435002 which is represented by Concept 4127451.
PROCEDURE_DATE 2013-01-14 The date on which the Procedure was performed.
PROCEDURE_DATATIME 2013-01-14 00:00:00 The date and time on which the procedure was performed. Midnight is used as time is unknown.
PROCEDURE_TYPE_ CONCEPT_ID 38000275 This column is intended to provide information about the provenance of the procedure record, i.e. does it come from an insurance claim, EHR order, etc. For this example the concept ID 38000275 (“EHR order list entry”) is used as the procedure record is from an EHR record.
MODIFIER_CONCEPT_ID 0 This is meant for a concept ID representing the modifier on the procedure. For example, if the record indicated that a CPT4 procedure was performed bilaterally then the concept ID 42739579 (“Bilateral procedure”) would be used.
QUANTITY 0 The quantity of Procedures ordered or administered. A missing Quantity, the numbers 0 and 1 all mean the same thing.
PROVIDER_ID NULL If the Procedure record has a Provider listed, the ID for that Provider goes in this field. This should be a foreign key to the PROVIDER_ID from the PROVIDER table.
VISIT_OCCURRENCE_ID 740 If known, this is the Visit (represented as VISIT_occurrence_id taken from the VISIT_OCCURRENCE table) during which the procedure was performed.
VISIT_DETAIL_ID NULL If known, this is the Visit detail (represented as VISIT_detail_id taken from the VISIT_DETAIL table) during which the procedure was performed.
PROCEDURE_SOURCE_VALUE 304435002 The code or information for the Procedure as it appears in the source data.
PROCEDURE_SOURCE_ CONCEPT_ID 4127451 This is the Concept that represents the procedure source value.
MODIFIER_SOURCE_VALUE NULL The source code for the modifier as it appears in the source data.

5.4 Additional Information

This chapter covers only a portion of the tables available in the OMOP CDM as examples of how data is represented. You are encouraged to visit the wiki site https://github.com/OHDSI/CommonDataModel/wiki for more information.

5.5 Summary

  • The OMOP CDM is designed to support the conduct of research to identify and evaluate associations between interventions and outcomes

  • The OMOP CDM is a “person-centric” model

  • Source codes are represented as standard concept ids