Complex File Structure with Examples Sample Clauses

Complex File Structure with Examples. The PRPL file is designed to reflect the sometimes complex and dynamic relationships between people and their private insurance. It allows maximum flexibility for researchers, but it also requires that they make analytical decisions in their research. The PRPL file is a person-round-policyholder-establishment-level file. There is one unique record for each unique combination of establishment (source of private insurance), policyholder, interview round, and covered person (policyholder or dependent). Thus, the PRPL file contains at least one record for each person in each round with private health insurance, or 63,494 total records. The PRPL file contains records for persons insured through establishments providing hospital/physician, Medigap, dental, vision, or prescription medication coverage. In most cases in this file, one person in the family has insurance from his or her employer, and this insurance covers everyone in the family. In this case, there is one record for each family member in each round, and each record flags the policyholder’s current main job and links to one job record in HC-124. However, other cases are more complex, and some hypothetical examples follow. • Xxxx and Xxxxx are both employed parents, both have health insurance through their employers, and both parents choose family coverage. In this case, there are two PRPL records for each family member in each round. • Xxxx and Xxxx are both employed parents. Xxxx has single coverage from his employer. Xxxx has family coverage from her employer. In this case, Xxxx and the children each have one PRPL record for each round. Xxxx has two records for each round. • Xxxxx has Medicare and Medicare supplemental insurance. In this case, Xxxxx has one PRPL record in each round for the Medicare supplemental insurance. There is no record for Medicare, because it is public insurance. • Xxxxxx is a child living with her mother. Both have Medicaid. Xxxxxx’s father, who does not live with them, has private insurance that covers Xxxxxx. Xxxxxx has one PRPL record in each round for the private insurance. There is no record for Medicaid, because it is public insurance. • Xxxx is uninsured. In this case, Xxxx does not have any PRPL records. • Xxxx has Medicaid instead of private coverage. In this xxxx, Xxxx does not have any PRPL records. • Xxxxxx is an employed parent with family coverage through his current main job. In this case, each family member’s PRPL record flags Xxxxxx’s current main job as the...
AutoNDA by SimpleDocs

Related to Complex File Structure with Examples

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Agreement Structure This Agreement includes Part 1 - General Terms, Part 2 - Country-unique Terms (if any), the LI, and the XxX and is the complete agreement between Licensee and Lenovo regarding the use of the Program. It replaces any prior oral or written communications between Licensee and Lenovo concerning Licensee’s use of the Program. The terms of Part 2 may replace or modify those of Part 1. To the extent of any conflict, the LI prevails over both Parts.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

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