Home › Forums › TMF Management, Content & Processing › Superseded documents
- This topic has 3 replies, 2 voices, and was last updated 2 years, 7 months ago by
Eldin Rammell.
-
AuthorPosts
-
-
July 7, 2022 at 10:07 am #4683
Elizabeth Chong
ParticipantDear all,
I’ve only started using eTMF about half a year ago. With paper TMFs, it was easy and we were expected, to draw a line through superseded documents and it becomes clear that a document is no longer relevant as the study progresses. Is there a similar way when using eTMF? -
July 7, 2022 at 12:00 pm #4684
Eldin Rammell
ParticipantHi Elizabeth,
Yes – a good eTMF solution should enable you to identify documents that have been superseded. There are different ways of achieving this. For many documents, a new version simply replaces the prior version (which, by definition, become superseded). So the eTMF solution should enable you to clearly distinguish between different versions of the same document and to show you the most up-to-date version. For some documents – especially those that have a defined period of applicability – this may be by use of an “effective until” date or a “status” field.
Kind regards,
Eldin. -
July 7, 2022 at 12:40 pm #4685
Elizabeth Chong
ParticipantHi Eldin,
Thanks. For documents such as protocol it might be easier to identify if they are all named consistently, as there is always going to be a protocol. For other plans, e.g maybe over time the entire plan gets merged with some other plan or is made obsolete or vendor changes, should we add notes in the document descriptor or is that actually not necessary?
-
July 11, 2022 at 10:02 am #4688
Eldin Rammell
ParticipantHi Elizabeth
There is an expectation that your TMF should provide document identification and version history. TMF regulatory guidance suggests that metadata should include information about versions. It can be assumed therefore that you need to implement some kind of system that easily allows you to identify that a document has been superseded by another. There is no simple answer how you achieve this. Ideally, your eTMF solution will provide you with a feature that clearly shows the version number and allows you to easily see when a document has been replaced by another. If the system does not provide this, then annotating superseded documents in some way (like you described) may be an acceptable alternative. That process should be documented so that it is consistently applied.
-
-
AuthorPosts
- You must be logged in to reply to this topic.