On this page
- Why "HIPAA-compliant" is not a certification
- The business associate agreement: your first non-negotiable
- Technical safeguards to verify
- Encryption at rest and in transit
- Access controls and role-based permissions
- Audit logs
- Automatic session timeouts
- Administrative safeguards: what the vendor's own house looks like
- Data residency and subprocessors
- Certifications that add credibility
- What healthcare-specific LMS platforms handle differently
- Evaluating compliance claims during a demo
- Pricing structures and hidden compliance costs
- Red flags that should stop a procurement
- Frequently asked questions
- Before you sign
Choosing a learning management system for a healthcare organization requires a review of the actual information, purpose and service relationships. Employee records and clinical competency data are not automatically protected health information (PHI). When services for a covered entity involve PHI, applicable HIPAA safeguards and business-associate contractual duties must be assessed before use; a healthcare label alone establishes neither applicability nor compliance.
Here's exactly what to look for, what questions to ask, and where healthcare organizations most often get caught out during procurement.
Why "HIPAA-compliant" is not a certification
There is no official HIPAA certification body. Any vendor can call their platform HIPAA-compliant—and many do—without any third-party verification. What HIPAA actually requires is that covered entities and their business associates implement specific safeguards and maintain documentation proving they've done so.
For an LMS, this matters because the platform may store or transmit:
- Employer-held employment and training records, which are excluded from HIPAA protection in that capacity; records held about an employee as a patient are different
- Competency scenarios, which may or may not contain identifiable patient health information
- Continuing education and credential data, which are not automatically PHI
- Patient information used in course content, whose status depends on its content and context; HIPAA de-identification requires Expert Determination or Safe Harbor, not just removing names
Properly de-identified information is not PHI. A vendor performing relevant services for a covered entity involving PHI may be a business associate, including a cloud provider maintaining encrypted ePHI without the key. Have counsel or the privacy lead classify the data flows and determine required BAAs and subprocessor obligations before using the platform for PHI.
The business associate agreement: your first non-negotiable
First determine whether the proposed services and data flows require a Business Associate Agreement. If they do, ask the vendor whether it will execute the required BAA for that scope before PHI is handled.
A BAA sets required contractual assurances for a business associate's handling of PHI. Failing to obtain a required BAA can violate HIPAA, but responsibility and liability depend on the parties' duties, conduct and applicable law; absence of a BAA does not by itself place all breach liability on one party.
A solid BAA should include:
- A clear description of the permitted uses of PHI
- A business associate's duty to notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 days after discovery, subject to applicable exceptions; review any stricter contractual or state-law duties
- Required contractual assurances for subcontractors whose relevant services involve PHI, rather than an assumption that every third-party service has the same HIPAA role
- Terms for returning or destroying PHI when the contract ends
- Acknowledgment that the vendor will support your compliance audits
If a vendor hesitates, adds conditions, or only offers a BAA on their most expensive tier, that tells you something about how seriously they take compliance overall.
Technical safeguards to verify
The HIPAA Security Rule imposes risk-based duties on covered entities and business associates handling ePHI. Addressable implementation specifications are not optional: assess and implement them when reasonable and appropriate, or document a reasonable and appropriate alternative. The following are procurement questions, not a universal mandate for particular algorithms or protocols and not a statement of Perceptors' available controls.
Encryption at rest and in transit
Ask the vendor to document encryption at rest, in transit and in backups for the proposed deployment, including algorithms and versions such as AES-256 and TLS 1.2 or higher where appropriate to your requirements. These are examples to assess, not universally prescribed HIPAA algorithms or proof that a platform supplies them.
Access controls and role-based permissions
The platform should support granular role-based access control, so a department manager can view their team's completion records without being able to access another department's data. Single sign-on integration with your existing identity provider (SAML 2.0 or OIDC) reduces credential-based breach risk and simplifies offboarding when staff leave.
Audit logs
The Security Rule requires audit controls to record and examine activity in systems containing or using ePHI. Assess the events, integrity protections, exports and retention needed for your intended use; learner completions and every access event are not automatically subject to identical requirements. The six-year rule for required Security Rule documentation runs from creation or last effective date, whichever is later, and is not a universal retention period for every learner record or access log.
Automatic session timeouts
A learner who walks away from a shared workstation shouldn't leave sensitive training data exposed. Configurable session timeouts are a basic control—and one that many platforms overlook or bury in settings.
Administrative safeguards: what the vendor's own house looks like
Technical controls only go so far. HIPAA's administrative safeguards require that vendors also manage their internal operations responsibly.
Ask vendors:
- Do employees who access customer data receive HIPAA training?
- Do you conduct regular risk assessments of your own infrastructure?
- What does your incident response plan look like, and how quickly do you notify customers of a breach?
- Have you ever experienced a reportable breach? If so, what happened and what changed?
A vendor who can't answer these questions clearly—or deflects them—hasn't built compliance into their culture. That matters more than any feature list.
Data residency and subprocessors
Cloud-hosted platforms almost always rely on subprocessors: third-party services for storage, email delivery, analytics, or video hosting. Each one that touches your data is a potential liability.
Ask for the subprocessor list and classify each service's role and PHI access. Relevant PHI-handling subcontractors require HIPAA contractual assurances; a generic data protection agreement is not automatically a substitute. Have counsel assess any additional state-law and cross-border duties rather than assuming data residency alone satisfies them.
For organizations with international staff or learners, clarify whether data ever leaves the country and under what legal framework cross-border transfers are handled.
Certifications that add credibility
While HIPAA has no official certification, several third-party frameworks provide meaningful assurance that a vendor takes security seriously.
SOC 2 Type II examines controls' operating effectiveness over the period specified in the report. The reviewed AICPA FAQ does not establish a universal six-month minimum. Confirm the actual report period, scope, exceptions and relevance with the auditor and vendor, and request appropriate due-diligence access. No Perceptors SOC 2 report is established here.
ISO 27001 is an international information security management standard. Its presence suggests the vendor has built systematic security practices rather than reacting to incidents after the fact.
HITRUST CSF is designed specifically for healthcare and maps directly to HIPAA requirements. Not all vendors pursue it—it's expensive and time-consuming—but its presence is a strong signal for organizations with high compliance requirements.
SOC 2, ISO 27001 and HITRUST are distinct from HIPAA obligations and educational certification. None establishes HIPAA suitability by itself, replaces a required BAA or removes your responsibility for deployment-specific due diligence.
What healthcare-specific LMS platforms handle differently
A general-purpose LMS can be configured to meet many HIPAA requirements, but platforms built for healthcare tend to handle several things better by default.
Clinical content often involves scenarios, assessments, and competency frameworks that general platforms simply weren't designed to support. Healthcare-specific platforms typically include assessment tools calibrated for clinical knowledge—structured around evidence-based guidelines rather than generic quiz formats.
They also tend to handle credentialing and continuing education tracking more cleanly, which matters when you need to demonstrate staff competency to accreditation bodies or during a regulatory audit.
Perceptors is built specifically for clinical teams and healthcare organizations. The platform uses AI agents to turn your existing course materials and subject-matter expertise into structured, learner-ready programs with built-in assessment and an evidence-grounded AI tutor. Courses are certified through the Geneva College of Longevity Science, and the platform runs entirely in the browser—no infrastructure for your IT team to manage.
Perceptors supports HIPAA, SOC 2 and HITRUST requirements as needed, scoped with each institution during discovery. Perceptors does not replace your clinical, academic, or compliance governance. See the current trust and governance statement.
Evaluating compliance claims during a demo
When you reach the demo stage, don't let the vendor control the entire conversation. Bring your compliance and IT teams, and ask to see specific things rather than accepting a polished walkthrough.
Ask to see:
- The audit log for a test user's session
- How a breach would be reported to your organization
- Where session timeouts and access roles are configured
- The BAA template before any contract discussion begins
- The most recent SOC 2 Type II report or equivalent
If the vendor can't demonstrate these things in a live environment—or promises to "send documentation later"—that's a gap worth taking seriously.
Pricing structures and hidden compliance costs
Some LMS vendors price compliance features separately. A basic tier might include the platform but not the BAA, audit logging, or SSO integration. When comparing costs across vendors, factor in what's actually included at each tier.
Perceptors uses per-learner pricing with no hidden infrastructure or upgrade fees. Specific rates aren't publicly listed, so organizations looking for a detailed quote should request a briefing directly. That kind of transparent pricing structure is worth asking about with any vendor—compliance features gated behind higher tiers can add up quickly across a large clinical workforce.
The pricing description does not establish that a BAA, encryption, SSO, audit logging, security reports or other HIPAA safeguards are available or included. Verify the institution-specific scope against the trust and governance statement.
Red flags that should stop a procurement
A few patterns should give you pause regardless of how strong the demo looked.
A BAA with carve-outs. Some vendors will sign a BAA but exclude certain data types or features. Read the agreement carefully and have legal review it before signing.
Breach notification terms needing legal review. For a breach of unsecured PHI, a business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery, subject to applicable exceptions. Counsel should assess the whole agreement, including any stricter duties; wording such as "reasonable time" does not alone establish that the contract fails.
No documented subprocessor list. If the vendor can't tell you who else touches your data, you can't complete your own risk assessment.
Compliance features gated behind enterprise tiers. If audit logs or SSO require an upgrade, ask whether the vendor has genuinely built compliance into their platform—or bolted it on as a premium add-on.
Insufficient audit evidence. Report-sharing restrictions may exist. Ask what appropriate due-diligence access or alternative evidence is available and assess its adequacy; refusal alone does not establish a motive.
Frequently asked questions
Does every LMS need to be HIPAA-compliant if it's used by a healthcare organization?
No. Healthcare use, staff credentials and training records do not automatically make data PHI or a vendor a business associate. Employer-held employment records are excluded in that capacity; records held about an employee as a patient are different. Properly HIPAA-de-identified information is not PHI. Relevant services for a covered entity involving PHI can create business-associate duties, including required contractual assurances. Have counsel classify the actual data flows; no verified industry-default prevalence is established here.
What's the difference between a BAA and a data processing agreement?
A BAA is specific to HIPAA and governs how a business associate handles protected health information. A data processing agreement (DPA) is typically used under GDPR or similar privacy frameworks and covers personal data more broadly. Healthcare organizations operating internationally may need both.
Can a cloud-hosted LMS be HIPAA-compliant?
Perceptors supports HIPAA, SOC 2 and HITRUST requirements as needed, scoped with each institution during discovery.
How often should we re-verify a vendor's compliance status?
At minimum, review compliance documentation annually or whenever the vendor announces significant changes to their infrastructure or subprocessors. Request an updated SOC 2 report each year and confirm your BAA still reflects the vendor's current service scope.
What happens if our LMS vendor has a breach?
For a breach of unsecured PHI, a business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery. A covered entity must notify affected individuals without unreasonable delay and no later than 60 days after discovery. For breaches affecting 500 or more individuals, HHS notification is without unreasonable delay and subject to the 60-day limit; for fewer than 500, it is due no later than 60 days after the end of the calendar year in which the breach was discovered. Media notice applies when more than 500 residents of a state or jurisdiction are affected, without unreasonable delay and no later than 60 days after discovery. Counsel must review discovery and agency rules, applicable exceptions including lawful law-enforcement delay, state law and any stricter contractual duties.
Is HIPAA compliance the same as HITECH compliance?
HITECH strengthened and expanded HIPAA obligations, including breach notification and business-associate duties. Do not treat a platform's general HIPAA statement as proof that every applicable obligation is satisfied; counsel should review the intended use, agreements and duties.
Do we need to audit the LMS vendor ourselves, or is their SOC 2 report sufficient?
A SOC 2 Type II report can inform due diligence, but its usefulness depends on its scope, period and findings. It does not establish HIPAA suitability or replace your risk assessment. Review deployment-specific obligations and any gaps in the evidence with the appropriate security and privacy reviewers.
Before you sign
A HIPAA-compliant LMS isn't something you can identify by a badge on a vendor's website. It's the result of specific contractual protections, documented technical controls, and a vendor culture that treats compliance as a baseline rather than a premium feature.
Start with intended-use and data-flow classification. Obtain any required BAA before PHI is handled, verify applicable safeguards and subprocessor assurances, and assess relevant audit evidence. Resolve legal and security gaps with your reviewers before procurement; this checklist does not establish that Perceptors supplies these controls or accepts PHI.
For clinical teams and healthcare organizations looking for a platform purpose-built for this environment, Perceptors is worth a closer look.
Perceptors supports HIPAA, SOC 2 and HITRUST requirements as needed, scoped with each institution during discovery. Perceptors does not replace your clinical, academic, or compliance governance. See the current trust and governance statement.
Sources and further reading
These are the links included in the supplied article. Company descriptions and source links do not independently verify every claim.

