Hi Cove,
I am a RA Specialist at a startup, and am writing a Configuration Management Plan for an SaMD product. The developers use Confluence a lot for internal documentation like release notes and information about noteworthy JIRA epics and tickets. I'm trying to figure out how to include this in the CMP, there's no SOP that controls this aspect - should I just mention that release notes are documented with the version number in Confluence with any changes controlled? We do have a doc control SOP that covers the identification of quality documents, but I'm not sure if everything that is in Confluence can be covered under a doc like the DHF or something similar.
Appreciate any inputs. Thanks!
I am a RA Specialist at a startup, and am writing a Configuration Management Plan for an SaMD product. The developers use Confluence a lot for internal documentation like release notes and information about noteworthy JIRA epics and tickets. I'm trying to figure out how to include this in the CMP, there's no SOP that controls this aspect - should I just mention that release notes are documented with the version number in Confluence with any changes controlled? We do have a doc control SOP that covers the identification of quality documents, but I'm not sure if everything that is in Confluence can be covered under a doc like the DHF or something similar.
Appreciate any inputs. Thanks!