<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: FDA 21 CFR Part 11 Compliance in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107089#M74974</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;So i guess i am not the only one asking about this,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;see thread:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.alfresco.com/viewtopic.php?t=5935&amp;amp;highlight=" rel="nofollow noopener noreferrer"&gt;http://forums.alfresco.com/viewtopic.php?t=5935&amp;amp;highlight=&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;however it seems that there is a lack of "&lt;/SPAN&gt;&lt;STRONG&gt;proper&lt;/STRONG&gt;&lt;SPAN&gt;" support for digital signatures, however there is a basic way to achieve electronic signatures &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;based on what i was told by one of the developers …..:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;â€œAs I understand it, the digital signature case is essentially as Paul described it.&amp;nbsp; They would like to have an in-flight workflow with a property sheet that would let approvers â€œsign their approvalâ€&amp;#157; to a document.&amp;nbsp; This signature would then be retained as part of the lifecycle history of that document.&lt;BR /&gt; &lt;BR /&gt;The actual signature itself would feature a re-authentication of sorts.&amp;nbsp; In my head, it would be a â€œsignâ€&amp;#157; button within the workflow property sheet.&amp;nbsp; Clicking it would reveal a password box.&amp;nbsp; Theyâ€™d fill in the box and click â€œattach my signatureâ€&amp;#157; at which point we could probably Ajax the auth call.&amp;nbsp; If successfully, their signature would be attached to the workflow or also to one or more payload objects"&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;but i am concerned that it does not really satisfy the requirement (see my thread and link to 21cfrpart11.com).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Slightly off-topic, another thing i would like is watermark generation and embedding during PDF conversion/creation.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 May 2007 16:06:44 GMT</pubDate>
    <dc:creator>kurtkbee</dc:creator>
    <dc:date>2007-05-17T16:06:44Z</dc:date>
    <item>
      <title>FDA 21 CFR Part 11 Compliance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107088#M74973</link>
      <description>I'm interested in deploying Alfresco in an FDA regulated environment, and the current release seems to be 21 CFR Part 11 complaint except for one feature. Alfresco doesn't have a digital signature capability. Does anyone know of a third party module that allows Alfresco to meet the Part 11 requireme</description>
      <pubDate>Thu, 17 May 2007 01:24:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107088#M74973</guid>
      <dc:creator>mstoakes</dc:creator>
      <dc:date>2007-05-17T01:24:45Z</dc:date>
    </item>
    <item>
      <title>Re: FDA 21 CFR Part 11 Compliance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107089#M74974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;So i guess i am not the only one asking about this,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;see thread:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.alfresco.com/viewtopic.php?t=5935&amp;amp;highlight=" rel="nofollow noopener noreferrer"&gt;http://forums.alfresco.com/viewtopic.php?t=5935&amp;amp;highlight=&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;however it seems that there is a lack of "&lt;/SPAN&gt;&lt;STRONG&gt;proper&lt;/STRONG&gt;&lt;SPAN&gt;" support for digital signatures, however there is a basic way to achieve electronic signatures &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;based on what i was told by one of the developers …..:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;â€œAs I understand it, the digital signature case is essentially as Paul described it.&amp;nbsp; They would like to have an in-flight workflow with a property sheet that would let approvers â€œsign their approvalâ€&amp;#157; to a document.&amp;nbsp; This signature would then be retained as part of the lifecycle history of that document.&lt;BR /&gt; &lt;BR /&gt;The actual signature itself would feature a re-authentication of sorts.&amp;nbsp; In my head, it would be a â€œsignâ€&amp;#157; button within the workflow property sheet.&amp;nbsp; Clicking it would reveal a password box.&amp;nbsp; Theyâ€™d fill in the box and click â€œattach my signatureâ€&amp;#157; at which point we could probably Ajax the auth call.&amp;nbsp; If successfully, their signature would be attached to the workflow or also to one or more payload objects"&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;but i am concerned that it does not really satisfy the requirement (see my thread and link to 21cfrpart11.com).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Slightly off-topic, another thing i would like is watermark generation and embedding during PDF conversion/creation.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2007 16:06:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107089#M74974</guid>
      <dc:creator>kurtkbee</dc:creator>
      <dc:date>2007-05-17T16:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: FDA 21 CFR Part 11 Compliance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107090#M74975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think that the digital signature signing the way you describe it would meet the Part 11 rule. The watermarking of PDFs is important, because of the requirement for document/signature binding.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The way public key encryption currently works requires that the official document must always live on the server along with the signature. If you download the official document to say a USB drive and take it home with you, there would be no way to offline verify the signature. One could make changes to the document and no one would be the wiser. If the document is watermarked as a copy of the official document, then an offline file or a printout would always indicate it is a copy.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unless Microsoft provides a better way to lockdown Word documents, a PDF is the best alternative for a file format for official documents.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2007 16:35:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/fda-21-cfr-part-11-compliance/m-p/107090#M74975</guid>
      <dc:creator>mstoakes</dc:creator>
      <dc:date>2007-05-17T16:35:35Z</dc:date>
    </item>
  </channel>
</rss>

