Sentinel Routine Querying Tool Documentation
Public
Commits
Amelia Thyen authored and Daniel Scarnecchia committed 5d4e92a98ca
| 19 19 | |Code Category|CODECAT|Type of each code category value included in the CODETYPE field (below) of this file. <br> <br> Valid values are: <ul> <li> **RX:** Drug code <li> **DX:** Diagnosis code <li> **PX:** Procedure code <li> **LB:** Lab code <li> **EN:** Encounter </li> </ul> <br> **Note 1:** if CODECAT = EN it is only applicable for cohort inclusion criteria. It cannot be used for switching cohort inclusion criteria or MIL cohort inclusion criteria. <br> <br> **Format:** SAS character $2. <br> **Example:** DX| |
| 20 20 | |Code Type|CODETYPE|Type of each code value included in the CODE field (below) of this file. <br> <br> Valid values are: <br> <br> <u> If CODECAT = RX: </u> <ul> <li> **ND:** 9- or 11- digit National Drug Code (US)<li> **SN:** SNOMED CT (US) <li> **SK:** SNOMED CT (UK/CPRD) <li> **DM:** Dictionary of Medicines and Devices (UK) <li> **DI:** Drug Identification Number (CA) <li> **RN:** RXNorm (US) <li> **AT:** Anatomical Therapeutic Chemical Classification (DK) <li> **CB:** Combo </li> </ul> <br> <u> If CODECAT = DX: </u> <ul> <li> **09:** ICD\-9-CM <li> **10:** ICD\-10-CM <li> **11:** ICD\-11-CM <li> **CB:** Combo <li> **OT:** Other </li> </ul> <br> <u> If CODECAT = PX: </u> <ul> <li> **09:** ICD\-9-CM <li> **10:** ICD\-10-PCS <li> **11:** ICD\-11-CM <li> **C4:** CPT\-4 (i.e., HCPCS Level I) <li> **HC:** HCPCS (i.e., HCPCS Level II) <li> **H3:** HCPCS Level III <li> **C2:** CPT Category II <li> **C3:** CPT Category III <li>**CV:** CDC vaccine CVX codes </li><li> **ND:** 11-digit NDC <li> **RE:** Revenue <li> **LO:** Local homegrown <li> **CB:** Combo <li> **OT:** Other </li> </ul> <br> <u> If CODECAT = LB: </u> <ul> <li> **01N:** extract quantitative lab test result using Sentinel Operations Center (SOC) defined lab code (see Lab Code Lookup Table) <li> **02N:** extract quantitative lab test result using LOINC <li> **'px'N:** extract quantitative lab test result using CPT <ul> <li> **09N:** ICD\-9-CM <li> **10N:** ICD\-10-CM <li> **11N:** ICD\-11-CM <li> **C4N:** CPT\-4 (i.e., HCPCS Level I) <li> **HCN:** HCPCS (i.e., HCPCS Level II) <li> **H3N:** HCPCS Level III <li> **C2N:** CPT Category II <li> **C3N:** CPT Category III <li> **NDN:** 11-digit NDC <li> **REN:** Revenue <li> **LON:** Local homegrown </li> </ul> <li> **01C:** extract qualitative lab test result using SOC-defined lab code (see Lab Code Lookup Table) <li> **02C:** extract qualitative lab test result using LOINC <li> **'px'C:** extract qualitative lab test result using the following codes <ul> <li> **09C:** ICD\-9-CM <li> **10C:** ICD\-10-CM <li> **11C:** ICD\-11-CM <li> **C4C:** CPT\-4 (i.e., HCPCS Level I) <li> **HCC:** HCPCS (i.e., HCPCS Level II) <li> **H3C:** HCPCS Level III <li> **C2C:** CPT Category II <li> **C3C:** CPT Category III <li> **NDC:** 11-digit NDC <li> **REC:** Revenue <li> **LOC:** Local homegrown </li> </ul> </ul> <br> <u> If CODECAT = EN: </u> <ul> <li> **AD:** Assign ADate to the extracted encounter <li> **DD:** Assign DDate to the extracted encounter </li> </ul> <br> **Note 1:** as the LOINC field is not populated by all Data Partners in the SCDM Laboratory Result table and the CPT code may not be specific to a particular lab test, it is strongly recommended that the Laboratory Result table be queried using SOC-defined lab codes. <br> <br> **Note 2:** when CODETYPE = DD and DDATE is missing, DDATE is assigned the encounter ADATE. <br><br> **Note 3:** if CODECAT = EN and CODETYPE=AD, the encounter is treated as an interval with length equal to the length of stay (i.e., number of days between ADate and DDate). <br><br> **Format:** SAS character $3. <br> **Example:** 09| |
| 21 21 | |Code|CODE|Drug code, procedure, diagnosis, and/or lab code of interest. <br> <br> **Note 1:** codes are matched using exact values (i.e., 3-digit code lookup requires an exact 3-digit code match). Wildcard match (\*) functionality is also available for ICD\-9 diagnosis codes (e.g., querying `250' * '0` would be used to find any ICD\-9-CM diagnosis codes for diabetes type II, or `250**` to find ICD\-9-CM diagnosis codes for all diabetes codes in the range `250.00-250.99`). To get 'starts with' codes, the user will have to specify `250`, `250*`, `250**`. <br> <br> **Note 2:** CODETYPE/CODECAT must be consistent with the expected format of the CODE value. <br> <br> **Note 3:** duplicate CODECAT-CODETYPE-CODE-CARESETTING-PRINCIPAL combinations are removed by the Query Request Package (QRP) algorithm. <br> <br> **Note 4:** `V` and `E` ICD\-9-CM diagnosis codes must be specified using uppercase `V` and `E`. <br><br> **Note 5:** for CODECAT=EN, the user should leave this parameter blank. <br><br> **Format:** SAS character $14. <br> **Example:** (CODECAT=RX; CODETYPE=ND): 12345678911| |
| 22 22 | |Medical Product Strength|STRENGTH|A strength associated with each medical product dispensing. User may need to convert the strength value to be measured in one of the standardized units, e.g., for a medical product with strength and unit listed as 10 grams, enter STRENGTH = 10000 and UNIT = "mg". <br><br> **Note 1:** STRENGTH can be left blank. <br><br> **Note 2:** if STRENGTH is specified, SAMEDAY (in Stockpiling file) must be set to either "aa" or "xa". <br><br> **Format:** Numeric <br> **Example:** 1000| |
| 23 23 | |Medical Product Unit|UNIT|Unit with which strength is measured for each medical product dispensing. <br><br> Valid values are: <ul><li> **mg:** Mass per each (milligram) <li> **mEq:** Particles per each (milliequivalents) <li> **IU:** Standardized amount per each (international unit) <li> **mL:** Volume per each (milliliter) <li> **mg/gm:** Mass per mass (milligram per gram) <li> **mg/mL:** Mass per volume (milligram per milliliter) <li> **mg/24hr:** Mass per time (milligram per 24-hours) <li> **mEq/gm:** Particles per mass (milliequivalent per gram) <li> **mEq/mL:** Particles per volume (milliequivalent per milliliter) <li> **IU/gm:** Standardized amount per mass (international unit per gram) <li> **IU/mL:** Standardized amount per volume (international unit per milliliter) <li> **mL/mL:** Volume per volume (milliliter per milliliter) <li> **gm/100gm:** Mass per 100 mass (gram per 100 grams) <li> **gm/100mL:** Mass per 100 volume (gram per 100 milliliters) <li> **mEq/100gm:** Particles per mass (milliequivalent per 100 grams) <li> **mEq/100mL:** Particles per volume (milliequivalent per 100 milliliters) <li> **IU/100gm:** Standardized amount per mass (international unit per 100 grams) <li> **IU/100mL:** Standardized amount per volume (international unit per 100 milliliters) <li> **mL/100mL:** Volume per 100 volume (milliliter per 100 milliliters) </ul></li><br> **Note 1:** only one UNIT of strength can be specified per each unique SUBCONDLEVEL. <br><br> **Note 2:** UNIT can be left blank. <br><br> **Format:** SAS character $10 <br> **Example:** mg| |
| 24 24 | |Care Setting and Diagnosis Position Requirements|CARESETTINGPRINCIPAL|Defines the care setting and principal diagnosis position requirements for each code. This field uses combination(s) of the SCDM variables care setting (ENCTYPE) and principal discharge diagnosis flag (PDX) to restrict the observance of codes to those in the requested care settings and with the requested diagnosis position. If no restrictions are required (e.g., user wants all care settings and any value of PDX), leave the field blank. The following are valid entries; all entries must be separated by a space: <ul> <li> **IPP:** inpatient hospital stays, principal diagnoses <li> **IPS:** inpatient hospital stays, secondary diagnoses <li> **IPX:** inpatient hospital stays, unclassified diagnoses <li> **ISP:** non-acute institutional stays, principal diagnoses <li> **ISS:** non-acute institutional stays, secondary diagnoses <li> **ISX:** non-acute institutional stays, unclassified diagnoses <li> **ED\***: emergency department encounters <li> **AV\***: ambulatory visits <li> **OA\***: other ambulatory visits </li> </ul> <br> **Note 1:** the wildcard symbol (\*) can be used to represent 'any' values of either care setting or principal discharge diagnosis flag. For example, CARESETTINGPRINCIPAL = `IP*` will restrict codes to those observed in the inpatient setting irrespective of the principal diagnosis flag value. CARESETTINGPRINCIPAL = `**P` will restrict diagnosis codes to those in the principal position, irrespective of the care setting. <br> <br> **Note 2:** the principal discharge diagnosis flag is only relevant for diagnosis codes. All other codes should use the `*` wildcard for the third digit of the CARESETTINGPRINCIPAL value. <br> <br> **Note 3:** CARESETTINGPRINCIPAL is allowed to vary between CODEs within the same GROUP. For example, CARESETTINGPRINCIPAL is allowed to equal `IPP` for one diagnosis code and `IPP EDP` for another diagnosis code *in the same GROUP.* <br> <br> **Note 4:** for CODECAT=EN, this parameter cannot be left blank. <br> <br> **Format:** SAS character $30 <br> **Example:** `IPX ED* **P`| |
| 25 25 | |Condition Exclusion Indicator|CONDINCLUSION|Indicates whether each criterion specified (i.e., CONDLEVEL value) is for an inclusion (=1) or exclusion (=0) criterion. <br> <br> **Note 1:** inclusion and exclusion criteria require continuous enrollment during the CONDFROM - day 0 period (below). <br> <br> **Note 2:** within GROUP values, CONDINCLUSION = 0 and CONDINCLUSION = 1 criteria are separated by an 'and' operator. For example, in a scenario with 1) CONDLEVEL = 'Diabetes' and CONDINCLUSION=1; and 2) CONDLEVEL = 'Heart_Failure' and CONDINCLUSION=0, the program will require presence of Diabetes **and** absence of Heart Failure for a patient to be eligible for cohort entry. <br> <br> **Note 3:** within GROUP values, CONDINCLUSION = 1 and CONDINCLUSION = 1 criteria are separated by an 'or' operator. For example, in a scenario with 1) CONDLEVEL = 'Diabetes' and CONDINCLUSION=1; and 2) CONDLEVEL = 'Heart_Failure' and CONDINCLUSION=1, the program will require presence of Diabetes **or** presence of Heart Failure for a patient to be eligible for cohort entry. <br> <br> **Note 4:** within GROUP values, CONDINCLUSION = 0 and CONDINCLUSION = 0 criteria are separated by an 'or' operator within the 'not' criteria. For example, in a scenario with 1) CONDLEVEL = 'Diabetes' and CONDINCLUSION=0; and 2) CONDLEVEL = 'Heart_Failure' and CONDINCLUSION=0, the program will require fulfillment of the exclusion critiera of Diabetes **or** Heart Failure for a patient to be eligible for cohort entry. Alternatively, we can illustrate the conditional criteria as `not(Diabetes or Heart Failure)`. (Note that this is *not* the same as `not(Diabetes) or not(Heart Failure)` but is instead equivalent to `not(Diabetes) and not(Heart Failure)` via Boolean logic.)<br> <br> **Format:** Numeric <br> **Example:** 1| |
| 26 26 | |Name of Inclusion/Exclusion Condition|CONDLEVEL|User-defined name to represent a unique inclusion or exclusion criterion. <br> <br> **Note 1:** within GROUP and CONDINCLUSION values, CONDLEVEL values indicate criteria separated by an 'or' operator. For example, in a scenario with 1) CONDLEVEL = 'Diabetes' and CONDINCLUSION=1; and 2) CONDLEVEL = 'Heart_Failure' and CONDINCLUSION=1, the program will require presence of Diabetes **or** presence of Heart Failure for a patient to be eligible for cohort entry. <br> <br> **Note 2:** CONDLEVEL values must be unique within a GROUP value regardless of CONDINCLUSION values. In other words, the same CONDLEVEL name cannot be used if CONDINCLUSION=0 and CONDINCLUSION=1. <br> <br> **Format:** SAS Character $30 <br> **Example:** Diabetes| |
| 27 27 | |Name of Inclusion/Exclusion Sub-condition|SUBCONDLEVEL|User-defined name to represent unique inclusion or exclusion criteria **within CONDLEVEL values**. Allows users to define an individual inclusion/exclusion criterion (e.g., Diabetes) using a complex algorithm (e.g., diagnosis codes **and** laboratory result values). <br> <br> **Note 1:** within GROUP, CONDINCLUSION, and CONDLEVEL values, criteria specified with a different SUBCONDLEVEL value are separated by an 'and' operator. For example, in a scenario with 1) CONDLEVEL = 'Diabetes', CONDINCLUSION=1, SUBCONDLEVEL= 'diagnoses' and SUBCONDINCLUSION=1; and 2) CONDLEVEL = 'Diabetes', CONDINCLUSION=1, SUBCONDLEVEL= 'HGBA1C' and SUBCONDINCLUSION=1, the program will define Diabetes as presence of a diagnosis code indicative of diabetes **and** a HGBA1C test result indicative of Diabetes. <br> <br> **Note 2:** SUBCONDLEVEL cannot be left blank. <br><br> **Note 3:** SUBCONDLEVEL values must be unique within a GROUP value regardless of CONDINCLUSION, CONDLEVEL, or SUBCONDINCLUSION values. For example, Diabetes_DX cannot be reused as a SUBCONDLEVEL name within multiple different CONDLEVEL values within one GROUP. <br> <br> **Format:** SAS Character $30 <br> **Example:** Diabetes_DX| |
| 28 28 | |Sub-condition Exclusion Indicator|SUBCONDINCLUSION|Indicates whether each SUBCONDLEVEL criterion is for an inclusion (=1) or exclusion (=0) criterion.<br> <br> **Note 1:** exclusion criteria (SUBCONDINCLUSION=0) require continuous enrollment during the CONDFROM–CONDTO period (below). <br><br> **Format:** Numeric <br> **Example:** 1| |
| 29 - | |Evaluation Period Start|CONDFROM|Used in combination with CONDTO (below). CONDFROM defines the start of the evaluation period for each CODE value specified, expressed in terms of 'days from Index Date'. For example, if Index Date=01/08/2009 and CONDFROM for a given condition code is set to -7, the QRP algorithm will start looking for that condition code on 01/01/2009. <br> <br> **Note 1:** CODE values within a same GROUP are allowed to have different evaluation periods and therefore have different CONDFROM and CONDTO values. Unlike the COVFROM and COVTO parameters in the COVARIATECODES file, when the code is an RX code, the values for CONDFROM and CONDTO can be different within the same STOCKGROUP. <br> <br> **Note 2:** the index date is 'day zero'. Therefore, if zero is included in the CONDFROM-CONDTO interval for a given CODE value, the index date is included in the evaluation period. <br> <br> **Note 3:** if CONDFROM > 0 then the evaluation period will start after the index date. <br> <br> **Note 4: special case**: when CONDFROM = missing the program considers an inclusion/exclusion criterion met if the member has no evidence of the exposure in <u>their entire available history before the value of CONDTO</u>. In this case, for an exclusion criterion, continuous enrollment is *not required* for the duration of the evaluation period (only explicitly defined enrollment criteria, e.g., specified using the ENRDAYS (Type 1, 2, 3, 5, 6)/T4PREGENRDAYS (Type 4) value, are required).<br> <br> **Format:** Numeric <br> **Example:** -180| |
| 30 - | |Evaluation Period End|CONDTO|Used in combination with CONDFROM (above). CONDTO defines the end of the evaluation period for each CODE value specified, expressed in terms of 'days from Index Date'. For example, if Index Date=01/08/2009 and CONDTO for a given condition code is set to -1, the QRP algorithm will look for that condition code between the CONDFROM date through 01/07/2009. <br> <br> **Note 1:** CODE values within a same GROUP are allowed to have different evaluation periods and therefore have different CONDFROM and CONDTO values. Unlike the COVFROM and COVTO parameters in the COVARIATECODES file, when the code is an RX code, the values for CONDFROM and CONDTO can be different within the same STOCKGROUP. <br> <br> **Note 2:** the index date is 'day zero'. Therefore if zero is included in the CONDFROM-CONDTO interval for a given CODE value the index date is included in the evaluation period. <br> <br> **Note 3: special case** : when CONDTO = missing the program considers an inclusion/exclusion criterion met if the member has no evidence of the exposure in <u>their entire available history after the index date</u>. In this case, for an exclusion criterion, continuous enrollment is *not required* for the duration of the evaluation period (only explicitly defined enrollment criteria, e.g., specified using the ENRDAYS (Type 1, 2, 3, 5, 6)/T4PREGENRDAYS (Type 4) value, are required). <br> <br> **Format:** Numeric <br> **Example:** -1 | |
| 29 + | |Evaluation Period Start|CONDFROM|Used in combination with CONDTO (below). CONDFROM defines the start of the evaluation period for each CODE value specified, expressed in terms of 'days from Index Date'. For example, if Index Date=01/08/2009 and CONDFROM for a given condition code is set to -7, the QRP algorithm will start looking for that condition code on 01/01/2009. <br> <br> **Note 1:** CODE values within a same GROUP are allowed to have different evaluation periods and therefore have different CONDFROM and CONDTO values. Unlike the COVFROM and COVTO parameters in the COVARIATECODES file, when the code is an RX code, the values for CONDFROM and CONDTO can be different within the same STOCKGROUP. <br> <br> **Note 2:** the index date is 'day zero'. Therefore, if zero is included in the CONDFROM-CONDTO interval for a given CODE value, the index date is included in the evaluation period. <br> <br> **Note 3:** if CONDFROM > 0 then the evaluation period will start after the index date. <br> <br> **Note 4: special case**: when CONDFROM = missing the program considers a covariate met if the member has the code in their entire available history that meets coverage rewhen CONDTO = missing the program considers a covariate met if the member has the code in their entire available history that meets coverage requirements before the value of CONDTO. In this case, continuous enrollment is not required for the duration of the evaluation period (only explicitly defined enrollment criteria, e.g., specified using the ENRDAYS (Type 1, 2, 3, 5, 6)/T4PREGENRDAYS (Type 4) value, are required). However the covariate must occur during an enrollment span. Code occurring outside of enrollment spans or during those that do not meet coverage requirements will not be considered.<br> <br> **Format:** Numeric <br> **Example:** -180| |
| 30 + | |Evaluation Period End|CONDTO|Used in combination with CONDFROM (above). CONDTO defines the end of the evaluation period for each CODE value specified, expressed in terms of 'days from Index Date'. For example, if Index Date=01/08/2009 and CONDTO for a given condition code is set to -1, the QRP algorithm will look for that condition code between the CONDFROM date through 01/07/2009. <br> <br> **Note 1:** CODE values within a same GROUP are allowed to have different evaluation periods and therefore have different CONDFROM and CONDTO values. Unlike the COVFROM and COVTO parameters in the COVARIATECODES file, when the code is an RX code, the values for CONDFROM and CONDTO can be different within the same STOCKGROUP. <br> <br> **Note 2:** the index date is 'day zero'. Therefore if zero is included in the CONDFROM-CONDTO interval for a given CODE value the index date is included in the evaluation period. <br> <br> **Note 3: special case**: when CONDTO = missing the program considers a covariate met if the member has the code in their entire available history that meets coverage requirements before the value of CONDTO. In this case, continuous enrollment is not required for the duration of the evaluation period (only explicitly defined enrollment criteria, e.g., specified using the ENRDAYS (Type 1, 2, 3, 5, 6)/T4PREGENRDAYS (Type 4) value, are required). However the covariate must occur during an enrollment span. Code occurring outside of enrollment spans or during those that do not meet coverage requirements will not be considered. <br> <br> **Format:** Numeric <br> **Example:** -1 | |
| 31 31 | |Indicates the Number of Instances for the Condition|CODEDAYS|Sets the minimum number of times SUBCONDLEVEL should be found in the baseline period. <br> <br> **Note 1:** multiple codes identified on the same day will only count once (i.e., count code days not code instances). <br> <br> **Note 2:** CODEDAYS is assessed independently from MINRXDAYS. If CODECAT = RX, CODEDAYS looks for dispensing dates, while MINRXDAYS looks for days supplied. <br><br> **Note 3:** if used as an inclusion criteria, the code must appear a minimum CODEDAYS # of times for the episode to be included. <br><br> **Note 4:** if used as an exclusion criteria, the episode will only be excluded if the code appears a minimum CODEDAYS # of times. <br><br> **Format:** Numeric <br> **Example:** 1 (default)| |
| 32 32 | |Forced Supply to Attach to a Code|CODESUPPLY|Indicates, for each code listed in the file, a forced supply that should be attached to the code. The specified code supply will replace RxSup for RX codes. <br> <br> **Note 1:** only RX codes are processed via the stockpiling algorithm. <br><br> **Note 2:** if CODECAT = EN and CODESUPPLY is specified, the value of CODESUPPLY will replace the length of stay of the encounter. <br><br> **Format:** Numeric <br> **Example:** 30| |
| 33 33 | |Minimum Days Covered in Inclusion/Exclusion Window|MINRXDAYS|Sets the minimum cumulative number of days covered by dispensing to require during the evaluation period within each SUBCONDLEVEL. Counts days supplied *after* stockpiling rules have been applied. <br><br> **Note 1:** user must enter same value for all codes within same SUBCONDLEVEL. <br><br> **Note 2:** multiple dispensings identified on the same day will only count once (i.e., counting unique days with evidence of medical product). <br><br> **Note 3:** only dispensings that meet the criteria set by DATEONLY will be included in the computation of MINRXDAYS. <br><br> **Note 4:** MINRXDAYS can only be used for SUBCONDLEVEL where all CODECAT = RX. <br><br> **Note 5:** MINRXDAYS is assessed independently from CODEDAYS. If CODECAT = RX, CODEDAYS looks for dispensing dates, while MINRXDAYS looks for days supplied. <br><br> **Note 6:** if MINRXDAYS is specified as an inclusion/exclusion criterion, OUTPUTDENOM will be automatically set to N. <br><br>**Format:** Numeric <br> **Example:** 1| |
| 34 34 | |Lookback Period Date Only|DATEONLY|Indicates if lookback period to define inclusion/exclusion criteria looks for evidence of a date or evidence of an interval. <br><br> If CODECAT = RX, the interval is defined by the days supplied and the date is defined by the dispensing date. <br><br> If CODECAT = EN and CODEYPE = AD, the interval is defined by the length of stay and the date is defined by the ADate. <br><br> If CODESUPPLY is specified, the interval is defined by the value of CODESUPPLY. <br><br> Valid values are: <br> <ul> <li> **N:** Lookback period should search for evidence of a date or an interval </li> <li> **Y:** Lookback period should search for evidence of a date only </li> </ul> <br> **Note 1:** each CONDLEVEL can only be associated with one DATEONLY value. <br> <br> **Format:** SAS character $1 <br> **Example:** Y| |
| 35 35 | |Minimum Cumulative Dose|MINCUMDOSE|Specifies the minimum cumulative dose of a medication to require during the evaluation period within each SUBCONDLEVEL. Cumulative dose is calculated as STRENGTH*RxAmt (STRENGTH is user-defined in the Inclusion/Exclusion File). Dose is only evaluated for dispensing days covered that are within the evaluation window. <br><br> **Note 1:** if MINCUMDOSE is specified, CONDFROM and CONDTO cannot be left blank. <br><br> **Note 2:** if not using minimum cumulative dose as an inclusion/exclusion criteria, MINCUMDOSE must be set to missing.<br><br> **Note 3:** if CODESUPPLY is specified, MINCUMDOSE should not be specified. <br><br> **Note 4:** dose criteria can only be used to restrict COHORTGRP, and cannot be used for MILGRP or switch ANALYSISGRP exclusions. <br><br> **Format:** Numeric <br> **Example:** 500| |
| 36 36 | |Minimum Average Filled Daily Dose|MINAFDD|Specifies the minimum average filled daily dose of a medication to require during the evaluation period within each SUBCONDLEVEL. Average filled daily dose is calculated as the sum of the filled daily dose of all dispensings [(STRENGTH*RxAmt)/RxSup] in the CONDFROM-CONDTO evaluation window divided by the number of dispensings. <br><br> **Note 1:** if CODESUPPLY is specified, MINAFDD cannot be specified. <br><br> **Note 2:** if not using minimum average filled daily dose as an inclusion/exclusion criteria, MINAFDD must be set to missing. <br><br> **Note 3:** dose criteria can only be used to restrict COHORTGRP, and cannot be used for MILGRP or switch ANALYSISGRP exclusions.<br><br> **Format:** Numeric <br> **Example:** 50| |
| 37 37 | |Maximum Average Filled Daily Dose|MAXAFDD|Specifies the maximum average filled daily dose of a medication to require during the evaluation period within each SUBCONDLEVEL. Average filled daily dose is calculated as the sum of the filled daily dose of all dispensings [(STRENGTH*RxAmt)/RxSup] in the CONDFROM-CONDTO evaluation window divided by the number of dispensings. <br><br> **Note 1:** if CODESUPPLY is specified, MAXAFDD cannot be specified. <br><br> **Note 2:** if not using maximum average filled daily dose as an inclusion/exclusion criteria, MAXAFDD must be set to missing. <br><br> **Note 3:** dose criteria can only be used to restrict COHORTGRP, and cannot be used for MILGRP or switch ANALYSISGRP exclusions.<br><br> **Format:** Numeric <br> **Example:** 50| |
| 38 38 | |Minimum Current Filled Daily Dose|MINCFDD|Indicates that only dispensings greater than or equal to the minimum current filled daily dose are considered in the lookback period to define inclusion/exclusion criteria. Current filled daily dose is calculated as [(STRENGTH*RxAmt)/RxSup] per dispensing. Only dispensings meeting the specified MINCFDD criteria in the CONDFROM-CONDTO evaluation window are considered for all other inclusion/exclusion criteria. <br><br> **Note 1:** if CODESUPPLY is specified, MINCFDD cannot be specified. <br><br> **Note 2:** if not using minimum current filled daily dose as an inclusion/exclusion criteria, MINCFDD must be set to missing. <br><br>**Note 3:** dose criteria can only be used to restrict COHORTGRP, and cannot be used for MILGRP or switch ANALYSISGRP exclusions.<br><br> **Format:** Numeric <br> **Example:** 50| |
| 39 39 | |Maximum Current Filled Daily Dose|MAXCFDD|Indicates that only dispensings less than or equal to the maximum current filled daily dose are considered in the lookback period to define inclusion/exclusion criteria. Current filled daily dose is calculated as [(STRENGTH*RxAmt)/RxSup] per dispensing. Only dispensings meeting the specified MAXCFDD criteria in the CONDFROM-CONDTO evaluation window are considered for all other inclusion/exclusion criteria. <br><br> **Note 1:** if CODESUPPLY is specified, MAXCFDD cannot be specified. <br><br> **Note 2:** if not using maximum current filled daily dose as an inclusion/exclusion criteria, MAXCFDD must be set to missing. <br><br> **Note 3:** dose criteria can only be used to restrict COHORTGRP, and cannot be used for MILGRP or switch ANALYSISGRP exclusions.<br><br> **Format:** Numeric <br> **Example:** 50| |
| 40 40 | |Source Population, Mother or Infant, for which Code Applies | CODEPOP| In queries restricting Mother-Infant pregnant cohorts, population source to query for code. <br> <br> Valid values are: <br> <ul> <li> **M:** indicates should look in mother claims only. </li><li> **I:** indicates should look in infant claims only. <li> **MI:** indicates should look in mother or infant claims.</li> <li> ***blank:*** not relevant to query. </li> </ul> <br> **Note 1:** only applicable to Type 4 analyses involving an MIL cohort. If left blank, CODEPOP will default to M (mother claims only). <br><br> **Format:** SAS character $2 <br> **Example:** M| |