Common use of Conventions for Describing Data Values Clause in Contracts

Conventions for Describing Data Values. ‌ The following table describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table describes Table 3-11 defines the data types used by the BCRC for its their external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within the PAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layoutslayout fields. Table 3-711: Data Type Key Key. Data Types Used by BCRC for Their External Interfaces (Inbound and Outbound) Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-0 to 9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 “ Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ XX299Y” Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Populate with spaces Internal Use Populate with spaces -Populate with spaces

Conventions for Describing Data Values. ‌ The following table describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP ADAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP SPAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table below describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards Formatting Standards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layout fieldsLayouts. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within the PAP SPAP Data Exchange Layout fields. Table 3-7: Data Type Key These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type// Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ ” Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 ” Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ XX299Y” Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards standards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ “000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. e.g., “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table below describes the data types used by the BCRC COBC for its external interfaces (inbound and outbound). The formatting atandards Formatting Standards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layout fieldsLayouts. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Type / Field Formatting Standard Examples Numeric Zero through 9 (0-0 🡪 9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Alpha- Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘„) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” 34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -Above standards should be used unless otherwise noted in layouts

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC COBC for its their external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within in the PAP Data Exchange Layout layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Type / Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Alpha- Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 “ Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘„) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” 34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces The above standards apply unless otherwise noted in layouts. VDSA Processing: CMS System Requirements Existing VDSA (Voluntary Data Sharing Agreement) Requirements that apply to the new MSP and Non-MSP files have been modified to assure that data from all VDSA partners is processed consistently. The System shall be able to receive an external file from a VDSA partner. The System shall be able to confirm the external VDSA partner file format. The System shall be able to match the valid VDSA partner external file to the Eligibility Database. The System shall be able to update a CMS record based on differences found between a valid VDSA partner external file and the Eligibility Database. The System shall display error descriptions in CHAPS for severe errors identified on BCBS and VDSA files.

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its their external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within the PAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layoutslayout fields. Table 3-711: Data Type Key Key. Data Types Used by BCRC for Their External Interfaces (Inbound and Outbound) Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-0 to 9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 “ Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ XX299Y” Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Populate with spaces Internal Use Populate with spaces -Populate with spaces

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its their external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within in the PAP Data Exchange Layout layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-718: Data Type Key (Data Type/Types Used by BCRC External Interfaces (inbound and Outbound) Data Type / Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 “ Data Type / Field Formatting Standard Examples Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: • Comma (,) • Ampersand (&) • Space ( ) • Dash (-) • Period (.) • Single quote (‘) • Colon (:) • Semicolon (;) • Number (#) • Forward slash (/) • At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” 34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Populate with spaces Internal Use Populate with spaces Populate with spaces NOTE: The above standards apply unless otherwise noted in layouts VDSA Processing: CMS System Requirements Existing VDSA (Voluntary Data Sharing Agreement) Requirements that apply to the new MSP and Non-MSP files have been modified to assure that data from all VDSA partners is processed consistently. • The System shall be able to receive an external file from a VDSA partner. The System shall be able to confirm the external VDSA partner file format. • The System shall be able to match the valid VDSA partner external file to the Eligibility Database. • The System shall be able to update a CMS MSP record based on differences found between a valid VDSA partner external file and the Eligibility Database. • The System shall be able to create an MSP transaction file from the VDSA partner MSP record and the Beneficiary Master Record. • The System shall display error descriptions in CHAPS for severe errors identified on BCBS and VDSA files.

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within the PAP SPAP Data Exchange Layout fields. Table 3-7: SPAP Data Type Key These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type// Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ ” Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 ” Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ XX299Y” Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its their external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within in the PAP Data Exchange Layout layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-711: Data Type Key Key. Data Types used by BCRC for their External Interfaces (Inbound and Outbound) Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 “ Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” 34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Populate with spaces Internal Use Populate with spaces Populate with spaces VDSA Processing: CMS System Requirements Existing VDSA (Voluntary Data Sharing Agreement) Requirements that apply to the new MSP and Non-MSP files have been modified to assure that data from all VDSA partners is processed consistently. • The System shall be able to receive an external file from a VDSA partner. The System shall be able to confirm the external VDSA partner file format. • The System shall be able to match the valid VDSA partner external file to the Eligibility Database. • The System shall be able to update a CMS record based on differences found between a valid VDSA partner external file and the Eligibility Database. • The System shall display error descriptions in CHAPS for severe errors identified on BCBS and VDSA files.

Conventions for Describing Data Values. ‌ The following table describes below defines the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with standard defined for each data type correspond corresponds to the requirements of data type identified for each field within the interface layout. This key is provided to augment assist in understanding the rules prescribing behind the formatting of the data values that are provided within the PAP SPAP Data Exchange Layout fields. Table 3-7: Data Type Key These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type// Field Formatting Standard Examples Numeric Zero through 9 (0-0  9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ ” Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " MM221 ” Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ XX299Y” Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” 34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -