MDW - Discover Metadata Catalogue

MDW Discover  > Synthea OMOP (CDM) - North East and North Cumbria @ 1351

MDW Discover

Browse All

London SDE

West Midlands SDE

Kent, Medway & Sussex SDE

MDW - Discover

Synthetic Primary Care Data ([Synthea](https://synthea.mitre.org/)) transformed into the Observational Medical Outcomes Partnership (OMOP) [Common Data Model](https://ohdsi.github.io/CommonDataModel/index.html) (CDM) 

Data is sourced from https://synthea.mitre.org/downloads using the 100 sample patient CSV variant of available downloads. Data has been transformed using the ETL methods described by https://github.com/OHDSI/ETL-Synthea

This is a patient level dataset of Primary Care data covering 100 synthetic patients

HDR UK

care_site_id

care_site_name

place_of_service_concept_id

location_id

care_site_source_value

place_of_service_source_value

The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.).

care_site

cdm_source_name

cdm_source_abbreviation

cdm_holder

cdm_source_description

source_documentation_reference

cdm_etl_reference

source_release_date

cdm_release_date

cdm_version

vocabulary_version

cmd_version_concept_id

The CDM_SOURCE table contains detail about the source database and the process used to transform the data into the OMOP Common Data Model.

cdm_source

concept_id

concept_name

domain_id

vocabulary_id

concept_class_id

standard_concept

concept_code

valid_start_date

valid_end_date

invalid_reason

The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and standardized analytics. Each Standard Concept belongs to one Domain, which defines the location where the Concept would be expected to occur within the data tables of the CDM. Concepts can represent broad categories (&lsquo;Cardiovascular disease&rsquo;), detailed clinical elements (&lsquo;Myocardial infarction of the anterolateral wall&rsquo;), or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.). Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom OMOP Concepts defined to cover various aspects of observational data analysis.

concept

condition_era_id

person_id

condition_concept_id

condition_era_start_date

condition_era_end_date

condition_occurrence_count

A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence and every Condition Occurrence record should be part of a Condition Era.

condition_era

condition_occurrence_id

condition_start_date

condition_start_datetime

condition_end_date

condition_end_datetime

condition_type_concept_id

stop_reason

provider_id

visit_occurrence_id

visit_detail_id

condition_source_value

condition_source_concept_id

condition_status_source_value

condition_status_concept_id

This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient.

condition_occurrence

death_date

death_datetime

death_type_concept_id

cause_concept_id

cause_source_value

cause_source_concept_id

The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data.

death

device_exposure_id

device_concept_id

device_exposure_start_date

device_exposure_start_datetime

device_exposure_end_date

device_exposure_end_datetime

device_type_concept_id

unique_device_id

production_id

quantity

device_source_value

device_source_concept_id

unit_concept_id

unit_source_value

unit_source_concept_id

The Device domain captures information about a person&rsquo;s exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures

device_exposure

drug_era_id

drug_concept_id

drug_era_start_date

drug_era_end_date

drug_exposure_count

gap_days

A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras. Every record in the DRUG_EXPOSURE table should be part of a drug era based on the dates of exposure.

drug_era

drug_exposure_id

drug_exposure_start_date

drug_exposure_start_datetime

drug_exposure_end_date

drug_exposure_end_datetime

verbatim_end_date

drug_type_concept_id

refills

days_supply

route_concept_id

lot_number

drug_source_value

drug_source_concept_id

route_source_value

dose_unit_source_value

This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs.

drug_exposure

address_1

address_2

city

state

county

location_source_value

The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites.

location

measurement_id

measurement_concept_id

measurement_date

measurement_datetime

measurement_time

measurement_type_concept_id

operator_concept_id

value_as_number

value_as_concept_id

range_low

range_high

measurement_source_value

measurement_source_concept_id

value_source_value

measurement_event_id

meas_event_field_concept_id

The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person&rsquo;s sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.

measurement

observation_id

observation_concept_id

observation_date

observation_datetime

observation_type_concept_id

value_as_string

qualifier_concept_id

observation_source_value

observation_source_concept_id

qualifier_source_value

observation_event_id

obs_event_field_concept_id

The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.

observation

observation_period_id

observation_period_start_date

observation_period_end_date

period_type_concept_id

This table contains records which define spans of time during which two conditions are expected to hold: (i) Clinical Events that happened to the Person are recorded in the Event tables, and (ii) absence of records indicate such Events did not occur during this span of time.

observation_period

payer_plan_period_id

payer_plan_period_start_date

payer_plan_period_end_date

payer_concept_id

payer_source_value

payer_source_concept_id

plan_concept_id

plan_source_value

plan_source_concept_id

sponsor_concept_id

sponsor_source_value

sponsor_source_concept_id

family_source_value

stop_reason_concept_id

stop_reason_source_value

stop_reason_source_concept_id

The PAYER_PLAN_PERIOD table captures details of the period of time that a Person is continuously enrolled under a specific health Plan benefit structure from a given Payer. Each Person receiving healthcare is typically covered by a health benefit plan, which pays for (fully or partially), or directly provides, the care. These benefit plans are provided by payers, such as health insurances or state or government agencies. In each plan the details of the health benefits are defined for the Person or her family, and the health benefit Plan might change over time typically with increasing utilization (reaching certain cost thresholds such as deductibles), plan availability and purchasing choices of the Person. The unique combinations of Payer organizations, health benefit Plans and time periods in which they are valid for a Person are recorded in this table.

payer_plan_period

gender_concept_id

year_of_birth

month_of_birth

day_of_birth

birth_datetime

race_concept_id

ethnicity_concept_id

person_source_value

gender_source_value

gender_source_concept_id

race_source_value

race_source_concept_id

ethnicity_source_value

ethnicity_source_concept_id

This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information.

person

procedure_occurrence_id

procedure_concept_id

procedure_date

procedure_datetime

This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.

procedure_occurrence

Synthea OMOP (CDM) - North East and North Cumbria

Documentation

Coverage

Provenance

Temporal

Accessibility

Access

Usage

Format and Standards

Origin