regulatory-compliance-ux

Audit and govern regulated content mutations with e-signatures and immutable history.

1|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill regulatory-compliance-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regulatory-compliance-ux
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/regulatory-compliance-ux
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill regulatory-compliance-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regulated content mutations require auditable trails and strict governance to defend inspections.

Core Features & Use Cases

  • Enforces mandatory reason-for-change on governed actions with an auditable trail.
  • Provides immutable change history and role-based visibility for provenance.
  • Integrates e-signature flows and escalation gating for regulated sign-offs.

Quick Start

Configure the system to require an auditable reason-for-change and sign-off flow for all mutations touching regulated content.

Frequently Asked Questions about regulatory-compliance-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a reason-for-change for regulated content mutations?

To enforce a reason-for-change for regulated content, configure the system to require an auditable reason-for-change and sign-off flow for all mutations touching governed records. This ensures compliance with 21 CFR Part 11 and GxP standards by applying explicit governance prompts via the UI.

What is the best way to implement two-factor e-signatures for GxP compliance?

The best way to implement two-factor e-signatures for GxP compliance is to integrate e-signature flows and escalation gating directly into regulated sign-offs. This provides immutable change history and role-based visibility for document submissions and study records.

How do I maintain an immutable audit trail for study records and submissions?

To maintain an immutable audit trail for study records and submissions, apply governed actions to creation, editing, approvals, and change histories. This satisfies 21 CFR Part 11 requirements by ensuring provenance and role-based visibility across regulated content.

Does this approach support role-based visibility for governed actions?

Yes, this approach supports role-based visibility for governed actions. It enforces role-based access and explicit governance prompts via the UI, ensuring that only authorized users can view or mutate regulated content during audits and sign-offs.

When do I need an audit trail for document approvals and sign-offs?

You need an audit trail for document approvals and sign-offs whenever handling regulated content that must satisfy 21 CFR Part 11 or GxP requirements. It captures immutable change history, mandatory reasons for change, and two-factor e-signatures for inspection defense.