clinical-trial-schema-designer
Clinical Trial Schema Designer
Purpose and Intent
The clinical-trial-schema-designer bridges the gap between clinical research and data engineering. It helps automate the creation of standardized data structures (CDISC) based on clinical protocols, reducing the manual effort required for data ingestion and submission preparation.
When to Use
- Study Setup: Use during the "Start-up" phase of a clinical trial to design the Electronic Data Capture (EDC) schemas.
- Data Integration: When merging data from multiple sources into a single study standard.
- Submission Prep: To ensure the data structure matches FDA/PMDA requirements for SDTM/ADaM.
When NOT to Use
- Unvalidated Systems: Clinical data must be handled in GxP-validated environments. This tool generates the design, but the implementation must follow strict validation protocols.
- Medical Decision Making: This is a data structuring tool, not a clinical diagnostic or treatment tool.
Error Conditions and Edge Cases
- Ambiguous Protocols: If the input text is vague about how a variable is measured, the generated schema may be incomplete.
- Non-Standard Studies: Phase 1 or highly experimental studies may use variables that don't fit existing CDISC domains perfectly.
More from jorgealves/agent_skills
python-security-scanner
Detect common Python vulnerabilities such as SQL injection, unsafe deserialization, and hardcoded secrets. Use as part of a secure SDLC for Python projects.
191gdpr-ccpa-privacy-auditor
Audits web applications to ensure declared privacy policies match actual technical data collection practices. Use to identify discrepancies in cookie usage, tracking scripts, and user data handling.
159prompt-injection-scanner
Audits agent skill instructions and system prompts for vulnerabilities to prompt hijacking and indirect injection. Use when designing new agent skills or before deploying agents to public environments where users provide untrusted input.
157pii-sanitizer
Detects and redacts Personally Identifiable Information (PII) like emails, phone numbers, and credit cards. Use when cleaning logs, datasets, or communications to comply with GDPR/CCPA privacy standards.
135hipaa-compliance-guard
Audits HealthTech applications for HIPAA technical safeguards like encryption and audit logging. Use when reviewing healthcare infrastructure or ensuring PHI is handled according to legal security standards.
133documentation-generator
Analyzes source code to automatically generate technical documentation and architecture diagrams. Use to maintain up-to-date API references and onboarding materials for engineering teams.
131