change-control

Create change requests and impact assessments for validated EDC systems.

1|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/nroze22/TalosixSkills --skill change-control-nroze22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-control
Source: https://github.com/nroze22/TalosixSkills/tree/main/.claude/skills/change-control
Command: npx skills add https://github.com/nroze22/TalosixSkills --skill change-control-nroze22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured process for managing changes to validated clinical trial systems, ensuring compliance, data integrity, and minimizing disruption.

Core Features & Use Cases

  • Formal Change Request (CR) Generation: Creates detailed CR documents outlining the change, justification, and affected systems.
  • Impact Assessment: Guides users through evaluating regulatory, functional, data integrity, validation, and operational impacts.
  • Classification & Documentation: Helps classify changes (Major, Minor, Emergency) and outlines required documentation for each.
  • Approval Workflows: Defines clear approval chains for different change types.
  • Use Case: When a new feature needs to be deployed to a validated Electronic Data Capture (EDC) system, this Skill ensures all necessary impact assessments, documentation, and approvals are obtained before implementation.

Quick Start

Use the change-control skill to initiate a new change request for a system modification.

Frequently Asked Questions about change-control

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

FAQPage Schema
How do I manage change control for validated clinical trial EDC systems?

Validated clinical trial EDC system change control requires formal change requests, impact assessments across regulatory and functional domains, and defined approval workflows to maintain compliance and data integrity.

What impact assessments are needed for GCP compliant system modifications?

GCP compliant system modifications require impact assessments across regulatory, functional, data integrity, validation, and operational domains to ensure changes do not disrupt ongoing clinical trials.

How do I classify major, minor, and emergency changes to validated systems?

Classifying major, minor, and emergency changes to validated systems involves evaluating the scope of the modification and its regulatory impact to determine the required documentation and approval chain.

What documentation is required for 21 CFR Part 11 change requests?

21 CFR Part 11 change requests require documentation detailing the change justification, affected systems, comprehensive impact assessment results, and formal approval signatures based on the change classification.

When do I need to initiate a formal change request for an EDC system?

A formal change request for an EDC system is needed whenever a new feature is deployed or a modification is made to a validated clinical trial system to ensure compliance.

Can I use this change control process for emergency EDC system updates?

Yes, the change control process supports emergency changes to EDC systems by defining specific approval workflows and documentation requirements tailored for urgent validated system modifications.