For chiropractic practices subject to HIPAA, technology and cybersecurity controls form part of the broader security program. The content below describes applicable technical scope and relevant boundaries — not legal, healthcare, privacy, regulatory, insurance, or compliance advice. Requirements vary based on the practice, information involved, vendors, systems, jurisdiction, and circumstances.
HIPAA Security Rule — Where Applicable
HIPAA applies to covered entities and business associates meeting the applicable legal definitions — not every chiropractic practice is automatically a covered entity. For practices subject to HIPAA, the Security Rule establishes requirements for protecting electronic protected health information through administrative, physical, and technical safeguards. Edge Secure can help implement and document applicable technology and cybersecurity safeguards supporting the practice's broader HIPAA security program. Edge Secure does not determine whether a practice is a covered entity, determine regulatory applicability, certify HIPAA compliance, or independently satisfy all HIPAA obligations.
Technology Is Only Part of the HIPAA Security Program
The HIPAA Security Rule includes administrative safeguards, physical safeguards, technical safeguards, organizational requirements, policies and procedures, and documentation requirements. Edge Secure's managed services primarily support applicable technology, cybersecurity, infrastructure, backup, recovery, and technical-control areas. Depending on the engagement, Edge Secure may also help document technology-related administrative processes. The practice remains responsible for the complete compliance program — an MSP security stack alone does not establish HIPAA compliance.
Security Risk Analysis
For regulated entities, risk analysis is foundational to the HIPAA Security Rule's security-management process. A HIPAA security risk analysis should consider potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI across the organization's environment — including systems containing ePHI, workstations, identity, networks, cloud applications, vendors, remote access, backup and recovery, and security controls. Edge Secure can help identify and document technology risks and applicable technical safeguards within the scope of an assessment or managed engagement. A routine help-desk service engagement does not automatically constitute a complete HIPAA risk analysis.
Risk Management
Identifying risks is only the beginning. Where HIPAA applies, the organization should manage identified risks using reasonable and appropriate measures based on its environment and circumstances. Edge Secure can help document technical findings, prioritize technology and security remediation, implement applicable safeguards, track applicable remediation, maintain technical evidence, and reassess technology risks as the environment changes. The practice remains responsible for broader organizational risk-management decisions and compliance oversight.
Technical Safeguards
Applicable technical-control areas may involve access control, authentication, audit controls, integrity protections, and transmission security. Edge Secure may support these areas through applicable services involving identity, MFA, access management, security logging, endpoint protection, email security, network security, encryption where applicable, monitoring, and user lifecycle management. No single product or configuration automatically satisfies a HIPAA technical safeguard requirement — controls should be evaluated in the context of the practice's environment and risk analysis.
Audit Controls & Security Logging
Different systems provide different logging capabilities. Edge Secure may manage or support identity and sign-in logs, endpoint-security logs, operating-system logs, network and security events, administrative events, backup logs, and other applicable technical monitoring. However, application-level audit capabilities depend on the application's functionality and configuration. Generic cybersecurity monitoring does not automatically replace all application audit-control requirements.
Business Associates & Business Associate Agreements
Where a vendor creates, receives, maintains, or transmits ePHI on behalf of a HIPAA covered entity or business associate in a manner that makes the vendor a business associate, an appropriate Business Associate Agreement may be required. The practice should understand which vendors access, store, process, transmit, or support systems containing ePHI. Edge Secure can help inventory technology vendors and document applicable technology relationships. Edge Secure does not determine legal business-associate status for every vendor — the practice should work with qualified legal and compliance professionals when the relationship is unclear. Having a BAA does not alone make a vendor or system appropriate or secure.
Cloud Applications & ePHI
Using a cloud application does not remove the practice's responsibility to understand how ePHI is protected. Where a cloud provider creates, receives, maintains, or transmits ePHI as a business associate, an appropriate BAA may be required. The practice should consider what information is stored, the vendor's role, access controls, authentication, security capabilities, backup and recovery, data ownership and access, integrations, and risk analysis. A platform offering a BAA is not automatically appropriate for PHI — vendor capabilities, configuration, and the practice's risk analysis all matter.
Marketing Technology & Data Boundaries
CRM and marketing platforms used for lead management, campaigns, prospective-patient communication, and marketing automation should not automatically be treated as clinical or practice-management systems. If a practice intends to place PHI or other regulated patient information into a marketing or CRM platform, it should first evaluate intended use, vendor capabilities, business-associate relationship where applicable, BAA availability and requirements, security, access, integrations, applicable privacy requirements, and risk analysis. Edge Secure does not make product-specific HIPAA compliance determinations for GoHighLevel, HubSpot, or any other marketing or CRM platform. Use the right system for the right information.
Technical Incident Response
During a cybersecurity incident, Edge Secure may perform or coordinate applicable technical actions such as investigating security alerts, containing affected managed systems, disabling compromised accounts, reviewing applicable logs, coordinating endpoint response, restoring systems and data, documenting technical events, and coordinating technology vendors. The practice and its qualified privacy, legal, and compliance professionals remain responsible for decisions involving HIPAA breach determination, patient notification, HHS and OCR notification, other regulatory notification, legal interpretation, and privacy obligations. Edge Secure does not independently make breach-notification decisions.
Cyber Insurance
Cyber insurance applications and policies may ask about controls such as MFA, endpoint protection, email security, backup, immutable and ransomware-resistant backup, security monitoring, incident response planning, privileged-access management, vulnerability management, and remote access controls. Requirements vary by carrier, policy, practice, and circumstances. Edge Secure can help implement and document applicable technical controls it manages. Edge Secure does not determine coverage, interpret policy language, guarantee underwriting approval, or guarantee claim eligibility.
Technical Controls You Can Document
Edge Secure can maintain documentation of applicable technical controls it manages. Examples may include user and account inventory, managed-device inventory, system and application inventory, MFA status on supported accounts, endpoint-security coverage, email-security configuration, vulnerability and patch status, network and security documentation, backup status, restore-validation results, recovery procedures, remote-access controls, vendor and dependency documentation, and applicable security-event documentation. For practices subject to HIPAA, these records may support portions of the organization's broader security, risk-management, documentation, and evaluation activities. Technical documentation does not automatically establish HIPAA compliance or satisfy all compliance requirements.
Responsibility Boundary
Where HIPAA applies, Edge Secure supports applicable technology and cybersecurity safeguards within the practice's broader security program. The practice remains responsible for regulatory applicability, policies, procedures, workforce requirements, privacy obligations, risk-management decisions, vendor and legal determinations, breach-notification decisions, and formal compliance.