Top

PCORnet v1

Tables

demographic

Demographics record the direct attributes of individual patients.

Fields

biobank_flag

Flag to indicate that one or more biobanked specimens are stored and available for research use. Examples of biospecimens could include plasma, urine, or tissue. If biospecimens are available, locally maintained “mapping tables” would be necessary to map between the DEMOGRAPHIC record and the originating biobanking system(s). If no known biobanked specimens are available, this field should be marked “No”.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id Explicitly maps to concept_id 4001345 in the ���Biobank_flag�۝ concept class.
PEDSnet v1 observation value_as_concept_id Explicitly maps to concept_id 4001345 in the ���Biobank_flag�۝ concept class.

birth_date

Date of birth.

Schema
Mappings
Model Table Field Comment
OMOP v4 person year_of_birth
OMOP v4 person month_of_birth
OMOP v4 person day_of_birth
PEDSnet v1 person year_of_birth
PEDSnet v1 person month_of_birth
PEDSnet v1 person day_of_birth

birth_time

Time of birth.

Schema

hispanic

A person of Cuban, Mexican, Puerto Rican, South or Central American, or other Spanish culture or origin, regardless of race.

Schema
Mappings
Model Table Field Comment
OMOP v4 person ethnicity_concept_id Limited to the concept_id values under the ���Hispanic�۝ concept class.
PEDSnet v1 person ethnicity_concept_id Limited to the concept_id values under the ���Hispanic�۝ concept class.

patid

Arbitrary person-level identifier used to link across tables. PATID is a pseudoidentifier with a consistent crosswalk to the true identifier retained by the source Data Partner. For analytical data sets requiring patient-level data, only the pseudoidentifier is used to link across all information belonging to a patient. The PATID must be unique within the data source being queried. Creating a unique identifier within a CDRN would be beneficial and acceptable. The PATID is not the basis for linkages across partners.

Schema
Mappings
Model Table Field Comment
OMOP v4 person person_id
PEDSnet v1 person person_id

race

Please use only one race value per patient. Details of categorical definitions: American Indian or Alaska Native: A person having origins in any of the original peoples of North and South America (including Central America), and who maintains tribal affiliation or community attachment. Asian: A person having origins in any of the original peoples of the Far East, Southeast Asia, or the Indian subcontinent including, for example, Cambodia, China, India, Japan, Korea, Malaysia, Pakistan, the Philippine Islands, Thailand, and Vietnam. Black or African American: A person having origins in any of the black racial groups of Africa. Native Hawaiian or Other Pacific Islander: A person having origins in any of the original peoples of Hawaii, Guam, Samoa, or other Pacific Islands. White: A person having origins in any of the original peoples of Europe, the Middle East, or North Africa.

Schema
Mappings
Model Table Field Comment
OMOP v4 person race_concept_id Limited to the concept_id values under the ���Race�۝ concept class.
PEDSnet v1 person race_concept_id Limited to the concept_id values under the ���Race�۝ concept class.

raw_hispanic

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 person ethnicity_source_value
PEDSnet v1 person ethnicity_source_value

raw_race

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 person race_source_value
PEDSnet v1 person race_source_value

raw_sex

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 person gender_source_value
PEDSnet v1 person gender_source_value

sex

Administrative sex.

Schema
Mappings
Model Table Field Comment
OMOP v4 person gender_concept_id Maps to the concept_id values under the ���Gender�۝ concept class.
PEDSnet v1 person gender_concept_id Maps to the concept_id values under the ���Gender�۝ concept class.

diagnosis

Diagnosis codes indicate the results of diagnostic processes and medical coding within healthcare delivery.

Fields

admit_date

Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.

Schema

dx

Diagnosis code. Leading zeroes and different levels of decimal precision are permissible in this field. Please populate the exact textual value of this diagnosis code, but remove source-specific suffixes and prefixes. Other codes should be listed as recorded in the source data.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence condition_concept_id
PEDSnet v1 condition_occurrence condition_concept_id

dx_source

Classification of diagnosis source. We include these categories to allow some flexibility in implementation. The context is to capture available diagnoses recorded during a specific encounter. It is not necessary to populate interim diagnoses unless readily available. Ambulatory encounters would generally be expected to have a source of “Final.”

Schema

dx_type

Diagnosis code type. We provide values for ICD and SNOMED code types. Other code types will be added as new terminologies are more widely used. Please note: The “Other” category is meant to identify internal use ontologies and codes.

Schema

enc_type

Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.

Schema

encounterid

Arbitrary encounter-level identifier. Used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence visit_occurrence_id
PEDSnet v1 condition_occurrence visit_occurrence_id

patid

Arbitrary person-level identifier. Used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 condition_occurrence person_id
PEDSnet v1 condition_occurrence person_id

pdx

Principal discharge diagnosis flag. Relevant only on IP and IS encounters. For ED, AV, and OA encounter types, mark as X = Unable to Classify. (Billing systems do not require a primary diagnosis for ambulatory visits (eg, professional services)) One principal diagnosis is expected, although in some instances more than one diagnosis may be flagged as principal.

Schema

providerid

Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.

Schema

raw_dx

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_dx_source

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_dx_type

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_pdx

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

encounter

Encounters are interactions between patients and providers within the context of healthcare delivery.

Fields

admit_date

Encounter or admission date.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence visit_start_date
PEDSnet v1 visit_occurrence visit_start_date

admit_time

Encounter or admission time.

Schema

admitting_source

Admitting source. Should be populated for Inpatient Hospital Stay (IP) and Non-Acute Institutional Stay (IS) encounter types. May be populated for Emergency Department (ED) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id Explicitly maps to concept_id 4145666 in the ���Admitting Source�۝ concept class.
PEDSnet v1 observation value_as_concept_id Explicitly maps to concept_id 4145666 in the ���Admitting Source�۝ concept class.

discharge_date

Discharge date. Should be populated for all Inpatient Hospital Stay (IP) and Non-Acute Institutional Stay (IS) encounter types. May be populated for Emergency Department (ED) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence visit_end_date
PEDSnet v1 visit_occurrence visit_end_date

discharge_disposition

Vital status at discharge. Should be populated for Inpatient Hospital Stay (IP) and Non-Acute Institutional Stay (IS) encounter types. May be populated for Emergency Department (ED) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id Explicitly maps to concept_id 44813951 in the ���Discharge Disposition�۝ concept class.
PEDSnet v1 observation value_as_concept_id Explicitly maps to concept_id 44813951 in the ���Discharge Disposition�۝ concept class.

discharge_status

Discharge status. Should be populated for Inpatient Hospital Stay (IP) and Non-Acute Institutional Stay (IS) encounter types. May be populated for Emergency Department (ED) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id Explicitly maps to concept_id 4137274 in the ���Discharge Status�۝ concept class.
PEDSnet v1 observation value_as_concept_id Explicitly maps to concept_id 4137274 in the ���Discharge Status�۝ concept class.

discharge_time

Discharge time.

Schema

drg

3-digit Diagnosis Related Group (DRG). Should be populated for IP and IS encounter types. May be populated for ED encounter types. Should be missing for AV or OA encounters. Use leading zeroes for codes less than 100. The DRG is used for reimbursement for inpatient encounters. It is a Medicare requirement that combines diagnoses into clinical concepts for billing. Frequently used in observational data analyses.

Schema
Mappings
Model Table Field Comment
OMOP v4 concept concept_code Explicitly maps to concept_id 3040646.
PEDSnet v1 concept concept_code Explicitly maps to concept_id 3040646.

drg_type

DRG code version. MS-DRG (current system) began on 10/1/2007. Should be populated for IP and IS encounter types. May be populated for ED encounter types. Should be missing for AV or OA encounters.

Schema

enc_type

Encounter type. Details of categorical definitions: Ambulatory Visit: Includes visits at outpatient clinics, physician offices, same day/ambulatory surgery centers, urgent care facilities, and other same-day ambulatory hospital encounters, but excludes emergency department encounters. Emergency Department (ED): Includes ED encounters that become inpatient stays (in which case inpatient stays would be a separate encounter). Excludes urgent care visits. ED claims should be pulled before hospitalization claims to ensure that ED with subsequent admission won’t be rolled up in the hospital event. Inpatient Hospital Stay: Includes all inpatient stays, including: same-day hospital discharges, hospital transfers, and acute hospital care where the discharge is after the admission date. Non-Acute Institutional Stay: Includes hospice, skilled nursing facility (SNF), rehab center, nursing home, residential, overnight non-hospital dialysis and other non-hospital stays. Other Ambulatory Visit: Includes other non-overnight AV encounters such as hospice visits, home health visits, skilled nursing facility visits, other non-hospital visits, as well as telemedicine, telephone and email consultations. May also include “lab only” visits (when a lab is ordered outside of a patient visit), “pharmacy only” (e.g., when a patient has a refill ordered without a face-to-face visit), “imaging only”, etc.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence place_of_service_concept_id Limited to concept_id values under the ���Encounter Type�۝ concept class.
PEDSnet v1 visit_occurrence place_of_service_concept_id Limited to concept_id values under the ���Encounter Type�۝ concept class.

encounterid

Arbitrary encounter-level identifier. Used to link across tables, including the ENCOUNTER, DIAGNOSIS, and PROCEDURE tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence visit_occurrence_id
PEDSnet v1 visit_occurrence visit_occurrence_id

facility_location

Geographic location (3 digit zip code). Should be left blank if not recorded in source system.

Schema
Mappings
Model Table Field Comment
OMOP v4 location zip
PEDSnet v1 location zip

facilityid

Arbitrary local facility code that identifies the hospital or clinic. Used for chart abstraction and validation. FACILITYID can be a true identifier, or a pseudoidentifier with a consistent crosswalk to the true identifier retained by the source Data Partner.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence care_site_id
PEDSnet v1 visit_occurrence care_site_id

patid

Arbitrary person-level identifier used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence person_id
PEDSnet v1 visit_occurrence person_id

providerid

Provider code for the provider who is most responsible for this encounter. For encounters with multiple providers choose one so the encounter can be linked to the diagnosis and procedure tables. As with the PATID, the provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.

Schema

raw_admitting_source

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id
PEDSnet v1 observation value_as_concept_id

raw_discharge_disposition

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id
PEDSnet v1 observation value_as_concept_id

raw_discharge_status

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id
PEDSnet v1 observation value_as_concept_id

raw_drg_type

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_enc_type

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema
Mappings
Model Table Field Comment
OMOP v4 visit_occurrence place_of_service_concept_id
PEDSnet v1 visit_occurrence place_of_service_concept_id

enrollment

Enrollment is a concept that defines a period of time during which all medically-attended events are expected to be observed. This concept is often insurance-based, but other methods of defining enrollment are possible.

Fields

chart

Chart abstraction flag is intended to answer the question, “Are you able to request (or review) charts for this person?” This flag does not address chart availability. Mark as “Yes” if there are no contractual or other restrictions between you and the individual (or sponsor) that would prohibit you from requesting any chart for this member. Note: This field is most relevant for health insurers that can request charts from affiliated providers. This field allows exclusion of patients from studies that require chart review to validate exposures and/or outcomes. It identifies patients for whom charts are never available and for whom the chart can never be requested.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_concept_id Explicitly maps to concept_id 4030450 in the ���Chart Availability�۝ concept class.
PEDSnet v1 observation value_as_concept_id Explicitly maps to concept_id 4030450 in the ���Chart Availability�۝ concept class.

enr_basis

When insurance information is not available but complete capture can be asserted some other way, please identify the basis on which complete capture is defined. Additional information on the approach identified will be required from each partner. ENR_BASIS is a property of the time period defined. A patient can have multiple entries in the table. Details of categorical definitions: Insurance: The start and stop dates are based upon the concept of enrollment with health plan insurance Geography: An assertion of complete data capture between the start and end dates based upon geographic characteristics, such as regional isolation Algorithmic: An assertion of complete data capture between the start and end dates, based on a locally developed or applied algorithm, often using multiple criteria Encounter-based: The start and stop dates are populated from the earliest-observed encounter and latest-observed encounter.

Schema

enr_end_date

Date of the end of the enrollment period. If the exact date is unknown, use the last day of the month.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation_period observation_period_end_date
PEDSnet v1 observation_period observation_period_end_date

enr_start_date

Date of the beginning of the enrollment period. If the exact date is unknown, use the first day of the month. For implementation of the CDM, a long span of longitudinal data is desirable; however, especially for historical data more than a decade old, the appropriate beginning date should be determined by the partner’s knowledge of the validity and usability of the data. More specific guidance can be provided through implementation discussions.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation_period observation_period_start_date
PEDSnet v1 observation_period observation_period_start_date

patid

Arbitrary person-level identifier used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation_period person_id
PEDSnet v1 observation_period person_id

procedure

Procedure codes indicate the discreet medical interventions and diagnostic testing, such as surgical procedures, administered within healthcare delivery.

Fields

admit_date

Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.

Schema

enc_type

Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.

Schema

encounterid

Arbitrary encounter-level identifier. Used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence visit_occurrence_id
PEDSnet v1 procedure_occurrence visit_occurrence_id

patid

Arbitrary person-level identifier. Used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence person_id
PEDSnet v1 procedure_occurrence person_id

providerid

Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.

Schema

px

Procedure code.

Schema
Mappings
Model Table Field Comment
OMOP v4 procedure_occurrence procedure_concept_id
PEDSnet v1 procedure_occurrence procedure_concept_id

px_type

Procedure code type. We include a number of code types for flexibility, but the basic requirement that the code refer to a medical procedure remains. Revenue codes are a standard concept in Medicare billing and can be useful for defining care settings. If those codes are available they can be included. Medications administered by clinicians can be captured in billing data and Electronic Health Records (EHRs) as HCPCS procedure codes. Administration (infusion) of chemotherapy is an example. We are now seeing NDCs captured as part of procedures because payers are demanding it for payment authorization. Inclusion of this code type enables those data partners that capture the NDC along with the procedure to include the data. Please note: The “Other” category is meant to identify internal use ontologies and codes.

Schema

raw_px

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_px_type

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

vital

Vital signs (such as height, weight, and blood pressure) directly measure an individual’s current state of attributes.

Fields

bp_position

Position for orthostatic blood pressure. Leave blank if blood pressure was not measured.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_concept_id Maps to the concept_id values under the ���BP Position�۝ concept class.
PEDSnet v1 observation observation_concept_id Maps to the concept_id values under the ���BP Position�۝ concept class.

diastolic

Diastolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, leave blank.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_number Explicitly maps to concept_id 3012888.
PEDSnet v1 observation value_as_number Explicitly maps to concept_id 3012888.

encounterid

Arbitrary encounter-level identifier. This is an optional relationship; the ENCOUNTERID should be present if the vitals were measured as part of healthcare delivery.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation visit_occurrence_id
PEDSnet v1 observation visit_occurrence_id

ht

Height (in inches) measured by standing. Only populated if measure was taken on this date. If missing, leave blank. Decimal precision is permissible.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_number Explicitly maps to concept_id 3036277.
PEDSnet v1 observation value_as_number Explicitly maps to concept_id 3036277.

measure_date

Date of vitals measure.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_date
PEDSnet v1 observation observation_date

measure_time

Time of vitals measure.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation observation_time
PEDSnet v1 observation observation_time

original_bmi

BMI if calculated in the source system. Important: Please do not calculate BMI during CDM implementation. This field should only reflect originating source system calculations, if height and weight are not stored in the source.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_number Explicitly maps to concept_id 3038553.
PEDSnet v1 observation value_as_number Explicitly maps to concept_id 3038553.

patid

Arbitrary person-level identifier. Used to link across tables.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation person_id
PEDSnet v1 observation person_id

raw_bp_position

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

raw_diastolic

Optional field for originating value of field, prior to formatting into the PCORnet CDM.

Schema

raw_systolic

Optional field for originating value of field, prior to formatting into the PCORnet CDM.

Schema

raw_vital_source

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.

Schema

systolic

Systolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, leave blank.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_number Explicitly maps to concept_id 3004249.
PEDSnet v1 observation value_as_number Explicitly maps to concept_id 3004249.

vital_source

Please note: The “Patient-reported” category can include reporting by patient’s family or guardian.

Schema

wt

Weight (in pounds). Only populated if measure was taken on this date. If missing, leave blank. Decimal precision is permissible.

Schema
Mappings
Model Table Field Comment
OMOP v4 observation value_as_number Explicitly maps to concept_id 3025315.
PEDSnet v1 observation value_as_number Explicitly maps to concept_id 3025315.