Independence Statement

Our commitment: ChatCME supports independent medical education. Accredited CME providers retain full control of educational content, objectives, and evaluation. Commercial supporters receive only de-identified, aggregated analytics. They do not influence content, the chat assistant’s behavior, or access to learner-level data.

What independence means here

  • Provider control

    The accredited CME provider (or, in jointly provided activities, the accredited provider) governs content selection, learning objectives, faculty, and publication decisions. See Admin Console.

  • No promotional influence

    Ineligible companies and other supporters have no editorial input, no access to configuration, and no ability to prioritize topics, drugs, or messages.

  • Clear boundaries

    Support is acknowledged as support, not sponsorship. ChatCME enforces activity-scoped retrieval, citations to source materials, and decline behavior when evidence is insufficient.

Roles and responsibilities

Accredited CME provider

Owns content, objectives, faculty oversight, disclosures, and approvals. Uses ChatCME to ingest materials, configure guardrails, preview answers, and publish.

Explore Admin Console →

ChatCME

Provides the platform: activity-scoped retrieval, guardrailed AI, citation-first answers, audit logs, outcomes analytics, and de-identified insight reporting.

Supporters (including commercial supporters)

May receive de-identified, aggregate reports and briefs. Do not receive raw data, learner identifiers, or access to editorial tools.

See what supporters receive →

Product design choices that protect independence

Activity-scoped retrieval

Answers are grounded only in the materials of the specific accredited activity. No cross-program retrieval.

See how scoping works →

Citation-first answers

Every substantive statement includes a citation tied to a slide or timestamp. Users can verify context immediately.

See citation features →

Guardrails and decline behavior

The assistant avoids speculative or off-label recommendations and declines when evidence is insufficient or out of scope.

Source allow-lists

Retrieval is limited to provider-approved sources for each activity.

Auditability

Admin tools record configuration changes, QA decisions, and publication events with timestamps and user roles.

See Admin Console →

Data privacy and de-identification

  • No learner-level reporting to supporters

    Reports provided to supporters contain only de-identified, aggregated data. No names, emails, IP addresses, or other identifiers.

  • Small-N protections

    We suppress or roll up metrics for small cohorts to reduce re-identification risk. Minimums can be configured with the provider.

  • Tenant isolation

    Each client’s data is logically isolated. Optional dedicated databases are available for stricter separation.

  • No sale of data

    Analytics are used only to provide services to the contracting provider and, when agreed, to produce de-identified aggregates for supporters.

Commercial support acknowledgments

Use “support” language, not “sponsor/sponsorship,” consistent with CME practice.

Example acknowledgment

“This activity is supported by an independent medical education grant from [Company].”

Example jointly provided line

“Jointly provided by [Accredited Provider] and [Organization].”

Conflicts, disclosures, and learning objectives

  • Disclosures

    Faculty and planner disclosures are managed by the provider per policy. ChatCME can display provider-supplied disclosure text within the activity.

  • Objectives alignment

    Editorial tools map items, seed questions, and analytics to the activity’s learning objectives so outcomes are reported in context. See Admin Console.

  • Needs assessment

    Knowledge-gap insights derive from real questions asked within the activity. These signals are aggregated and de-identified. See what supporters receive.

What supporters receive and what they do not

Receive

  • De-identified knowledge-gap themes
  • Momentum over time
  • High-level engagement trends
  • Grant-ready briefs or CSV exports

Do not receive

  • Learner-level data
  • Raw chat transcripts
  • Access to the Admin Console
  • Control over content, prompts, or retrieval scope

Language and claims we avoid

  • We avoid implying clinical effectiveness, product preference, or brand promotion.

  • We do not claim higher-level outcomes (performance or patient outcomes) unless measured and reported per provider policy.

  • We do not present supporter-specific messaging, links, or calls to action inside learning content.

Security and compliance posture

Privacy by design

De-identification for analytics; no learner-level reporting to supporters.

Security

Encryption in transit and at rest; role-based access control; audit logs.

Security & trust details →

Compliance

HIPAA safeguards under a BAA when PHI is processed; SOC 2 aligned controls and processes.

Reporting concerns

If you believe any content or feature compromises independence, contact your program lead and our compliance team at compliance@erudio.com. We will review and, when necessary, remove or correct material promptly.

Summary

Independence is built into the product and the process. Accredited providers decide what is taught and how it is measured. ChatCME ensures answers are scoped, cited, and auditable. Supporters may view de-identified patterns, not people, and never shape the education.