SAS User File for H182 Data This file contains information and sample SAS programs to create a permanent SAS dataset for users who want to use SAS in processing the MEPS data provided in this PUF release. There are two ways to create a permanent SAS dataset, using either the SAS transport data file (H182.SSP) or the ASCII data file (H182.DAT) supplied in this PUF release. Section A provides a sample SAS program for the first alternative, which is to convert the SAS transport data file to a regular SAS dataset using the SAS PROCedure: XCOPY. Section B provides a sample SAS program for the second alternative, which is to read data from the ASCII data file using a SAS DATA step with INFILE, INPUT, and LABEL statements. Section C explains format-related SAS statements that a user may optionally use when working with the SAS dataset. Examples of SAS programs (DATA step or PROC) are provided in all three sections, primarily for the benefit of inexperienced users. Section D contains complete SAS statements that must be used in the programs described in Sections B and C. INCLUDED BELOW ARE NOTES APPLICABLE TO USERS OF SAS VERSION 8 OR HIGHER. ****************************************************************************** The sample SAS programs provided in Sections A and B show how to create a permanent SAS dataset from the data files provided in this PUF release. A. A Sample SAS Program for Converting the SAS Transport File to a Permanent SAS Dataset The SAS PROCedure XCOPY will read a SAS transport file and convert the data to regular SAS format, storing the output in a permanent SAS dataset. This permanent SAS dataset can then be used for all future processing and analyses. Below is a sample SAS program that can be used to convert the SAS transport file to a permanent SAS dataset (in a Windows environment, with SAS V8 or higher). LIBNAME PUFLIB 'C:\MEPS\SASDATA'; FILENAME IN1 'C:\MEPS\DOWNLOAD\H182.SSP'; PROC XCOPY IN=IN1 OUT=PUFLIB IMPORT; RUN; SAS transport files, SAS data files, and SAS program files each should be stored in separate locations (directory names). Storing different types of SAS files in one location can cause errors with converting or retrieving data. Below are SAS statements to print a list of variables and a few sample records from the permanent SAS dataset: PROC CONTENTS DATA=PUFLIB.H182; TITLE 'List of Variables in MEPS H182 SAS Dataset'; RUN; PROC PRINT DATA=PUFLIB.H182 (OBS=20); TITLE 'First 20 Observations in MEPS H182 SAS Dataset'; RUN; The LIBNAME statement tells SAS the location (directory name) to store the permanent SAS dataset which is output by PROC XCOPY. The FILENAME statement tells SAS the location (complete directory and file name) of the input SAS transport data file. NOTES: 1) If you have an error reading a SAS data file you created, the problem may be a result of where you are storing and/or how you are retrieving the data. First check the data library for multiple releases of SAS files (e.g., V8 or higher with file extensions of '.SAS7BDAT' and V6 with file extensions of '.SD2') stored in the same location. a) You can avoid errors when reading these files by including the SAS release within the LIBNAME statement - e.g., LIBNAME PUFLIB V8 'C:\MEPS\SASDATA'; or b) Store SAS data files with different file extensions such as .SD2 and .SAS7BDAT, in separate folders (do not co-mingle V8 and V6 files in the same folder); or c) When importing transport files, output the SAS dataset to a different library than the one which contains the downloaded SAS transport file - e.g., LIBNAME PUFLIB 'C:\MEPS\SASDATA'; FILENAME IN1 'C:\MEPS\DOWNLOAD\Hxxx.SSP'; PROC XCOPY IN=IN1 OUT=PUBLIB IMPORT; RUN; 2) The names used in the LIBNAME and FILENAME statements shown above (i.e., PUFLIB, IN1) are arbitrary; they are only temporary aliases. 3) The directory and file names used in the LIBNAME and FILENAME statements shown above are Windows syntax and may need to be modified for other operating systems such as UNIX, MAC/OS, VMS, or OS/2. 4) H182 is the internal SAS dataset name (also the PC file name, without the extension) prior to the creation of the SAS transport data file. After running PROC XCOPY, the output SAS dataset assumes the same dataset name (or file name). Hence, in the example above, a file named H182.SAS7BDAT will be created under the C:\MEPS\SASDATA directory when PROC XCOPY runs successfully. 5) The SAS transport file H182.SSP was created from a SAS V9 data file, using PROC COPY. This file has been tested for use with SAS V8 or higher. This file may work with earlier versions of SAS, although it has not been tested with those versions. Users who are unable to use this SAS transport file should instead convert the ASCII data file H182.DAT to a SAS dataset as described in Section B. B. A Sample SAS Program for Converting the ASCII Data File to a Permanent SAS Dataset The complete SAS statements (INPUT and LABEL) included in Section D are intended to save time for those users wishing to create a permanent SAS dataset from the H182.DAT ASCII data file. These statements must be used in combination with other SAS statements to create the appropriate SAS program, as shown below. To use the statements provided in Section D to create a SAS program, you will need an ASCII text editor. If you are using an interactive form of SAS (Windows, UNIX, OS2, etc.), use the editor provided as part of the SAS software. Following is a sample SAS program that will convert the ASCII data file to SAS format: LIBNAME PUFLIB 'C:\MEPS\SASDATA'; FILENAME IN1 'C:\MEPS\DOWNLOAD\H182.DAT'; DATA PUFLIB.H182; INFILE IN1 LRECL=73; INPUT .....; * to user: insert the complete INPUT statement that is provided in Section D; LABEL .....; * to user: insert the complete LABEL statement that is provided in Section D; RUN; Here is an explanation of the SAS statements used in the program above. LIBNAME statement: This tells SAS the location (directory name) of the permanent SAS dataset. FILENAME statement: This tells SAS the location of the input ASCII data file. DATA statement: This signifies the beginning of a SAS DATA step and specifies the output SAS dataset, referencing the LIBNAME entry (PUFLIB) and assigning an internal SAS dataset name (H182). In the example, after the successful completion of the DATA step, a PC file named H182.SAS7BDAT would have been created in the C:\MEPS\SASDATA directory. INFILE statement: This tells SAS the location (directory and file name) of the input ASCII data file. Also provided is the logical record length (73 bytes), with the default of RECFM=V implied when this parameter is omitted. LRECL and RECFM are optional parameters in the INFILE statement. With regard to these options, please note the following: the ASCII data file H182.DAT contains a 2-byte carriage return/line feed at the end of each record. When converting to a PC-SAS file, the LRECL option should be used to specify the record length to avoid use of a default record length by PC-SAS. If the RECFM=V option is used, the LRECL option must be specified as the logical record length (e.g., 73 for H182.DAT). If RECFM=F is used, then the LRECL value must be specified as the logical record length plus 2 (75 for H182.DAT). Note that if the RECFM option is omitted, then the default option of RECFM=V is automatically used, and LRECL should be specified as the logical record (73 for H182.DAT). INPUT statement: This specifies the input record layout, giving names and the beginning and ending column positions for data items (which become SAS variables) in the ASCII data file (H182.DAT). Variable type (numeric or character) is also defined via the INPUT statement. LABEL statement: This associates descriptive names with the SAS variables. RUN statement: This tells SAS to execute all commands up to this point. See Section A.1 above for tips on retrieving and storing the permanent SAS data files. C. Optional Format-related SAS Statements If a user wants to use formats for the SAS variables, a SAS format library must first be created. Below is a SAS program that will accomplish this: LIBNAME PUFLIB 'C:\MEPS\SASDATA'; PROC FORMAT LIBRARY=PUFLIB; VALUE .....; * to user: insert the complete set of VALUE statements found in Section D; VALUE .....; .......... ; RUN; Below is an example of how to use the SAS formats defined by the PROC FORMAT procedure: LIBNAME PUFLIB 'C:\MEPS\SASDATA'; OPTIONS FMTSEARCH=(PUFLIB); PROC FREQ DATA=PUFLIB.H182; TABLES .... / LIST MISSING; FORMAT varnam1 fmtnam1. Varnam2 fmtnam2. .... ; * to user: substitute varnam1 and fmtnam1 with actual variable names and format names; * Insert the FORMAT statement provided in Section D, if you are using all the variables in the TABLES statement; TITLE 'Frequency Distributions ....'; RUN; Here is an explanation of the SAS statements used above. LIBNAME statement: This tells SAS the location (directory name) of the SAS format library. Please note that SAS datasets (file name extension is 'SAS7BDAT' for SAS V8 or higher and 'SD2' for SAS V6) and format libraries (file name extension is 'SAS7BCAT' for SAS V8 or higher and 'SC2' for SAS V6) can be stored under the same directory. OPTIONS FMTSEARCH=...: This specifies the SAS format library. PROC FORMAT statement: This identifies the SAS procedure that will make SAS formats according to VALUE statements. Formats will be stored in a file named FORMATS.SAS7BCAT. Please note that the option 'LIBRARY=...' can be omitted if the user does not want to create a permanent SAS format library. When simply 'PROC FORMAT;' is used, the formats are defined only for the duration of the batch SAS program or an interactive SAS session. VALUE statement: This gives a) names to formats; and b) descriptive labels for individual values, or range of values. The format names can then be invoked using a FORMAT statement if desired. PROC FREQ statement: This identifies the SAS procedure that generates frequency distributions of variables specified in the TABLES statement, formatted if a FORMAT statement is used. The input SAS dataset is specified in the 'DATA=' option. FORMAT statement: This associates existing formats with variables. When using this statement, the formats must have already been created with a PROC FORMAT procedure. RUN statement: This tells SAS to execute all commands up to this point. NOTES: 1) Use of formats is entirely optional, and depends on the types of analyses that you are doing. It is recommended that you create and use them as appropriate. 2) The names used in the LIBNAME and FILENAME statements shown above (i.e., PUFLIB, IN1) are arbitrary; they are only temporary aliases. 3) You only create the permanent SAS dataset once. Additional analyses can be run using this permanent dataset. 4) The file and directory specifications in the LIBNAME and FILENAME statements are Windows syntax and may need to be modified for other operating systems such as UNIX, MAC/OS, VMS, or OS/2. D. SAS Statements This section contains SAS INPUT, LABEL, FORMAT, and VALUE statements for use in converting the ASCII H182.DAT file into a SAS dataset, and for creating SAS formats. * INPUT STATEMENTS; INFILE IN LRECL=73; INPUT @1 DUPERSID $8.0 @9 MULTSPEC 2.0 @11 MULTLOC 2.0 @13 MULTLOC2 2.0 @15 PRACTYPX 2.0 @17 NUMDOC 3.0 @20 NUMPCP 2.0 @22 NUMNPA 2.0 @24 PRACXRAY 2.0 @26 ACO 2.0 @28 CAPITATD 2.0 @30 MEDHOME 2.0 @32 PERMCAID 2.0 @34 BASESAL 2.0 @36 ROLEX 2.0 @38 POWNERX 2.0 @40 SAMEDAY 2.0 @42 PCREMIND 2.0 @44 QUALCARE 2.0 @46 CASEMGR 2.0 @48 HOSDCCHK 2.0 @50 EHREMR 2.0 @52 EHRRMIND 2.0 @54 SECMSGS 2.0 @56 MOSWT15F 13.6 @69 VARSTR 4.0 @73 VARPSU 1.0 ; * FORMAT STATEMENTS; FORMAT DUPERSID $DUPERSID. MULTSPEC MOSQ. MULTLOC MOSQ. MULTLOC2 LOCATION. PRACTYPX TYPE. NUMDOC NUMDOC. NUMPCP NUMPCP. NUMNPA NUMPA. PRACXRAY MOSQ. ACO MOSQ. CAPITATD MOSQ. MEDHOME MOSQ. PERMCAID MEDICAID. BASESAL MOSQ. ROLEX ROLE. POWNERX OWNER. SAMEDAY MOSQ. PCREMIND MOSQ. QUALCARE MOSQ. CASEMGR MOSQ. HOSDCCHK DISCHARG. EHREMR MOSQ. EHRRMIND ERH. SECMSGS ERH. MOSWT15F MOSWT15F. VARSTR VARSTR. VARPSU VARPSU. ; * LABEL STATEMENTS; LABEL DUPERSID='PERSON ID (DUID + PID)' MULTSPEC='MULTISPECIALTY GROUP PRACTICE' MULTLOC ='DOES PRACT HAVE MORE THAN 1 LOCATION' MULTLOC2='RESPONSES FOR ALL OR 1 LOC' PRACTYPX='PRACTICE DESCRIPTION' NUMDOC ='APPROX # FT + PT PHYSICIANS IN PRACTICE' NUMPCP ='APPROX # PRIM CARE PHYSICIANS IN PRACT' NUMNPA ='APPROX # NURSE PRACTNRS + PHYS ASSISTS' PRACXRAY='PRACTICE XRAY CHEST & EXTREMITIES ONSITE' ACO ='PARTICIPATE IN ACO W/MEDICRE OR PRIV INS' CAPITATD='PRACTICE HAS CAPITATED CONTRACTS' MEDHOME ='CERTIFIED PATIENT-CENTERED MEDICAL HOME' PERMCAID='PERCENT COVERED BY MEDICAID' BASESAL ='PHYSICIANS PAID BASE SALARY' ROLEX ='ROLE OF RESPONDENT IN PRACTICE' POWNERX ='PRACTICE OWNERSHIP' SAMEDAY ='PRACT SET TIME ASIDE FOR SAME-DAY APPTS' PCREMIND='SEND PREVENTIVE CARE REMINDERS TO P' QUALCARE='REPORTS TO PHYS ON CLINICAL QUAL CARE' CASEMGR ='CASE MANAGER COORDINATE PATIENT CARE' HOSDCCHK='CHECK IN W/P 48 HRS AFTER HOSP DISCHARGE' EHREMR ='PRACTICE USES EHR OR EMR' EHRRMIND='EHR/EMR REMINDERS FOR GUIDELINES/SCREEN' SECMSGS ='EHR/EMR EXCHANGE SECURE MESSAGES W/P' MOSWT15F='MOS FILE FINAL PERSON WEIGHT, 2015' VARSTR ='VARIANCE ESTIMATION STRATUM - 2015' VARPSU ='VARIANCE ESTIMATION PSU - 2015' ; * VALUE STATEMENTS; VALUE DISCHARG -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' 3 = '3 PRACT DOESNT KNOW WHEN PTS DISCHARGED' ; VALUE $DUPERSID '60011103' - '80569101' = '60011103 - 80569101' ; VALUE ERH -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE (NO EHR)' 1 = '1 YES' 2 = '2 NO' ; VALUE LOCATION -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE (SINGLE LOCATION)' 1 = '1 INCLUSIVE OF THE PRACTICE AS A WHOLE' 2 = '2 EXCLUSIVE TO THIS LOCATION' ; VALUE MEDICAID -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 LESS THAN 10 PERCENT' 2 = '2 10-50 PERCENT' 3 = '3 GREATER THAN 50 PERCENT' ; VALUE MOSQ -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE MOSWT15F 852.270203 - 392544.909654 = '852.270203 - 392544.909654' ; VALUE NUMDOC -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 0 = '0' 1 = '1' 2 - 3 = '2-3' 4 - 10 = '4-10' 11 - 50 = '11-50' 51 - 100 = '51-100' 101 - 249 = '101-249' 250 = '250+' ; VALUE NUMPA -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 0 = '0' 1 = '1' 2 - 3 = '2-3' 4 - 10 = '4-10' 11 - 49 = '11-49' 50 = '50+' ; VALUE NUMPCP -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 0 = '0' 1 = '1' 2 - 3 = '2-3' 4 - 10 = '4-10' 11 - 50 = '11-50' 51 - 79 = '51-79' 80 = '80+' ; VALUE OWNER -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 1 = '1 PHYSICIANS IN PRACTICE' 2 = '2 ANOTHER PHYSICIAN GROUP' 3 = '3 NONPROFIT/GOVT CLINIC' 4 = '4 ACADEMIC' 5 = '5 HMO' 6 = '6 INDEPENDENT PRACTICE' 7 = '7 HOSPITAL OWNED' 8 = '8 CORPORATION OWNED' 91 = '91 OTHER, PLEASE SPECIFY' ; VALUE ROLE -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 1 = '1 PRACTICE ADMINISTRATOR' 2 = '2 MEDICAL DIRECTOR' 3 = '3 PHYSICIAN' 4 = '4 OFFICE OR OTHER MANAGER' 5 = '5 OFFICE STAFF NON-MANAGERIAL' 6 = '6 NON-PHYSICIAN MEDICAL' 7 = '7 BILLING' 8 = '8 RECEPTIONIST' 91 = '91 OTHER, PLEASE SPECIFY' ; VALUE TYPE -9 = '-9 NOT ASCERTAINED' -8 = "-8 DON'T KNOW" -7 = '-7 REFUSED' 1 = '1 AN INDEPENDENT PRACTICE' 2 = '2 A PHYSICIAN NETWORK OWNED BY HOSPITAL' 3 = '3 A NONPROFIT OR GOVT CLINIC' 4 = '4 PRACT OWNED BY ACADEMIC MEDICAL CENTER' 5 = '5 AN HMO' 6 = '6 CORPORATION OWNED' 91 = '91 OTHER, PLEASE SPECIFY' ; VALUE VARPSU 1 - 3 = '1 - 3' ; VALUE VARSTR 1001 - 1165 = '1101 - 1165' ;