Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Qualify a vendor or supplier of GxP-relevant software or services. Covers vendor risk classification, assessment questionnaire design, desk and on-site audit approaches, quality agreement evaluation, SLA review, and ongoing monitoring cadence definition. Use when selecting a new vendor for a GxP-critical system, onboarding a cloud provider for regulated data, performing a periodic re-qualification, when a vendor audit finding requires re-assessment, or when EU Annex 11 or ICH Q10 requires supplier qualification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Conduct a GxP audit of computerized systems and processes. Covers audit planning, opening meetings, evidence collection, finding classification (critical/major/minor), CAPA generation, closing meetings, report writing, and follow-up verification. Use for scheduled internal audits, supplier qualification audits, pre-inspection readiness assessments, for-cause audits triggered by deviations or data integrity concerns, or periodic compliance posture reviews of validated systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Implement electronic signatures compliant with 21 CFR Part 11 Subpart C and EU Annex 11. Covers signature manifestation (signer, date/time, meaning), signature-to-record binding, biometric vs non-biometric controls, policy creation, and user certification requirements. Use when a computerized system requires legally binding electronic signatures for GxP records, when replacing wet-ink signatures in regulated workflows, when implementing batch release or document approval workflows, or when a regulatory gap reveals missing signature controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training before go-live, an audit finding cites inadequate training, organisational changes introduce new roles, a periodic programme review is due, or inspection preparation requires demonstrating training adequacy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Perform a Computer Systems Validation (CSV) assessment following GAMP 5 methodology. Covers user requirements, risk assessment, IQ/OQ/PQ planning, traceability matrix creation, and validation summary reporting. Use when a new computerized system is being introduced in a GxP environment, when an existing validated system is undergoing significant change, when periodic revalidation is required, or when a regulatory inspection demands a validation gap analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트
Decommission a validated computerized system at end-of-life. Covers data retention assessment by regulation, data migration validation (mapping, transformation, reconciliation), archival strategy, access revocation, documentation archival, and stakeholder notification. Use when a validated system is being replaced, reaching end-of-life without replacement, vendor support is discontinued, multiple systems are consolidating, or regulatory changes render a system obsolete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pjt222/agent-almanac☆ 422026년 10월 15일 업데이트