Skip to main content
AnnouncementLaunching an AI Powered Portal for Our Clients to stay updated about their Agency.
CognitiveHC · Website Policies

HIPAA Compliance

Information handling, engagement scope and the agreements to discuss before agency records are shared.

What this page covers

This page explains considerations for information handling in an agency support engagement. It is not a HIPAA certification, a security assessment, a signed Business Associate Agreement or a guarantee that every workflow meets all applicable requirements.

The responsibilities that apply depend on the services performed, the information involved and the relevant laws and agreements.

Understanding protected information

Whether information is protected health information depends on the information, the context in which it is held and the organization’s role under the HIPAA Rules. Removing one obvious identifier does not by itself establish that a record is safe to share through a public form.

For an initial business discussion, describe the operational issue without identifying a patient. For example, you can explain that authorization dates and visit dates need reconciliation without supplying names, member numbers, medical records or screenshots containing identifiers.

A fictional or general workflow example can support discovery without turning a public enquiry into a transfer of agency records.

Business Associate Agreements

HHS explains that an organization providing certain services involving protected health information on behalf of a covered entity may be a business associate. Where applicable, a written Business Associate Agreement addresses permitted uses, disclosures and required protections.

The actual engagement determines whether such an arrangement is required. Read the HHS business-associate guidance. This website page does not replace the required agreement.

Before records or system access are shared

Discuss the intended service, the information needed, who would have access, the systems and transfer routes involved, and any required agreements before sharing agency records or credentials.

Access to an agency’s EHR, EVV, billing system or files should be defined through the engagement and applicable information-handling arrangements. A general enquiry, discovery call or website login does not by itself authorize access or data sharing.

Minimum necessary and defined access

HHS describes a minimum-necessary standard for certain uses, disclosures and requests for protected health information, with exceptions and context-specific requirements. The HHS minimum-necessary guidance explains its scope.

In a service discussion, identify what information each task requires, which person or role needs access and which actions remain with the agency. Do not assume that broad access is appropriate simply because a person can sign in to a system. The applicable rules and agreements determine the requirements for the actual work.

Safeguards and service-specific review

The HIPAA Security Rule addresses administrative, physical and technical safeguards for electronic protected health information where the Rule applies. The HHS Security Rule summary explains the framework.

For a proposed engagement, discuss the safeguards and responsibilities relevant to its scope, including access permissions, workforce roles, devices, vendors, incident handling, retention and termination. This page does not establish that a particular control, assessment, training program or certification has been completed.

Practical information-handling questions

Before an engagement involves protected information, the parties should discuss the workflow and the responsibilities that need to be documented. Useful questions include:

  • Which records and systems are needed for the agreed tasks?
  • Who approves access, reviews exceptions and authorizes the next action?
  • Which channels are appropriate for transferring information?
  • How are questions or suspected information-handling issues escalated?
  • What happens to access and records when a role or engagement changes?
  • Which vendor or subcontractor arrangements are relevant?

These are scoping questions, not a representation that a specific assessment, procedure or technical safeguard has already been completed.

Vendors, systems and subcontractors

Providers or subcontractors that would handle protected health information need an applicability, access and agreement review appropriate to the actual work. A website form, scheduling service or general business tool is not automatically an approved route for agency PHI.

Public forms are for business enquiries

Do not submit patient names, medical records, member identifiers, passwords or other sensitive records through the public enquiry form or a discovery-call description. Begin with a general description of the workflow you want to discuss.

Contact our policy contact about information-handling questions or concerns without attaching sensitive records in the initial message. Discuss the appropriate reporting or transfer route separately.

Raising an information-handling concern

Contact the named policy contact if you have a question or concern about information handling connected with a CognitiveHC business discussion or engagement. Start with a general description, the business contact route involved and when you noticed the issue. Do not include affected patient records or credentials in the initial message.

Discuss an appropriate route for any further details. Applicable reporting duties, responsibilities and time requirements depend on the actual event, the organization’s role, the governing law and the relevant agreements; this webpage does not replace those obligations.

Agency responsibilities and individual requests

Agencies retain their clinical, professional, legal and payer responsibilities. A support engagement or checklist does not remove those responsibilities or guarantee compliance or payer approval.

Individuals seeking access to or changes in their medical records should contact the relevant healthcare provider or agency. CognitiveHC’s role and any related obligations depend on its actual services and agreements. Our Privacy Policy addresses public website enquiries and usage information.

Contact and operator

Cognitive Healthcare Consulting, LLC.
7900 International Drive
Bloomington, MN 55425

Policy contact: Shyam Sundar S
Email: SSanders@CognitiveHC.Com
Phone: +1 (651) 273-6170

Please describe your question without attaching patient records, passwords or other sensitive information.