File Naming Convention. All files submitted to the HCCD shall have a naming convention developed to facilitate file management without requiring access to the contents. All files names will follow the template: a. Examples i. TEST_0000_201606MEv01.txt ii. PROD_0000_201606MEv02.txt • TESTorPROD – TEST for test files; PROD for production files • Reporting EntityID – This is the Reporting Entity ID assigned to each submitter • Period ending date expressed as CCYYMM (four-digit calendar year and two- digit month; for example, 201403 indicates a March 2014 end date). • File Type – Member Eligibility (ME), Medical Claims (MC), Pharmacy Claims (PC), Provider (MP), • Version number: This is used to differentiate multiple submissions of the same file. This will be important if a file needs to be resubmitted to resolve an issue such as a validation failure. The letter v should be used, followed by two digits, starting with v01. You must include the leading zero. Original submissions of all files should be labeled v01. The HCCD will not accept files that have the same name as an existing file. • File extension (.txt)
Appears in 1 contract
Sources: Data Submission and Use Agreement
File Naming Convention. All files submitted to the HCCD shall have a naming convention developed to facilitate file management without requiring access to the contents. All files names will follow the template:
a. Examples
i. TEST_0000_201606MEv01.txt
ii. PROD_0000_201606MEv02.txt • TESTorPROD – TEST for test files; PROD for production files • Reporting EntityID – This is the Reporting Entity ID assigned to each submitter • Period ending date expressed as CCYYMM (four-digit four-‐digit calendar year and two- two-‐ digit month; for example, 201403 indicates a March 2014 end date). • File Type – Member Eligibility (ME), Medical Claims (MC), Pharmacy Claims (PC), Provider (MP), • Version number: This is used to differentiate multiple submissions of the same file. This will be important if a file needs to be resubmitted to resolve an issue such as a validation failure. The letter v should be used, followed by two digits, starting with v01. You must include the leading zero. Original submissions of all files should be labeled v01. The HCCD will not accept files that have the same name as an existing file. • File extension (.txt)
Appears in 1 contract
Sources: Data Submission and Use Agreement
File Naming Convention. All files submitted to the HCCD shall have a naming convention developed to facilitate file management without requiring access to the contents. All files names will follow the template:
a. Examples
i. TEST_0000_201606MEv01.txt
TEST_0000_201606MEv01.txt ii. PROD_0000_201606MEv02.txt • TESTorPROD – TEST for test files; PROD for production files • Reporting EntityID – This is the Reporting Entity ID assigned to each submitter • Period ending date expressed as CCYYMM (four-digit calendar year and two- digit month; for example, 201403 indicates a March 2014 end date). • File Type – Member Eligibility (ME), Medical Claims (MC), Pharmacy Claims (PC), Provider (MP), • Version number: This is used to differentiate multiple submissions of the same file. This will be important if a file needs to be resubmitted to resolve an issue such as a validation failure. The letter v should be used, followed by two digits, starting with v01. You must include the leading zero. Original submissions of all files should be labeled v01. The HCCD will not accept files that have the same name as an existing file. • File extension (.txt)
Appears in 1 contract
Sources: Healthcare Claims Data Base Data Submission and Use Agreement