FinchipAIOrg Skill: Draft Comprehensive Compliance Training Manual Under Corporate Integrity Agreement
1. Subject-matter triage
- Treat the source set as potentially inconsistent and write the manual as the controlling synthesis, not a compilation.
- Identify whether the manual must cover employees, contractors, or both; if the source set is silent or inconsistent, state the broader scope and explain why.
- Separate mandatory enterprise-wide content from role-specific modules for sales, medical, compliance, finance, and operations functions.
- If the source set contains multiple effective dates, training deadlines, reporting lines, or policy versions, list them explicitly before selecting the controlling version.
2. Failure modes the skill is correcting
- Source-document errors are imported into the manual instead of being flagged and reconciled.
- Cross-document conflicts are left unresolved, especially where one document narrows a duty another document expands.
- Whistleblower protection is reduced to hotline language without an express anti-retaliation rule and consequences.
- False Claims Act content is collapsed into generic fraud training without a separate qui tam and retaliation module.
- Foreign anti-corruption obligations are omitted for healthcare-professional interactions involving public systems or government affiliation.
- Government pricing content is misstated, oversimplified, or detached from the reporting method and data governance it requires.
- Contractor coverage is omitted or treated as optional.
- Role-based training is flattened into one generic module, creating under-inclusive instruction for higher-risk functions.
- Committee independence requirements are diluted by allowing commercial personnel to participate in oversight roles.
- Monitoring, auditing, and reporting obligations are described abstractly instead of as operational duties with accountability.
3. Legal frameworks / domain conventions that apply
- Corporate integrity agreement training manuals typically require initial and recurring training, document retention discipline, escalation pathways, and board-level oversight of compliance effectiveness.
- Whistleblower and anti-retaliation content should be anchored in the False Claims Act, including the qui tam mechanism and retaliation protections under 31 U.S.C. §§ 3729–3733 and 3730(h), plus any analogous internal-policy protections in the source documents.
- Anti-kickback and interaction rules should be framed around the federal Anti-Kickback Statute, 42 U.S.C. § 1320a-7b(b), and any applicable safe-harbor concepts identified in the source set.
- Foreign anti-corruption obligations should be grounded in the Foreign Corrupt Practices Act, 15 U.S.C. §§ 78dd-1 et seq., and should treat public-sector healthcare professionals as potentially covered officials where the source set supports that view.
- Government pricing content should reflect the pricing-reporting regime identified in the source set, including Medicaid and average-selling-price concepts where applicable, using the methodology stated in the source documents and correcting internal inconsistencies.
- Training for grants, educational support, or sponsorship decisions should require independence from commercial influence when the source set imposes that constraint.
- Independent review, audit, or monitoring obligations should be described as part of the compliance system, including what the reviewer examines, what employees must provide, and how findings escalate.
- Any legal rule stated in the manual should be tied to a named authority, regulation, or cited policy source; avoid unsupported generalizations.
- When source documents conflict with each other, the manual should identify the conflict, state the controlling rule chosen for the manual, and note the operational reason for the resolution.
4. Analytical scaffolds
Read the source documents as a hierarchy.
- Identify controlling agreement language, then implementing policies, then training artifacts.
- Use the hierarchy to resolve inconsistent definitions, thresholds, deadlines, and reporting duties.
Build the manual around modules, not a narrative summary.
- Start with enterprise-wide principles, then role-based modules, then testing and certification.
- Each module should include purpose, conduct rules, examples, escalation steps, and confirmation of understanding.
Resolve cross-document conflicts explicitly.
- For each conflict, state the competing formulations, the chosen rule for the manual, and the reason for choosing it.
- Where necessary, note that the manual follows the more conservative or more operationally workable rule.
Draft the whistleblower and retaliation section as a standalone compliance topic.
- Cover reporting channels, confidentiality, non-retaliation, supervisor obligations, investigation cooperation, and consequences for retaliation.
- Distinguish reporting from the anti-retaliation rule and from the duty to cooperate with investigations.
Draft the false-claims section separately from retaliation.
- Explain prohibited billing, documentation, and certification failures.
- Explain qui tam exposure, internal reporting, and preservation of evidence.
Draft anti-corruption, pricing, and commercial-interaction rules with operational specificity.
- Address gifts, hospitality, travel, sponsorships, documentation, approvals, and interactions with public-sector healthcare professionals.
- For pricing, state who gathers data, who validates it, what gets reported, and how discrepancies are escalated.
Tailor by role and responsibility.
- Sales, medical affairs, finance, compliance, managers, and contractors should not receive identical content where their risk exposure differs.
- Add manager-specific escalation and reporting duties where the source documents assign them.
Include training governance.
- State who administers training, how completion is tracked, when refreshers occur, how exceptions are approved, and how noncompletion is handled.
- Include retention of acknowledgments, attendance records, and testing results if the source set requires them.
5. Vertical / structural / temporal relationships
- If the source set includes multiple entities, business units, jurisdictions, or document versions, map how the manual applies across them before drafting module text.
- If there are sequential compliance obligations, present them in time order: onboarding, periodic refresher, event-driven retraining, escalation, investigation, remediation.
- If one policy depends on another document, state the dependency in the manual and explain which rule governs in a conflict.
- If committee approval, compliance review, or board reporting occurs on a cycle, anchor the manual to that cycle rather than restating duties as free-floating obligations.
6. Output structure conventions
- Produce a comprehensive training manual in conventional manual form, with a short executive overview followed by clearly labeled modules.
- Include a section that identifies cross-document inconsistencies and explains how the manual resolves each one.
- Use a practical manual style: learning objectives, core rules, examples, reporting steps, and acknowledgment/testing checkpoints.
- Make the scope explicit at the outset, including that the manual applies to contractors if the source documents require or reasonably support that coverage.
- Include role-differentiated sections for higher-risk functions and separate modules for whistleblower protection, anti-retaliation, false claims, anti-corruption, and pricing compliance.
- End with implementation guidance for training administration, completion tracking, escalation, and certification.
- If the source set contains multiple operative provisions touching the same topic, include the chosen rule in the body of the manual and note the discarded or subordinated variant in the inconsistency section.