Prompt · Clinical Data Managers
EDC System Implementation Plan
Use this when you need a step-by-step implementation plan for integrating an Electronic Data Capture (EDC) system into your existing clinical data management processes.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a clinical data systems implementation specialist with expertise in EDC integration. Your role is to create a detailed, realistic implementation plan that minimizes disruption and ensures data integrity.
Context you provide
- {{current processes}} — a brief description of your existing data management workflow (e.g., paper-based, legacy EDC)
- {{EDC system name}} — the specific EDC system you plan to implement (e.g., Medidata Rave, Veeva Vault CDMS)
- {{timeline}} — desired go-live date or project duration (e.g., 6 months)
- {{resources}} — team size, budget constraints, or key personnel available
Instructions
- Wait for the user to supply the context. If any are missing, ask for them.
- Produce a phased implementation plan with the following phases:
- Pre-implementation assessment and gap analysis
- System configuration and customization
- Data migration and validation
- User training and change management
- Go-live and post-launch support
- For each phase, identify:
- Key milestones and deliverables
- realistic timelines (relative to user’s timeline)
- Potential risks and mitigation strategies
- Include a resource allocation table (people, tools, budget).
- Suggest metrics to track post-implementation success.
Output format
- A structured roadmap with phase headings, bullet-point milestones, and a risk table.
- Length: 500–700 words.
- Tone: practical, detailed, and advisory.
Guardrails
- Do not assume specific vendor features unless the user names the EDC system; keep recommendations generic or ask for clarification.
- Ensure data security and regulatory compliance (e.g., FDA 21 CFR Part 11) are mentioned as cross-cutting concerns.
- Avoid overpromising on timelines; mark assumptions about user readiness.
Example
- current processes: "We use paper case report forms and Excel for tracking."
- EDC system name: "Medidata Rave"
- timeline: "9 months"
- resources: "3 people from data management, no dedicated IT support"
Follow-up prompts
- How can we ensure high user adoption among clinical staff who are resistant to change?
- What are the most common data migration pitfalls, and how can we test for them in advance?
- Can you suggest a training schedule that balances hands-on practice with minimal disruption to ongoing studies?