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 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.
stringPlease 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.
stringCondition 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).
stringCondition code type. Please note: The “Other” category is meant to identify internal use ontologies and codes.
stringArbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.
stringRefers 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.
stringPlease note that onset date is a very precise concept. Please do not map data unless they precisely match this definition. The REPORT_DATE concept may be a better fit for many systems.
dateRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringDate 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.
dateDate 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.
dateReported mortality information for patients.
Fields
Date of death.
dateWhen date of death is imputed, this field indicates which parts of the date were imputed.
stringFor 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)
stringGuidance: “Other, locally defined” may be used to indicate presence of deaths reported from EHR systems, such as inpatient hospital deaths or dead on arrival.
stringRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringThe individual causes associated with a reported death.
Fields
Cause of death code. Please include the decimal point in ICD codes (if any).
stringCause of death code type.
stringConfidence in the accuracy of the cause of death based on source, match, number of reporting sources, discrepancies, etc.
stringSource 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.
stringCause of death type. There should be only one underlying cause of death.
stringRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringDemographics record the direct attributes of individual patients.
Fields
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â€ù.
stringDate of birth.
dateTime of birth.
stringA person of Cuban, Mexican, Puerto Rican, South or Central American, or other Spanish culture or origin, regardless of race.
stringArbitrary 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.
stringTotal: 13
| 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 |
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.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringAdministrative sex. 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.
stringDiagnosis codes indicate the results of diagnostic processes and medical coding within healthcare delivery.
Fields
Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.
dateArbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.
stringDiagnosis 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.
stringClassification 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.”
stringDiagnosis 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.
stringPlease note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.
stringRefers to: encounter / encounterid
Arbitrary encounter-level identifier. Used to link across tables.
stringRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringPrincipal 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.
stringPlease note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOutpatient pharmacy dispensing, such as prescriptions filled through a neighborhood pharmacy with a claim paid by an insurer. Outpatient dispensing is not commonly captured within healthcare systems.
Fields
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.
numberDispensing date (as close as possible to date the person received the dispensing).
dateDays 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.
numberArbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.
stringNational 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)
stringRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringRefers 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.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringEncounters are interactions between patients and providers within the context of healthcare delivery.
Fields
Encounter or admission date.
dateEncounter or admission time.
stringAdmitting 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.
stringDischarge 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.
dateVital 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.
stringDischarge 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.
stringDischarge time.
string3-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.
stringDRG 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.
stringEncounter 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. 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. 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.
stringArbitrary encounter-level identifier. Used to link across tables, including the ENCOUNTER, DIAGNOSIS, and PROCEDURE tables.
stringTotal: 7
| 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 |
Geographic location (3 digit zip code). Should be null if not recorded in source system.
stringArbitrary 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.
stringRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringProvider 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.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringThis 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.
stringEnrollment 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 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.
stringWhen 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.
stringDate of the end of the enrollment period. If the exact date is unknown, use the last day of the month.
dateDate 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.
dateRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringAttributes associated with the specific PCORnet datamart implementation.
Fields
Data management strategy currently present in the ADMIT_DATE field on the ENCOUNTER table Please see notes for additional definitions.
stringData management strategy currently present in the BIRTH_DATE field on the DEMOGRAPHIC table Please see notes for additional definitions.
stringVersion currently implemented within this datamart (for example, 1.0, 2.0, 3.0).
numberDatamart includes claims data source(s)
stringDatamart includes EHR data source(s)
stringDescriptive name of the datamart
stringstringThis identifier is assigned by DSSNI operations
stringData management strategy currently present in the DISCHARGE_DATE field on the ENCOUNTER table Please see notes for additional definitions.
stringData management strategy currently present in the DISPENSE_DATE field on the DISPENSING table Please see notes for additional definitions.
stringData management strategy currently present in the ENR_END_DATE field on the ENROLLMENT table Please see notes for additional definitions.
stringData management strategy currently present in the ENR_START_DATE field on the ENROLLMENT table Please see notes for additional definitions.
stringData management strategy currently present in the LAB_ORDER_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.
stringData management strategy currently present in the MEASURE_DATE field on the VITAL table Please see notes for additional definitions.
stringDescriptive name of the network
stringThis identifier is assigned by DSSNI operations
stringData management strategy currently present in the ONSET_DATE field on the CONDITION table Please see notes for additional definitions.
stringData management strategy currently present in the PRO_DATE field on the PRO_CM table Please see notes for additional definitions.
stringData management strategy currently present in the PX_DATE field on the PROCEDURES table Please see notes for additional definitions.
stringMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateMost 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.
dateData management strategy currently present in the REPORT_DATE field on the CONDITION table Please see notes for additional definitions.
stringData management strategy currently present in the RESOLVE_DATE field on the CONDITION table Please see notes for additional definitions.
stringData management strategy currently present in the RESULT_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.
stringData management strategy currently present in the RX_END_DATE field on the PRESCRIBING table Please see notes for additional definitions.
stringData management strategy currently present in the RX_ORDER_DATE field on the PRESCRIBING table Please see notes for additional definitions.
stringData management strategy currently present in the RX_START_DATE field on the PRESCRIBING table Please see notes for additional definitions.
stringData management strategy currently present in the SPECIMEN_DATE field on the LAB_RESULT_CM table Please see notes for additional definitions.
stringLaboratory result Common Measures (CM) use specific types of quantitative and qualitative measurements from blood and other body specimens. These standardized measures are defined in the same way across all PCORnet networks.
Fields
Abnormal result indicator. This value comes from the source data; do not apply logic to create it.
stringRefers 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.
stringLogical 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.
stringLaboratory result common measure, a categorical identification for the type of test, which is harmonized across all contributing data partners. Please note that it is possible for more than one LOINC code, CPT code, and/or local code to be associated with one LAB_NAME.
stringDate test was ordered.
dateOptional variable for local and standard procedure codes, used to identify the originating order for the lab test.
stringProcedure code type, if applicable.
stringArbitrary 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.
stringModifier 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 3-10) 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)
stringModifier 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 3-10) 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)
stringUpper 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.
stringLower 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.
stringRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringImmediacy 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).
stringLocal facility code that identifies the hospital or clinic. Taken from facility claims.
stringLocal 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.
stringLocal 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.
stringLocal code for ordering provider department.
stringLocal 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.
stringThe 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.
stringOriginal units for the result in your source data.
stringResult date.
dateLocation 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.
stringModifier 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.
stringStandardized/converted result for quantitative results. This variable should be null for qualitative results. Please see the reference tables for additional details.
numberStandardized result for qualitative results. This variable should be NI for quantitative results. Please see the reference tables for additional details and information on acceptable values for each qualitative LAB_NAME.
stringResult time.
stringConverted/standardized units for the result. Please see the standard abbreviations reference table for additional details.
stringDate specimen was collected.
dateSpecimen source. All records will have a specimen source; some tests have several possible values for SPECIMEN_SOURCE. Please see the reference tables for additional details.
stringTime specimen was collected.
stringPatients who are enrolled in PCORnet clinical trials.
Fields
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.
stringRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringDate on which the participant completes participation in the trial.
dateDate on which the participant enrolled in the trial (generally coincides with trial consent process).
dateTextual 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
stringEach TRIAL_SITEID is assigned by the PCORnet trial coordinating center.
stringIf applicable, date on which the participant withdraws consent from the trial.
dateEach TRIALID is assigned by the PCORnet trial’s coordinating center.
stringProvider orders for medication dispensing and/or administration.
Fields
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.
stringRefers to: demographic / patid
Arbitrary person-level identifier used to link across tables.
stringArbitrary 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.
stringTotal: 1
| Table | Field | Name |
|---|---|---|
| dispensing | prescribingid | fk_dispensing_prescribingid |
Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating, full textual medication name from the source.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringBasis of the medication order
stringNumber of days supply ordered, as specified by the prescription.
numberEnd date of order (if available).
dateSpecified frequency of medication.
stringOrder date of the prescription by the provider.
dateOrder time of the prescription by the provider.
stringProvider code for the provider who prescribed the medication. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.
stringQuantity ordered.
numberNumber of refills ordered (not including the original prescription). If no refills are ordered, the value should be zero.
numberStart date of order. This attribute may not be consistent with the date on which the patient actually begin taking the medication.
dateWhere 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
numberPatient-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
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.
stringRefers to: demographic / patid
Arbitrary person-level identifier for the patient for whom the PRO response was captured. Used to link across tables.
stringIndicates 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.
stringArbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.
stringThe date of the response.
datePCORnet identifier for the specific Common Measure item. Please see the Common Measures reference table for more details.
stringLOINC code for item context and stem. Please see the reference table for known LOINC codes for each common measure. 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.
stringMethod of administration. Electronic includes responses captured via a personal or tablet computer, at web kiosks, or via a smartphone.
stringThe 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.
stringThe numeric response recorded for the item. Please see the Common Measures reference table for the list of valid responses for each item.
numberThe time of the response.
stringOptional field for originating code, such as LOINC candidate codes that have not yet been adopted
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringProcedure codes indicate the discreet medical interventions and diagnostic testing, such as surgical procedures, administered within healthcare delivery.
Fields
Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.
datePlease note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.
stringRefers to: encounter / encounterid
Arbitrary encounter-level identifier. Used to link across tables.
stringRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringArbitrary identifier for each unique record. Does not need to be persistent across refreshes, and may be created by methods such as sequence or GUID.
stringPlease note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.
stringProcedure code.
stringNew to v2.0. Date the procedure was performed.
dateNew 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.
stringProcedure 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.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringVital signs (such as height, weight, and blood pressure) directly measure an individual’s current state of attributes.
Fields
Position for orthostatic blood pressure. This value should be null if blood pressure was not measured.
stringDiastolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, this value should be null.
numberRefers to: encounter / encounterid
Arbitrary encounter-level identifier. This is an optional relationship; the ENCOUNTERID should generally be present if the vitals were measured as part of healthcare delivery captured by this datamart.
stringHeight (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.
numberDate of vitals measure.
dateTime of vitals measure.
stringBMI 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.
numberRefers to: demographic / patid
Arbitrary person-level identifier. Used to link across tables.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set.
stringOptional field for originating value of field, prior to formatting into the PCORnet CDM.
stringOptional field for originating value of field, prior to formatting into the PCORnet CDM.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set. New to v2.0.
stringOptional field for originating value of field, prior to mapping into the PCORnet CDM value set. New to v2.0.
stringIndicator 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]
stringSystolic blood pressure (in mmHg). Only populated if measure was taken on this date. If missing, this value should be null.
numberThis field is new to v2.0 with revised value set and field definition in v3.0. Indicator for any form of tobacco
stringThis field is new to v2.0, with revised value set in v3.0. Type(s) of tobacco used.
stringPlease 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 v3.0: 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).
stringArbitrary 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.
stringWeight (in pounds). Only populated if measure was taken on this date. If missing, this value should be null. Decimal precision is permissible.
number