The Input and Response File Data Layouts Sample Clauses

The Input and Response File Data Layouts. ‌ The business rules for use of the Input File immediately follow the data file layout itself. If the partner sends more than one Input File in one day, the system will process the files without terminating, or abending, the job. If the first Input File passes its edit checks, it is processed, and a Response File is sent to the partner, per current processes. If second and subsequent input files sent that day pass their edit checks, they are added to a multiple file submissions report for review by the BCRC.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
The Input and Response File Data Layouts. ‌ A – The SPAP Input File. This is the data set transmitted from an SPAP partner to CMS (the BCRC) on a monthly basis. It is used to report information regarding the SPAP enrollees – people who are eligible for and enrolled in an SPAP and receive coverage through such a plan. Full file replacement is the method used to update eligibility files. Each month’s transmitted file will fully replace the previous month’s file. The business rules for use of the SPAP Input File immediately follow the data file layout itself. Please note that the SPAP Data Sharing Agreement makes reference to the SPAP Input File as Attachment A. The layout in this version of the User Guide represents the most current version of this Attachment. If the partner sends more than one SPAP Input File in one day, the system will process the files without terminating. If the first input file passes its edit checks, it is processed, and a response file is sent to the partner, per current processes. If second and subsequent input files sent that day pass their edit checks, they are added to a multiple file submissions report for review by the BCRC.
Sample 1Sample 2Sample 3
The Input and Response File Data Layouts. A. The PAP Input File: This is the data set transmitted from a PAP partner to the COBC on a monthly basis. It is used to report information regarding PAP enrollees – individuals who are eligible for and enrolled in a PAP and receive pharmaceutical coverage through such a plan. Full file replacement is the method used to update eligibility files. Each month’s transmitted file will fully replace the previous month’s file. The business rules for use of the PAP Input File immediately follow the data file layout itself. 1. SSN 9 1-9 Numeric Social Security Number. If unavailable, fill with spaces. 2. HICN 12 10-21 Alpha-Numeric Medicare Health Insurance Claim Number (HICN). Required if SSN not provided. If unavailable, fill with spaces. 3. Surname 6 22-27 Text Surname of Covered Individual – Required. 4. First Initial 1 28-28 Text First Initial of Covered Individual – Required. 5. DOB 8 29-36 Date Date of Birth of Covered Individual – Required. CCYYMMDD 6. Sex Code 1 37-37 Numeric Sex of Covered Individual – Required. 0: Unknown 1: Male 2: Female 7. Effective Date 8 38-45 Date Effective Date of PAP Coverage – Required. CCYYMMDD 8. Termination Date* 8 46-53 Date Termination Date of PAP Coverage – Required. CCYYMMDD *Use all zeros if open-ended 9. N-Plan ID 10 54-63 Filler Future use; for National Health Plan Identifier. Fill with spaces only. 10. Rx ID/Policy Number 20 64-83 Text Populate this field with all 9s. Required.
Sample 1
The Input and Response File Data Layouts. ‌ A – The SPAP Input File. This is the data set transmitted from an SPAP partner to CMS (the BCRC) on a monthly basis. It is used to report information regarding the SPAP enrollees – people who are eligible for and enrolled in an SPAP and receive coverage through such a plan. Full file replacement is the method used to update eligibility files. Each month’s transmitted file will fully replace the previous month’s file. SPAP partners are required to continue to include coverage records for 3 years after the termination date of the coverage. The business rules for use of the SPAP Input File immediately follow the data file layout itself. Please note that the SPAP Data Sharing Agreement makes reference to the SPAP Input File as Attachment A. The layout in this version of the User guide represents the most current version of this Attachment. If the partner sends more than one SPAP Input File in one day, the system will process the files without terminating. If the first input file passes its edit checks, it is processed, and a response file is sent to the partner, per current processes. If second and subsequent input files sent that day pass their edit checks, they are added to a multiple file submissions report for review by the BCRC.
Sample 1
The Input and Response File Data Layouts. A – The MSP (Medicare Secondary Payer) Input File. This is the data set transmitted from a VDSA partner to CMS that is used to report information regarding Active Covered Individuals – people who are currently working (not carried as retired), and a spouse and (or) other dependents, and who are enrolled in and covered by an employer group health plan (GHP). At a minimum, we require the partner to include information about all Active Covered Individuals who are at least 55 years of age, and older. We have found that about ninety-seven percent of all Medicare beneficiaries are 55 and above.
Sample 1
The Input and Response File Data Layouts. A – The MSP (Medicare Secondary Payer) Input File. This is the data set transmitted from a VDSA partner to CMS that is used to report information regarding Active Covered Individuals – people who are currently working (not carried as retired), and a spouse and (or) other dependents, and who are enrolled in and covered by an employer group health plan (GHP). At a minimum, we require the partner to include information about all Active Covered Individuals who are at least 55 years of age, and older. We have found that about ninety-seven percent of all Medicare beneficiaries are 55 and above. 1. HIC Number 12 1-12 Alpha- Numeric Beneficiary’s Health Insurance Claim Number. Required if SSN not provided. Populate with spaces if unavailable. 2. Beneficiary Surname 6 13-18 Text Beneficiary’s Last Name – Required. 3. Beneficiary First Initial 1 19-19 Alpha Beneficiary’s First Initial – Required. 4. Beneficiary Date of Birth 8 20-27 Date Beneficiary’s DOB (CCYYMMDD) – Required. 5. Beneficiary Sex Code 1 28-28 Numeric Beneficiary’s Sex – Required. Valid Values: 0 = Unknown 1 = Male 2 = Female 6. DCN 15 29-43 Text Document Control Number; assigned by the VDSA partner. Mandatory. Each record shall have a unique DCN. 7. Transaction Type 1 44-44 Numeric Type of Maintenance – Required. Valid Values: ‘0’ = Add Record ‘1’ = Delete record ‘2’ = Update record 8. Coverage Type 1 45-45 Alpha- Numeric Type of Insurance – Required. Valid Values: ‘J’ = Hospital Only ‘K’ = Medical Only ‘A’ = Hospital and Medical ‘U’ = Drug Only (network Rx) ‘V’ = Drug with Major Medical Field Name Size Displacement Data Type Description (non-network Rx) ‘W’ = Comprehensive Coverage –Hosp/Med/Drug (network Rx) ‘X’ = Hospital and Drug (network Rx) ‘Y’ = Medical and Drug (network Rx) ‘Z’ = Health Reimbursement Account (non-network Rx) ‘4’ = Comprehensive Coverage –Hosp/Med/Drug (non-network Rx) ‘5’ = Hospital and Drug (non- network Rx) ‘6’ = Medical and Drug (non- network Rx) 9. Beneficiary Social Security Number 9 46-54 Numeric Beneficiary’s SSN – Required if HICN not provided. Populate with 9 spaces if unavailable. 10. Effective Date 8 55-62 Date Start Date of Covered Individual’s Primary Coverage by Insurer. (CCYYMMDD) – Required. 11. Termination Date 8 63-70 Date End Date of Covered Individual’s Primary Coverage. CCYYMMDD, Required. *Use all zeros if open-ended. 12. Relationship Code 2 71-72 Numeric Covered Individual’s Relation to Policy Holder – Required. Valid values: ‘01’ = Covered Individual ...
Sample 1
The Input and Response File Data Layouts. ‌ If the partner sends more than one PAP Input File in one day, the system will process the files without terminating, or abending, the job. If the first input file passes its edit checks, it is processed, and a response file is sent to the partner, per current processes. If second and subsequent input files sent that day pass their edit checks, they are added to a multiple file submissions report for review by the BCRC.
Sample 1
AutoNDA by SimpleDocs
The Input and Response File Data Layouts. ‌ The business rules for use of the PAP Input File immediately follow the data file layout itself. If the partner sends more than one PAP Input File in one day, the system will process the files without terminating, or abending, the job. If the first input file passes its edit checks, it is processed, and a response file is sent to the partner, per current processes. If second and subsequent input files sent that day pass their edit checks, they are added to a multiple file submissions report for review by the BCRC.
Sample 1

Related to The Input and Response File Data Layouts

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Personnel File An employee, or the President of the Union, or his/her designate, with the written authority of the employee, shall be entitled to review the employee's personnel file(s), both paper and, if applicable, electronic, in the office in which the file is normally kept, in order to facilitate the investigation of a grievance. The employee or the President, as the case may be, shall give the Employer adequate notice prior to having access to such file(s).

  • Access to Review Materials The Servicer will give the Asset Representations Reviewer access to the Review Materials for all of the Subject Receivables within sixty (60) calendar days after receipt of the review notice in one or more of the following ways in the Servicer’s reasonable discretion: (i) by electronic posting of Review Materials to a password-protected website to which the Asset Representations Reviewer has access, (ii) by providing originals or photocopies of documents relating to the Subject Receivables at one of the properties of the Servicer or (iii) in another manner agreed by the Servicer and the Asset Representations Reviewer. The Servicer may redact or remove PII from the Review Materials so long as all information in the Review Materials necessary for the Asset Representations Reviewer to complete the Asset Review remains intact and unchanged.

  • Personnel Files ‌ An employee, or his/her certified representative with the written consent of the employee, may inspect that employee's personnel file with the exception of all material obtained from other employers and agencies at the time that employee was hired. An employee shall be advised of, and entitled to read, any written statement by the employee's supervisor or departmental Management regarding his/her work performance or conduct if such statement is to be placed in his/her personnel file. The employee shall acknowledge that he/she has read such material by affixing his/her signature on the copy to be filed, with the understanding that such signature merely signifies that he/she has read the material to be filed but does not necessarily indicate agreement with its content. If the employee refuses to sign, the supervisor shall note his/her refusal on the copy to be filed along with the supervisor's signature and the signature of a witness to the employee's refusal to sign. The employee may file a grievance regarding any such document within the prescribed time limits of the grievance procedure. If the employee fails to file a grievance within the designated time limits, the document becomes part of the official file. If the employee does file a grievance within the designated time limits, said document shall not be placed in the official file nor referenced in any Performance Evaluation or Appraisal of Promotability until the grievance procedure or civil service appeal rights have been exhausted. Grievances filed under this provision shall not be subject to the Arbitration provisions of the Grievance Procedure unless they involve violation of a specific provision of this agreement. Management agrees that no properly used full paid sick leave used in the twelve months immediately prior to an Appraisal of Promotability or a Performance Evaluation will be referenced on such forms. The employee may attach his/her statement to any document within twenty (20) business days if he/she chooses not to file a grievance regarding such document or within ten (10) business days following final determination if he/she has filed a grievance regarding such document. On reviewing his/her personnel file, an employee may request and have any written warnings issued more than one year prior placed in an envelope and sealed in his/her personnel file except as such may be a part of an official permanent record. On the face of the sealed envelope it shall read "The contents herein shall be disclosed only upon written consent of the subject employee or by subpoena or other legal process from a public body of competent jurisdiction." The date the contents of the sealed envelope will be destroyed shall also appear on the face of envelope. That date shall be two (2) years from the date of issue of the documents in the sealed envelope. An employee on reviewing his/her personnel file, may request and have any written warnings or reprimand(s) issued more than two (2) years prior removed from his/her personnel file except as such may be a part of an official permanent record. All departments employing peace officers covered by the Peace Officers Bill of Rights shall comply with its provisions.

  • Access to Personnel Files All employees shall be allowed access to their personnel files during normal working hours for inspection and/or copies of documents which will be provided by the Employer. Such inspection shall be made subject to prior arrangement with the Employer.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!