<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OHSAS 18001 EXPERT &#187; OHSMS Implementation</title>
	<atom:link href="http://ohsas18001expert.com/category/ohsms-implementation/feed/" rel="self" type="application/rss+xml" />
	<link>http://ohsas18001expert.com</link>
	<description>Operational Health and Safety</description>
	<lastBuildDate>Tue, 20 Apr 2010 18:48:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Olympic Death &#8211; Lessons for an OHSMS</title>
		<link>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/</link>
		<comments>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 19:13:18 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[competency]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[risk assessment]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=340</guid>
		<description><![CDATA[The death of Georgian luger Nodar Kumaritashvili at the beginning the 2010 Olympic Games was tragic.  Even though most workplaces are clearly not the same as an Olympic sports facility, there are &#8220;lessons to be learned&#8221; from this tragedy for occupational health and safety professionals.   Arguing whether the individual hurt was at fault is not productive.  As the Georgian President Mikheil [...]]]></description>
			<content:encoded><![CDATA[<p>The death of Georgian luger Nodar Kumaritashvili at the beginning the 2010 Olympic Games was tragic. </p>
<p>Even though most workplaces are clearly not the same as an Olympic sports facility, there are &#8220;lessons to be learned&#8221; from this tragedy for occupational health and safety professionals.  </p>
<ul>
<li>Arguing whether the individual hurt was at fault is not productive.  As the Georgian President Mikheil Saakashvili stated &#8211; &#8220;&#8230;no sports mistake is supposed to lead to a death.&#8221;  When individuals die as a result of workplace incidents, the sentiment is the same.  Blaming the worker is just as counterproductive as blaming an athlete.</li>
<li>Consideration of &#8221;human factors&#8221; is both critical to preventing injury and more difficult and complex than it initially seems. </li>
</ul>
<p>What are those complexities?</p>
<p><span id="more-340"></span>First, consideration of human factors must consider each person as an individual.  Unlike machines, humans are not identical.  Each person is unique in size and statue, physical capabilities and emotional responses.  Protecting all workers means protecting each individual.</p>
<p>Second, there is a relationship between the consideration of human factors associated with a task and the development of the competency needed to perform that task.  Much of the disagreement expressed about the luge crash has focused on the skill and experience of Nodar.  The same issue is often a factor in industrial accidents &#8211; inexperienced workers have a higher accident rate.</p>
<p>Finally, our view of what is an acceptable risk evolves over time.  In a recent <a href="http://motorsport.com/news/article.asp?ID=357919&amp;FS=F1" target="_blank">blog post</a> on <a href="http://www.motorsport.com">www.motorsport.com</a>, Max Mosley, the former president of Formula One&#8217;s governing body, is quoted as saying &#8220;The International Luge Federation is where Formula One was 40 years ago &#8211; the whole mindset is wrong.&#8221; </p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
<p> </p>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;HELP &#8211; I&#8217;m out of RAM&#8221;</title>
		<link>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/</link>
		<comments>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 21:18:39 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[risk assessment]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=331</guid>
		<description><![CDATA[OHSAS 18001 requires that your organization’s procedure for hazard identification and risk assessment take into account “human behavior, capabilities and other human factors”.  Many organizations partially address this requirement by establishing an ergonomics program in order to address physical human factors.  Only a few organizations explicitly address mental human factors as a part of their [...]]]></description>
			<content:encoded><![CDATA[<p>OHSAS 18001 requires that your organization’s procedure for hazard identification and risk assessment take into account “human behavior, capabilities and other human factors”. </p>
<p>Many organizations partially address this requirement by establishing an ergonomics program in order to address physical human factors.  Only a few organizations explicitly address mental human factors as a part of their hazard identification and risk assessment. </p>
<p>Yet, <em><span style="text-decoration: underline;">mental</span></em> human factors are very real and can be just as important as <em><span style="text-decoration: underline;">physical</span></em> human factors.  In some cases, they are even more important.  For example, when one is driving a car, factors that reduce mental acuity – such as talking on a cell phone – are typically much more significant than physical capabilities.  The dangers of being distracted while driving is important enough that the first Distracted Driving Summit was held last fall and the U.S. Department of Transportation has set up a <a href="http://www.distraction.gov/" target="_blank">Distracted Driving website</a>. </p>
<p>The human brain has been described as having “a very large hard drive but limited random access memory (RAM).”  As demonstrated by our proficiency at trivia games and success in answering questions on quiz shows like Jeopardy, the human brain is capable of storing a great deal of information.  On the other hand, studies show that most people have difficulty remembering more than 7±2 items at a time in <a href="http://en.wikipedia.org/wiki/Short-term_memory" target="_blank">short term memory</a>.  Our mental processes were developed for a very different environment than we find ourselves in today.  In the past, our modes of information delivery moved much, much slower with significantly fewer “inputs per minute.”  </p>
<p>Yet we design work environments as if this mental limitation does not exist. </p>
<p>We expect individuals to work at full capacity in environments with multiple stimuli.  We set up equipment lines so they are efficient for the machines but terrible environments for the people who have to work there.  We design work processes and work shifts as if mental limitations do not exist.</p>
<p>Unfortunately, when accidents do occur – which they inevitably will – we blame the individuals involved and tell them how “bad” they are. </p>
<p>I’m not sure if this is silly, sad or tragic but it sure is NOT a sound management system approach.</p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Strategy vs. Implementation &#8211; Which is Important?</title>
		<link>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/</link>
		<comments>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 21:59:54 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[strategic planning]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=327</guid>
		<description><![CDATA[I have been working for over a year with a project team developing a strategy for improving a management system process that is of great importance to that organization.  It was a major effort that culminated in a presentation to the executive management team. They loved it. That should be great – right? Well&#8230; The problem with [...]]]></description>
			<content:encoded><![CDATA[<p>I have been working for over a year with a project team developing a strategy for improving a management system process that is of great importance to that organization.  It was a major effort that culminated in a presentation to the executive management team.</p>
<p>They loved it.</p>
<p>That should be great – right?</p>
<p>Well&#8230; The problem with an “approved strategy” is that now someone has to implement it.</p>
<p>This is a common issue that arises when an organization establishes an occupational safety and health management system.  The company tasks a team that sets up the framework for the OHSMS, someone writes up the procedures to match the conceptual framework and objectives are established for the various improvement initiatives that have been envisioned.</p>
<p>Then comes implementation &#8211; “doing what you say you are going to do.”  This is often the hard part.</p>
<p>For success – you need BOTH strategy and implementation.  </p>
<ul>
<li>If you have strategy without implementation, you may have great plans but the organization will get no benefits from the strategic planning (the “dusty manuals” syndrome).</li>
<li>If you have implementation without strategy, you will have action but are likely to miss the mark and end up doing the wrong things well (the “ready, fire, aim” syndrome).</li>
</ul>
<p>For a good discussion of the important of getting it right and doing it right – check out the following blog post – <a href="http://blog.smartdraw.com/archive/2009/09/22/strategy-is-execution-don-t-shoot-yourself-in-the-foot.aspx " target="_blank">Strategy IS Execution.</a></p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Out with the Old &#8211; In with the New</title>
		<link>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/</link>
		<comments>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 15:07:03 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[record control]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=317</guid>
		<description><![CDATA[The start of the New Year is good time to pause, reflect and clean out. Many organizations use the start of the year as a time to review their OH&#38;S management system objectives and set new ones.  If their OH&#38;S programs are lagging in their implementation, new approaches or new assignments are considered.  This is [...]]]></description>
			<content:encoded><![CDATA[<p>The start of the New Year is good time to pause, reflect and clean out.</p>
<p>Many organizations use the start of the year as a time to review their OH&amp;S management system objectives and set new ones.  If their OH&amp;S programs are lagging in their implementation, new approaches or new assignments are considered. </p>
<p>This is also a good time to address all that PAPER – either physical paper or electronic paper.  This includes all those completed hazard evaluation forms, inspection checklists, excel spreadsheets, meeting notices and minutes, e-mails with various interested parties, incident investigations, corrective action reports,….</p>
<p>When I help develop record control processes and procedures for an organization, one of the concepts I try to incorporate is the inclusion of record schedules with record breaks and scheduled clean-out days. <span id="more-317"></span></p>
<p>A record schedule is a document that defines how a record is to be kept, how long it needs to be maintained in an active storage location and when it should be destroyed.  <a href="http://www.epa.gov/records/faqs/schedules.htm" target="_self">U.S. EPA has an informative discussion of the purpose and use of record schedules on its web site. </a></p>
<p>The first key to using a record schedule is organizing your records in a way that makes complying with your record retention requirements as easy as possible.  This usually means using record breaks – usually defined points in time when you start a new file. For example, rather than filing all of your records pertaining to a particular topic randomly in one file folder (physical or electronic), you file them by year so you can move an entire year’s worth of records to a different location (off-site storage or electronic archive) at one time. </p>
<p>The second key to using a record schedule is actually setting aside a time for moving old records out of active storage locations and getting rid of unnecessary records in accordance with your organization’s record retention policies. </p>
<p>Although this often appears to be an unimportant mundane task to “put off to another day” it is important to the smooth functioning of your OHSMS. </p>
<p>So, schedule your record clean-out day today.  By the way, wear comfortable clothes and order a pizza.  It will make the job easier.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ban the Blame</title>
		<link>http://ohsas18001expert.com/2009/12/15/ban-the-blame/</link>
		<comments>http://ohsas18001expert.com/2009/12/15/ban-the-blame/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 13:29:20 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[corrective action]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[preventive action]]></category>
		<category><![CDATA[root causes]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=314</guid>
		<description><![CDATA[One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong.  This is not easy.  Often, the [...]]]></description>
			<content:encoded><![CDATA[<p>One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong. </p>
<p>This is not easy.  Often, the root cause investigation ends with a determination along the lines of “Joe screwed up.”  We play the blame game.</p>
<p>Why?</p>
<p><span id="more-314"></span>There have been a number of reasons advanced for this and most of them are probably true – at least in part.</p>
<p>Last week, a colleague lent me his copy of Dan Gano’s book – <a href="http://www.amazon.com/Apollo-Root-Cause-Analysis-Thinking/dp/1883677114/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1260882984&amp;sr=1-1" target="_blank">Apollo Root Cause Analysis.</a>  This book sets out a different way of approaching root cause analysis by focusing on defining a problem in terms of both the action and the conditions that caused the particular effect you are analyzing.  For example, you don’t get a fire (an effect) unless you have an ignition source (an action) as well as two conditions (fuel and oxygen at the right concentrations).  Remove either condition (fuel/oxygen) or the action (ignition) and the effect (fire) does not occur.</p>
<p>What I liked most about the book, however, was not the root cause methodology advanced in the book but the explanation of why we so often fall into the blame game.</p>
<p>In a word &#8211; storytelling.</p>
<p>As humans, we have a long tradition of storytelling.  It comes naturally to us.  It is how we have transmitted information for generations.  Everyone likes a good story.</p>
<p>Integral to storytelling is identifying your actors – answering the question “who” is central to telling a good story.  As Gano points out in his book, most incident reports provide a prime example of storytelling.  The initial focus is typically on who did what.  Unfortunately, for purposes of root cause analysis, storytelling sets us up for failure because it keeps us focused on the story &#8211; who, what, where and when &#8211; rather than focusing our attention on identifying the causes of an incident. </p>
<p>So when you are investigating an incident or nonconformity, tell your story.  It is, after all, human nature and likely irresistible.  But when you start your root cause analysis, put the story aside and take the “who” completely out of the analysis.  Remove the names and strike the identifiers.  Instead, focus your attention on the actions and conditions that lead to the situation (effect) that you are investigating.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/12/15/ban-the-blame/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Timely&#8221; Incident Investigation</title>
		<link>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/</link>
		<comments>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 17:52:09 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=290</guid>
		<description><![CDATA[Section 4.5.3.1 of OHSAS 18001 requires that OH&#38;S incident investigations “be performed in a timely manner”. So &#8211; What is Timely? Neither OHSAS 18002 nor the dictionary (my primary sources for interpreting the OHSAS 18001 requirements) provides much help.  OHSAS 18002 does not explicitly discuss this particular requirement of the OHSAS 18001 standard. The dictionary [...]]]></description>
			<content:encoded><![CDATA[<p>Section 4.5.3.1 of OHSAS 18001 requires that OH&amp;S incident investigations “be performed in a timely manner”.</p>
<p><em><strong>So &#8211; What is Timely?</strong></em></p>
<p>Neither OHSAS 18002 nor the dictionary (my primary sources for interpreting the OHSAS 18001 requirements) provides much help. </p>
<p>OHSAS 18002 does not explicitly discuss this particular requirement of the OHSAS 18001 standard.</p>
<p>The dictionary isn’t particularly helpful either. It defines timely as – “well-timed, in time, occurring at a suitable time, opportunely“. The legal dictionary definition is “falling within a prescribed or reasonable time.”<span id="more-290"></span></p>
<p>As a practical matter, there are several components to a “timely” incident investigation –</p>
<ul>
<li> “The CSI Factor” – As in the TV show CSI, you will want to do your immediate investigation of an incident (who, what, when and where) while the facts are fresh – before memories fade and “the evidence” disappears.</li>
<li>Dealing with Imminent Risks – Hazards that are imminent risks (e.g. defective ladders, broken guards on operating equipment) need to be addressed immediately.</li>
<li>Preventing Future Injuries – Since the primary purpose of incident investigation is prevention of injuries, the root causes of an incident (why and how) need to be determined and addressed before another similar incident occurs.</li>
</ul>
<p>An investigation does not need to be completed all at once in order to be timely.</p>
<p>An incident investigation is often done in two stages:</p>
<ol>
<li>Initial information collection – preserving the evidence</li>
<li>Root cause analysis – determining what the evidence means</li>
</ol>
<p>The initial of collection of information about the incident usually needs to be done quickly. The root cause analysis typically takes more time.</p>
<p>So what do you think? Let me know by completing the survey below or posting a comment.<br />
<!-- Altering or removing this link is a breach of the Vizu Terms and Conditions -->
<div style="font-family:Arial, Helvetica, sans-serif; font-size:9px;height:20px;text-align:center;width:320px;margin:0;padding:0;letter-spacing:-.5px"><a href="http://www.vizu.com" target="_blank"><span style="color:#999;text-decoration:underline;font-size:9px;">Online Surveys</span></a><span style="color:#999;">&nbsp;&amp;&nbsp;</span><a href="http://answers.vizu.com/market-research.htm" target="_blank"><span style="color:#999;text-decoration:underline;font-size:9px;">Market Research</span></a></div>
<p><embed src="http://wp.vizu.com/vizu_poll.swf" quality="high" scale="noscale" wmode="transparent" bgcolor="#ffffff" width="320" height="432" name="vizu_poll" align="middle" allowScriptAccess="always" type="application/x-shockwave-flash" FlashVars="js=false&#038;pid=189829&#038;ad=false&#038;vizu=true&#038;links=true&#038;mainBG=eeeeee&#038;questionText=000000&#038;answerZoneBG=EEEEEE&#038;answerItemBG=cc9966&#038;answerText=000000&#038;voteBG=C8C8C8&#038;voteText=000000"></embed> </p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information Overload</title>
		<link>http://ohsas18001expert.com/2009/10/27/information-overload/</link>
		<comments>http://ohsas18001expert.com/2009/10/27/information-overload/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 20:43:59 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=266</guid>
		<description><![CDATA[One of the signfiicant tasks associated with implementing any management system is managing information &#8211; typically lots of information.  Usually, way too much information.  As I discussed in a previous post &#8211; Data Sprawl &#8211; Not Just an IT Problem, the fact that we are now managing &#8220;virtual information&#8221; leads us to believe that the [...]]]></description>
			<content:encoded><![CDATA[<p>One of the signfiicant tasks associated with implementing any management system is managing information &#8211; typically lots of information.  Usually, way too much information.  As I discussed in a previous post &#8211; <a href="http://ohsas18001expert.com/2008/07/21/data-sprawl-not-just-an-it-problem/" target="_self">Data Sprawl &#8211; Not Just an IT Problem</a>, the fact that we are now managing &#8220;virtual information&#8221; leads us to believe that the more information we have the better.</p>
<p>Not true. </p>
<p>As this video points out, at some point more information simply makes us stupid.</p>
<p> <object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="445" height="364" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/CXFEBbPIEOI&amp;hl=en&amp;fs=1&amp;rel=0&amp;color1=0xe1600f&amp;color2=0xfebd01&amp;border=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="445" height="364" src="http://www.youtube.com/v/CXFEBbPIEOI&amp;hl=en&amp;fs=1&amp;rel=0&amp;color1=0xe1600f&amp;color2=0xfebd01&amp;border=1" allowfullscreen="true" allowscriptaccess="always"></embed></object></p>
<p>This is an important point to remember as you are establishing, implementing and maintaining your OH&amp;S management system.  As you are developing your procedures, programs, forms, inspection sheets, training programs, meeting minutes, e-mail updates&#8230;&#8230; remember that the human brain only has so much capacity. </p>
<p>Use it wisely.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/10/27/information-overload/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating OHSMS Documentation</title>
		<link>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/</link>
		<comments>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 15:16:49 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[audit]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=244</guid>
		<description><![CDATA[A reader recently asked – Why is that OH&#38;S management system manuals so often repeat the language of the OHSAS 18001 standard – isn’t that redundant? Yes and No. During management system implementation, the constant repetition of the OHSAS 18001 language feels redundant.  You are referring to OHSAS 18001 constantly – in drafting procedures, discussing processes, [...]]]></description>
			<content:encoded><![CDATA[<p>A reader recently asked –</p>
<p><em>Why is that OH&amp;S management system manuals so often repeat the language of the OHSAS 18001 standard – isn’t that redundant?</em></p>
<p>Yes and No.</p>
<p><span id="more-244"></span>During management system implementation, the constant repetition of the OHSAS 18001 language feels redundant.  You are referring to OHSAS 18001 constantly – in drafting procedures, discussing processes, creating forms and developing training programs.  You probably feel – “enough already with the arcane standards speak.”  Since you are so close to the initial drafting of the manual and other procedures, it is clear in your mind what the OHSAS 18001 requirements are and how you are planning to meet them.</p>
<p>As with most things, memories and associations fade with time. </p>
<p>One of my favorite Christmas stories is that each year when we got together with my mother and my husband’s parents for Christmas, my Mother would start a question with “What year was it when we ….”  A lively discussion would ensue as we tried to remember exactly what year it was that we did some particular activity – &#8220;Was it 1997 or was it 2000?&#8221;  My mother has since passed away but we still discuss “What year was it when we …” at Christmas &#8211; and I am reminded of her presence.</p>
<p>A similar thing happens with your management system manuals and procedures.  Over time, people will forget both WHAT they need to do and WHY if you don’t actually include the requirements in your Manual.  The “shall clauses” in the OHSAS 18001 standard are unlikely to be remembered and may not actually be met if you don’t explicitly include them in your own OHSMS documentation.</p>
<p>One of the tests of the completeness of a management system manual is whether you can file the standard away (never refer to it again), and still have a management system that continues to be in conformance with the requirements of OHSAS 18001. </p>
<p>In fact, the hallmark of a good internal audit program is that audits are performed against the organization’s own OHSMS documentation – its manual and procedures – NOT against the OHSAS 18001 standard.  Conformance with the OHSMS manual IS conformance with OHSAS 18001.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/09/30/creating-ohsms-documentation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Challenges &amp; Opportunities in Developing OHSMS Standards</title>
		<link>http://ohsas18001expert.com/2009/09/04/challenges-opportunities-in-developing-ohsms-standards/</link>
		<comments>http://ohsas18001expert.com/2009/09/04/challenges-opportunities-in-developing-ohsms-standards/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 14:13:27 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[Featured Articles]]></category>
		<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Standards & Certification]]></category>
		<category><![CDATA[Upcoming Events]]></category>
		<category><![CDATA[health care]]></category>
		<category><![CDATA[NIOSH NORA]]></category>
		<category><![CDATA[patient safety]]></category>
		<category><![CDATA[respirators]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=237</guid>
		<description><![CDATA[This week I had the opportunity to attend and give a presentation at the NIOSH NORA Health Care and Social Assistance Sector Council Meeting in Washington DC.  It was the first NIOSH NORA meeting I have attended and I found the discussion both very enlightening and somewhat scary. At this meeting I gave a presentation [...]]]></description>
			<content:encoded><![CDATA[<p>This week I had the opportunity to attend and give a presentation at the NIOSH NORA Health Care and Social Assistance Sector Council Meeting in Washington DC.  It was the first NIOSH NORA meeting I have attended and I found the discussion both very enlightening and somewhat scary.</p>
<p>At this meeting I gave a presentation &#8211; <em><a href="http://www.managementsystemexpert.com/conversations-with-experts/challenges-opportunities-in-developing-ohsms-standards/" target="_blank">Challenges &amp; Opportunities in Developing OHSMS Standards</a></em> &#8211; that outlined five common barriers to implementing Occupational Health and Safety Management Systems.  Also giving presentations on this topic were Mike Seymour from <a href="http://www.osha.gov/" target="_blank">OSHA</a> and Barbara Braun from <a href="http://www.jointcommission.org/" target="_blank">The Joint Commission</a>.  Mike Seymour discussed the OHSMS guidance document that OSHA is currently in the process of developing and Barbara Braun discussed how the Joint Commission standards also include worker safety requirements.  As several of the attendees pointed out, there is a clear and obvious link between patient safety and worker safety.</p>
<p>The purpose of these presentations was to assist the <a href="http://www.cdc.gov/niosh/programs/hcsa/emerging.html" target="_blank">HCSA Sector Council</a> in developing implementation plans for the new National Occupational Research Agenda for this sector <a href="http://www.cdc.gov/niosh/review/public/183/default.html" target="_blank">(currently out for public comment until the end of October 2009)</a>.  A key strategic goal in this agenda is promoting the use of OH&amp;S management systems and improving safety culture in healthcare organizations.</p>
<p>The scary part of the meeting&#8230;</p>
<p>The critical issues that need to be addressed to protect health care workers &#8211; particularly as it relates to the H1N1 pandemic.  There was a great deal of discussion concerning the precautions that need to be taken related to providing proper respiratory protection - NOT JUST SURGICAL MASKS &#8211; and the <a href="http://www.infectioncontroltoday.com/hotnews/nurse-survey-flu-readiness-in-hospitals.html" target="_blank">current lack of hospital preparedness</a>.  The importance of this topic was emphasized by the <a href="http://abcnews.go.com/Health/SwineFlu/wireStory?id=8481429" target="_blank">advisory issued by the Institute of Medicine yesterday </a>that urges health care workers to use N95 respirators instead of surgical masks for protection.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009) </h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/09/04/challenges-opportunities-in-developing-ohsms-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Need for PM</title>
		<link>http://ohsas18001expert.com/2009/07/31/the-need-for-pm/</link>
		<comments>http://ohsas18001expert.com/2009/07/31/the-need-for-pm/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 11:57:23 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[OH&S controls]]></category>
		<category><![CDATA[preventive maintenance]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=196</guid>
		<description><![CDATA[What do the National Mall, my homeowner’s association and your OH&#38;S management system have in common? The need to pay for preventive maintenance. When we moved to Florida, we purposely choose to live in a neighborhood that did NOT have a golf course, community center or jointly owned “common areas.”  Instead, we choose a neighborhood [...]]]></description>
			<content:encoded><![CDATA[<p>What do the National Mall, my homeowner’s association and your OH&amp;S management system have in common?</p>
<p><span style="font-size: large;"><strong><span style="font-size: small;">The need to pay for preventive maintenance.</span></strong></span></p>
<p>When we moved to Florida, we purposely choose to live in a neighborhood that did NOT have a golf course, community center or jointly owned “common areas.”  Instead, we choose a neighborhood that had a voluntary homeowners association – not a mandatory one.  A couple of years ago, a few neighbors wanted to “beautify” the neighborhood by putting up signs and installing landscaping.  They did so.  Then, because the plantings they put in were dying and you could not see the new signs at night, they wanted to add irrigation and lighting.  They did so.  Needless to say, once they realized that these things were costing money, there was an attempt to impose mandatory fees to pay for the on-going expense.  It didn’t happen.  These neighbors became upset when the rest of the neighborhood was not interested in paying for their neighborhood beautification efforts.</p>
<p>According to last <a href="http://www.tampabay.com/incoming/article1021187.ece" target="_blank">Friday’s paper</a>, the National Mall is slipping into a state of neglect. Apparently, ducks died last year of avian botulism because the water in a mall pool was so foul, the Jefferson Memorial is sinking into the mud and the soil is so compacted in places that grass can’t grow.  Yet, Congress has refused to provide funding to pay for the necessary upkeep.</p>
<p>What do these stories have in common? </p>
<p>The failure to recognize that &#8211; “If you build it, you’ve got to maintain it.”</p>
<p>This is an important warning to keep in mind as you develop your OH&amp;S management system. </p>
<p>Whatever systems you put in place <span style="text-decoration: underline;">must</span> be maintained –</p>
<ul>
<li>Documents need to be reviewed and revised</li>
<li>Software needs to be maintained and updated</li>
<li>Controls need to be inspected and maintained</li>
</ul>
<p>All of this costs money.</p>
<p>Make sure you consider the long-term preventive maintenance costs before you put systems, software and controls in place.  If you can’t maintain them, you may only make things worse.</p>
<p><span style="font-family: 'Arial','sans-serif'; font-size: 8pt;">© ENLAR<sup>®</sup> Compliance Services, Inc. (2009)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/07/31/the-need-for-pm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
