SAS User File for H94B 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 (H94B.SSP) or the ASCII data file (H94B.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 data 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'; FILENAME IN1 'C:\MEPS\H94B.SSP'; PROC XCOPY IN=IN1 OUT=PUFLIB IMPORT; RUN; If the user wants a list of variables and a few sample records in the permanent SAS dataset, following are the SAS statements to accomplish these. PROC CONTENTS DATA=PUFLIB.H94B; TITLE 'List of Variables in MEPS H94B SAS Dataset'; RUN; PROC PRINT DATA=PUFLIB.H94B (OBS=20); TITLE 'First 20 Observations in MEPS H94B 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 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'; 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 data set to a different library than the one which contains the downloaded SAS Transport file - e.g., LIBNAME PUFLIB 'C:\MEPS'; FILENAME IN1 'C:DOWNLOAD\Hxx.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) H94B 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 H94B.SAS7BDAT will be created under the C:\MEPS directory when PROC XCOPY runs successfully. 5) The SAS transport file H94B.SSP was created from a PC-SAS Version 8 data file, using PROC COPY. This file has been tested for use with SAS version 8 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 H94B.DAT to a SAS data set 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 H94B.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'; FILENAME IN1 'C:\MEPS\H94B.DAT'; DATA PUFLIB.H94B; INFILE IN1 LRECL=YYYYY; 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 (H94B). In the example, after the successful completion of the DATA step, a PC file named H94B.SAS7BDAT would have been created in the C:\MEPS 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 (YYYYY 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 H94B.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., YYYYY for H94B.DAT). If RECFM=F is used, then the LRECL value must be specified as the logical record length plus 2 (XXXXX for H94B.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 (YYYYY for H94B.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 (H94B.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'; 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'; OPTIONS FMTSEARCH=(PUFLIB); PROC FREQ DATA=PUFLIB.H94B; 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') and format libraries (file name extension is 'SAS7BDAT') 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.SAS7BDAT. 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 will generate 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 type 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 data set 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 H94B.DAT file into a SAS data set, and for creating SAS formats. * INPUT STATEMENTS; INFILE IN LRECL=314; INPUT @1 DUID 5.0 @6 PID 3.0 @9 DUPERSID $8.0 @17 EVNTIDX $12.0 @29 EVENTRN 1.0 @30 FFEEIDX $12.0 @42 PANEL 2.0 @44 DVDATEYR 4.0 @48 DVDATEMM 2.0 @50 DVDATEDD 2.0 @52 GENDENT 2.0 @54 DENTHYG 2.0 @56 DENTTECH 2.0 @58 DENTSURG 2.0 @60 ORTHODNT 2.0 @62 ENDODENT 2.0 @64 PERIODNT 2.0 @66 DENTYPE 2.0 @68 EXAMINE 2.0 @70 CLENTETX 2.0 @72 CLENTETH 2.0 @74 JUSTXRYX 2.0 @76 JUSTXRAY 2.0 @78 FLUORIDE 2.0 @80 SEALANTX 2.0 @82 SEALANT 2.0 @84 FILLINGX 2.0 @86 FILLING 2.0 @88 INLAY 2.0 @90 CROWNSX 2.0 @92 CROWNS 2.0 @94 ROOTCANX 2.0 @96 ROOTCANL 2.0 @98 GUMSURGX 2.0 @100 GUMSURG 2.0 @102 RECLVISX 2.0 @104 RECLVIS 2.0 @106 EXTRACT 2.0 @108 IMPLANTX 2.0 @110 IMPLANT 2.0 @112 ABSCESS 2.0 @114 ORALSURX 2.0 @116 ORALSURG 2.0 @118 BRIDGESX 2.0 @120 BRIDGES 2.0 @122 DENTUREX 2.0 @124 DENTURES 2.0 @126 REPAIR 2.0 @128 ORTHDONX 2.0 @130 ORTHDONT 2.0 @132 WHITENX 2.0 @134 WHITEN 2.0 @136 TMDTMJ 2.0 @138 DENTPROX 2.0 @140 DENTPROC 2.0 @142 DENTOTHX $25.0 @167 DENTOTHR $25.0 @192 DENTMED 2.0 @194 FFDVTYPE 2.0 @196 FFBEF05 2.0 @198 FFTOT06 2.0 @200 DVSF05X 7.2 @207 DVMR05X 7.2 @214 DVMD05X 7.2 @221 DVPV05X 7.2 @228 DVVA05X 7.2 @235 DVTR05X 7.2 @242 DVOF05X 7.2 @249 DVSL05X 7.2 @256 DVWC05X 7.2 @263 DVOR05X 7.2 @270 DVOU05X 6.2 @276 DVOT05X 7.2 @283 DVXP05X 7.2 @290 DVTC05X 8.2 @298 IMPFLAG 1.0 @299 PERWT05F 12.6 @311 VARSTR 3.0 @314 VARPSU 1.0 ; * FORMAT STATEMENTS; FORMAT DUID DUID. PID PID. DUPERSID $DUPERS. EVNTIDX $EVNTIDX. EVENTRN EVENTRNF. FFEEIDX $FFEEIDX. PANEL PANELF. DVDATEYR DVDTEYRF. DVDATEMM DVDTEMMF. DVDATEDD DVDTEDDF. GENDENT GENDENTF. DENTHYG DENTHYGF. DENTTECH DENTTCHF. DENTSURG DENTSRGF. ORTHODNT ORTHODNF. ENDODENT ENDODENF. PERIODNT PERIODNF. DENTYPE DENTYPEF. EXAMINE EXAMINEF. CLENTETX CLENTHXF. CLENTETH CLENTTHF. JUSTXRYX JUSTXRXF. JUSTXRAY JUSTXRAF. FLUORIDE FLUORIDF. SEALANTX SEALANXF. SEALANT SEALANTF. FILLINGX FILLINXF. FILLING FILLINGF. INLAY INLAYF. CROWNSX CROWNXF. CROWNS CROWNSF. ROOTCANX ROOTCAXF. ROOTCANL ROOTCANF. GUMSURGX GUMSURXF. GUMSURG GUMSURGF. RECLVISX RECLVIXF. RECLVIS RECLVISF. EXTRACT EXTRACTF. IMPLANTX IMPLNTXF. IMPLANT IMPLANTF. ABSCESS ABSCESSF. ORALSURX ORALSRXF. ORALSURG ORALSURF. BRIDGESX BRIDGEXF. BRIDGES BRIDGESF. DENTUREX DENTURXF. DENTURES DENTUREF. REPAIR REPAIRF. ORTHDONX ORTHDNXF. ORTHDONT ORTHDONF. WHITENX WHITENXF. WHITEN WHITENF. TMDTMJ TMDTMJF. DENTPROX DENTPRXF. DENTPROC DENTPROF. DENTOTHX $DENTTXF. DENTOTHR $DENTOTF. DENTMED DENTMEDF. FFDVTYPE FFDVTYPF. FFBEF05 FFBEF05F. FFTOT06 FFTOT06F. DVSF05X DVSF05XF. DVMR05X DVMR05XF. DVMD05X DVMD05XF. DVPV05X DVPV05XF. DVVA05X DVVA05XF. DVTR05X DVTR05XF. DVOF05X DVOF05XF. DVSL05X DVSL05XF. DVWC05X DVWC05XF. DVOR05X DVOR05XF. DVOU05X DVOU05XF. DVOT05X DVOT05XF. DVXP05X DVXP05XF. DVTC05X DVTC05XF. IMPFLAG IMPFLAGF. PERWT05F PERWT05F. VARSTR VARSTRF. VARPSU VARPSUF. ; * LABEL STATEMENTS; LABEL DUID ='DWELLING UNIT ID' PID ='PERSON NUMBER' DUPERSID='PERSON ID (DUID + PID)' EVNTIDX ='EVENT ID' EVENTRN ='EVENT ROUND NUMBER' FFEEIDX ='FLAT FEE ID' PANEL ='PANEL NUMBER' DVDATEYR='EVENT DATE - YEAR' DVDATEMM='EVENT DATE - MONTH' DVDATEDD='EVENT DATE - DAY' GENDENT ='GENERAL DENTIST SEEN' DENTHYG ='DENTAL HYGIENIST SEEN' DENTTECH='DENTAL TECHNICIAN SEEN' DENTSURG='DENTAL SURGEON SEEN' ORTHODNT='ORTHODONTIST SEEN' ENDODENT='ENDODONTIST SEEN' PERIODNT='PERIODONTIST SEEN' DENTYPE ='OTHER DENTAL SPECIALIST SEEN' EXAMINE ='GENERAL EXAM OR CONSULTATION' CLENTETX='EDITED CLENTETH' CLENTETH='CLEANING, PROPHYLAXIS, OR POLISHING' JUSTXRYX='EDITED JUSTXRAY' JUSTXRAY='X-RAYS, RADIOGRAPHS OR BITEWINGS' FLUORIDE='FLUORIDE TREATMENT' SEALANTX='EDITED SEALANT' SEALANT ='SEALANT APPLICATION' FILLINGX='EDITED FILLING' FILLING ='FILLINGS' INLAY ='INLAYS' CROWNSX ='EDITED CROWNS' CROWNS ='CROWNS OR CAPS' ROOTCANX='EDITED ROOTCANL' ROOTCANL='ROOT CANAL' GUMSURGX='EDITED GUMSURG' GUMSURG ='PERIODONTAL SCALING, ROOT PLANING OR GUM' RECLVISX='EDITED RECLVIS' RECLVIS ='PERIODONTAL RECALL VISIT' EXTRACT ='EXTRACTION, TOOTH PULLED' IMPLANTX='EDITED IMPLANT' IMPLANT ='IMPLANTS' ABSCESS ='ABSCESS OR INFECTION TREATMENT' ORALSURX='EDITED ORALSURG' ORALSURG='ORAL SURGERY' BRIDGESX='EDITED BRIDGES' BRIDGES ='BRIDGES' DENTUREX='EDITED DENTURES' DENTURES='DENTURES OR PARTIAL DENTURES' REPAIR ='REPAIR OF BRIDGES/DENTURES OR RELINING' ORTHDONX='EDITED ORTHDONT' ORTHDONT='ORTHODONTIA, BRACES OR RETAINERS' WHITENX ='EDITED WHITEN' WHITEN ='BONDING, WHITENING, OR BLEACHING' TMDTMJ ='TREATMENT FOR TMD OR TMJ' DENTPROX='EDITED DENTPROC' DENTPROC='OTHER DENTAL PROCEDURES' DENTOTHX='EDITED DENTOTHR' DENTOTHR='OTHER SPECIFIED DENTAL PROCEDURES' DENTMED ='RECEIVED MEDICINE INCLUDING FREE SAMPLE' FFDVTYPE='FLAT FEE BUNDLE' FFBEF05 ='TOTAL # OF VISITS IN FF BEFORE 2005' FFTOT06 ='TOTAL # OF VISITS IN FF AFTER 2005' DVSF05X ='AMOUNT PAID, FAMILY (IMPUTED)' DVMR05X ='AMOUNT PAID, MEDICARE (IMPUTED)' DVMD05X ='AMOUNT PAID, MEDICAID (IMPUTED)' DVPV05X ='AMOUNT PAID, PRIVATE INSURANCE (IMPUTED)' DVVA05X ='AMOUNT PAID, VETERANS (IMPUTED)' DVTR05X ='HC-AMTPD, TRICARE/CHAMPVA (IMPUTED)' DVOF05X ='AMOUNT PAID, OTHER FEDERAL (IMPUTED)' DVSL05X ='AMOUNT PAID, STATE & LOCAL GOV (IMPUTED)' DVWC05X ='AMOUNT PAID, WORKERS COMP (IMPUTED)' DVOR05X ='AMOUNT PAID, OTHER PRIVATE (IMPUTED)' DVOU05X ='AMOUNT PAID, OTHER PUBLIC (IMPUTED)' DVOT05X ='AMOUNT PAID, OTHER INSURANCE (IMPUTED)' DVXP05X ='SUM OF DVSF05X-DVOT05X (IMPUTED)' DVTC05X ='HHLD REPORTED TOTAL CHARGE (IMPUTED)' IMPFLAG ='IMPUTATION STATUS' PERWT05F='EXPENDITURE FILE PERSON WEIGHT, 2005' VARSTR ='VARIANCE ESTIMATION STRATUM, 2005' VARPSU ='VARIANCE ESTIMATION PSU, 2005' ; * VALUE STATEMENTS; VALUE ABSCESSF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE BRIDGESF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE BRIDGEXF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE CLENTHXF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE CLENTTHF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE CROWNSF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE CROWNXF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE DENTHYGF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE DENTMEDF -9 = '-9 NOT ASCERTAINED' -8 = '-8 DK' -7 = '-7 REFUSED' -1 = '-1 INAPPLICABLE' 1 = '1 YES' 2 = '2 NO' ; VALUE $DENTOTF '-1' = '-1 INAPPLICABLE' '-7' = '-7 REFUSED' '-8' = '-8 DK' '-9' = '-9 NOT ASCERTAINED' '1' = '1' '17 UP TEETH PULLED TOTAL' = '17 UP TEETH PULLED TOTAL' '4 COSMETIC GOLD OVERLAYS' = '4 COSMETIC GOLD OVERLAYS' '91' = '91' 'ADJ BITE' = 'ADJ BITE' 'ADJUST FILLING' = 'ADJUST FILLING' 'ADJUST PLATE' = 'ADJUST PLATE' 'ADJUSTED BRACES' = 'ADJUSTED BRACES' 'ADJUSTED NIGHTGUARD' = 'ADJUSTED NIGHTGUARD' 'ADJUSTMENT OF BRACES' = 'ADJUSTMENT OF BRACES' 'ADJUSTMENT OF NIGHT GUARD' = 'ADJUSTMENT OF NIGHT GUARD' 'AGGRAVATED NERVE' = 'AGGRAVATED NERVE' 'AMALGAM' = 'AMALGAM' 'ANKER SORE' = 'ANKER SORE' 'ANTIBIOTIC TREATMENT' = 'ANTIBIOTIC TREATMENT' 'APICOECTOMY' = 'APICOECTOMY' 'APPLIANCE FITTING FOR JAW' = 'APPLIANCE FITTING FOR JAW' 'APPLIANCES' = 'APPLIANCES' 'APPLIED PACKING' = 'APPLIED PACKING' 'BANDAGE CHANGED' = 'BANDAGE CHANGED' 'BANDAGES CHANGED' = 'BANDAGES CHANGED' 'BIOPSY OF TONGUE' = 'BIOPSY OF TONGUE' 'BITE ADJUSTMENT' = 'BITE ADJUSTMENT' 'BLEACHING' = 'BLEACHING' 'BONE CHIP REMOVAL' = 'BONE CHIP REMOVAL' 'BONE GRAFT' = 'BONE GRAFT' 'BONE REPLACEMENT' = 'BONE REPLACEMENT' 'BONE TRANSP F/U' = 'BONE TRANSP F/U' 'BONEREPLACEMENT GRAFT' = 'BONEREPLACEMENT GRAFT' 'BRACE ADJUSTMENT' = 'BRACE ADJUSTMENT' 'BRACE ADJUSTMENTS' = 'BRACE ADJUSTMENTS' 'BRACE REMOVAL' = 'BRACE REMOVAL' 'BRACERSADJUSTMENTS' = 'BRACERSADJUSTMENTS' 'BRACES' = 'BRACES' 'BRACES ADJUSTMENT' = 'BRACES ADJUSTMENT' 'BRACES ADJUSTMENTS' = 'BRACES ADJUSTMENTS' 'BRACES BANDS REPLACED' = 'BRACES BANDS REPLACED' 'BRACES REMOVAL' = 'BRACES REMOVAL' 'BRACES TAKEN OFF' = 'BRACES TAKEN OFF' 'BRACKETS ON TEETH' = 'BRACKETS ON TEETH' 'BROKEN TEETH' = 'BROKEN TEETH' 'BROKEN TEETH-PER TOOTH' = 'BROKEN TEETH-PER TOOTH' 'BROKEN TOOTH' = 'BROKEN TOOTH' 'BROKEN TOOTH LOWER LFT' = 'BROKEN TOOTH LOWER LFT' 'BROKEN TOOTH PREPARATION' = 'BROKEN TOOTH PREPARATION' 'BROKEN TOOTH REPAIRED' = 'BROKEN TOOTH REPAIRED' 'BUBBLE ON GUMS' = 'BUBBLE ON GUMS' 'BUILT TOOTH UP' = 'BUILT TOOTH UP' 'CALL FOR APPT.' = 'CALL FOR APPT.' 'CALL FOR RX' = 'CALL FOR RX' 'CALLED TO ORDER BLEACH' = 'CALLED TO ORDER BLEACH' 'CAP' = 'CAP' 'CAP FELL OFF' = 'CAP FELL OFF' 'CARE OF JAW FLAREUP-TMD' = 'CARE OF JAW FLAREUP-TMD' 'CAVITY' = 'CAVITY' 'CEMENT CROWN' = 'CEMENT CROWN' 'CHANGED FILLING