蒲公英 - 制药技术的传播者 GMP理论的实践者

搜索
查看: 5402|回复: 18
收起左侧

[石头968] 【每日一问】定义“计划变更、非计划变更、临时变更”的意义是什么?

[复制链接]
药师
发表于 2014-3-17 16:19:12 | 显示全部楼层 |阅读模式

欢迎您注册蒲公英

您需要 登录 才可以下载或查看,没有帐号?立即注册

x
看到某群在讨论一个问题:
计划变更、非计划变更、临时变更?
这三个有什么不同,我真的稀里糊涂,我认为根本没必要这么分,区分的意义是什么呢?嫌GMP管理不够复杂,是吧?显得自己内功深厚,是吧?
还有人把偏差分为:计划偏差、非计划偏差、临时偏差?
不知道都从哪里弄来的这些个超意识流的名词,搞得我这个非质量管理的人一头雾水。
真的无语……
谁能解释一下,这样区分是为什么呢?为了更好地实施GMP吗?

回复

使用道具 举报

大师
发表于 2014-3-17 16:21:06 | 显示全部楼层
我听过“计划偏差”,其实就是个小变更呗。都是砖家的噱头。。
回复

使用道具 举报

药徒
发表于 2014-3-17 16:37:21 | 显示全部楼层
我就认得变更

其他的都是投机取巧的产物,体现出日常管理的随意性。
回复

使用道具 举报

药生
发表于 2014-3-17 16:44:26 | 显示全部楼层
我在考虑要不要把某园关于这个讨论帖的连接给贴过来
回复

使用道具 举报

药师
 楼主| 发表于 2014-3-17 17:15:24 | 显示全部楼层
liver98 发表于 2014-3-17 16:44
我在考虑要不要把某园关于这个讨论帖的连接给贴过来

可以直接粘贴文字,如果确实讨论的比较精彩,文字又多不便于复制,也可以复制链接,蒲公英还是开放的吧
回复

使用道具 举报

药徒
发表于 2014-3-17 17:31:08 | 显示全部楼层
坐等专家分析。。。
回复

使用道具 举报

药生
发表于 2014-3-17 20:00:01 | 显示全部楼层
忘了帖子的名字了,使用召回大招了 @zhulikou431 以前在丁香园有个讨论到计划性偏差和非计划性偏差的,能不能找的到
回复

使用道具 举报

药师
 楼主| 发表于 2014-3-17 20:43:01 | 显示全部楼层
liver98 发表于 2014-3-17 20:00
忘了帖子的名字了,使用召回大招了 @zhulikou431 以前在丁香园有个讨论到计划性偏差和非计划性偏差的,能不 ...

搜索一下
回复

使用道具 举报

药徒
发表于 2014-4-9 20:37:31 | 显示全部楼层
{:soso_e120:}变更是计划性的;偏差是非计划性的
回复

使用道具 举报

药徒
发表于 2014-4-10 15:48:12 | 显示全部楼层
变更,偏差是必须的,临时变更,计划偏差是管理的细化,有助于对变更和偏差的管理,实施与否不影响GMP符合性。根据自己企业的实际情况确定是否实施。
回复

使用道具 举报

发表于 2014-4-11 15:43:22 | 显示全部楼层
我只听说过有计划的属于变更,没有计划的属于偏差!变更都是有计划的!
从没听说过计划变更、非计划变更、临时变更!
回复

使用道具 举报

药士
发表于 2016-6-9 13:56:59 | 显示全部楼层
东方文明 发表于 2014-4-10 15:48
变更,偏差是必须的,临时变更,计划偏差是管理的细化,有助于对变更和偏差的管理,实施与否不影响GMP符合 ...

按照这篇文章中说道的http://www.pharmtech.com/regulat ... a-change-management,应该没有计划偏差的概念,计划偏差(比如预期停电)应该属于变更,或者叫做临时变更的说法。偏差的都是非预期的,同时都是事后评价,而针对于变更都是预期的,事前进行评价。
所以个人觉得应该没有非计划变更,计划偏差、临时偏差(偏差能让他就存么??肯定是临时性的)的概念,应该有临时变更,永久变更的概念。
但是又有一个问题,
case1:针对于某些设备的改造,需要进行变更申请,但是由于这是一次比较重大的改造,我需要对设备进行change trail(就是对设备进行相对比较小的改造用于测试),以作为该次变更申请与否判定,那么对于这个前期局部的改造是按照什么管理呢(测试后需要恢复原来的验证状态)??是按照临时变更管理吗???
case2:如果前期的change trail就是该次变更申请的改造(即:测试所涉及的改造就相当于本次变更的全部内容),如果后期change trail测试成功,那么是否是该临时变更总结变成永久变更。那么是否是针对于任意一次变更,都是从临时变更发起(应为你不会100%保证变更的成功),当变更最终确认成功后再转为永久变更???如果不成功,临时变更终结,然后回到原来状态。@愚公想改行

Regulation and Compliance Q&A: Change ManagementQ&A with Peter Smith, Strategic Compliance Consulting, PAREXEL International, and a former senior official with FDA, on change management best practices.

Jun 02, 2012

By Pharmaceutical Technology Editors
Pharmaceutical Technology
Volume 36, Issue 6



Q. Can you offer any best practices for change management?


Peter Smith
A. I have dealt with change management for many years at various pharmaceutical companies and I have seldom found a program that is fully compliant and that works effectively and efficiently. Based on my experience and input from other PAREXEL consultants, among the most common problems are impact assessments and documentation of the change, as described below.
Impact assessment: In many cases, proposed changes are not properly and thoroughly assessed for risk. Appropriate departments should always evaluate changes to determine their potential impact on a validated process, critical equipment, and product quality, as well as the potential regulatory impact.

Documentation of the change: When a change is being considered, the topic is often widely and frequently discussed, and is clearly understood among the site staff. When it comes to the documentation, the scope of the change, rationale, and justification for the change, as well as other details, little is written since "everyone knows what is going on." Then, when a third party (read: FDA Investigator) reviews the documentation package, it lacks details, which gives the impression that the evaluation or risk assessment is inadequate or incomplete. The documentation package should tell the complete story such that the third party can reach the same conclusion without provoking many questions.


Zone in on: Regulation
Below are a few additional best practices for running an effective and efficient change-control management program.
Do not use "planned deviations."Many companies use the erroneous concept of "planned deviations," which are not deviations at all, but rather, changes. These changes are often temporary and handled within the deviation management system or similar program. Deviations are unexpected events wherein some control is lost and the product quality impact of the event must be evaluated retrospectively. No one wants to "plan to deviate" and deviations raise a red flag to regulators.
Changes on the other hand, are planned events where the potential impact is evaluated prospectively. This holds true even for a temporary change where the change is for one batch–the potential impact of the change on that one batch must be evaluated prior to the change being implemented, even if immediately before the batch is to be manufactured. Therefore, changes that are referred to as "planned deviations" should be managed under a change-control program, which should provide for emergency and temporary changes.
Avoid unauthorized changes. Individuals sometimes implement a change outside of the change control mechanism. Such changes may be well-intentioned "good ideas," but nonetheless are unauthorized and undocumented. A common example of an unauthorized, "good-idea" change may occur with respect to modification when "like-for-like" parts are not available and a repair is made with a nonequivalent part. In other cases, some change-control processes may be so cumbersome that changes cannot be approved on short notice. Implementing a change prior to a full evaluation and approval, however, constitutes an unauthorized change.
Limit the number of change management SOPs. Many companies have an excessive number of SOPs that relate to changes. Sometimes, each department has its own change control procedure or each topic (e.g., processes, analytical methods, facilities, equipment, materials, documents, computer systems) is managed under a separate SOP. These situations cause confusion, inconsistencies, overlap, and gaps. One company had 27 SOPs that addressed changes in one way or another, such that it was unclear where to even begin the change process.
Watch for cumulative changes. Companies must consider that multiple individual changes categorized as "minor" on their own merit may have a cumulative effect on product quality and the impact of multiple changes should be evaluated.
Follow-up and closure. Companies often fail to follow-up after a change to verify that it was implemented as approved, provided the intended outcome, is effective, and has not caused other "unintended" changes. The follow-up should provide for closure in a timely manner. The appropriate timeframe for follow-up and closure can vary dependent of the type of change, but should be verified before product affected by the change is released. Changes should not be left "open" for an excessive length of time.





回复

使用道具 举报

药士
发表于 2016-6-9 14:51:33 | 显示全部楼层
其中提到These changes are often temporary and handled within the deviation management system or similar program,临时变更通过偏差管理系统或者其他系统处理,这个怎么理解呢????
回复

使用道具 举报

药士
发表于 2016-6-13 17:26:38 | 显示全部楼层
今天又在who的一份指南(草案) deviation handling and quality risk management中确实也提到这个planned deviation的概念,dizzy了
http://www.who.int/immunization_standards/vaccine_quality/deviation_handling_qrm/en/
PLANNED DEVIATION.png
回复

使用道具 举报

药徒
发表于 2017-12-2 16:53:13 | 显示全部楼层
beiwei5du 发表于 2016-6-13 17:26
今天又在who的一份指南(草案) deviation handling and quality risk management中确实也提到这个planned  ...

GMP指南质量管理体系上,也有提到,有个药企偏差分类:计划内暂时性偏差和计划外偏差
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

×发帖声明
1、本站为技术交流论坛,发帖的内容具有互动属性。您在本站发布的内容:
①在无人回复的情况下,可以通过自助删帖功能随时删除(自助删帖功能关闭期间,可以联系管理员微信:8542508 处理。)
②在有人回复和讨论的情况下,主题帖和回复内容已构成一个不可分割的整体,您将不能直接删除该帖。
2、禁止发布任何涉政、涉黄赌毒及其他违反国家相关法律、法规、及本站版规的内容,详情请参阅《蒲公英论坛总版规》。
3、您在本站发表、转载的任何作品仅代表您个人观点,不代表本站观点。不要盗用有版权要求的作品,转贴请注明来源,否则文责自负。
4、请认真阅读上述条款,您发帖即代表接受上述条款。

QQ|手机版|蒲公英|ouryao|蒲公英 ( 京ICP备14042168号-1 )  增值电信业务经营许可证编号:京B2-20243455  互联网药品信息服务资格证书编号:(京)-非经营性-2024-0033

GMT+8, 2025-5-6 15:17

Powered by Discuz! X3.4运维单位:苏州豚鼠科技有限公司

Copyright © 2001-2020, Tencent Cloud.

声明:蒲公英网站所涉及的原创文章、文字内容、视频图片及首发资料,版权归作者及蒲公英网站所有,转载要在显著位置标明来源“蒲公英”;禁止任何形式的商业用途。违反上述声明的,本站及作者将追究法律责任。
快速回复 返回顶部 返回列表