9 Getting Started

This section provides users with detailed information on program setup and configuration of the master program parameters. For more information on the technical requirements for running the QA MIL Package, please refer to section 1.2: Technical Requirements.

To run this package, users must supply the following:

A Mother-Infant Linkage Table⁶ in Sentinel Common Data Model format.⁷
A computing environment which meets the Minimum Technical Specifications

9.1 Program Set-up

Clone the QA MIL Package: git clone https://dev.sentinelsystem.org/scm/qa/qa_package.git⁸
In the QA MIL Package directory, open the file sasprograms/00.0_scdm_data_qa_review_master_file.sas
1. Edit the parameters as directed by the code comments (for detailed specifications for the master program file parameters, see Table 3.1) and then save.
When distributed, the QA MIL Package should be executed in Batch mode.

9.2 Master Program Parameters

The master SAS Program found in sasprograms/00.0_scdm_mil_data_qa_review_master_file.sas contains several parameters that must be specified by the user. These include the directory containing the QA MIL Package, project, work plan, Data Partner identifiers, and a version identifier. Table 9.1 contains detailed specifications for master program parameters.

Table 9.1: List and description of parameters to be populated for program set-up
Parameter	Field Name	Description
Path name for staged MIL table	EVALUATE_MIL	Location of staged MIL table under review.
		Note 1: If multiple paths are necessary, delimit with a single space
		Format: Alphanumeric
		Example: /sentinel/etl22/phaseB
Path name for location of [Mother-Infant Identify] results	DPL_MI	Path name for location of [Mother-Infant Identify] results in Phase A dplocal folder
		Note 1: Created by the QA Program Package or a standalone Mother-Infant Identification request (mir)
		Format: Alphanumeric
		Example: /sentinel/etl22/phaseA/soc_qar_wp999_nsdp_v01/dplocal/
Mother-Infant Linkage table name	_MILTABLE	Specifies the mother-infant linkage table name. Value should exclude the .sas7bdat file name. Default values are provided.
		Format: Alphanumeric
		Example: mother_infant_linkage
Path name for Common Components	SCC	Path to directory containing executed Phase A Common Components (cca) associated with this ETL
		Note 1: Request ID should be included in path name
		Note 2: Data Partners who do not have Common Components output related to their Phase A ETL should leave this blank and populate parameters specified in Table 9.2.
		Format: Alphanumeric
		Example: /sentinel/etl22/soc_cca_wp001_xxxx_v01/
Project Identifier	PROJID	Project identifier for internal SOC identification and tracking
		Format: Alphanumeric
		Example: soc
Work Plan Type	WPTYPE	Work plan type for internal SOC identification and tracking.
		Valid Values: qmr: Used for package distributions aimed at Sentinel Distributed Database Data Partners qcm: Used for package distributions aimed at Rapid COVID Distributed Database Data Partners qmd: Used for beta test packages
		Note 1: This value is used to conditionally select the appropriate inputfiles for the distributed database type.
		Format: Alphanumeric
		Example: qmr
Workplan Identifier	WPID	Work plan identifier for internal SOC identification and tracking.
		Note 1: Should follow the format wp[###].
		Note 2: Should be used to uniquely identify packages distributed against given ETL
		Format: Alphanumeric
		Example: wp001
Data Partner Identifier	DPID	Data Partner identifier for internal SOC identification and tracking.
		Format: Alphanumeric
		Example: nsdp
Version Identifier	VERID	Version identifier for internal SOC identification and tracking. Should track each re-distribution of the package (if multiple distributions are required).
		Note 1: Should follow the format v[##].
		Format: Alphanumeric
		Example: v01
ETL Number	_ETL	ETL Number for this request.
		Note 1:: This needs to be the same ETL number for Phase A
		Format: Alphanumeric
		Example: 22

Table 9.2 contains detailed specifications for master program parameters which need to be filled out only by Data Partners who lack Common Components output.

Table 9.2: Parameters to be populated for program set-up in the absence of Common Components
Parameter	Field Name	Description
Data Partner Identifier	_DP	A descriptive identifier for the Data Partner organization.
		Note 1: This should be a 3-6 UPPERCASE character abbreviation.
		Format: Alphanumeric
		Example: NSDP
Path name for this request package’s folder	_PACKAGEROOT	Location of this request package’s root directory.
		Format: Alphanumeric
		Example: /apps/sentinel/
Path name for this ETL’s Phase A SCDM Tables	PROD_SCDM	Specify the file path to the location of this ETL’s Phase A Sentinel Common Data Model (SCDM) datasets.
		Format: Alphanumeric
		Example: /apps/sentinel/ETL22/PhaseA/SCDM
SCDM Minimum Date	_DP_MINDATE	The overall SCDM minimum date.
		Note 1: Value can be found in QA Package output.
		Note 2: Defaults to `“01Jan2000”d`
		Format: SASDate (“DDMMMYYYY”d)
		Example: “01Jan2000”d
SCDM Maximum Date	_DP_MAXDATE	The overall SCDM maximum date.
		Note 1: Value can be found in QA Package output.
		Format: SASDate (“DDMMMYYYY”d)
		Example: “31Jan2022”d
ETL Number	_ETL_	ETL number for the current Phase A production ETL.
		Format: Alphanumeric
		Example: 22
Sentinel Common Data Model Version	_SCDMVER	Parameter indicating the version of the Sentinel Common Data Model associated with this ETL.
		Format: Alphanumeric
		Example: 8.1.0
Enrollment table name	ENRTABLE	Specifies the enrollment table name. Value should exclude the .sas7bdat file name. Default values are provided.
Enrollment table name	ENRTABLE	Example: enrollment
Demographic table name	DEMTABLE	Specifies the demographic table name. Value should exclude the .sas7bdat file name. Default values are provided.
Demographic table name	DEMTABLE	Example: demographic
Dispensing Table name	DISTABLE	Specifies the dispensing table name. Value should exclude the .sas7bdat file name. Default values are provided.
Dispensing Table name	DISTABLE	Example: dispensing
Encounter Table name	ENCTABLE	Specifies the encounter table name. Value should exclude the .sas7bdat file name. Default values are provided.
Encounter Table name	ENCTABLE	Example: encounter
Diagnosis Table name	DIATABLE	Specifies the diagnosis table name. Value should exclude the .sas7bdat file name. Default values are provided.
Diagnosis Table name	DIATABLE	Example: diagnosis
Procedure Table name	PROCTABLE	Specifies the procedure table name. Value should exclude the .sas7bdat file name. Default values are provided.
Procedure Table name	PROCTABLE	Example: procedure
Facility Table name	FACTABLE	Specifies the facility table name. Value should exclude the .sas7bdat file name. Default values are provided.
Facility Table name	FACTABLE	Example: facility
Provider Table name	PVDTABLE	Specifies the provider table name. Value should exclude the .sas7bdat file name. Default values are provided.
Provider Table name	PVDTABLE	Example: provider
Lab Results Table name	LABTABLE	Specifies the Lab Results table name. Value should exclude the .sas7bdat file name.
Lab Results Table name	LABTABLE	Example: lab_results
Death Table name	DEATHTABLE	Specifies the death table name. Value should exclude the .sas7bdat file name.
Death Table name	DEATHTABLE	Example: death
Cause of Death Table name	CODTABLE	Specifies the cause of death table name. Value should exclude the .sas7bdat file name.
Provider Table name	CODTABLE	Example: cause_of_death
Vital Signs Table name	VITTABLE	Specifies the vital signs table name. Value should exclude the .sas7bdat file name.
Vital Signs Table name	VITTABLE	Example: vital_signs
Inpatient Pharmacy Table name	IPHARMTABLE	Specifies the inpatient pharmacy table name. Value should exclude the .sas7bdat file name.
Inpatient Pharmacy Table name	IPHARMTABLE	Example: ip_rx
Inpatient Transfusion Table name	ITRANSTABLE	Specifies the inpatient transfusion table name. Value should exclude the .sas7bdat file name.
Inpatient Transfusion Table name	ITRANSTABLE	Example: ip_trx
Prescribing Table name	PRETABLE	Specifies the prescribing table name. Value should exclude the .sas7bdat file name.
Prescribing Table name	PRETABLE	Example: prescribing
Patient Reported Measures Survey Table name	PRSTABLE	Specifies the patient reported measures survey table name. Value should exclude the .sas7bdat file name.
Patient Reported Measures Survey Table name	PRSTABLE	Example: prs
Patient Reported Measures Response Table name	PRRTABLE	Specifies the patient reported measures response table name. Value should exclude the .sas7bdat file name.
Patient Reported Measures Response Table name	PRRTABLE	Example: prr

All information in the Mother-Infant Linkage Table will be pulled from the Quality Assurance Program output files r01_mother_deliveries and / or r02_infants, created by a separate Mother-Infant Identification Program run as part of the core Quality Assurance Package (see Mother-Infant Identification Module). Please note that this does not include the variable MatchMethod. MatchMethod is a DP populated field that indicates the method used to match mothers and infants.↩︎
Please refer to the Sentinel Common Data Model documentation for the Mother-Infant Linkage Table specifications.↩︎
Please note that the QA MIL Package folder should correspond to the Request ID of the QA MIL Package.↩︎