fields.csv

TABLE_NAME,FIELD_NAME,RDBMS_DATA_TYPE,SAS_DATA_TYPE,DATA_FORMAT,REPLICATED_FIELD,UNIT_OF_MEASURE,VALUESET,FIELD_DEFINITION,FIELD_ORDER,CHANGED_IN_THIS_VERSION
DEMOGRAPHIC,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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 each PCORnet data mart. Creating a unique identifier within a network would be beneficial and acceptable. The PATID is not the basis for linkages across data partners.",1,NO
DEMOGRAPHIC,BIRTH_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date of birth.,2,NO
DEMOGRAPHIC,BIRTH_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time of birth.,3,NO
DEMOGRAPHIC,SEX,RDBMS Text(2),SAS Char(2),,NO,,YES,Sex assigned at birth (definition updated in v3.1).,4,NO
DEMOGRAPHIC,SEXUAL_ORIENTATION,RDBMS Text(2),SAS Char(2),,NO,,YES,Sexual orientation. (New field added in v3.1.),5,NO
DEMOGRAPHIC,GENDER_IDENTITY,RDBMS Text(2),SAS Char(2),,NO,,YES,Current gender identity. ,6,NO
DEMOGRAPHIC,HISPANIC,RDBMS Text(2),SAS Char(2),,NO,,YES,"A person of Cuban, Mexican, Puerto Rican, South or Central American, or other Spanish culture or origin, regardless of race.",7,NO
DEMOGRAPHIC,RACE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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.",8,NO
DEMOGRAPHIC,BIOBANK_FLAG,RDBMS Text(1),SAS Char(1),,NO,,YES,"Flag to indicate that one or more biobanked specimens are stored and available for research use. Examples of biospecimens could include blood, urine, or tissue (eg, skin cells, organ tissues). 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”.",9,NO
DEMOGRAPHIC,PAT_PREF_LANGUAGE_SPOKEN,RDBMS Text(3),SAS Char(3),,NO,,YES (also see PATIENT_PREF_LANGUAGE_SPOKEN in the ValueSet Reference File),Preferred spoken language of communication as expressed by the patient.,10,NO
DEMOGRAPHIC,RAW_SEX,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",11,NO
DEMOGRAPHIC,RAW_SEXUAL_ORIENTATION,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",12,NO
DEMOGRAPHIC,RAW_GENDER_IDENTITY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",13,NO
DEMOGRAPHIC,RAW_HISPANIC,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",14,NO
DEMOGRAPHIC,RAW_RACE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",15,NO
DEMOGRAPHIC,RAW_PAT_PREF_LANGUAGE_SPOKEN,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",16,NO
ENCOUNTER,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"Arbitrary encounter-level identifier. Used to link across tables, including the ENCOUNTER, DIAGNOSIS, and PROCEDURES tables.",17,NO
ENCOUNTER,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,18,NO
ENCOUNTER,ADMIT_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Encounter or admission date.,19,NO
ENCOUNTER,ADMIT_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Encounter or admission time.,20,NO
ENCOUNTER,DISCHARGE_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Discharge date. ,21,NO
ENCOUNTER,DISCHARGE_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Discharge time.,22,NO
ENCOUNTER,PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",23,NO
ENCOUNTER,FACILITY_LOCATION,RDBMS Text(5),SAS Char(5),,NO,,NO,Geographic location (5-digit zip code).,24,NO
ENCOUNTER,ENC_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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 facility 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 v3.1). 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. 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 v3.1). Observation Stay: “Hospital outpatient services given to help the doctor decide if the patient needs to be admitted as an inpatient or 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 v3.1). 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 v3.1). Non-Acute Institutional Stay: Includes hospice, skilled nursing facility (SNF), rehab center, nursing home, residential, overnight non-hospital dialysis, and other non-hospital stays. Telehealth: Includes telemedicine or virtual visits, which can be conducted via video, phone or other means. Other Ambulatory Visit: Includes other non-overnight AV encounters such as hospice visits, home health visits, skilled nursing visits, other non-hospital visits, as well as 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.",25,NO
ENCOUNTER,FACILITYID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",26,NO
ENCOUNTER,DISCHARGE_DISPOSITION,RDBMS Text(2),SAS Char(2),,NO,,YES,Vital status at discharge.,27,NO
ENCOUNTER,DISCHARGE_STATUS,RDBMS Text(2),SAS Char(2),,NO,,YES,Discharge status.,28,NO
ENCOUNTER,DRG,RDBMS Text(3),SAS Char(3),,NO,,NO,3-digit Diagnosis Related Group (DRG). 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.,29,NO
ENCOUNTER,DRG_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,DRG code version. ,30,NO
ENCOUNTER,ADMITTING_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Admitting source. ,31,NO
ENCOUNTER,PAYER_TYPE_PRIMARY,RDBMS Text(5) ,SAS Char(5),,NO,,YES (also see PAYER_TYPE_ in the ValueSet Reference File),Categorization of payer type for primary payer associated with the encounter,32,NO
ENCOUNTER,PAYER_TYPE_SECONDARY,RDBMS Text(5),SAS Char(5),,NO,,YES (also see PAYER_TYPE_ in the ValueSet Reference File),Categorization of payer type for secondary payer associated with the encounter,33,NO
ENCOUNTER,FACILITY_TYPE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see FACILITY_TYPE in the ValueSet Reference File),Description of the facility where the encounter occurred.,34,NO
ENCOUNTER,RAW_SITEID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",35,NO
ENCOUNTER,RAW_ENC_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",36,NO
ENCOUNTER,RAW_DISCHARGE_DISPOSITION,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",37,NO
ENCOUNTER,RAW_DISCHARGE_STATUS,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",38,NO
ENCOUNTER,RAW_DRG_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",39,NO
ENCOUNTER,RAW_ADMITTING_SOURCE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",40,NO
ENCOUNTER,RAW_FACILITY_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",41,NO
ENCOUNTER,RAW_PAYER_TYPE_PRIMARY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",42,NO
ENCOUNTER,RAW_PAYER_NAME_PRIMARY,RDBMS Text(x),SAS Char(x),,NO,,NO,Primary payer name as denoted in the source system.  Used to derive PAYER_TYPE_PRIMARY if validated process does not exist.,43,NO
ENCOUNTER,RAW_PAYER_ID_PRIMARY,RDBMS Text(x),SAS Char(x),,NO,,NO,Primary PAYER identifier as denoted in the source system.  Used to derive PAYER_TYPE_PRIMARY if validated process does not exist.,44,NO
ENCOUNTER,RAW_PAYER_TYPE_SECONDARY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",45,NO
ENCOUNTER,RAW_PAYER_NAME_SECONDARY,RDBMS Text(x),SAS Char(x),,NO,,NO,Secondary payer name as denoted in the source system.  Used to derive PAYER_TYPE_SECONDARY if validated process does not exist.,46,NO
ENCOUNTER,RAW_PAYER_ID_SECONDARY,RDBMS Text(x),SAS Char(x),,NO,,NO,Secondary PAYER identifier as denoted in the source system.  Used to derive PAYER_TYPE_SECONDARY if validated process does not exist.,47,NO
ENROLLMENT,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,48,NO
ENROLLMENT,ENR_START_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"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.",49,NO
ENROLLMENT,ENR_END_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Date of the end of the enrollment period. If the exact date is unknown, use the last day of the month.",50,NO
ENROLLMENT,CHART,RDBMS Text(1),SAS Char(1),,NO,,YES,"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.  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.",51,NO
ENROLLMENT,ENR_BASIS,RDBMS Text(1),SAS Char(1),,NO,,YES,"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 v3.1.) 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 v3.1 to include drug coverage.",52,NO
DIAGNOSIS,DIAGNOSISID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",53,NO
DIAGNOSIS,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,54,NO
DIAGNOSIS,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier. Used to link across tables.,55,NO
DIAGNOSIS,ENC_TYPE,RDBMS Text(2),SAS Char(2),,YES,,YES,Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.,56,NO
DIAGNOSIS,ADMIT_DATE,RDBMS Date,SAS Date (Numeric),,YES,DATE,NO,Please note: This is a field replicated from the ENCOUNTER table. See the ENCOUNTER table for definitions.,57,NO
DIAGNOSIS,PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Identifier associated with the provider most responsible for the diagnosis.,58,NO
DIAGNOSIS,DX,RDBMS Text(18),SAS Char(18),,NO,,NO,"Diagnosis 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. (Description updated in v3.1.)",59,NO
DIAGNOSIS,DX_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,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.,60,NO
DIAGNOSIS,DX_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Date diagnosis was recorded, if known.",61,NO
DIAGNOSIS,DX_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,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.,62,NO
DIAGNOSIS,DX_ORIGIN,RDBMS Text(2),SAS Char(2),,NO,,YES,"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 v3.1.",63,NO
DIAGNOSIS,PDX,RDBMS Text(2),SAS Char(2),,NO,,YES,Principal discharge diagnosis flag.,64,NO
DIAGNOSIS,DX_POA,RDBMS Text(2),SAS Char(2),,NO,,YES,"Flag to denote whether diagnosis was present on inpatient admission.  Y=Diagnosis present at time of inpatient admission.  N=Diagnosis not present at time of inpatient admission.  U=Documentation insufficient to determine if the condition was present at the time of inpatient admission.  W=Clinically undetermined.  Provider unable to clinically determine whether the condition was present at the time of inpatient admission.  1=Unreported / not used.  Exempt from present-on-admission reporting.
",65,NO
DIAGNOSIS,RAW_DX,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",66,NO
DIAGNOSIS,RAW_DX_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",67,NO
DIAGNOSIS,RAW_DX_SOURCE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",68,NO
DIAGNOSIS,RAW_PDX,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",69,NO
DIAGNOSIS,RAW_DX_POA,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",70,NO
PROCEDURES,PROCEDURESID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",71,NO
PROCEDURES,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,72,NO
PROCEDURES,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier. Used to link across tables.,73,NO
PROCEDURES,ENC_TYPE,RDBMS Text(2),SAS Char(2),,YES,,YES,Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.,74,NO
PROCEDURES,ADMIT_DATE,RDBMS Date,SAS Date (Numeric),,YES,DATE,NO,Please note: This is a field replicated from the ENCOUNTER table. See ENCOUNTER table for definitions.,75,NO
PROCEDURES,PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Identifier of the PROVIDER most associated with the procedure order.,76,NO
PROCEDURES,PX_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"PX_DATE should reflect the date the procedure was performed, if known. Leave blank if you cannot determine if or when the procedure was performed.",77,NO
PROCEDURES,PX,RDBMS Text(11),SAS Char(11),,NO,,NO,Procedure code.,78,NO
PROCEDURES,PX_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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 v3.1 to combine CPT and HCPCS codes into one category; also, ICD-9 value set item typo corrected to ICD-9-PCS.",79,NO
PROCEDURES,PX_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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 v3.1.",80,NO
PROCEDURES,PPX,RDBMS Text(2),SAS Char(2),,NO,,YES,Principal procedure flag.,81,NO
PROCEDURES,RAW_PX,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",82,NO
PROCEDURES,RAW_PX_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",83,NO
PROCEDURES,RAW_PPX,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",84,NO
VITAL,VITALID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",85,NO
VITAL,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,86,NO
VITAL,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,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 v3.1.),87,NO
VITAL,MEASURE_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date of vitals measure.,88,NO
VITAL,MEASURE_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time of vitals measure.,89,NO
VITAL,VITAL_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Please note: The “Patient-reported” category can include reporting by patient’s family or guardian. ,90,NO
VITAL,HT,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"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 v3.1.",91,NO
VITAL,WT,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"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 v3.1.",92,NO
VITAL,DIASTOLIC,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"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 v3.1.",93,NO
VITAL,SYSTOLIC,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"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 v3.1.",94,NO
VITAL,ORIGINAL_BMI,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"BMI if calculated in the source system. Decimal precision is permissible (new guidance added in v3.1). 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 v3.1.",95,NO
VITAL,BP_POSITION,RDBMS Text(2),SAS Char(2),,NO,,YES,Position for orthostatic blood pressure. This value should be null if blood pressure was not measured.,96,NO
VITAL,SMOKING,RDBMS Text(2),SAS Char(2),,NO,,YES,"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/standards-certification/2014-edition-draft-test-procedures/170-314-a-11-smoking-status-2014-test-procedure-draft-v1.0.pdf [retrieved May 11, 2015]",97,NO
VITAL,TOBACCO,RDBMS Text(2),SAS Char(2),,NO,,YES,Indicator for any form of tobacco.,98,NO
VITAL,TOBACCO_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Type(s) of tobacco used.,99,NO
VITAL,RAW_DIASTOLIC,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to formatting into the PCORnet CDM.",100,NO
VITAL,RAW_SYSTOLIC,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to formatting into the PCORnet CDM.",101,NO
VITAL,RAW_BP_POSITION,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",102,NO
VITAL,RAW_SMOKING,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",103,NO
VITAL,RAW_TOBACCO,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",104,NO
VITAL,RAW_TOBACCO_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",105,NO
DISPENSING,DISPENSINGID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",106,NO
DISPENSING,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,107,NO
DISPENSING,PRESCRIBINGID,RDBMS Text(x),SAS Char(x),,NO,,NO,"This is an optional relationship to the PRESCRIBING table, and may not be generally available. One prescribing order may generate multiple dispensing records.",108,NO
DISPENSING,DISPENSE_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Dispensing date (as close as possible to date the person received the dispensing).,109,NO
DISPENSING,NDC,RDBMS Text(11),SAS Char(11),,NO,,NO,"National Drug Code in the 11-digit, no-dash, HIPAA format. Please expunge any place holders (such as dashes or extra digits).",110,NO
DISPENSING,DISPENSE_SOURCE,RDBMS Text(2),SAS Char(2),,No,,YES,Source of the dispensing information.,111,NO
DISPENSING,DISPENSE_SUP,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,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 v3.1.,112,NO
DISPENSING,DISPENSE_AMT,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"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 v3.1.",113,NO
DISPENSING,DISPENSE_DOSE_DISP,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"Dose of a given mediation, as dispensed",114,NO
DISPENSING,DISPENSE_DOSE_DISP_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Units of measure associated with the dose of the medication as dispensed,115,NO
DISPENSING,DISPENSE_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _ROUTE in the ValueSet Reference File),Route of delivery,116,NO
DISPENSING,RAW_NDC,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",117,NO
DISPENSING,RAW_DISPENSE_DOSE_DISP,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",118,NO
DISPENSING,RAW_DISPENSE_DOSE_DISP_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",119,NO
DISPENSING,RAW_DISPENSE_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",120,NO
LAB_RESULT_CM,LAB_RESULT_CM_ID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",121,NO
LAB_RESULT_CM,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,122,NO
LAB_RESULT_CM,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",123,NO
LAB_RESULT_CM,SPECIMEN_SOURCE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see SPECIMEN_SOURCE in the ValueSet Reference File),Do not derive a specimen source based on the LOINC code. Please map the specimen source present in the source system to the appropriate code in the Value Set Appendix.,124,YES (MODIFIED VALUESET)
LAB_RESULT_CM,LAB_LOINC,RDBMS Text(10),SAS Char(10),,NO,,NO,"Logical Observation Identifiers, Names, and Codes (LOINC®) from the Regenstrief Institute.  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.",125,NO
LAB_RESULT_CM,LAB_RESULT_SOURCE,RDBMS Text (2),SAS Char(2),,NO,,YES,Source of the information for the lab result,126,NO
LAB_RESULT_CM,LAB_LOINC_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Source/provenance of the LOINC code for this result.
Details of categorical definitions:
Instrument: Assigned by the instrument used to process the sample and generate the result.
Laboratory Information Management System (LIMS): Code is assigned by the system used to manage laboratory results, either stand-alone or as part of the EHR.
HL7 Feed: Code is assigned from an external HL7 feed (e.g., by a Health Information Exchange).
Data warehouse: LOINC codes are generated during the extract-transform-load (ETL) procedures used to populate a standalone data warehouse or reporting database.
PCORnet ETL: LOINC codes are assigned as part of the ETL process used to populate the PCORnet CDM.
Other CDM: Codes are assigned through the ETL used to populate a CDM that is upstream from the PCORnet ETL.  
",127,NO
LAB_RESULT_CM,PRIORITY,RDBMS Text(2),SAS Char(2),,NO,,YES,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).,128,NO
LAB_RESULT_CM,RESULT_LOC,RDBMS Text(2),SAS Char(2),,NO,,YES,"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.",129,NO
LAB_RESULT_CM,LAB_PX,RDBMS Text(11),SAS Char(11),,NO,,NO,"Optional variable for local and standard procedure codes, used to identify the originating order for the lab test.",130,NO
LAB_RESULT_CM,LAB_PX_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Procedure code type, if applicable. Value set modified in v3.1 to combine CPT and HCPCS codes into one category; also, ICD-9 value set item typo corrected to specify ICD-9-PCS.",131,NO
LAB_RESULT_CM,LAB_ORDER_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date test was ordered.,132,NO
LAB_RESULT_CM,SPECIMEN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date specimen was collected.,133,NO
LAB_RESULT_CM,SPECIMEN_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time specimen was collected.,134,NO
LAB_RESULT_CM,RESULT_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Result date.,135,NO
LAB_RESULT_CM,RESULT_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Result time.,136,NO
LAB_RESULT_CM,RESULT_QUAL,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _QUAL in the ValueSet Reference File),Standardized result for qualitative results. This variable should be NI for quantitative results.,137,YES (MODIFIED VALUESET)
LAB_RESULT_CM,RESULT_SNOMED,RDBMS Text(x),SAS Char(x),,NO,,NO,"If the qualitative result has been mapped to SNOMED CT, the corresponding SNOMED code can be placed here.",138,NO
LAB_RESULT_CM,RESULT_NUM,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,Standardized/converted result for quantitative results.,139,NO
LAB_RESULT_CM,RESULT_MODIFIER,RDBMS Text(2),SAS Char(2),,NO,,YES,Modifier for result values.,140,NO
LAB_RESULT_CM,RESULT_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Converted/standardized units for the quantitative result.,141,NO
LAB_RESULT_CM,NORM_RANGE_LOW,RDBMS Text(10),SAS Char(10),,NO,,NO,"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.",142,NO
LAB_RESULT_CM,NORM_MODIFIER_LOW,RDBMS Text(2),SAS Char(2),,NO,,YES,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 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),143,NO
LAB_RESULT_CM,NORM_RANGE_HIGH,RDBMS Text(10),SAS Char(10),,NO,,NO,"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.",144,NO
LAB_RESULT_CM,NORM_MODIFIER_HIGH,RDBMS Text(2),SAS Char(2),,NO,,YES,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 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),145,NO
LAB_RESULT_CM,ABN_IND,RDBMS Text(2),SAS Char(2),,NO,,YES,Abnormal result indicator. This value comes from the source data; do not apply logic to create it.,146,NO
LAB_RESULT_CM,RAW_LAB_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,Local name related to an individual lab test.,147,NO
LAB_RESULT_CM,RAW_LAB_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Local code related to an individual lab test.,148,NO
LAB_RESULT_CM,RAW_PANEL,RDBMS Text(x),SAS Char(x),,NO,,NO,Local code related to a battery or panel of lab tests.,149,NO
LAB_RESULT_CM,RAW_RESULT,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",150,NO
LAB_RESULT_CM,RAW_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,Original units for the result in your source data.,151,NO
LAB_RESULT_CM,RAW_ORDER_DEPT,RDBMS Text(x),SAS Char(x),,NO,,NO,Local code for ordering provider department.,152,NO
LAB_RESULT_CM,RAW_FACILITY_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Local facility code that identifies the hospital or clinic. Taken from facility claims.,153,NO
CONDITION,CONDITIONID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",154,NO
CONDITION,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,155,NO
CONDITION,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",156,NO
CONDITION,REPORT_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"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.",157,NO
CONDITION,RESOLVE_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"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.",158,NO
CONDITION,ONSET_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"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 v3.1.)",159,NO
CONDITION,CONDITION_STATUS,RDBMS Text(2),SAS Char(2),,NO,,YES,Condition status corresponding with REPORT_DATE.,160,NO
CONDITION,CONDITION,RDBMS Text(18),SAS Char(18),,NO,,NO,"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 v3.1.)",161,NO
CONDITION,CONDITION_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Condition code type.  Please note: The “Other” category is meant to identify internal use ontologies and codes.,162,NO
CONDITION,CONDITION_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Please note: The “Patient-reported” category can include reporting by a proxy, such as patient’s family or guardian.",163,NO
CONDITION,RAW_CONDITION_STATUS,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",164,NO
CONDITION,RAW_CONDITION,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",165,NO
CONDITION,RAW_CONDITION_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",166,NO
CONDITION,RAW_CONDITION_SOURCE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",167,NO
PRO_CM,PRO_CM_ID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",168,NO
PRO_CM,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier for the patient for whom the PRO response was captured. Used to link across tables.,169,NO
PRO_CM,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",170,NO
PRO_CM,PRO_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,The date of the response.,171,NO
PRO_CM,PRO_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,The time of the response.,172,NO
PRO_CM,PRO_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Terminology / vocabulary used to describe the PRO item.
More information on PROMIS, Neuro-QoL and ASQC-Me and the NIH Toolbox can be found on the HealthMeasures website. (www.healthmeasures.net)
The Patient-Reported Outcome version of the Common Terminology Criteria for Adverse Events (PRO-CTCAE™) is maintained by the National Cancer Institute. (https://healthcaredelivery.cancer.gov/pro-ctcae/)
Information on the Hospital Consumer Assessment of Healthcare Providers and Systems (HPCAHPS) is located here:
http://www.hcahpsonline.org",173,NO
PRO_CM,PRO_ITEM_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,Short name or code of the PRO item in the vocabulary/terminology specified in PRO_TYPE.,174,NO
PRO_CM,PRO_ITEM_LOINC,RDBMS Text(10),SAS Char(10),,NO,,NO,"LOINC® code for the PRO item, if available. 

Logical Observation Identifiers, Names, and Codes (LOINC) from the Regenstrief Institute.  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.
",175,NO
PRO_CM,PRO_RESPONSE_TEXT,RDBMS Text(x),SAS Char(x),,NO,,NO,"Text version of the response recorded for the item, if available/applicable.",176,NO
PRO_CM,PRO_RESPONSE_NUM,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,,177,NO
PRO_CM,PRO_METHOD,RDBMS Text(2),SAS Char(2),,NO,,YES,"Method of administration. Electronic includes responses captured via a personal or tablet computer, at web kiosks, or via a smartphone.",178,NO
PRO_CM,PRO_MODE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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.",179,NO
PRO_CM,PRO_CAT,RDBMS Text(2),SAS Char(2),,NO,,YES,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.,180,NO
PRO_CM,PRO_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the information for the PRO result.,181,NO
PRO_CM,PRO_ITEM_VERSION,RDBMS Text(x),SAS Char(x),,NO,,NO,Version of the item/question.,182,NO
PRO_CM,PRO_MEASURE_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,"Short name or code of the PRO measure/form that item belongs to, if item is being administered as part of a measure",183,NO
PRO_CM,PRO_MEASURE_SEQ,RDBMS Text(x),SAS Char(x),,,,NO,Arbitrary ID/sequence number used to link PRO item responses that are associated with the same measure/form.  ,184,NO
PRO_CM,PRO_MEASURE_SCORE,RDBMS Number(x),SAS Numeric(length 8),,,,NO,Overall raw score for the PRO measure.,185,NO
PRO_CM,PRO_MEASURE_THETA,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,The value of theta reported from the CAT PROMIS results.  Only applies to items that are administered as part of a measure.,186,NO
PRO_CM,PRO_MEASURE_SCALED_TSCORE,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,Standardized score based on the total raw score for the instrument.  Only applies to items that are administered as part of a measure.,187,NO
PRO_CM,PRO_MEASURE_STANDARD_ERROR,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,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.,188,NO
PRO_CM,PRO_MEASURE_COUNT_SCORED,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,Number of PRO item responses that were involved in the scoring of the measure.,189,NO
PRO_CM,PRO_MEASURE_LOINC,RDBMS Text(10),SAS Char(10),,NO,,NO,"LOINC® code for the PRO item, if available. 

Logical Observation Identifiers, Names, and Codes (LOINC) from the Regenstrief Institute.  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.
",190,NO
PRO_CM,PRO_MEASURE_VERSION,RDBMS Text(x),SAS Char(x),.,NO,,NO,Version of the measure.,191,NO
PRO_CM,PRO_ITEM_FULLNAME,RDBMS Text(x),SAS Char(x),.,NO,,NO,Full name of the PRO item.,192,NO
PRO_CM,PRO_ITEM_TEXT,RDBMS Text(x),SAS Char(x),.,NO,,NO,Text of the PRO item question.,193,NO
PRO_CM,PRO_MEASURE_FULLNAME,RDBMS Text(x),SAS Char(x),.,NO,,NO,Full name of the PRO measure.,194,NO
PRESCRIBING,PRESCRIBINGID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",195,NO
PRESCRIBING,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,196,NO
PRESCRIBING,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier. This is an optional relationship; the ENCOUNTERID should be present if the prescribing activity is directly associated with an encounter.,197,NO
PRESCRIBING,RX_PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Provider code for the provider who prescribed the medication. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.,198,NO
PRESCRIBING,RX_ORDER_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Order date of the prescription by the provider.,199,NO
PRESCRIBING,RX_ORDER_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Order time of the prescription by the provider.,200,NO
PRESCRIBING,RX_START_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Start date of order. This attribute may not be consistent with the date on which the patient actually begin taking the medication.,201,NO
PRESCRIBING,RX_END_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,End date of order (if available).,202,NO
PRESCRIBING,RX_DOSE_ORDERED,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,"Dose of a given mediation, as ordered by the provider",203,NO
PRESCRIBING,RX_DOSE_ORDERED_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Units of measure associated with the dose of the medication as ordered by the provider,204,NO
PRESCRIBING,RX_QUANTITY,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,Quantity ordered.,205,NO
PRESCRIBING,RX_DOSE_FORM,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _DOSE_FORM in the ValueSet Reference File),The unit associated with the quantity prescribed.  This is equivalent to RxNorm Dose Form.,206,NO
PRESCRIBING,RX_REFILLS,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"Number of refills ordered (not including the original prescription). If no refills are ordered, the value should be zero.",207,NO
PRESCRIBING,RX_DAYS_SUPPLY,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"Number of days supply ordered, as specified by the prescription.",208,NO
PRESCRIBING,RX_FREQUENCY,RDBMS Text(2),SAS Char(2),,NO,,YES,Specified frequency of medication.,209,NO
PRESCRIBING,RX_PRN_FLAG,RDBMS Text(1),SAS Char(1),,NO,,YES,Flag to indicate that all or part of medication frequency instructions includes “as needed.”,210,NO
PRESCRIBING,RX_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _ROUTE in the ValueSet Reference File),Route of medication delivery.,211,NO
PRESCRIBING,RX_BASIS,RDBMS Text(2),SAS Char(2),,NO,,YES,"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 v3.1.)",212,NO
PRESCRIBING,RXNORM_CUI,RDBMS Text (8),SAS Char(8),,NO,,NO,"Where an RxNorm mapping exists for the source medication, this field contains the RxNorm concept identifier (CUI) at the highest possible specificity. v3.1 modification: field types changed to character because the National Library of Medicine specifies this variable as a character type.",213,NO
PRESCRIBING,RX_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the prescribing information.,214,NO
PRESCRIBING,RX_DISPENSE_AS_WRITTEN,RDBMS Text(2),SAS Char(2),,NO,,YES,Flag to indicate whether the provider indicated that the medication order was to be dispensed as written.,215,NO
PRESCRIBING,RAW_RX_MED_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating, full textual medication name from the source.",216,NO
PRESCRIBING,RAW_RX_FREQUENCY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",217,NO
PRESCRIBING,RAW_RXNORM_CUI,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",218,NO
PRESCRIBING,RAW_RX_QUANTITY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",219,NO
PRESCRIBING,RAW_RX_NDC,RDBMS Text(x),SAS Char(x),,NO,,NO,"Optional field for originating value of field, prior to mapping into the PCORnet CDM value set.",220,NO
PRESCRIBING,RAW_RX_DOSE_ORDERED,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",221,NO
PRESCRIBING,RAW_RX_DOSE_ORDERED_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",222,NO
PRESCRIBING,RAW_RX_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",223,NO
PRESCRIBING,RAW_RX_REFILLS,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",224,NO
PCORNET_TRIAL,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,225,NO
PCORNET_TRIAL,TRIALID,RDBMS Text(20),SAS Char(20),,NO,,NO,Each TRIALID is assigned by the PCORnet trial’s coordinating center.,226,NO
PCORNET_TRIAL,PARTICIPANTID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",227,NO
PCORNET_TRIAL,TRIAL_SITEID,RDBMS Text(x),SAS Char(x),,NO,,NO,Each TRIAL_SITEID is assigned by the PCORnet trial coordinating center.,228,NO
PCORNET_TRIAL,TRIAL_ENROLL_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date on which the participant enrolled in the trial (generally coincides with trial consent process).,229,NO
PCORNET_TRIAL,TRIAL_END_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date on which the participant completes participation in the trial.,230,NO
PCORNET_TRIAL,TRIAL_WITHDRAW_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"If applicable, date on which the participant withdraws consent from the trial.",231,NO
PCORNET_TRIAL,TRIAL_INVITE_CODE,RDBMS Text(20),SAS Char(20),,NO,,NO,"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.",232,NO
DEATH,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,233,NO
DEATH,DEATH_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date of death.,234,NO
DEATH,DEATH_DATE_IMPUTE,RDBMS Text(2),SAS Char(2),,NO,,YES,"When date of death is imputed, this field indicates which parts of the date were imputed.",235,NO
DEATH,DEATH_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,,236,NO
DEATH,DEATH_MATCH_CONFIDENCE,RDBMS Text(2),SAS Char(2),,NO,,YES,"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. ",237,NO
DEATH_CAUSE,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,238,NO
DEATH_CAUSE,DEATH_CAUSE,RDBMS Text(8),SAS Char(8),,NO,,NO,Cause of death code. Please include the decimal point in ICD codes (if any).,239,NO
DEATH_CAUSE,DEATH_CAUSE_CODE,RDBMS Text(2),SAS Char(2),,NO,,YES,Cause of death code type.,240,NO
DEATH_CAUSE,DEATH_CAUSE_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Cause of death type. There should be only one underlying cause of death.,241,NO
DEATH_CAUSE,DEATH_CAUSE_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of cause of death information.,242,NO
DEATH_CAUSE,DEATH_CAUSE_CONFIDENCE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Confidence in the accuracy of the cause of death based on source, match, number of reporting sources, discrepancies, etc.",243,NO
MED_ADMIN,MEDADMINID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique MED_ADMIN record.,244,NO
MED_ADMIN,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables.,245,NO
MED_ADMIN,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier. The ENCOUNTERID should be present.,246,NO
MED_ADMIN,PRESCRIBINGID,RDBMS Text(x),SAS Char(x),,NO,,NO,"This is an optional relationship to the PRESCRIBING table, and may not be generally available. One prescribing order may generate multiple administration records.",247,NO
MED_ADMIN,MEDADMIN_PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Provider code for the provider who prescribed the medication. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.,248,NO
MED_ADMIN,MEDADMIN_START_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date medication administration started/occurred,249,NO
MED_ADMIN,MEDADMIN_START_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time medication administration started/occurred,250,NO
MED_ADMIN,MEDADMIN_STOP_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date medication administration ended,251,NO
MED_ADMIN,MEDADMIN_STOP_TIME,RDBMS Text(5),SAS Time (Numeric),HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time medication administration ended,252,NO
MED_ADMIN,MEDADMIN_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Medication code type,253,NO
MED_ADMIN,MEDADMIN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Medication code,254,NO
MED_ADMIN,MEDADMIN_DOSE_ADMIN,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,"Dose of a given mediation, as administered by the provider",255,NO
MED_ADMIN,MEDADMIN_DOSE_ADMIN_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Units of measure associated with the dose of the medication as administered by the provider,256,NO
MED_ADMIN,MEDADMIN_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _ROUTE in the ValueSet Reference File),Route of medication delivery.,257,NO
MED_ADMIN,MEDADMIN_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the medication administration record.,258,NO
MED_ADMIN,RAW_MEDADMIN_MED_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating, full textual medication name from the source.",259,NO
MED_ADMIN,RAW_MEDADMIN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",260,NO
MED_ADMIN,RAW_MEDADMIN_DOSE_ADMIN,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",261,NO
MED_ADMIN,RAW_MEDADMIN_DOSE_ADMIN_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",262,NO
MED_ADMIN,RAW_MEDADMIN_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",263,NO
PROVIDER,PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",264,NO
PROVIDER,PROVIDER_SEX,RDBMS Text(2),SAS Char(2),,NO,,YES,Sex assigned at birth.,265,NO
PROVIDER,PROVIDER_SPECIALTY_PRIMARY,RDBMS Text(x),SAS Char(x),,NO,,YES (also see PROVIDER_SPECIALTY_PRIMARY in the ValueSet Reference File),Primary specialty of the provider,266,YES (MODIFIED VALUESET)
PROVIDER,PROVIDER_NPI,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,National Provider Identifier (NPI) of the provider.,267,NO
PROVIDER,PROVIDER_NPI_FLAG,RDBMS Text(1),SAS Char(1),,NO,,YES,Flag to indicate whether partner has access to the National Provider Identifier (NPI) of the provider.,268,NO
PROVIDER,RAW_PROVIDER_SPECIALTY_PRIMARY,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value of field, prior to mapping into the PCORnet CDM value set.",269,NO
OBS_CLIN,OBSCLINID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique OBS_CLIN record.,270,NO
OBS_CLIN,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,271,NO
OBS_CLIN,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier used to link across tables.,272,NO
OBS_CLIN,OBSCLIN_PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Provider code for the provider who ordered the observation. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.,273,NO
OBS_CLIN,OBSCLIN_START_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date of observation/measurement.,274,NO
OBS_CLIN,OBSCLIN_START_TIME,RDBMS Text(5),SAS Time (Numeric),Format as HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time of observation/measurement.,275,NO
OBS_CLIN,OBSCLIN_STOP_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date observation/measurement ended.,276,NO
OBS_CLIN,OBSCLIN_STOP_TIME,RDBMS Text(5) ,SAS Time (Numeric),Format as HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time observation/measurement ended.,277,NO
OBS_CLIN,OBSCLIN_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Terminology / vocabulary used to describe the clinical observation.,278,NO
OBS_CLIN,OBSCLIN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Code of the clinical observation in the vocabulary/terminology specified in OBSCLIN_TYPE.,279,NO
OBS_CLIN,OBSCLIN_RESULT_QUAL,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _QUAL in the ValueSet Reference File),Standardized result for qualitative results. This variable should be NI for quantitative results.,280,YES (MODIFIED VALUESET)
OBS_CLIN,OBSCLIN_RESULT_TEXT,RDBMS Text(x),SAS Char(x),,NO,,NO,Narrative/textual clinical observations,281,NO
OBS_CLIN,OBSCLIN_RESULT_SNOMED,RDBMS Text(x),SAS Char(x),,NO,,NO,"If the qualitative result has been mapped to SNOMED CT, the corresponding SNOMED code can be placed here.",282,NO
OBS_CLIN,OBSCLIN_RESULT_NUM,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,Standardized/converted result for quantitative results.,283,NO
OBS_CLIN,OBSCLIN_RESULT_MODIFIER,RDBMS Text(2),SAS Char(2),,NO,,YES,Modifier for result values.,284,NO
OBS_CLIN,OBSCLIN_RESULT_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Converted/standardized units for the result.,285,NO
OBS_CLIN,OBSCLIN_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the information for the observation or measurement.,286,NO
OBS_CLIN,OBSCLIN_ABN_IND,RDBMS Text(2),SAS Char(2),,NO,,YES,"Abnormal result indicator. This value comes from the source data; do not apply logic to create it.  If field is blank in source data, map to the appropriate flavor of null.",287,NO
OBS_CLIN,RAW_OBSCLIN_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,Local name related to an individual clinical observation/measurement.,288,NO
OBS_CLIN,RAW_OBSCLIN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Local code related to an individual clinical observation/measurement.,289,NO
OBS_CLIN,RAW_OBSCLIN_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,Terminology related to the code in RAW_OBSGEN_CODE.,290,NO
OBS_CLIN,RAW_OBSCLIN_RESULT,RDBMS Text(x),SAS Char(x),,NO,,NO,"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.",291,NO
OBS_CLIN,RAW_OBSCLIN_MODIFIER,RDBMS Text(x),SAS Char(x),,NO,,NO,The original modifier text as represented in your source data.,292,NO
OBS_CLIN,RAW_OBSCLIN_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,Original units for the result in your source data.,293,NO
OBS_GEN,OBSGENID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique OBS_GEN record.,294,NO
OBS_GEN,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,295,NO
OBS_GEN,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,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.,296,NO
OBS_GEN,OBSGEN_PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Provider code for the provider who recorded the observation. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier.,297,NO
OBS_GEN,OBSGEN_START_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date of observation/measurement,298,NO
OBS_GEN,OBSGEN_START_TIME,RDBMS Text(5) ,SAS Time (Numeric),Format as HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time of observation/measurement.,299,NO
OBS_GEN,OBSGEN_STOP_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date observation/measurement ended.,300,NO
OBS_GEN,OBSGEN_STOP_TIME,RDBMS Text(5) ,SAS Time (Numeric),Format as HH:MI using 24-hour clock and zero-padding for hour and minute,NO,TIME,NO,Time observation/measurement ended.,301,NO
OBS_GEN,OBSGEN_TYPE,RDBMS Text(30),SAS Char(30),,NO,,YES,"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.",302,NO
OBS_GEN,OBSGEN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Standardized code denoting the observations based on the terminology/vocabulary specified in OBSGEN_TYPE,303,NO
OBS_GEN,OBSGEN_RESULT_QUAL,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _QUAL in the ValueSet Reference File),Standardized result for qualitative results. This variable should be NI for quantitative results.,304,YES (MODIFIED VALUESET)
OBS_GEN,OBSGEN_RESULT_TEXT,RDBMS Text(x),SAS Char(x),,NO,,NO,Narrative/textual observations.,305,NO
OBS_GEN,OBSGEN_RESULT_NUM,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,Standardized/converted result for quantitative results.,306,NO
OBS_GEN,OBSGEN_RESULT_MODIFIER,RDBMS Text(2),SAS Char(2),,NO,,YES,Modifier for result values.,307,NO
OBS_GEN,OBSGEN_RESULT_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Converted/standardized units for the result.,308,NO
OBS_GEN,OBSGEN_TABLE_MODIFIED,RDBMS Text(3),SAS Char(3),,NO,,YES,Table name when observation describes attributes of an existing record in the CDM.,309,NO
OBS_GEN,OBSGEN_ID_MODIFIED,RDBMS Text(x),SAS Char(x),,NO,,NO,Identifier when observation describes attributes of an existing record in the CDM.,310,NO
OBS_GEN,OBSGEN_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the information for the observation or measurement. ,311,NO
OBS_GEN,OBSGEN_ABN_IND,RDBMS Text(2),SAS Char(2),,NO,,YES,"Abnormal result indicator. This value comes from the source data; do not apply logic to create it.  If field is blank in source data, map to the appropriate flavor of null.",312,NO
OBS_GEN,RAW_OBSGEN_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,Local name related to an individual clinical observation/measurement.,313,NO
OBS_GEN,RAW_OBSGEN_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Local code related to an individual clinical observation/measurement.,314,NO
OBS_GEN,RAW_OBSGEN_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,Terminology related to the code in RAW_OBSGEN_CODE.,315,NO
OBS_GEN,RAW_OBSGEN_RESULT,RDBMS Text(x),SAS Char(x),,NO,,NO,The original test result value as seen in your source data.,316,NO
OBS_GEN,RAW_OBSGEN_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,Original units for the result in your source data.,317,NO
HASH_TOKEN,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.PATID is passed through the Datavant DeID module in order to be associated with the generated encrypted keyed hashes.,318,NO
HASH_TOKEN,TOKEN_01,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 01 in Datavant DeID. Enforced through PCORnet configuration setting.,319,NO
HASH_TOKEN,TOKEN_02,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 02 in Datavant DeID. Enforced through PCORnet configuration setting.,320,NO
HASH_TOKEN,TOKEN_03,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 03 in Datavant DeID. Enforced through PCORnet configuration setting.,321,NO
HASH_TOKEN,TOKEN_04,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 04 in Datavant DeID. Enforced through PCORnet configuration setting.,322,NO
HASH_TOKEN,TOKEN_05,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 05 in Datavant DeID. Enforced through PCORnet configuration setting.,323,NO
HASH_TOKEN,TOKEN_16,RDBMS Text(x),SAS Char(x),,NO,,NO,Encrypted keyed hash generated from PII using token strategy 16 in Datavant DeID. Enforced through PCORnet configuration setting.,324,NO
LDS_ADDRESS_HISTORY,ADDRESSID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique address record. ,325,NO
LDS_ADDRESS_HISTORY,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier. Used to link across tables.,326,NO
LDS_ADDRESS_HISTORY,ADDRESS_USE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Purpose of the address.
Details of categorical definitions:
Home: A communication address at home.
Work: An office address.  First choice for business-related contacts during business hours.
Temp: A temporary address.
Old/Incorrect: This address is no longer in use (or was never correct but retained for records).",327,NO
LDS_ADDRESS_HISTORY,ADDRESS_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Type of address.
Details of categorical definitions:
Postal: mailing address – PO Boxes and care-of addresses.
Physical: A physical address that can be visited.
Both: An address that is both physical and postal.",328,NO
LDS_ADDRESS_HISTORY,ADDRESS_PREFERRED,RDBMS Text(2),SAS Char(2),,NO,,YES,"Indicates whether this address is the preferred one for a given patient, address use and address type within a given address period.",329,NO
LDS_ADDRESS_HISTORY,ADDRESS_CITY,RDBMS Text(x),SAS Char(x),,NO,,NO,"The name of the city, town, village or other community.",330,NO
LDS_ADDRESS_HISTORY,ADDRESS_STATE,RDBMS Text(2),SAS Char(2),,NO,,YES (also see STATE in the ValueSet Reference File),"State, as represented by 2-digit postal abbreviation.",331,NO
LDS_ADDRESS_HISTORY,ADDRESS_ZIP5,RDBMS Text(5),SAS Char(5),,NO,,NO,5-digit postal code for the address.,332,NO
LDS_ADDRESS_HISTORY,ADDRESS_ZIP9,RDBMS Text(9),SAS Char(9),,NO,,NO,9-digit postal code for the address.,333,NO
LDS_ADDRESS_HISTORY,ADDRESS_PERIOD_START,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Initial date when the address is known to be in use.,334,NO
LDS_ADDRESS_HISTORY,ADDRESS_PERIOD_END,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Date when address was no longer in use.,335,NO
IMMUNIZATION,IMMUNIZATIONID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique IMMUNIZATION record. ,336,NO
IMMUNIZATION,PATID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary person-level identifier used to link across tables. ,337,NO
IMMUNIZATION,ENCOUNTERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary encounter-level identifier. This should be present if the immunization activity is directly associated with an encounter.,338,NO
IMMUNIZATION,PROCEDURESID,RDBMS Text(x),SAS Char(x),,NO,,NO,This is an optional relationship to the PROCEDURES table and is not expected to be available for all immunizations.  One procedure may generate multiple immunization records.,339,NO
IMMUNIZATION,VX_PROVIDERID,RDBMS Text(x),SAS Char(x),,NO,,NO,Provider code for the provider who delivered the immunization. The provider code is a pseudoidentifier with a consistent crosswalk to the real identifier. ,340,NO
IMMUNIZATION,VX_RECORD_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Date immunization was recorded (i.e., date record was created).",341,NO
IMMUNIZATION,VX_ADMIN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Date immunization was administered, if known.",342,NO
IMMUNIZATION,VX_CODE_TYPE,RDBMS Text(2),SAS Char(2),,NO,,YES,Immunization code type.,343,NO
IMMUNIZATION,VX_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,Immunization code,344,NO
IMMUNIZATION,VX_STATUS,RDBMS Text(2),SAS Char(2),,NO,,YES,Status of the immunization.,345,NO
IMMUNIZATION,VX_STATUS_REASON,RDBMS Text(2),SAS Char(2),,NO,,YES,Reason immunization is incomplete or not done.,346,NO
IMMUNIZATION,VX_SOURCE,RDBMS Text(2),SAS Char(2),,NO,,YES,Source of the prescribing information.,347,NO
IMMUNIZATION,VX_DOSE,RDBMS Number(x),SAS Numeric(length 8),,NO,,NO,Dose of a given immunization,348,NO
IMMUNIZATION,VX_DOSE_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Units of measure associated with the dose of the immunization as delivered by the provider,349,NO
IMMUNIZATION,VX_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _ROUTE in the ValueSet Reference File),Immunization administration route. ,350,NO
IMMUNIZATION,VX_BODY_SITE,RDBMS Text (x),SAS Char(x),,NO,,YES (also see VX_BODY_SITE in the ValueSet Reference File),Immunization administration body site. ,351,NO
IMMUNIZATION,VX_MANUFACTURER,RDBMS Text(x),SAS Char(x),,NO,,YES (also see VX_MANUFACTURER in the ValueSet Reference File),Manufacturer of the immunization.,352,YES (MODIFIED VALUESET)
IMMUNIZATION,VX_LOT_NUM,RDBMS Text(x),SAS Char(x),,NO,,NO,Lot number of the immunization.,353,NO
IMMUNIZATION,VX_EXP_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Expiration date of the immunization.,354,NO
IMMUNIZATION,RAW_VX_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating, full textual immunization name from the source.",355,NO
IMMUNIZATION,RAW_VX_CODE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",356,NO
IMMUNIZATION,RAW_VX_CODE_TYPE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",357,NO
IMMUNIZATION,RAW_VX_DOSE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",358,NO
IMMUNIZATION,RAW_VX_DOSE_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",359,NO
IMMUNIZATION,RAW_VX_ROUTE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",360,NO
IMMUNIZATION,RAW_VX_BODY_SITE,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",361,NO
IMMUNIZATION,RAW_VX_STATUS,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",362,NO
IMMUNIZATION,RAW_VX_STATUS_REASON,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",363,NO
IMMUNIZATION,RAW_VX_MANUFACTURER,RDBMS Text(x),SAS Char(x),,NO,,NO,"Field for originating value, prior to mapping into the PCORnet CDM value set.",364,NO
HARVEST,NETWORKID,RDBMS Text(10),SAS Char(10),,NO,,NO,This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) ,365,NO
HARVEST,NETWORK_NAME,RDBMS Text(20),SAS Char(20),,NO,,NO,"Descriptive name of the network.
This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) ",366,NO
HARVEST,DATAMARTID,RDBMS Text(10),SAS Char(10),,NO,,NO,This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) ,367,NO
HARVEST,DATAMART_NAME,RDBMS Text(20),SAS Char(20),,NO,,NO,"Descriptive name of the datamart.
This identifier is assigned by the PCORnet Distributed Research Network Operations Center (DRN OC) ",368,NO
HARVEST,DATAMART_PLATFORM,RDBMS Text(2),SAS Char(2),,NO,,YES,,369,NO
HARVEST,CDM_VERSION,RDBMS Text(3),SAS Char(3),,NO,,YES,Version currently implemented within this datamart.,370,NO
HARVEST,DATAMART_CLAIMS,RDBMS Text(2),SAS Char(2),,NO,,YES,Datamart includes claims data source(s),371,NO
HARVEST,DATAMART_EHR,RDBMS Text(2),SAS Char(2),,NO,,YES,Datamart includes EHR data source(s),372,NO
HARVEST,TOKEN_ENCRYPTION_KEY,RDBMS Text(x),SAS Char(x),,NO,,NO,Name of the key used to generate the encrypted hash tokens.,373,NO
HARVEST,BIRTH_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the BIRTH_DATE field on the DEMOGRAPHIC table. Please see notes for additional definitions.,374,NO
HARVEST,ENR_START_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the ENR_START_DATE field on the ENROLLMENT table. Please see notes for additional definitions.,375,NO
HARVEST,ENR_END_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the ENR_END_DATE field on the ENROLLMENT table. Please see notes for additional definitions.,376,NO
HARVEST,ADMIT_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the ADMIT_DATE field on the ENCOUNTER table. Please see notes for additional definitions.,377,NO
HARVEST,DISCHARGE_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the DISCHARGE_DATE field on the ENCOUNTER table. Please see notes for additional definitions.,378,NO
HARVEST,DX_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the DX_DATE field on the DIAGNOSIS table. Please see notes for additional definitions.,379,NO
HARVEST,PX_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the PX_DATE field on the PROCEDURES table. Please see notes for additional definitions.,380,NO
HARVEST,RX_ORDER_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the RX_ORDER_DATE field on the PRESCRIBING table. Please see notes for additional definitions.,381,NO
HARVEST,RX_START_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the RX_START_DATE field on the PRESCRIBING table. Please see notes for additional definitions.,382,NO
HARVEST,RX_END_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the RX_END_DATE field on the PRESCRIBING table. Please see notes for additional definitions.,383,NO
HARVEST,DISPENSE_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the DISPENSE_DATE field on the DISPENSING table. Please see notes for additional definitions.,384,NO
HARVEST,LAB_ORDER_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the LAB_ORDER_DATE field on the LAB_RESULT_CM table. Please see notes for additional definitions.,385,NO
HARVEST,SPECIMEN_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the SPECIMEN_DATE field on the LAB_RESULT_CM table. Please see notes for additional definitions.,386,NO
HARVEST,RESULT_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the RESULT_DATE field on the LAB_RESULT_CM table. Please see notes for additional definitions.,387,NO
HARVEST,MEASURE_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the MEASURE_DATE field on the VITAL table. Please see notes for additional definitions.,388,NO
HARVEST,ONSET_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the ONSET_DATE field on the CONDITION table. Please see notes for additional definitions.,389,NO
HARVEST,REPORT_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the REPORT_DATE field on the CONDITION table. Please see notes for additional definitions.,390,NO
HARVEST,RESOLVE_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the RESOLVE_DATE field on the CONDITION table. Please see notes for additional definitions.,391,NO
HARVEST,PRO_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy currently present in the PRO_DATE field on the PRO_CM table. Please see notes for additional definitions.,392,NO
HARVEST,DEATH_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the DEATH_DATE field in the DEATH table.,393,NO
HARVEST,MEDADMIN_START_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the MEDADMIN_START_DATE field in the MED_ADMIN table.,394,NO
HARVEST,MEDADMIN_STOP_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the MEDADMIN_STOP_DATE field in the MED_ADMIN table.,395,NO
HARVEST,OBSCLIN_START_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the OBSCLIN_START_DATE field in the OBS_CLIN table.,396,NO
HARVEST,OBSCLIN_STOP_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the OBSCLIN_STOP_DATE field in the OBS_CLIN table.,397,NO
HARVEST,OBSGEN_START_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the OBSGEN_START_DATE field in the OBS_GEN table.,398,NO
HARVEST,OBSGEN_STOP_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the OBSGEN_STOP_DATE field in the OBS_GEN table.,399,NO
HARVEST,ADDRESS_PERIOD_START_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the ADDRESS_PERIOD_START_MGMT field in the LDS_ADDRESS_HISTORY table.,400,NO
HARVEST,ADDRESS_PERIOD_END_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the ADDRESS_PERIOD_END_MGMT field in the LDS_ADDRESS_HISTORY table.,401,NO
HARVEST,VX_RECORD_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the VX_RECORD_DATE_MGMT field in the IMMUNIZATION table.,402,NO
HARVEST,VX_ADMIN_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the VX_ADMIN_DATE_MGMT field in the IMMUNIZATION table.,403,NO
HARVEST,VX_EXP_DATE_MGMT,RDBMS Text(2),SAS Char(2),,NO,,YES,Data management strategy employed for the VX_EXP_DATE_MGMT field in the IMMUNIZATION table.,404,NO
HARVEST,REFRESH_DEMOGRAPHIC_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,405,NO
HARVEST,REFRESH_ENROLLMENT_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,406,NO
HARVEST,REFRESH_ENCOUNTER_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,407,NO
HARVEST,REFRESH_DIAGNOSIS_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,408,NO
HARVEST,REFRESH_PROCEDURES_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,409,NO
HARVEST,REFRESH_VITAL_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,410,NO
HARVEST,REFRESH_DISPENSING_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,411,NO
HARVEST,REFRESH_LAB_RESULT_CM_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,412,NO
HARVEST,REFRESH_CONDITION_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,413,NO
HARVEST,REFRESH_PRO_CM_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,414,NO
HARVEST,REFRESH_PRESCRIBING_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,415,NO
HARVEST,REFRESH_PCORNET_TRIAL_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,416,NO
HARVEST,REFRESH_DEATH_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,417,NO
HARVEST,REFRESH_DEATH_CAUSE_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,418,NO
HARVEST,REFRESH_MED_ADMIN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,419,NO
HARVEST,REFRESH_OBS_CLIN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,420,NO
HARVEST,REFRESH_PROVIDER_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,421,NO
HARVEST,REFRESH_OBS_GEN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,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.,422,NO
HARVEST,REFRESH_HASH_TOKEN_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Most recent date on which the present data were loaded into the HASH_TOKEN table. This date should be null if the table does not have records.,423,NO
HARVEST,REFRESH_LDS_ADDRESS_HX_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Most recent date on which the present data were loaded into the LDS_ADDRESS_HISTORY table. This date should be null if the table does not have records.,424,NO
HARVEST,REFRESH_IMMUNIZATION_DATE,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,Most recent date on which the present data were loaded into the IMMUNIZATION table. This date should be null if the table does not have records.,425,NO
LAB_HISTORY,LABHISTORYID,RDBMS Text(x),SAS Char(x),,NO,,NO,Arbitrary identifier for each unique LAB_HISTORY record.,426,NO
LAB_HISTORY,LAB_LOINC,RDBMS Text(10),SAS Char(10),,NO,,NO,"Logical Observation Identifiers, Names, and Codes (LOINC®) from the Regenstrief Institute. 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. ",427,NO
LAB_HISTORY,LAB_FACILITYID,RDBMS Text(x),SAS Char(x),,NO,,NO,"Arbitrary local code that identifies the facility providing lab results. Used in instances where partners are aggregating laboratory results from a number of different organizations. LAB_FACILITYID can be a true identifier, or a pseudoidentifier with a consistent crosswalk to the true identifier retained by the source data partner.",428,NO
LAB_HISTORY,SEX,RDBMS Text(2),SAS Char(2),,NO,,YES,Sex to which this unit and range applies.,429,NO
LAB_HISTORY,RACE,RDBMS Text(2),SAS Char(2),,NO,,YES,"Race to which this unit and range applies. 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.",430,NO
LAB_HISTORY,AGE_MIN_WKS,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"Minimum age to which this unit and range applies, in weeks.",431,NO
LAB_HISTORY,AGE_MAX_WKS,RDBMS Number(x),SAS Numeric(length 8),"RDBMS number supports 15 total digits, 8 after decimal; SAS numeric length 8",NO,,NO,"Maximum age to which this unit and range applies, in weeks.",432,NO
LAB_HISTORY,RESULT_UNIT,RDBMS Text(x),SAS Char(x),,NO,,YES (also see _UNIT in the ValueSet Reference File),Converted/standardized units for the specified LOINC.,433,NO
LAB_HISTORY,NORM_RANGE_LOW,RDBMS Text(10),SAS Char(10),,NO,,NO,"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.",434,NO
LAB_HISTORY,NORM_MODIFIER_LOW,RDBMS Text(2),SAS Char(2),,NO,,YES,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 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),435,NO
LAB_HISTORY,NORM_RANGE_HIGH,RDBMS Text(10),SAS Char(10),,NO,,NO,"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.",436,NO
LAB_HISTORY,NORM_MODIFIER_HIGH,RDBMS Text(2),SAS Char(2),,NO,,YES,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 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),437,NO
LAB_HISTORY,PERIOD_START,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Initial date when the unit and range are known to be in use for the specified age range, race, sex and facility.",438,NO
LAB_HISTORY,PERIOD_END,RDBMS Date,SAS Date (Numeric),,NO,DATE,NO,"Date when the unit and range are no longer in use for the specified age range, race, sex and facility.",439,NO
LAB_HISTORY,RAW_LAB_NAME,RDBMS Text(x),SAS Char(x),,NO,,NO,Local name related to an individual lab test.,440,NO
LAB_HISTORY,RAW_UNIT,RDBMS Text(x),SAS Char(x),,NO,,NO,Original units in your source data.,441,NO
LAB_HISTORY,RAW_RANGE,RDBMS Text(x),SAS Char(x),,NO,,NO,Original reference range in your source data.,442,NO