Highlighting Compliance for HR

Posted on
Like what you see? Share it.Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone

<p><strong>Oxfordshire, England &mdash; Jan. 2</strong><br />Cobent has published a white paper that examines the increasing regulatory requirements placed upon HR and training directors and suggests a best practice method of providing tamperproof training records.<br /><br />Increasingly, regulated industries &mdash; notably those in the life sciences sector &mdash; require organizations to keep comprehensive data and reports showing compliance to regulatory needs. While these must be robust and come from an unimpeachable source, manual record keeping can be easily flawed, and electronic record keeping is not foolproof either &mdash; although one system now meets the requirements of the most stringent regulations.<br /><br />This is the main conclusion of “Best Practice Approach to Learning Compliance Management in Regulated Industries” &mdash; a new white paper from regulatory compliance systems specialists Cobent Group.<br /><br />Cobent, a provider of solutions for e-learning, training and compliance-led process management across the entire range of international blue-chip companies, fast-growth startups, and public sector organizations, claims that its learning and compliance system (LCS) is currently a leading product in helping to meet these guidelines. <br /><br />&ldquo;Most LMSs employ a process which is open to a number of possible unauthorized interventions,&rdquo; explained Jordan Ambrose, Cobent&rsquo;s sales director. &ldquo;Even with electronic automation, the integrity and validity of the training document could be called into question under a compliance audit.&rdquo;<br /><br />Cobent, a U.K.-based company, believes that the most stringent compliance regulations in the world are those of the United States Food and Drug Administration (FDA) &mdash; especially its 21 CFR Part 11, which aims to achieve more efficient work practices and demonstrate the validity of information where computers were used to replace previously paper-based operations.<br /><br />According to Howard Sears, Cobent&rsquo;s CEO: &ldquo;Part 11 was designed to produce a minimum set of standards for electronic records and signatures, making them equivalent to conventional paper records. Importantly, these regulations apply not just to businesses in the U.S. but also to any company internationally selling into the U.S. market.<br /><br />&ldquo;Regulation 21 CFR Part 11 is now a benchmark standard for any system which keeps electronic documents or uses electronic signatures.&rdquo;<br /><br />Ambrose added: &ldquo;So, it is no longer enough just to provide an electronic equivalent of the manual process unless the system on which this is achieved passes the requirements of 21 CFR Part 11. <br /><br />&ldquo;Since the Cobent LCS system is compliant with the technical controls required for the storage of electronic records under FDA 21 CFR Part 11, the client can be confident that all data changes are recorded and security is assured through a comprehensive permission hierarchy and the administration of e-signatures.<br /><br />&ldquo;The area where compliance and learning meet is now one where there is significant need for adherence to regulations. Failing to provide the necessary integrity in the process of training and collecting the required data is a risk that no organization should take,&rdquo; said Ambrose.<br /><br />Copies of the white paper are available, free on request, from Jordan Ambrose at Cobent, at jambrose@cobent.com. </p>

Like what you see? Share it.Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone


Posted in Archive|


Leave a comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>