Specified Data Elements Sample Clauses

Specified Data Elements. VA will transmit to ED a file including the name (last, middle and first), DOB, SSN, most recent Unemployability Determination Date and/or the most recent 100% Rating Determination Date for each veteran in receipt of VA disability compensation benefits based on either of these two types of VA determinations.
AutoNDA by SimpleDocs
Specified Data Elements. OPM will electronically transmit the following information: name, SSN, date of birth (DOB), civil service claim number, and amount of current gross civil service benefits. SSA will conduct the match using the individual’s SSN, name, and DOB on both the OPM file and the MDB.
Specified Data Elements. 1. The OPM input record will contain the full name, SSN, date of birth, and necessary State Verification and Exchange System (SVES) indicator, as required to extract Title II data from SSA’s MBR via SVES. 2. SSA will verify the OPM input file SSNs using the Numident database, as well as match the requested input file against SSA’s MBR. SSA will provide Title II status and associated data from the MBR to OPM via SVES.
Specified Data Elements. The DoD will provide CMS with a finder file for the Under and Over 65 Populations to match against an assigned CMS HICN or Medicare Beneficiary Identifier (MBI) which are contained within EDB. 1. Finder file for the Under and Over 65 Populations Finder file sent from DoD will contain: SSN, date of birth, sex code, first and last name. The finder file will be used for social security number matching against an assigned HICN or MBI number. 2. Reply file for the Under and Over 65 Population CMS will provide DoD with a reply file which will contain: SSN, date of birth, sex code, first name, last name, and Medicaredata.
Specified Data Elements. 1. The file OPM provides will contain the full name, SSN, date of birth, and necessary State Verification and Exchange System (SVES) indicator, as required to extract Title II data from SSA’s MBR via SVES. 2. SSA will verify the SSNs that OPM submits using the Enumeration System. If the SSN does not verify, SSA will provide a code indicating the reason for the failure. When the SSN verifies, SSA will match the SSN against the MBR. SSA will provide Title II status and associated data from the MBR to OPM via SVES. See Appendix E (SVES Record Layout) for the full list of data elements from the MBR.
Specified Data Elements. 1. The file OPM provides will contain the full name, SSN, date of birth, and necessary State Verification and Exchange System (SVES) indicator, as required to extract Title II data from SSA’s MBR via SVES. 2. SSA will verify the SSNs that OPM submits using the Enumeration System. If the SSN does not verify, SSA will provide a code indicating the reason for the failure. When the SSN verifies, SSA will match the SSN against the MBR. SSA will provide Title II status and associated data from the MBR to OPM via SVES.
Specified Data Elements. ED will transmit to SSA the name (last and first), DOB, and SSN for each borrower request. ED will send identifying information from the NSLDS database via Secure File Transfer Protocol (SFTP) using encryption that meets the requirements of Federal Information Processing Standards (FIPS) publication 140-2, “Security Requirements for Cryptographic Modules.” SSA will process the verification request and send a response to ED via SFTP using the FIPS-140-2 standards. • If SSA matches a record based on SSN, name, and DOB in the DCF and the medical data indicates MINE status, SSA will provide ED the SSN, name, DOB and a “Y” indicator. • If SSA matches a record based on SSN, name, and DOB in the DCF, but the medical data does not indicate MINE status, SSA will not return any information to ED. • If SSA matches a record based on SSN, but not on name or DOB in the DCF, SSA will return an “N” indicator to ED. • If the SSN does not match any records contained in SSA’s DCF, SSA will not return any information to ED.
AutoNDA by SimpleDocs
Specified Data Elements. VA will provide CMS with electronic file(s) in a format defined by CMS containing identifying information requil'ed to match VA records with CMS records. Data fields will include one or more of the following elements: 1. Name of Provider/Business 2. Tax Identification number (TIN) [EIN, JTIN or SSN] 3. National Provider Identifier (NPI) 4. State(s) in which the provider is providing services 5. Specialty Code or Taxonomy Code As discussed in 11. B. above, upon matching TIN or NPI, CMS will then provide VA the matched data elements above and the following additional fields:
Specified Data Elements. See Attachment 3 for the original source agency data elements used in this match.
Specified Data Elements. ED will transmit to SSA the data elements of SSN, first name, last name, and date of birth for each matching verification request. ED will send identifying information from applicant files via Secure File Transfer Protocol (SFTP) using encryption that meets the requirements of Federal Information Processing Standards (FIPS) publication 140-2, “Security Requirements for Cryptographic Modules.” SSA will process the verification request and send a response to ED via SFTP using the FIPS-140-2 standards. If SSA verifies the data and there are multiple SSNs assigned to the individual, SSA also provides up to five SSNs. SSA will provide a “match” or “no match” response and in the case of a “no match” response, the reason for the “no match.” See Attachment 2 for the EVS User Guide, which outlines the possible verification response codes and other information returned, as well as input and output file specifications.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!