Common use of Conventions for Describing Data Values Clause in Contracts

Conventions for Describing Data Values. The table below defines the data types used by BCRC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Numeric Zero through 9 (0  9) Padded with leading zeroes Numeric (5): “12345” Numeric (5): “00045” 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): “MM221 “ Text 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): “▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇” Text (12): “ ▇▇▇-▇▇▇-▇▇▇▇” 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 • 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 table below defines the data types used by BCRC COBC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Numeric Zero through 9 (0  9) Padded with leading zeroes Numeric (5): “12345” Numeric (5): “00045” 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): “MM221 “ Text 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): “▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇” Text (12): “ ▇▇▇-▇▇▇-▇▇▇▇” 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 • The above standards apply unless otherwise noted in layouts. 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.