Part of the data protection rule states that subcontractor trading partners must “accept the same restrictions and conditions as those that apply to the counterparty with respect to that information.” www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.htmlsearchsecurity.techtarget.com/definition/business-associatewww.mwe.com/en/thought-leadership/publications/2013/02/new-hipaa-regulations-affect-business-associates__www.hhs.gov/hipaa/for-professionals/covered-entities/sample-business-associate-agreement-provisions/index.html Things became much more confusing than the hipaa hitech omnibus rule in 2013, the simpler definition of counterparty to so-called a subcontractor. Subcontractors, such as a software developer or host, are typically service or technology organizations that provide additional services to partners that provide services to covered businesses. (h) to the extent that the counterparty must meet one or more obligations of the insured business in accordance with Part E of 45 CFR Part 164, the Part E requirements that apply to the entity covered in the performance of those obligations; and Direct employees do not need to sign a BAA. This is because the people who work for you are part of your organization and are not considered business partners. Yet they are still covered by HIPAA laws. As agents, you are responsible for training them in data protection and security. This applies not only to your regular full-time employees, but also to apprentices, temporary workers, volunteers and everyone else who is under your direct control. Does a contractor have to comply with any provision of your BAA? The data protection rule seems to say so. The rule is that all counterparties accept restrictions identical to those of the counterparty. There are exceptions to this definition, however (see 45 CFR 160.103) and the extent of the relationship between a covered business and a creditor may change over time. The counterparty agreement guarantees the use of a retention chain for PIS. A seller of a business covered by HIPAA must enter into a contract with the covered company and a subcontractor used by a counterparty is also required to enter into a contract of this type. A subcontractor is a consideration for consideration and is not covered by the ba/covered enterprise contract.

A separate contract must be signed before access to PHI is granted. The chain can be longer and further away from the covered entity that transmits the ePHI, the greater the potential for violations of the HIPAA business association agreement. BAAs must be signed by all covered entities when their trading partner processes PHI, which first passes through the covered entity. There is a list of the features covered below. More information can be found on the HHS.gov page on hipaa Covered Entities. “BAA” is an acronym for the Business Associate Agreement, a branch concept for what HIPAA rules call a “Business Associate Contract.” Same thing. General provision. The data protection rule requires that a covered entity receive satisfactory assurances from its counterparty that the counterparty adequately protects the protected health information it receives or creates on behalf of the entity concerned.

Satisfactory assurances must be made in writing, either in the form of a contract or other agreement between the covered entity and the counterparty. Covered companies may be fined for not entering into a HIPAA counterparty agreement or for entering into an incomplete agreement – while HITECH 78 FR 5574 AAS are required to comply with the HIPAA safety rule, even if no HIPAA counterparty agreement is reached.