Top

PCORnet v4.1

Tables

condition

A condition represents a patient’s diagnosed and self-reported health conditions and diseases. The patient’s medical history and current state may both be represented.

Fields

condition

Condition code.Some codes will contain leading zeroes, and different levels of decimal precision may also be present. This field is a character field, not numeric, to accommodate these coding conventions. Please populate the exact value of this diagnosis code, but remove any source-specific suffixes and prefixes. (Description updated in v4.)

Schema

condition_source

Please note: The ‘Patient-reported’ category can include reporting by a proxy, such as patient’s family or guardian. Guidance: ‘Registry cohort’ generally refers to cohorts of patients flagged with a certain set of characteristics for management within a health system. ‘Patient-reported’ can include self-reported medical history and/or current medical conditions, not captured via healthcare problem lists or registry cohorts.

Schema

condition_status

Condition status corresponding with REPORT_DATE. Guidance: The value of IN=Inactive may be used in situations where a condition is not resolved, but is not currently active (for example, psoriasis).

Schema

condition_type

Condition code type. Please note: The ‘Other’ category is meant to identify internal use ontologies and codes. Value set items updated to reference both the Clinical Modification (CM) and the Procedure Coding (PCS) context for ICD-9, ICD-10, and ICD-11 (update made in v4).

Schema

conditionid

Arbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier used to link across tables. This is an optional field, and should only be populated if the item was collected as part of a healthcare encounter. If more than one encounter association is present, this field should be populated with the ID of the encounter when the condition was first entered into the system. However, please note that many conditions may be recorded outside of an encounter context.

Schema

onset_date

The onset date concept here refers to ‘the date and time when problem (illness, disorder, or symptom) started’ (ONC:MU Clinical Data Set, caDSR 4973971). This is a different concept than report date, which is the date on which the medical status was collected. An onset date should generally be considered independently of the observer or provider. However, the judgment of when a condition ‘started’ depends on the disease, the frequency of visits, and many other factors. It is not clear that any facility or physician employs this field in a manner which can be trusted without validation during analysis. (New definition added in v4.)

Schema

patid

Refers to: demographic / patid

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

Schema

raw_condition

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

Schema

raw_condition_source

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

Schema

raw_condition_status

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

Schema

raw_condition_type

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

Schema

report_date

Date condition was noted, which may be the date when it was recorded by a provider or nurse, or the date on which the patient reported it. Please note that this date may not correspond to onset date.

Schema

resolve_date

Date condition was resolved, if resolution of a transient condition has been achieved. A resolution date is not generally expected for chronic conditions, even if the condition is managed.

Schema

death

Reported mortality information for patients.

Fields

death_date

Date of death.

Schema

death_date_impute

When date of death is imputed, this field indicates which parts of the date were imputed.

Schema

death_match_confidence

For situations where a probabilistic patient matching strategy is used, this field indicates the confidence that the patient drawn from external source data represents the actual patient. Should not be present where DEATH_SOURCE is L (locally-defined). May not be applicable for DEATH_SOURCE=T (tumor registry data)

Schema

death_source

Guidance: “Other, locally defined” may be used to indicate presence of deaths reported from EHR systems, such as inpatient hospital deaths or dead on arrival.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

death_cause

The individual causes associated with a reported death.

Fields

death_cause

Cause of death code. Please include the decimal point in ICD codes (if any).

Schema

death_cause_code

Cause of death code type.

Schema

death_cause_confidence

Confidence in the accuracy of the cause of death based on source, match, number of reporting sources, discrepancies, etc.

Schema

death_cause_source

Source of cause of death information. Guidance: “Other, locally defined” may be used to indicate presence of deaths reported from EHR systems, such as inpatient hospital deaths or dead on arrival.

Schema

death_cause_type

Cause of death type. There should be only one underlying cause of death.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

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

birth_date

Date of birth.

Schema

birth_time

Time of birth.

Schema

gender_identity

Current gender identity.

Schema

hispanic

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

Schema

pat_pref_language_spoken

Preferred spoken language of communication as expressed by the patient. New field in v4.

Schema

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
Inbound References

Total: 16

Table Field Name
enrollment patid fk_enrollment_patid
encounter patid fk_encounter_patid
diagnosis patid fk_diagnosis_patid
procedures patid fk_procedures_patid
vital patid fk_vital_patid
dispensing patid fk_dispensing_patid
lab_result_cm patid fk_lab_result_cm_patid
condition patid fk_condition_patid
pro_cm patid fk_pro_cm_patid
prescribing patid fk_prescribing_patid
pcornet_trial patid fk_pcornet_trial_patid
death patid fk_death_patid
death_cause patid fk_death_cause_patid
med_admin patid fk_medadmin_patid
obs_clin patid fk_obsclin_patid
obs_gen patid fk_obsgen_patid

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

raw_gender_identity

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

Schema

raw_hispanic

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

Schema

raw_pat_pref_language_spoken

Schema

raw_race

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

Schema

raw_sex

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

Schema

raw_sexual_orientation

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

Schema

sex

Administrative sex. v4 definition updated: Sex assigned at birth v2.0 guidance added: The “Ambiguousâ€ù category may be used for individuals who are physically undifferentiated from birth. The “Otherâ€ù category may be used for individuals who are undergoing gender re-assignment.

Schema

sexual_orientation

Sexual orientation.

Schema

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

diagnosisid

Arbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

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. Some codes will contain leading zeroes, and different levels of decimal precision may also be present. This field is a character field, not numeric, to accommodate these coding conventions. (Description updated in v4.)

Schema

dx_origin

Source of the diagnosis information. Billing pertains to internal healthcare processes and data sources. Claim pertains to data from the bill fulfillment, generally data sources held by insurers and other health plans. New field added in v4.

Schema

dx_poa

Flag to denote whether diagnosis was present on inpatient admission.

Schema

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

Refers to: encounter / encounterid

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

Schema

patid

Refers to: demographic / patid

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

Schema

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 principle diagnosis per encounter is expected, although in some instances more than one diagnosis may be flagged as principal.

Schema

providerid

Refers to: provider / 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_poa

Field for originating value, 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

dispensing

Outpatient pharmacy dispensing, such as prescriptions filled through a neighborhood pharmacy with a claim paid by an insurer. Outpatient dispensing may not be directly captured within healthcare systems.

Fields

dispense_amt

Number of units (pills, tablets, vials) dispensed. Net amount per NDC per dispensing. This amount is typically found on the dispensing record. Positive values are expected. Important: Please do not calculate during CDM implementation. This field should only reflect originating source system calculations. Number precision and scale updated in v4.

Schema

dispense_date

Dispensing date (as close as possible to date the person received the dispensing).

Schema

dispense_dose_disp

Dose of a given mediation, as dispensed

Schema

dispense_dose_disp_unit

Units of measure associated with the dose of the medication as dispensed

Schema

dispense_route

Route of delivery

Schema

dispense_sup

Days supply. Number of days that the medication supports based on the number of doses as reported by the pharmacist. This amount is typically found on the dispensing record. Integer values are expected. Important: Please do not calculate during CDM implementation. This field should only reflect originating source system calculations. Number precision and scale updated in v4.

Schema

dispensingid

Arbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

ndc

National Drug Code in the 11-digit, no-dash, HIPAA format. Please expunge any place holders (such as dashes or extra digits). If needed, guidance on normalization for other forms of NDC can be found: http://www.nlm.nih.gov/research/umls/rxnorm/docs/2012/rxnorm_doco_full_2012-1.html (see section 6)

Schema

patid

Refers to: demographic / patid

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

Schema

prescribingid

Refers to: prescribing / prescribingid

This is an optional relationship to the PRESCRIBING table, and may not be generally available. One prescribing order may generate multiple dispensing records.

Schema

raw_dispense_dose_disp

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_dispense_dose_disp_unit

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_dispense_route

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_ndc

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

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) and ED-to-Inpatient (EI) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema

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) and ED-to-Inpatient (EI) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema

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) and ED-to-Inpatient (EI) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema

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) and ED-to-Inpatient (EI) encounter types. Should be missing for ambulatory visit (AV or OA) encounter types.

Schema

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 Emergency Department (ED) and ED-to-Inpatient (EI) 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

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 Emergency Department (ED) and ED-toInpatient (EI) 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. Does not include observation stays, where known (guidance added in v4). Emergency Department Admit to Inpatient Hospital Stay: Permissible substitution for preferred state of separate ED and IP records. Only for use with data sources where the individual records for ED and IP cannot be distinguished (new to v2.0). 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. Does not include observation stays, where known (guidance added in v4). Observation Stay: ‚ÄúHospital outpatient services given to help the can be discharged. Observations services may be given in the emergency department or another area of the hospital.‚Äù Definition from Medicare, CMS Product No. 11435, https://www.medicare.gov/Pubs/pdf/11435.pdf (new value set item added in v4). Institutional Professional Consult: Permissible substitution when services provided by a medical professional cannot be combined with the given encounter record, such as a specialist consult in an inpatient setting; this situation can be common with claims data sources (new value set item added in v4). 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

encounterid

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

Schema
Inbound References

Total: 10

Table Field Name
diagnosis encounterid fk_diagnosis_encounterid
procedures encounterid fk_procedures_encounterid
vital encounterid fk_vital_encounterid
lab_result_cm encounterid fk_lab_result_cm_encounterid
condition encounterid fk_condition_encounterid
pro_cm encounterid fk_pro_cm_encounterid
prescribing encounterid fk_prescribing_encounterid
med_admin encounterid fk_medadmin_encounterid
obs_clin encounterid fk_obsclin_encounterid
obs_gen encounterid fk_obsgen_encounterid

facility_location

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

Schema

facility_type

Appendix for a list of acceptable values. Description of the facility where the encounter occurred.

Schema

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

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

payer_type_primary

Categorization of payer type for primary payer associated with the encounter

Schema

payer_type_secondary

Categorization of payer type for secondary payer associated with the encounter

Schema

providerid

Refers to: provider / 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

raw_discharge_disposition

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

Schema

raw_discharge_status

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

Schema

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

raw_facility_type

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_payer_id_primary

Primary PAYER identifier as denoted in the source system. Used to derive PAYER_TYPE_PRIMARY if validated process does not exist.

Schema

raw_payer_id_secondary

Secondary PAYER identifier as denoted in the source system. Used to derive PAYER_TYPE_SECONDARY if validated process does not exist.

Schema

raw_payer_name_primary

Primary payer name as denoted in the source system. Used to derive PAYER_TYPE_PRIMARY if validated process does not exist.

Schema

raw_payer_name_secondary

Secondary payer name as denoted in the source system. Used to derive PAYER_TYPE_SECONDARY if validated process does not exist.

Schema

raw_payer_type_primary

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_payer_type_secondary

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_siteid

This field is new to v2.0. Optional field for locally-defined identifier intended for local use; for example, where a network may have multiple sites contributing to a central data repository. This attribute may be sensitive in certain contexts; the intent is for internal network use only, and not to enable site quality comparisons.

Schema

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

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: Medical insurance coverage: The start and stop dates are based upon enrollment where the health plan has any responsibility for covering medical care for the member during this enrollment period (i.e., if you expect to observe medical care provided to this member during the enrollment period). Outpatient prescription drug coverage: The start and stop dates are based on enrollment where the health plan has any responsibility for covering outpatient prescription drugs for the member during this enrollment period (i.e., if you expect to observe outpatient pharmacy dispensings for this member during this enrollment period). (New value set item added in v4.) 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. Field definition and value sets modified in v4 to include drug coverage.

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

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

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

harvest

Attributes associated with the specific PCORnet datamart implementation.

Fields

admit_date_mgmt

Data management strategy currently present in the ADMIT_DATE field on the ENCOUNTER table Please see notes for additional definitions.

Schema

birth_date_mgmt

Data management strategy currently present in the BIRTH_DATE field on the DEMOGRAPHIC table Please see notes for additional definitions.

Schema

cdm_version

Version currently implemented within this datamart (for example, 1.0, 2.0, 3.0). Number precision and scale updated in v4.

Schema

datamart_claims

Datamart includes claims data source(s)

Schema

datamart_ehr

Datamart includes EHR data source(s)

Schema

datamart_name

Descriptive name of the datamart. This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) (description updated in v4)

Schema

datamart_platform

Schema

datamartid

This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) (description updated in v4)

Schema

death_date_mgmt

Data management strategy employed for the DEATH_DATE field in the DEATH table.

Schema

discharge_date_mgmt

Data management strategy currently present in the DISCHARGE_DATE field on the ENCOUNTER table Please see notes for additional definitions.

Schema

dispense_date_mgmt

Data management strategy currently present in the DISPENSE_DATE field on the DISPENSING table Please see notes for additional definitions.

Schema

enr_end_date_mgmt

Data management strategy currently present in the ENR_END_DATE field on the ENROLLMENT table Please see notes for additional definitions.

Schema

enr_start_date_mgmt

Data management strategy currently present in the ENR_START_DATE field on the ENROLLMENT table Please see notes for additional definitions.

Schema

lab_order_date_mgmt

Data management strategy currently present in the LAB_ORDER_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.

Schema

measure_date_mgmt

Data management strategy currently present in the MEASURE_DATE field on the VITAL table Please see notes for additional definitions.

Schema

medadmin_start_date_mgmt

Data management strategy employed for the MEDADMIN_START_DATE field in the MED_ADMIN table.

Schema

medadmin_stop_date_mgmt

Data management strategy employed for the MEDADMIN_END_DATE field in the MED_ADMIN table.

Schema

network_name

Descriptive name of the network. This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) (description updated in v4)

Schema

networkid

This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) (description updated in v4)

Schema

obsclin_date_mgmt

Data management strategy employed for the OBSCLIN_DATE field in the OBS_CLIN table.

Schema

obsgen_date_mgmt

Data management strategy employed for the OBSGEN_DATE field in the OBS_GEN table.

Schema

onset_date_mgmt

Data management strategy currently present in the ONSET_DATE field on the CONDITION table Please see notes for additional definitions.

Schema

pro_date_mgmt

Data management strategy currently present in the PRO_DATE field on the PRO_CM table Please see notes for additional definitions.

Schema

px_date_mgmt

Data management strategy currently present in the PX_DATE field on the PROCEDURES table Please see notes for additional definitions.

Schema

refresh_condition_date

Most recent date on which the present data were loaded into the CONDITION table. This date should be null if the table does not have records.

Schema

refresh_death_cause_date

Most recent date on which the present data were loaded into the DEATH_CAUSE table. This date should be null if the table does not have records.

Schema

refresh_death_date

Most recent date on which the present data were loaded into the DEATH table. This date should be null if the table does not have records.

Schema

refresh_demographic_date

Most recent date on which the present data were loaded into the DEMOGRAPHIC table. This date should be null if the table does not have records.

Schema

refresh_diagnosis_date

Most recent date on which the present data were loaded into the DIAGNOSIS table. This date should be null if the table does not have records.

Schema

refresh_dispensing_date

Most recent date on which the present data were loaded into the DISPENSING table. This date should be null if the table does not have records.

Schema

refresh_encounter_date

Most recent date on which the present data were loaded into the ENCOUNTER table. This date should be null if the table does not have records.

Schema

refresh_enrollment_date

Most recent date on which the present data were loaded into the ENROLLMENT table. This date should be null if the table does not have records.

Schema

refresh_lab_result_cm_date

Most recent date on which the present data were loaded into the LAB_RESULT_CM table. This date should be null if the table does not have records.

Schema

refresh_med_admin_date

Most recent date on which the present data were loaded into the MED_ADMIN table. This date should be null if the table does not have records.

Schema

refresh_obs_clin_date

Most recent date on which the present data were loaded into the OBS_CLIN table. This date should be null if the table does not have records.

Schema

refresh_obs_gen_date

Most recent date on which the present data were loaded into the OBS_GEN table. This date should be null if the table does not have records.

Schema

refresh_pcornet_trial_date

Most recent date on which the present data were loaded into the PCORNET_TRIAL table. This date should be null if the table does not have records.

Schema

refresh_prescribing_date

Most recent date on which the present data were loaded into the PRESCRIBING table. This date should be null if the table does not have records.

Schema

refresh_pro_cm_date

Most recent date on which the present data were loaded into the PRO_CM table. This date should be null if the table does not have records.

Schema

refresh_procedures_date

Most recent date on which the present data were loaded into the PROCEDURES table. This date should be null if the table does not have records.

Schema

refresh_provider_date

Most recent date on which the present data were loaded into the PROVIDER table. This date should be null if the table does not have records.

Schema

refresh_vital_date

Most recent date on which the present data were loaded into the VITAL table. This date should be null if the table does not have records.

Schema

report_date_mgmt

Data management strategy currently present in the REPORT_DATE field on the CONDITION table Please see notes for additional definitions.

Schema

resolve_date_mgmt

Data management strategy currently present in the RESOLVE_DATE field on the CONDITION table Please see notes for additional definitions.

Schema

result_date_mgmt

Data management strategy currently present in the RESULT_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.

Schema

rx_end_date_mgmt

Data management strategy currently present in the RX_END_DATE field on the PRESCRIBING table Please see notes for additional definitions.

Schema

rx_order_date_mgmt

Data management strategy currently present in the RX_ORDER_DATE field on the PRESCRIBING table Please see notes for additional definitions.

Schema

rx_start_date_mgmt

Data management strategy currently present in the RX_START_DATE field on the PRESCRIBING table Please see notes for additional definitions.

Schema

specimen_date_mgmt

Data management strategy currently present in the SPECIMEN_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.

Schema

lab_result_cm

Laboratory result Common Measures (CM) use specific types of quantitative and qualitative measurements from blood and other body specimens. The common measures are defined in the same way across all PCORnet networks, but this table can also include other types of lab results.

Fields

abn_ind

Abnormal result indicator. This value comes from the source data; do not apply logic to create it.

Schema

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier used to link across tables. This is an optional field, and should only be populated if the lab was collected as part of a healthcare encounter.

Schema

lab_loinc

Logical Observation Identifiers, Names, and Codes (LOINC) from the Regenstrief Institute. Results with local versions of LOINC codes (e.g., LOINC candidate codes) should be included in the RAW_table field, but the LOINC variable should be set to missing. Current LOINC codes are from 3-7 characters long but Regenstrief suggests a length of 10 for future growth. The last digit of the LOINC code is a check digit and is always preceded by a hyphen. All parts of the LOINC code, including the hyphen, must be included. Do not pad the LOINC code with leading zeros. Please see the LOINC reference table for known LOINC codes for each LAB_NAME.

Schema

lab_order_date

Date test was ordered.

Schema

lab_px

Optional variable for local and standard procedure codes, used to identify the originating order for the lab test.

Schema

lab_px_type

Procedure code type, if applicable. Value set modified in v4 to combine CPT and HCPCS codes into one category; also, ICD-9 value set item typo corrected to specify ICD-9-PCS

Schema

lab_result_cm_id

Arbitrary identifier for each unique LAB_RESULT_CM record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

norm_modifier_high

Modifier for NORM_RANGE_HIGH values. For numeric results one of the following needs to be true: 1) Both MODIFIER_LOW and MODIFIER_HIGH contain EQ (e.g. normal values fall in the range 40) 2) MODIFIER_LOW contains GT or GE and MODIFIER_HIGH contains NO (e.g. normal values are >3 with no upper boundary) 3) MODIFIER_HIGH contains LT or LE and MODIFIER_LOW contains NO (e.g. normal values are <=10 with no lower boundary)

Schema

norm_modifier_low

Modifier for NORM_RANGE_LOW values. For numeric results one of the following needs to be true: 1) Both MODIFIER_LOW and MODIFIER_HIGH contain EQ (e.g. normal values fall in the range 40) 2) MODIFIER_LOW contains GT or GE and MODIFIER_HIGH contains NO (e.g. normal values are >3 with no upper boundary) 3) MODIFIER_HIGH contains LT or LE and MODIFIER_LOW contains NO (e.g. normal values are <=10 with no lower boundary)

Schema

norm_range_high

Upper bound of the normal range assigned by the laboratory. Value should only contain the value of the upper bound. The symbols >, <, >=, <= should be removed. For example, if the normal range for a test is >100 and <300, then “300” should be entered.

Schema

norm_range_low

Lower bound of the normal range assigned by the laboratory. Value should only contain the value of the lower bound. The symbols >, <, >=, <= should be removed. For example, if the normal range for a test is >100 and <300, then “100” should be entered.

Schema

patid

Refers to: demographic / patid

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

Schema

priority

Immediacy of test. The intent of this variable is to determine whether the test was obtained as part of routine care or as an emergent/urgent diagnostic test (designated as Stat or Expedite).

Schema

raw_facility_code

Local facility code that identifies the hospital or clinic. Taken from facility claims.

Schema

raw_lab_code

Local code related to an individual lab test. This variable will not be used in queries, but may be used by local programmers to associate a record with a particular LAB_NAME.

Schema

raw_lab_name

Local code related to an individual lab test. This variable will not be used in queries, but may be used by local programmers to associate a record with a particular LAB_NAME.

Schema

raw_order_dept

Local code for ordering provider department.

Schema

raw_panel

Local code related to a battery or panel of lab tests. This variable will not be used in queries, but may be used by local programmers to associate a record with a particular LAB_NAME.

Schema

raw_result

The original test result value as seen in your source data. Values may include a decimal point, a sign or text (e.g., POSITIVE, NEGATIVE, DETECTED). The symbols >, <, >=, <= should be removed from the value and stored in the Modifier variable instead.

Schema

raw_unit

Original units for the result in your source data.

Schema

result_date

Result date.

Schema

result_loc

Location of the test result. Point of Care locations may include anticoagulation clinic, newborn nursery, finger stick in provider office, or home. The default value is ‘L’ unless the result is Point of Care. There should not be any missing values.

Schema

result_modifier

Modifier for result values. Any symbols in the RAW_RESULT value should be reflected in the RESULT_MODIFIER variable. For example, if the original source data value is “<=200” then RAW_RESULT=200 and RESULT_MODIFIER=LE. If the original source data value is text then RESULT_MODIFIER=TX. If the original source data value is a numeric value then RESULT_MODIFIER=EQ.

Schema

result_num

Standardized/converted result for quantitative results. Please see the Implementation Guidance for additional details (description updated for v4). v3.1 modification: SAS data type corrected to Numeric. Number precision and scale updated in v3.1.

Schema

result_qual

Standardized result for qualitative results. This variable should be NI for quantitative results. Please see the Implementation Guidance for additional details and information on acceptable values for each qualitative LAB_NAME (description updated in v4).

Schema

result_snomed

If the qualitative result has been mapped to SNOMED CT, the corresponding SNOMED code can be placed here.

Schema

result_time

Result time.

Schema

result_unit

Converted/standardized units for the result. Please see the Implementation Guidance for additional details (description updated in v4).

Schema

specimen_date

Date specimen was collected.

Schema

specimen_source

Specimen source. All records will have a specimen source; some tests have several possible values for SPECIMEN_SOURCE. Please see the Implementation Guidance for additional details. (Description updated for v4.)

Schema

specimen_time

Time specimen was collected.

Schema

med_admin

Records of medications administered to patients by healthcare providers. These administrations may take place in any setting, including inpatient, outpatient or home health encounters

Fields

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier. This is an optional relationship because not all vital sign measures will be associated with a healthcare encounter. (New description added in v4.)

Schema

medadmin_code

Medication code

Schema

medadmin_dose_admin

Dose of a given mediation, as administered by the provider. Do not impute or derive if not expressly defined in the source system as a discrete field.

Schema

medadmin_dose_admin_unit

Units of measure associated with the dose of the medication as administered by the provider. Do not impute or derive if not expressly defined in the source system as a discrete field. Choose the standardized unit of measure that is most reflective of the source data. The Value Set Appendix contains a list of the units most commonly associated with medication records. Partners can use this table to aid in their mapping efforts, but they should refer back to the full value set if they have a medication record with a unit of measure that is not present in this curated list.

Schema

medadmin_providerid

Refers to: provider / providerid

Provider code for the provider who prescribed the medication. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.

Schema

medadmin_route

Route of medication delivery.

Schema

medadmin_source

Source of the medication administration record. This field is a derived attribute, and is not expected to be an explicit data field within a source system. Use “OD” for medication orders entered into the EHR. Use “DR” for all medication orders that are derived or imputed through analytical procedures (e.g., natural language processing). This does not apply to administrations mapped from a superset terminology or drug database (e.g., MediSpan, FDB). For those records, use “OD” (General Guidance #4).

Schema

medadmin_start_date

Date medication administration started/occurred

Schema

medadmin_start_time

Time medication administration started/occurred

Schema

medadmin_stop_date

Date medication administration ended

Schema

medadmin_stop_time

Time medication administration ended

Schema

medadmin_type

This field is a derived attribute, and is not expected to be an explicit data field within a source system  If mapping from medication database (e.g., MediSpan, FDB), and it is possible to map to RxNorm and NDC, RxNorm is the preferred term type. If medication administration records are stored natively as NDC, do not convert to RxNorm.

Schema

medadminid

Arbitrary identifier for each unique MED_ADMIN record.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

prescribingid

This is an optional relationship to the PRESCRIBING table, and may not be generally available. One prescribing order may generate multiple administration records.

Schema

raw_medadmin_code

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_medadmin_dose_admin

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_medadmin_dose_admin_unit

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_medadmin_med_name

Field for originating, full textual medication name from the source.

Schema

raw_medadmin_route

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

obs_clin

Standardized qualitative and quantitative clinical observations about a patient

Fields

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier used to link across tables.

Schema

obsclin_code

Code of the clinical observation in the vocabulary/terminology specified in OBSCLINTYPE. Results with local versions of LOINC codes (e.g., LOINC candidate codes) should be included in the RAW table field. The last digit of the LOINC code is a check digit and is always preceded by a hyphen. All parts of the LOINC code, including the hyphen, must be included. Do not pad codes with leading zeros.

Schema

obsclin_date

Date of observation/measurement

Schema

obsclin_providerid

Refers to: provider / providerid

Provider code for the provider who ordered the observation. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.

Schema

obsclin_result_modifier

Modifier for result values.

Schema

obsclin_result_num

Standardized/converted result for quantitative results. Used to store quantitative results, including the numeric component of numeric results that contain operators (e.g., “= 0.5”). See guidance for RESULT_MODIFIER for further details.

Schema

obsclin_result_qual

Standardized result for qualitative results. This variable should be NI for quantitative results. If qualitative result cannot be harmonized to a value in OBSCLIN_RESULT_QUAL value set, please ensure that RAW_OBSCLIN_RESULT is populated with result value.

Schema

obsclin_result_snomed

If the qualitative result has been mapped to SNOMED CT, the corresponding SNOMED code can be placed here. Partners are not expected to derive or impute if not present in the source system.

Schema

obsclin_result_text

Narrative/textual clinical observations

Schema

obsclin_result_unit

Converted/standardized units for the result.

Schema

obsclin_time

Time of observation/measurement.

Schema

obsclin_type

Terminology / vocabulary used to describe the clinical observation.

Schema

obsclinid

Arbitrary identifier for each unique OBS_CLIN record.

Schema

patid

Refers to: demographic / patid

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

Schema

raw_obsclin_code

Local code related to an individual clinical observation/measurement.

Schema

raw_obsclin_modifier

The original modifier text as represented in your source data.

Schema

raw_obsclin_name

Local name related to an individual clinical observation/measurement.

Schema

raw_obsclin_result

The original test result value as seen in your source data. Values may include a decimal point, a sign or text (e.g., POSITIVE, NEGATIVE, DETECTED). The symbols >, <, >=, <= should be removed from the value and stored in the Modifier variable instead.

Schema

raw_obsclin_type

Terminology related to the code in RAW_OBSGEN_CODE.

Schema

raw_obsclin_unit

Original units for the result in your source data.

Schema

obs_gen

This table provides a generalized structure for storing observations and is not optimized for analytical efficiency. As elements from this table are used in studies and/or distributed queries, additional representations of those data elements (i.e., new table structures) may be required to better support those activities

Fields

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier used to link across tables. This field should be populated if the observation was recorded as part of a healthcare encounter.

Schema

obsgen_code

Standardized code denoting the observations based on the terminology/vocabulary specified in OBSGEN_TYPE

Schema

obsgen_date

Date of observation/measurement

Schema

obsgen_id_modified

Identifier when observation describes attributes of an existing record in the CDM. If observation record modifies something other than the patient (i.e., attribute about an encounter), a link to that record can be included here. If a value is listed in OBSGEN_TABLE_MODIF IED, then a corresponding ID should be listed in OBSGEN_ID_MODIFIED. If modifying a record in OBS_GEN, the value of OBSGEN_ID_MODIFIED must be different than the value of OBSGENID for that record.

Schema

obsgen_providerid

Refers to: provider / providerid

Provider code for the provider who recorded the observation. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.

Schema

obsgen_result_modifier

Modifier for result values. Any symbols in the RAW_RESULT value should be reflected in the RESULT_MODIFIER variable.For example, if the original source data value is “<=200” then RAW_RESULT=200 and RESULT_MODIFIER=LE. RESULT_NUM would also be set to “200”. If the original source data value is text, then RESULT_MODIFIER=TX If the original source data value is a numeric value, then RESULT_MODIFIER=EQ

Schema

obsgen_result_num

Standardized/converted result for quantitative results. Used to store quantitative results, including the numeric component of numeric results that contain operators (e.g., “= 0.5”). See guidance for RESULT_MODIFIER for further details.

Schema

obsgen_result_qual

Standardized result for qualitative results. This variable should be NI for quantitative results. Use RAW_OBSGEN_RESULT to store qualitative results that cannot be harmonized to the defined value set.

Schema

obsgen_result_text

Narrative/textual observations.

Schema

obsgen_result_unit

Converted/standardized units for the result.

Schema

obsgen_table_modified

Table name when observation describes attributes of an existing record in the CDM. If observation record modifies something other than the patient (i.e., attribute about an encounter), a link to that table can be included here. If a value is listed in OBSGEN_TABLE_MODIF IED, then a corresponding ID should be listed in OBSGEN_ID_MODIFIED.

Schema

obsgen_time

Time of observation/measurement.

Schema

obsgen_type

Terminology/vocabulary used to describe the observation. Networks/partners can define their own terminologies with strings starting with UD. Strings that start with PC are reserved for network-wide activities and will be assigned by the Coordinating Center.

Schema

obsgenid

Arbitrary identifier for each unique OBS_GEN record.

Schema

patid

Refers to: demographic / patid

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

Schema

raw_obsgen_code

Local code related to an individual clinical observation/measurement.

Schema

raw_obsgen_name

Local name related to an individual clinical observation/measurement.

Schema

raw_obsgen_result

The original test result value as seen in your source data.

Schema

raw_obsgen_type

Terminology related to the code in RAW_OBSGEN_CODE.

Schema

raw_obsgen_unit

Original units for the result in your source data.

Schema

pcornet_trial

Patients who are enrolled in PCORnet clinical trials.

Fields

participantid

Arbitrary person-level identifier used to uniquely identify a participant in a PCORnet trial. PARTICIPANTID is never repeated or reused for a specific clinical trial, and is generally assigned by trial-specific processes. It may be the same as a randomization ID.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

trial_end_date

Date on which the participant completes participation in the trial.

Schema

trial_enroll_date

Date on which the participant enrolled in the trial (generally coincides with trial consent process).

Schema

trial_invite_code

Textual strings used to uniquely identify invitations sent to potential participants, and allows acceptances to be associated back to the originating source. Where used, there should generally be a unique combination of PATID, TRIAL_NAME, and INVITE_CODE within each datamart. For example, this might include “co-enrollment ID strings” for e-mail invites or “verification codes” for letter invites

Schema

trial_siteid

Each TRIAL_SITEID is assigned by the PCORnet trial coordinating center.

Schema

trial_withdraw_date

If applicable, date on which the participant withdraws consent from the trial.

Schema

trialid

Each TRIALID is assigned by the PCORnet trial’s coordinating center.

Schema

prescribing

Provider orders for medication dispensing and/or administration. These orders may take place in any setting, including the inpatient or outpatient basis.

Fields

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier. This is an optional relationship; the ENCOUNTERID should be present if the prescribing activity is directly associated with an encounter.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier used to link across tables.

Schema

prescribingid

Arbitrary identifier for each unique PRESCRIBING record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema
Inbound References

Total: 1

Table Field Name
dispensing prescribingid fk_dispensing_prescribingid

raw_rx_dose_ordered

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_rx_dose_ordered_unit

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_rx_frequency

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

Schema

raw_rx_med_name

Optional field for originating, full textual medication name from the source.

Schema

raw_rx_ndc

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

Schema

raw_rx_quantity

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

Schema

raw_rx_refills

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_rx_route

Field for originating value, prior to mapping into the PCORnet CDM value set.

Schema

raw_rxnorm_cui

Optional field for originating value of field, prior to mapping into the PCORnet CDM value set. v4 modification: field types changed to character because the National Library of Medicine specifies this variable as a character type.

Schema

rx_basis

Basis of the medication order. The PRESCRIBING table can contain orders for many different activities, and this field is intended to connect the provider’s prescribing order with how the order was fulfilled (such as outpatient dispensing or administration by a healthcare professional). (Value set items updated and field definition expanded in v4.)

Schema

rx_days_supply

Number of days supply ordered, as specified by the prescription. Number precision and scale updated in v4.

Schema

rx_dispense_as_written

Flag to indicate whether the provider indicated that the medication order was to be dispensed as written.

Schema

rx_dose_form

The unit associated with the quantity prescribed.

Schema

rx_dose_ordered

Dose of a given mediation, as ordered by the provider

Schema

rx_dose_ordered_unit

Units of measure associated with the dose of the medication as ordered by the provider

Schema

rx_end_date

End date of order (if available).

Schema

rx_frequency

Specified frequency of medication.

Schema

rx_order_date

Order date of the prescription by the provider.

Schema

rx_order_time

Order time of the prescription by the provider.

Schema

rx_prn_flag

Flag to indicate that all or part of medication frequency instructions includes Òas needed.Ó

Schema

rx_providerid

Refers to: provider / providerid

Provider code for the provider who prescribed the medication. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.

Schema

rx_quantity

Quantity ordered. Number precision and scale updated in v4.

Schema

rx_quantity_unit

The unit associated with the quantity prescribed. New field added in v4.

Schema

rx_refills

Number of refills ordered (not including the original prescription). If no refills are ordered, the value should be zero. Number precision and scale updated in v4.

Schema

rx_route

Route of medication delivery.

Schema

rx_source

Source of the prescribing information.

Schema

rx_start_date

Start date of order. This attribute may not be consistent with the date on which the patient actually begin taking the medication.

Schema

rxnorm_cui

Where an RxNorm mapping exists for the source medication, this field contains the RxNorm concept identifier (CUI) at the highest possible specificity. If more than one option exists for mapping, the following ordered strategy may be adopted: 1)Semantic generic clinical drug 2)Semantic Branded clinical drug 3)Generic drug pack 4)Branded drug pack

Schema

pro_cm

Patient-reported outcome Common Measures are standardized measures that are defined in the same way across all PCORnet networks. Each measure is recorded at the individual item level: an individual question/statement, paired with its standardized response options.

Fields

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier used to link across tables. This is an optional field, and should only be populated if the item was collected as part of a healthcare encounter.

Schema

patid

Refers to: demographic / patid

Arbitrary person-level identifier for the patient for whom the PRO response was captured. Used to link across tables.

Schema

pro_cat

Indicates whether Computer Adaptive Testing (CAT) was used to administer the survey or instrument that the item was part of. May apply to electronic (EC) and telephonic (PH or IV) modes.

Schema

pro_cm_id

Arbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

pro_date

The date of the response.

Schema

pro_item

PCORnet identifier for the specific Common Measure item. Please see the Common Measures reference table for more details. Character length increased in v4 to accommodate the potential for additional ontologies.

Schema

pro_item_fullname

Full name of the PRO item.

Schema

pro_item_loinc

LOINC® code for the PRO item, if available.

Schema

pro_item_name

Short name or code of the PRO item in the vocabulary/terminology specified in PRO_TYPE.

Schema

pro_item_text

Text of the PRO item question.

Schema

pro_item_version

Version of the item/question.

Schema

pro_loinc

LOINC code for item context and stem. the Implementation Guidance for known LOINC codes for each common measure (description updated in v4). Logical Observation Identifiers, Names, and Codes (LOINC) from the Regenstrief Institute. Results with local versions of LOINC codes (e.g., LOINC candidate codes) should be included in the RAW_table field, but the PRO_LOINC variable should be set to missing. Current LOINC codes are from 3-7 characters long but Regenstrief suggests a length of 10 for future growth. The last digit of the LOINC code is a check digit and is always preceded by a hyphen. All parts of the LOINC code, including the hyphen, must be included. Do not pad the LOINC code with leading zeros.

Schema

pro_measure_count_scored

Number of PRO item responses that were involved in the scoring of the measure.

Schema

pro_measure_fullname

Full name of the PRO measure.

Schema

pro_measure_loinc

LOINC® code for the PRO item, if available.

Schema

pro_measure_name

Short name or code of the PRO measure/form that item belongs to, if item is being administered as part of a measure

Schema

pro_measure_scaled_tscore

Standardized score based on the total raw score for the instrument. Only applies to items that are administered as part of a measure.

Schema

pro_measure_score

Overall raw score for the PRO measure.

Schema

pro_measure_seq

Arbitrary ID/sequence number used to link PRO item responses that are associated with the same measure/form.

Schema

pro_measure_standard_measure

Possible range of the actual final score based on the scaled T-score. Only applies to items that are administered as part of a measure.

Schema

pro_measure_theta

The value of theta reported from the CAT PROMIS results. Only applies to items that are administered as part of a measure.

Schema

pro_measure_version

Version of the measure.

Schema

pro_method

Method of administration. Electronic includes responses captured via a personal or tablet computer, at web kiosks, or via a smartphone.

Schema

pro_mode

The person who responded on behalf of the patient for whom the response was captured. A proxy report is a measurement based on a report by someone other than the patient reporting as if he or she is the patient, such as a parent responding for a child, or a caregiver responding for an individual unable to report for themselves. Assistance excludes providing interpretation of the patient’s response.

Schema

pro_response_num

The numeric response recorded for the item. Please see the Common Measures reference table for the list of valid responses for each item. Number precision and scale updated in v4.

Schema

pro_response_text

Text version of the response recorded for the item, if available/applicable.

Schema

pro_time

The time of the response.

Schema

pro_type

Terminology / vocabulary used to describe the PRO item.

Schema

procedures

Procedure codes indicate the discreet medical interventions and diagnostic testing, such as surgical procedures and lab orders, delivered within a healthcare context.

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

Refers to: encounter / encounterid

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

Schema

patid

Refers to: demographic / patid

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

Schema

ppx

Principal procedure flag.

Schema

proceduresid

Arbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

providerid

Refers to: provider / providerid

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

Schema

px

Procedure code.

Schema

px_date

New to v2.0.Date the procedure was performed.

Schema

px_source

New to v2.0. Source of the procedure information. Order and billing pertain to internal healthcare processes and data sources. Claim pertains to data from the bill fulfillment, generally data sources held by insurers and other health plans. Length of data types updated in v4.

Schema

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. Value set modified in v4 to combine CPT and HCPCS codes into one category; also, ICD-9 value set item typo corrected to ICD-9-PCS.

Schema

raw_ppx

Field for originating value, prior to mapping into the PCORnet CDM value set.

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

provider

Data about the providers who are involved in the care processes documented in the CDM

Fields

provider_npi

National Provider Identifier (NPI) of the provider.

Schema

provider_npi_flag

Flag to indicate whether partner has access to the National Provider Identifier (NPI) of the provider. This field is a derived attribute, and is not expected to be an explicit data field within a source system

Schema

provider_sex

Sex assigned at birth. The “Ambiguous” category may be used for individuals who are physically undifferentiated from birth. The “Other” category may be used for individuals who are undergoing gender re-assignment.

Schema

provider_specialty_primary

Primary specialty of the provider

Schema

providerid

Arbitrary identifier for each unique PROVIDER record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema
Inbound References

Total: 7

Table Field Name
med_admin medadmin_providerid fk_medadmin_providerid
encounter providerid fk_encounter_providerid
diagnosis providerid fk_diagnosis_providerid
procedures providerid fk_procedures_providerid
prescribing rx_providerid fk_prescribing_providerid
obs_clin obsclin_providerid fk_obsclin_providerid
obs_gen obsgen_providerid fk_obsgen_providerid

raw_provider_specialty_primary

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. This value should be null if blood pressure was not measured.

Schema

diastolic

Diastolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, this value should be null. Number precision and scale updated in v4

Schema

encounterid

Refers to: encounter / encounterid

Arbitrary encounter-level identifier. This is an optional relationship because not all vital sign measures will be associated with a healthcare encounter. (New description added in v4.)

Schema

ht

Height (in inches) measured by standing. Only populated if measure was taken on this date. If missing, this value should be null. Decimal precision is permissible. Number precision and scale updated in v4

Schema

measure_date

Date of vitals measure.

Schema

measure_time

Time of vitals measure.

Schema

original_bmi

BMI if calculated in the source system. Decimal precision is permissible (new guidance added in v4). 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. Number precision and scale updated in v4.

Schema

patid

Refers to: demographic / patid

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

Schema

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_tobacco

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

Schema

raw_tobacco_type

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

Schema

smoking

Indicator for any form of tobacco that is smoked. Per Meaningful Use guidance, “…smoking status includes any form of tobacco that is smoked, but not all tobacco use.” “’Light smoker’ is interpreted to mean less than 10 cigarettes per day, or an equivalent (but less concretely defined) quantity of cigar or pipe smoke. ‘Heavy smoker’ is interpreted to mean greater than 10 cigarettes per day or an equivalent (but less concretely defined) quantity of cigar or pipe smoke.” “…we understand that a “current every day smoker” or “current some day smoker” is an individual who has smoked at least 100 cigarettes during his/her lifetime and still regularly smokes every day or periodically, yet consistently; a “former smoker” would be an individual who has smoked at least 100 cigarettes during his/her lifetime but does not currently smoke; and a “never smoker” would be an individual who has not smoked 100 or more cigarettes during his/her lifetime.” http://www.healthit.gov/sites/default/files/standardscertification/2014-edition-draft-test-procedures/170-314-a-11- smoking-status-2014-test-procedure-draft-v1.0.pdf [retrieved May 11, 2015]

Schema

systolic

Systolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, this value should be null. Number precision and scale updated in v4

Schema

tobacco

This field is new to v2.0 with revised value set and field definition in v4.0. Indicator for any form of tobacco

Schema

tobacco_type

This field is new to v2.0, with revised value set in v4.1. Type(s) of tobacco used.

Schema

vital_source

Please note: The “Patient-reported” category can include reporting by patient’s family or guardian. v2.0 amendment: The new categorical value of PD and HD have been added. v2.0 guidance added with slight modification in v4.1: If unknown whether data are received directly from a device feed, use the more general context (such as patient-reported, healthcare delivery setting, or registry).

Schema

vitalid

Arbitrary identifier for each unique VITAL record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.

Schema

wt

Weight (in pounds). Only populated if measure was taken on this date. If missing, this value should be null. Decimal precision is permissible. Number precision and scale updated in v4

Schema