Commits

Andrew Simon authored 813bc7e764d
DEV-14611: Add L2comparison file
No tags

files/file0040-l2comparison.md

Added
1 +![alt text](https://dev.sentinelsystem.org/projects/AP/repos/sentinel-analytic-packages/raw/resources/logo.png?at=refs%2Fheads%2Fmaster)
2 +
3 +# Sentinel Routine Querying Reporting Tool
4 +
5 +## L2 Comparison File Parameters
6 +
7 +The L2 Comparison File file is optional. This file must be specified if creating an L2 (inferential analysis) report. This file defines the output to include in the report and model parameters.
8 +
9 +**Table 1. L2COMPARISONFILE specification**
10 +
11 +| **Parameter** | **Field Name** | **Description** |
12 +| --- | --- | --- |
13 +|Group Name for Analysis|ANALYSISGRP|Name to differentiate exposure of interest/reference pairs. <br> <br> **Note 1:** ANALYSISGRP must correspond to values of ANALYSISGRP included in distributed input files. <br><br> **Format:** SAS character $40; no special characters (e.g., commas, periods, hyphens, spaces, etc.) allowed, and underscores must be used to mark spaces. <br> **Example:** drug_a_and_drug_b|
14 +|Group Display Order|ORDER|Unique number for each ANALYSISGRP. This is used to determine the order of ANALYSISGRPs in the report. All ANALYSISGRPs should receive a unique ORDER value. ORDER values should start at 1 and be contiguous. <br><br> **Format:** Numeric <br> **Example:** 1|
15 +|RunID Corresponding to ANALYSISGRP|RUNID|RunID assigned to the run that corresponds to the specified ANALYSISGRP. <br> <br> **Format:** SAS character $5<br> **Example:** r01|
16 +|Output PS Distribution Histograms|OUTPUTPSDISTRIBUTION| Indicator specifying whether to output histograms of PS distribution between exposure and control cohorts, before and after adjustment, when applicable. <br><br> Valid values are: <ul><li> **Y:** Output PS histograms </li><li> **N:** Do not output PS histograms </ul></li> **Format:** SAS character $1<br> **Example:** Y|
17 +|Output Conditional Analysis|OUTPUTCONDITIONAL| Indicator specifying whether to output conditional analysis <br><br> Valid values are: <ul><li> **Y:** Output conditional analysis in report </li><li> **N:** Do not output conditional analysis </ul></li> **Note 1:** specification of OUTPUTCONDITIONAL is relevant only to Type 2 PS fixed ratio matching analyses (conditional analyis will be automatically output for a PS variable ratio matching, PS stratification, or covariate stratification report). **Format:** SAS character $1<br> **Example:** Y|
18 +|Output Unconditional Analysis|OUTPUTUNCONDITIONAL| Indicator specifying whether to output unconditional analysis in report. <br><br> Valid values are: <ul><li> **Y:** Output unconditional analysis </li><li> **N:** Do not output unconditional analysis </ul></li> **Note 1:** specification of OUTPUTUNCONDITIONAL is relevant only to Type 2 PS fixed ratio matching analyses (unconditional analyis will be automatically output for a Type 4 PS fixed ratio matching report)<br><br> **Format:** SAS character $1<br> **Example:** Y|
19 +|Output Forest Plot|OUTPUTFORESTPLOT| Indicator specifying whether to output forest plots in report. <br><br> Valid values are: <ul><li> **Y:** Output forest plots </li><li> **N:** Do not output forest plots </ul></li> <br> **Format:** SAS character $1<br> **Example:** Y|
20 +| Categorical Variables to Add to Covariate Model | CLASSVARS | **Details:** List of categorical variables to include in the Cox model for adjustment. Applicable when utilizing patient level data only.<br><br> **Valid values** include classification variables included in input analytic file [RUNID]\_adjusted\_[periodid].sas7bdat <br><br>**Format:** SAS character - length can vary <br>**Example:** sex |
21 +| Continuous Variables to Add to Covariate Model | NOCLASSVARS | **Details:** Additional continuous variables, separated by a space, to add to Cox model for adjustment. <br><br>**Valid values** include continuous variables included in input analytic file [runid]\_adjusted\_[periodid].sas7bdat <br><br>**Input type:** Optional <br>**Format:** SAS character - length can vary <br>**Example:** NUMIP |
22 +| Convergence Status to Consider | CONVRULE | Enter the convergence status values for considering whether the model has converged.<br><br> **Valid values are:** <ul><li> 0: Convergence satisfied </li><li> 0: Missing initial values for some parameters </li><li> 1: Quasi-complete separation </li><li> 1: Complete separation </li><li> 2: Ridging has failed to improve the likelihood </li><li> 2: Iteration limit reached without convergence </li><li> 2 or 3: Missing initial values for some of the parameters </li><li> 2 or 3: Line search has failed to improve the likelihood </li><li> 2 or 3: Improper initial values for the intercept estimates </li><li> 3: Improper initial values for estimating the model parameters</ul></li> **Note 1:** Specify multiple values via a space-separated list <br><br> **Note 2:** Valid values based on variable STATUS from dataset [runid]\_estimates\_[periodid].sas7bdat <br><br> **Note 3:** Only DPs meeting convergence status requirement will be considered for effect estimates. <br><br> **Format:** SAS character - length can vary <br> **Example:** 0,1 |
23 +| Number of HDPS variables to select from each DP | TOPNHDPS | **Details:** Enter the number of high-dimensional propensity score (HDPS) variables to select from each Data Partner.<br><br>**Format:** Numeric <br>**Example:** 10|
24 +
25 +
26 +<br>
27 +<br>
28 +________________________________________________________________
29 +
30 +
31 +<br>

Everything looks good. We'll let you know here if there's anything you should know about.

Add shortcut