<?xml version="1.0" encoding="utf-8"?>
<feed version="0.3" xmlns="http://purl.org/atom/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en">
<title>Louisiana Law Blog</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/" />
<modified>2013-05-15T14:32:58Z</modified>
<tagline>Louisiana Lawyers, Attorneys &amp; Law Firm</tagline>
<id>tag:www.louisianalawblog.com,2013://81</id>
<generator url="http://www.movabletype.org/" version="3.34">Movable Type</generator>
<copyright>Copyright (c) 2013, Steven Boutwell</copyright>
<entry>
<title>CLS Bank:  Software Patents at Risk?</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/intellectual-property-cls-bank-software-patents-at-risk.html" />
<modified>2013-05-15T14:32:58Z</modified>
<issued>2013-05-14T22:45:29Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.375691</id>
<created>2013-05-14T22:45:29Z</created>
<summary type="text/plain"><![CDATA[By Lee Vail On May 10, 2013, the Federal Circuit, sitting en banc, handed down its opinion in CLS Bank Int&rsquo;l v. Alice Corp., No. 2011-1301, slip op. (Fed. Cir. May 10, 2013). The majority of the Federal Circuit judges...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Intellectual Property</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">Lee Vail</a></p>
<p>On May 10, 2013, the Federal Circuit, sitting <em>en banc</em>, handed down its opinion in <em>CLS Bank Int&rsquo;l v. Alice Corp</em>., No. 2011-1301, slip op. (Fed. Cir. May 10, 2013). The majority of the Federal Circuit judges agreed on little other than that the method and computer-readable medium claims involved in the dispute were patent ineligible.  Essentially, Alice Corporation owned patents that the Federal Circuit found to be nothing more than abstract ideas based on use of escrow accounts and record keeping associated with the settling of transactions.  However, the Court failed to agree on the reasoning as to why such claims were ineligible subject matter with the judges evenly split regarding the eligibility of comparable computer systems claims.</p>]]>
<![CDATA[<p>The panel of ten Federal Circuit Justices was so fractured in their reasoning that the &ldquo;decision&rdquo; constitutes six separate opinions.  In the most basic sense, the Judges agreed that prior Supreme Court precedent require that patent claims containing abstract ideas must have meaningful limitations.  However, a group of five Judges (Lourie, Dyk, Prost, Reyna, and Wallach) rejected patent eligibility of the computer system claims, concluding that incorporation of the method into a computer program was an insufficient limitation.  This opinion drew heavily from the Supreme Court&rsquo;s language in <em>Mayo Collaborative Servs. v. Prometheus Labs., Inc.,</em> 132 S.Ct. 1289, 1298 (2012), a case which ultimately invalidated a process patent dealing with the treatment of Crohn&rsquo;s Disease by monitoring transformations occurring in the human patient&rsquo;s body.  In <em>Mayo</em>, the Court invalidated the patent through the use of a judicially created exclusion by ruling that the process was based on a law of nature.  Although it was proposed that the <em>Mayo </em>claims contained other non-law of nature elements such as administering drugs and measuring the results, the court was unpersuaded, holding:</p>
<p style="margin-left: 40px;">[these] step[s] tells doctors to engage in well-understood, routine, conventional activity previously engaged in by scientists who work in the field. Purely &ldquo;conventional or obvious&rdquo; &ldquo;[pre]-solution activity&rdquo; is normally not sufficient to transform an unpatentable law of nature into a patent-eligible application of such a law.  132 S.Ct. at 1298.</p>
<p>With <em>Mayo </em>in mind, the Federal Circuit noted that routine and conventional steps are insufficient limitations to an otherwise patent ineligible subject matter (i.e., laws of nature, natural phenomena, and abstract ideas) to overcome the judicially created exclusion.  Lourie Slip op. at 20-21. Since, computers are routinely adapted with software to perform all sorts of tasks, this opinion carries the implication that the inclusion of a computer within the claim is not a substantive limitation.  Lourie Slip op. at 36-37.  This implication seems to contradict long standing caselaw which has held that new computer software indeed creates a new computer. <em>In re Alappat</em>, 33 F.3d 1526 (Fed. Cir 1994).  The opinion of the five Judges strongly denote their belief that recent Supreme Court decisions may have overturned <em>Alappat </em>and, in light of the possible overruling of <em>Alappat</em>, that the incorporation of a computer program into a computer, relying on an abstract idea, is not patent eligible.  Lourie Slip op. at 37.  If this viewpoint is allowed to stand, all computer programs, which at a basic level rely to some degree on one of the three judicially excluded criteria, may be excluded from patent protection.</p>
<p>A second group of four Judges (Rader, Linn, Moore, and O&rsquo;Malley) were no less than horrified by the majority opinion.  These Judges stressed that the scope of patent eligibility under 35 U.S.C. &sect;101 is intended to be broadly interpreted while the judicially created exceptions are limited.  In a dissenting-in-part opinion, these Judges cut to the chase about the potentially devastating outcome of their counterpart&rsquo;s holding, stating:</p>
<p style="margin-left: 40px;">[a]nd let&rsquo;s be clear: if all of these claims, including the system claims, are not patent-eligible, this case is the death of hundreds of thousands of patents, including all business methods, financial system, and software patents as well as many computer implemented and telecommunications patents.  Moore (dissenting-in-part) Slip op. at 2.</p>
<p>These Judges view the judicially created exceptions as being limited, especially when applied to a machine such as a computer. These judges would hold patent eligible a claim wherein a <em>&ldquo;computer plays a meaningful role . . . and the claim does not pre-empt virtually all uses of an underlying abstract idea.&rdquo; </em>Rader (concurring in part) Slip op. at 2.  In the end, Judge Newman generally disagreed with all of the other nine judges by concluding that all the claims were patent eligible.  His vote brought the vote for patent eligibility for the computer system claim up to five, resulting in an overall tie on the issue.</p>
<p>In conclusion, Chief Judge Rader of the Federal Circuit, in apparent frustration, criticized the Supreme Court for their decisions in various cases including <em>Parker v. Flook,</em> 437 U.S. 584 (1978), <em>Bilski v. Kappos</em>, 130 S.Ct. 3218 (2010), and <em>Mayo</em>.  In a last adage, Chief Justice Radar advised: &ldquo;When all else fails, consult the statute.&rdquo; Radar (additional reflections) Slip op. at 2-3.  Until a final decision on this matter is handed down by the Supreme Court, the status of computer system claims that contain judicially excluded subject matter (i.e., a majority of computer system claims) is completely up in the air. <br />
&nbsp;</p>]]>
</content>
</entry>
<entry>
<title>On the Horizon, Revisions to the Louisiana Private Works Act: &quot;The More Things Change, the More they Stay the Same&quot;</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/construction-law-on-the-horizon-revisions-to-the-louisiana-private-works-act-the-more-things-change-the-more-they-stay-the-same.html" />
<modified>2013-05-15T19:42:23Z</modified>
<issued>2013-05-14T20:09:49Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.375677</id>
<created>2013-05-14T20:09:49Z</created>
<summary type="text/plain"><![CDATA[By David K. Nelson All persons associated with non-public construction projects in Louisiana are affected by, and should be familiar with, the Louisiana Private Works Act. La. R.S. 9:4801, et. seq. (&ldquo;PWA&rdquo;). The two fundamental policies behind the implementation of...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Construction Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1194654.html">David K. Nelson</a></p>
<p>All persons associated with non-public construction projects in Louisiana are affected by, and should be familiar with, the Louisiana Private Works Act. La. R.S. 9:4801, <em>et. seq.</em> (&ldquo;PWA&rdquo;).&nbsp; The two fundamental policies behind the implementation of the PWA summarized are:</p>
<ol>
    <li>To protect those who contribute to the improvement of immovable property by ensuring that the owner does not benefit from their labor without compensating them; and</li>
    <li>To incentivize the owner to take reasonable steps to ensure that contractors and suppliers are paid.</li>
</ol>
<p>The PWA was first enacted in 1981 and was based upon the work and recommendations of the official advisory law revision commission and, the law reform agency and legal research agency of the State of Louisiana &ndash; The Louisiana Law Institute. Over the last thirty years, numerous amendments and revisions to the PWA have resulted in piece-meal changes to certain provisions that lead to confusion, ambiguity, and potential traps for the unwary.</p>
<p>Recognizing the undesirable effects of the many revisions, the 2012 Louisiana Legislature has once again turned to the Louisiana Law Institute for its recommendations to simplify and better organize the provisions of the PWA.</p>]]>
<![CDATA[<p>On February 15, 2013, the Louisiana Law Institute issued its report to the Legislature stating, &ldquo;&hellip;to restore the integrity and in cohesiveness of the act, the law institute feels that more comprehensive review of the act as a whole is warranted, particularly with respect to the numerous changes that have been enacted over the last three decades.&rdquo; Based upon the February report, the changes being considered are not expected to be &ldquo;wholesale revisions&rdquo; with &ldquo;far-reaching substantive effects.&rdquo; Rather, the focus will be to eliminate the ambiguities and inconsistencies resulting from the last thirty years of legislative revision.</p>
<p>Presumably, upon completion of its study, the Law Institute is expected to provide recommendations for specific revisions to the PWA. The February report does not provide a comprehensive list of provisions being evaluated; however, a review of the eight questions set out in the report suggests that several revisions may be on the horizon.</p>
<p>The eight questions are:</p>
<p><strong>1.) Should a contractor who has filed a timely Notice of Contract with proper surety bond attached be afforded a simple means of causing the cancellation of record of a Statement of Claim or Privilege?</strong></p>
<ul>
    <li>Stated differently, if a payment bond is filed at the start of the job, why should a contractor have to obtain a second bond to &quot;bond off a lien&quot;?</li>
</ul>
<p><strong>2.) Should the notice provisions of the Act be consolidated in a central location and adjusted to better accomplish their intended purpose?</strong></p>
<ul>
    <li>Currently the PWA contains approximately seven provisions requiring a claimant to provide notice to an owner or contractor; however, the period of time within which such notice must be given varies as does the triggering event. Consolidation and uniformity would eliminate these &ldquo;traps for the unwary&rdquo; contained in the current PWA.</li>
</ul>
<p><strong>3.) Should a contractor under a construction contract of more than $25,000.00 be deprived of any privilege upon the immovable if he fails to file a timely Notice of Contract?</strong></p>
<ul>
    <li>Most of the PWA privileges that arise from the timely filing of a statement of claim and privilege are given retroactive effect to the date the Notice of Contract was filed or the date work commenced. The time period between the start of work and the expiration of the period of time to file a statement of claim and privilege is often measured in years.&nbsp; During this interval the privileges that arise under the PWA are essentially &ldquo;hidden liens&rdquo; even though they do not appear of record.</li>
</ul>
<ul>
    <li>Possible revisions include:
    <ul>
        <li>Reducing the penalty for not filing the Notice of Contract to the loss of the retroactive effect of the contractor&rsquo;s statement of claim and privilege, instead of the loss of the privilege altogether;</li>
        <li>Requiring the Notice of Contract be filed by the lender or title attorney.</li>
    </ul>
    </li>
</ul>
<p><strong>4.) Should language be added to the Act making explicit that a personal claim against an owner is extinguished if the claimant fails to take the necessary action to preserve his privilege?</strong></p>
<ul>
    <li>The PWA establishes two separate but related rights. It creates a &ldquo;claim&rdquo; (a cause of action) in favor of a subcontractor or laborer against the owner and the contractor in the absence of contractual privity. It also establishes a privilege on the owner&rsquo;s immovable property to the extent of the value of work performed. The privilege arises out of the timely filing of a statement of claim and privilege. Some courts have held that the failure to timely file the statement of claim and privilege only results in the loss of the privilege and <strong>does not</strong> result in the loss of the claim.
    <ul>
        <li>The Law Institute will study and provide its recommendation as to whether the loss of privilege should result in the loss of the claim also.</li>
    </ul>
    </li>
</ul>
<p><strong>5.) Should an outside time limitation be placed on the filing a Statement of Claim and Privilege when a timely Notice of Contract has been filed, just as an outside time limitation exists when no Notice of Contract is filed?</strong></p>
<ul>
    <li>Current PWA&nbsp;provisions are counterintuitive.
    <ul>
        <li>Under the PWA now, if a Notice of Contract is timely filed, the person to whom a claim or privilege is granted under the PWA has thirty days after the filing of a notice of termination to file a statement of claim or privilege. If the owner does not remember to file the notice of termination, the period for filing statements of claim and privilege never commences to run.</li>
        <li>If a Notice of Contract is not filed, the period of time to file a statement of claim or privilege is sixty days from the notice of termination, substantial completion, or abandonment of the work.</li>
        <li>Why should the filing of the Notice of Contract work to the detriment of the owner?</li>
    </ul>
    </li>
</ul>
<p><strong>6.) Should the Act be amended to address the level of specificity that a claimant must include in a Statement of Claim or Privilege?</strong></p>
<ul>
    <li>Currently, PWA requires the Statement of Claim and Privilege to set forth &ldquo;<em>the amount and nature of the obligation giving rise to the claim or privilege and reasonably identify the elements comprising it including the person for whom and to whom the contract was performed, materials supplied, or services rendered</em>.&rdquo; Recent cases have required more specificity in terms of what must be set forth. (i.e., a claim rejected where the amount of the claim was provided with a description of &ldquo;for trim, millwork, etc.&rdquo;, but itemized invoices were not attached).
    <ul>
        <li>The Law Institute will evaluate the degree of specificity that should be required.</li>
    </ul>
    </li>
</ul>
<p><strong>7.)&nbsp; Should the Act explicitly state that a contractor enjoys no right of subrogation to the claims and privileges of his own laborers?</strong></p>
<ul>
    <li>If a general contractor fails to file a Notice of Contract, it loses its privilege. However, recent cases have allowed a general contractor to assert the privilege of its laborers by way of subrogation. As such, this general contractor enjoys the priority of a laborer&rsquo;s privilege and outranks all competing mortgages and vendors privileges.
    <ul>
        <li>The Law Institute will evaluate the need for specific revisions to the PWA to clarify that a general contractor cannot assert though subrogation the laborer&rsquo;s privileges of its employees.</li>
    </ul>
    </li>
</ul>
<p><strong>8.) Are additional protections for homeowners warranted?</strong></p>
<ul>
    <li>In 2004, the Law Institute was asked by the Legislature to evaluate the inequity which exists when a homeowner pays the general contractor and then is forced to pay again if the general contractor does not pay his subcontractors or suppliers. No revisions to the PWA were recommended at that time.</li>
    <li>The 2012 legislative request did not specifically mention this inequity; however, the Law Institute has indicated its intention to conduct further study to determine if the protection of homeowners from the double payment potential is warranted.</li>
    <li>Protection measures which may be evaluated include:
    <ul>
        <li>Excluding residential work below a certain dollar value;</li>
        <li>Limiting claims to those in direct contract with the owner;</li>
        <li>Limiting the type of claimants who could assert such a claim;</li>
        <li>Excluding homeowners altogether.</li>
    </ul>
    </li>
</ul>
<p>The PWA has been revised and amended in some fashion every year since it was first enacted thirty years ago. These changes have resulted in the unintended creation of ambiguity and uncertainty. The legislative recognition of these concerns and its request for further study from the Law Institute suggest that several clarifications and/or revisions to the PWA are on the horizon.</p>]]>
</content>
</entry>
<entry>
<title>Proposed Amendments to OIG Safe Harbor and Stark Physician Self-Referral Exception for Electronic Health Records</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/health-law-proposed-amendments-to-oig-safe-harbor-and-stark-physician-selfreferral-exception-for-electronic-health-records.html" />
<modified>2013-04-10T18:36:35Z</modified>
<issued>2013-04-10T18:15:09Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.373699</id>
<created>2013-04-10T18:15:09Z</created>
<summary type="text/plain">By Deborah J. Juneau Normal 0 false false false EN-US X-NONE X-NONE Those health care providers and suppliers who are contemplating accepting donations of electronic health records software and training services should be aware of proposed amendments to the regulations...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Health Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1193231.html">Deborah J. Juneau</a></p>
<p><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves />
<w:TrackFormatting />
<w:DoNotShowRevisions />
<w:DoNotPrintRevisions />
<w:DoNotShowMarkup />
<w:DoNotShowComments />
<w:DoNotShowInsertionsAndDeletions />
<w:DoNotShowPropertyChanges />
<w:PunctuationKerning />
<w:ValidateAgainstSchemas />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF />
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables />
<w:SnapToGridInCell />
<w:WrapTextWithPunct />
<w:UseAsianBreakRules />
<w:DontGrowAutofit />
<w:SplitPgBreakAndParaMark />
<w:DontVertAlignCellWithSp />
<w:DontBreakConstrainedForcedTables />
<w:DontVertAlignInTxbx />
<w:Word11KerningPairs />
<w:CachedColBalance />
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math" />
<m:brkBin m:val="before" />
<m:brkBinSub m:val="&#45;-" />
<m:smallFrac m:val="off" />
<m:dispDef />
<m:lMargin m:val="0" />
<m:rMargin m:val="0" />
<m:defJc m:val="centerGroup" />
<m:wrapIndent m:val="1440" />
<m:intLim m:val="subSup" />
<m:naryLim m:val="undOvr" />
</m:mathPr></w:WordDocument>
</xml><![endif]-->Those health care providers and suppliers who are contemplating accepting donations of electronic health records software and training services should be aware of proposed amendments to the regulations that might protect such arrangements under the anti-kickback statute and the Stark physician self-referral law. The Department of Health and Human Services, Office of Inspector General (&ldquo;OIG&rdquo;) is proposing to amend the anti-kickback safe harbor pertaining to electronic health records (&ldquo;EHR&rdquo;) items and services found at 42 CFR 1001.952(y).<span style="mso-spacerun:yes">&nbsp; </span>The Centers for Medicare and Medicaid Services (&ldquo;CMS&rdquo;) is proposing the same amendments to the Stark physician self-referral exception pertaining to donations of certain EHR software and directly related training services found at 42 CFR 411.357(w).<span style="mso-spacerun:yes">&nbsp; </span>The OIG safe harbor and physician self-referral exception were promulgated in 2006 to protect certain arrangements involving the donation by permitted donors of interoperable electronic health records software or information technology and training services.<span style="mso-spacerun:yes">&nbsp; </span>Both proposed rules make the identical changes to the protections offered under the safe harbor and exception.<!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" />
<w:LsdException Locked="false" Priority="39" Name="toc 1" />
<w:LsdException Locked="false" Priority="39" Name="toc 2" />
<w:LsdException Locked="false" Priority="39" Name="toc 3" />
<w:LsdException Locked="false" Priority="39" Name="toc 4" />
<w:LsdException Locked="false" Priority="39" Name="toc 5" />
<w:LsdException Locked="false" Priority="39" Name="toc 6" />
<w:LsdException Locked="false" Priority="39" Name="toc 7" />
<w:LsdException Locked="false" Priority="39" Name="toc 8" />
<w:LsdException Locked="false" Priority="39" Name="toc 9" />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" />
<w:LsdException Locked="false" Priority="37" Name="Bibliography" />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" />
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]--></p>
<p class="MsoNormal" style="text-align:justify">First, the proposed amendments would update the provision under which EHR software is deemed interoperable. Interoperable has been defined to mean &ldquo;able to communicate and exchange data accurately, effectively, securely, and consistently with different information technology systems, software applications, and networks, in various settings, and exchange data such that the clinical or operational purpose and meaning of the data are preserved and unaltered.&rdquo; Both CMS and the OIG consider interoperability to be an important concept to reduce the risk that parties might use the donated software and technology to capture referrals. Both considered that, if the donated technology is interoperable, the recipient would be able to use the technology to transmit EHR not only to the donor but to others, including competitors of the donor, and would not be &ldquo;locked-in&rdquo; to communications with the donor only.<span style="mso-spacerun:yes">&nbsp; </span></p>]]>
<![CDATA[<p>The current regulations provide that software is deemed to be interoperable if a certifying body &ldquo;recognized by the Secretary&rdquo; of HHS has certified the software within no more than 12 months prior to the date the software was donated to the recipient.<span style="mso-spacerun:yes">&nbsp; </span>The proposed amendments would modify this deeming provision to be in accord with the certification program for EHR technology by the Office of the National Coordinator (&ldquo;ONC&rdquo;) for Health Information Technology.<span style="mso-spacerun:yes">&nbsp; </span>The amendments will recognize that the ONC is responsible for recognizing certifying bodies that complete an authorization process established by the ONC.<span style="mso-spacerun:yes">&nbsp; </span>Thus, with the proposed amendments, a certifying body must be &ldquo;authorized by the National Coordinator for Health Information Technology&rdquo; rather than &ldquo;recognized by the Secretary.&rdquo;</p>
<p>The proposed amendments would also modify the time period within which the software must have been certified, changing it from the current 12 months prior to the donation of the software.<span style="mso-spacerun:yes">&nbsp; </span>The ONC developed a regulatory process that is anticipated to occur over a two-year regulatory interval, so the change would bring the safe harbor and exception in line with that time period.<span style="mso-spacerun:yes">&nbsp; </span>The amendments propose to remove the 12-month time period and provide that software would be eligible for deeming to be interoperable if, on the date it is provided to the recipient, it has been certified to any edition of the EHR certification criteria identified in the then-applicable definition of Certified EHR Technology in 42 CFR Part 170.<span style="mso-spacerun:yes">&nbsp; </span>The 2013 applicable definition for Certified EHR Technology identifies both the 2011 and the 2014 editions of EHR certification criteria, while the 2014 definition identifies only the 2014 edition.<span style="mso-spacerun:yes">&nbsp; </span>The OIG and CMS are seeking comments on whether the 12-month period should be retained.</p>
<p>Second, the proposed amendments would delete the requirement that the donated software must contain electronic prescribing capability.<span style="mso-spacerun:yes">&nbsp; </span>The OIG and CMS considered that most EHR systems include an electronic prescribing component and referred to legislation enacted to address electronic prescribing, including the electronic prescribing incentive programs in place.<span style="mso-spacerun:yes">&nbsp;</span></p>
<p><span style="mso-spacerun:yes">Third, the amendments propose to extend the sunset deadline for the safe harbor and the exception from December 31, 2013 to December 31, 2016, to coincide with the last year to receive a Medicare EHR incentive payment and to participate in a Medicaid EHR incentive program.<span style="mso-spacerun:yes">&nbsp; </span>Both the OIG and CMS are considering December 31, 2021 as an alternative sunset date to coincide with the end of EHR Medicaid incentives and asked for comments on the alternative date or whether some other sunset date should be considered.</span></p>
<p><span style="mso-spacerun:yes">Fourth, in response to comments that suggested abusive donations were being made, the proposed amendments would limit the scope of protected donors. The current safe harbor protects any donor that is an individual or entity that provides patients with health care items or services covered by a Federal health care program and submits claims or requests for payments for the items or services directly or through reassignment to Medicare, Medicaid, or other Federal health care programs and that otherwise meets the regulatory requirements. The Stark exception permitted donation by any Designated Health Service entity. The original proposals by the OIG and CMS would have limited the scope of protected donors to hospitals, group practices, prescription drug plan sponsors, and Medicare Advantage organizations.<span style="mso-spacerun:yes">&nbsp; </span>The proposed amendments would return to this limited scope of donors.<span style="mso-spacerun:yes">&nbsp; </span>The OIG and CMS are seeking comments on whether other individuals or entities with front-line patient care responsibilities should be included, such as safety net providers.<span style="mso-spacerun:yes">&nbsp; </span>They are also considering whether to retain the current definition of protected donors but to exclude certain suppliers of ancillary services, such as laboratory companies, durable medical equipment suppliers, and independent home health agencies. &nbsp;The proposed limitation on the scope of permissible donors is viewed as a means to prevent donations that subvert the intent of the safe harbor and exception by locking in referrals.<span style="mso-spacerun:yes">&nbsp; </span>The OIG and CMS also invited comments on what new or modified conditions could be added to achieve the goals of:<span style="mso-spacerun:yes">&nbsp; </span>1) preventing the misuse of the safe harbor and exception that results in data and referral lock-in; and 2) of encouraging the free exchange of data in accordance with protections of privacy.</span></p>
<p><span style="mso-spacerun:yes">Finally, the preambles to the 2006 Final Rules for the safe harbor and exception defined the term<span style="mso-spacerun:yes">&nbsp; </span>&ldquo;&rsquo;software, information technology and training services necessary and used predominantly&rsquo; for electronic health records purposes&rdquo; to include the following, by way of example:<span style="mso-spacerun:yes">&nbsp; </span>[i] interface and translation software; rights, licenses, and intellectual property related to electronic health records software; connectivity services, including broadband and wireless internet services; clinical support and information services related to patient care (but not separate research or marketing support services); maintenance services; secure messaging (e.g., permitting physicians to communication with patients through electronic<span style="mso-spacerun:yes">&nbsp; </span>messaging); training and support services (such as access to help desk services). <span style="mso-spacerun:yes">&nbsp;</span>Both the OIG and CMS declined the request to include this definition in the regulatory text but requested public input on the issue.</span></p>]]>
</content>
</entry>
<entry>
<title>Louisiana&apos;s Unique Retainage Escrow Requirements for Construction Contracts</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/construction-law-louisianas-unique-retainage-escrow-requirements-for-construction-contracts.html" />
<modified>2013-05-15T16:13:44Z</modified>
<issued>2013-04-05T21:41:34Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.373442</id>
<created>2013-04-05T21:41:34Z</created>
<summary type="text/plain">By G. Trippe Hawthorne Background of Louisiana Revised Statute 9:4815 Louisiana has a unique statute in its Private Works Act which requires owners to deposit retainage funds in an interest bearing escrow account for construction contracts over $50,000. While a...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Construction Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192723.html">G. Trippe Hawthorne</a></p>
<p><strong>Background of Louisiana Revised Statute 9:4815</strong></p>
<p>Louisiana has a unique statute in its Private Works Act which requires owners to deposit retainage funds in an interest bearing escrow account for construction contracts over $50,000.  While a number of other states have statutory provisions as to how much retainage may be withheld under a construction contract, Louisiana&rsquo;s statute, which does not regulate those substantive terms, instead dictates how those funds are handled during the course of the project.</p>
<p>The statute, found at Louisiana Revised Statute 9:4815, was added to the Private Works Act by <a href="http://www.louisianalawblog.com/Act%20638%20of%202010.pdf">Act 638 of 2010</a>.  While the bill as originally introduced applied to all funds withheld from periodic payments by an Owner, the final version of the Act applies only to &ldquo;retainage.&rdquo;<br />
&nbsp;</p>]]>
<![CDATA[<p><strong>Requirements of the Retainage Statute</strong></p>
<p>The retainage statute applies to construction contracts over $50,000.  It requires the owner to deposit funds withheld from periodic payments as retainage into an interest bearing escrow account.</p>
<p>The retainage statute primarily applies to commercial construction, as residential and industrial construction projects are generally included within the Act&rsquo;s express exclusions for single family or double family residences and various industrial facilities.</p>
<p>The retainage statute requires that the escrow account be under the control of an escrow agent mutually agreeable to the owner and contractor and provides specific guidelines for when the disputed and undisputed retainage funds should be released following completion of the work.</p>
<p>Last, the retainage statute provides a qualified immunity for the escrow agent and financial institution where the escrow account is maintained.</p>
<p><strong>Limited Application</strong></p>
<p>Since its introduction in 2010, this escrow requirement has been largely ignored in practice, due in large part to the absence of any penalty or enforcement mechanisms.</p>
<p><strong>Waiver</strong></p>
<p>It has become common practice in construction agreements executed since 2010 for the parties to waive the escrow requirements of the Act.  The question of whether or not the provisions of the retainage statute can be waived has been the subject of some debate.  On one hand, the language of 9:4815 is imperative.  It says that the retainage, &ldquo;shall be deposited by the owner into an interest bearing account.&rdquo;  On the other side of the argument is the absence of any penalty or enforcement mechanism and the current state of Louisiana law, that the broader protections of the Private Works Act are not considered to be matters of public policy, and may be waived.  There are no published decisions addressing this issue.<br />
<br />
<strong>Prospective Amendments</strong></p>
<p>In 2012, the author of Act 638 of 2010 introduced a bill that would have expressly dictated that the requirements of 9:4814 are not waivable (<a href="http://www.louisianalawblog.com/SB340%202012.pdf">SB 340</a>).  He has prefiled a similar bill for the 2013 session, <a href="http://www.louisianalawblog.com/SB%20137%202013.pdf">Senate Bill 137</a>, which would prohibit waiver of the escrow requirements, but which would also raise the contract amount from $50,000 to $500,000.</p>
<p>It will be interesting to see whether SB 137 fares better in 2013 than did SB 340 in 2012.<br />
&nbsp;</p>]]>
</content>
</entry>
<entry>
<title>USCIS Updates Form I-9 for Employment Eligibility Verification</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-uscis-updates-form-i9-for-employment-eligibility-verification.html" />
<modified>2013-03-24T18:03:13Z</modified>
<issued>2013-03-24T18:00:25Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.372606</id>
<created>2013-03-24T18:00:25Z</created>
<summary type="text/plain"><![CDATA[By Zoe W. Vermeulen The U.S. Citizenship and Immigration Services (&ldquo;USCIS&rdquo;) released a revised Employment Eligibility Verification form, Form I-9, on March 8, 2013. The revised form contains formatting changes, the inclusion of additional data fields for employee email addresses...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-2035641.html">Zoe W. Vermeulen</a></p>
<p>The U.S. Citizenship and Immigration Services (&ldquo;USCIS&rdquo;) released a revised Employment Eligibility Verification form, Form I-9, on March 8, 2013. The revised form contains formatting changes, the inclusion of additional data fields for employee email addresses and telephone numbers, and improved instructions. Employers must begin using the new form by May 7, 2013, but should not complete a new Form I-9 for current employees if a properly completed Form I-9 is already on file. The new Form I-9 can be identified by the date 03/08/13 in the bottom left corner of the document. Failure to use the revised Form I-9 after May 7, 2013 is an administrative violation that may result in penalties. The fines for paperwork violations range from $110 to $1,100 per violation.</p>
<p>The number of Form I-9 audits has increased dramatically over the past decade, rising from only three audits in 2004, to 500 audits in 2008, and 3,004 audits in 2012. I-9 audits may result from unhappy former employees complaining to the U.S. Immigration and Customs Enforcement (&ldquo;ICE&rdquo;). ICE may also target employers connected to the U.S. infrastructure, such as power plants and food-service businesses.</p>
<p>Employers are required to complete a Form I-9 for each new employee hired in the United States in order to verify the identity and employment authorization of the individual. Form I-9 is not filed with USCIS or any other government agency. Rather, an employer must retain Form I-9 for three years after the employee&rsquo;s date of hire or one year after the date the employment ends, whichever is later. An employer&rsquo;s I-9 Forms are subject to inspection by the Department of Homeland Security, the Department of Labor, and the Office of Special Counsel for Immigration-Related Unfair Employment Practices.</p>
<p>Employers can download the new form and instructions <a href="http://www.uscis.gov/files/form/i-9.pdf">here</a>.&nbsp; <br />
&nbsp;</p>]]>

</content>
</entry>
<entry>
<title>In Through the Out Door:  Preparing for Your Business Exit Opportunity</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/business-and-corporate-in-through-the-out-door-preparing-for-your-business-exit-opportunity.html" />
<modified>2013-03-21T13:52:33Z</modified>
<issued>2013-03-20T19:28:54Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.372386</id>
<created>2013-03-20T19:28:54Z</created>
<summary type="text/plain"><![CDATA[On April 11, Kean Miller's Merger &amp; Acquisition team will present a business briefing In Through the Out Door: Preparing for Your Business Exit Opportunity. The program will be held from 3:15 - 6:00 PM at the Baton Rouge office...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Business and Corporate</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>On April 11, Kean Miller's <a href="http://www.keanmiller.com/lawyer-attorney-1265723.html">Merger &amp;&nbsp;Acquisition team</a> will present a business briefing <em>In Through the Out Door:&nbsp; Preparing for Your Business Exit Opportunity</em>.&nbsp; The program will be held from 3:15 - 6:00 PM at the Baton Rouge office of Kean Miller LLP&nbsp;(II City Plaza, 400 Convention Street, 7th Floor, 70802).</p>
<p>The program will provide an in-depth briefing on closely-held, private company mergers and acquisitions.&nbsp; Attendees will learn about business and legal challenges of an exit strategy, key issues to be aware of, and the risks and rewards in preparing for, marketing, structuring and executing an exit sale of a business.</p>
<p>Speakers include Kean Miller attorneys <a href="http://www.keanmiller.com/lawyer-attorney-1189851.html">Dean Cazenave</a>, <a href="http://www.keanmiller.com/lawyer-attorney-1190046.html">Blane Clark</a>,<a href="http://www.keanmiller.com/lawyer-attorney-1189971.html"> Linda Clark</a>, <a href="http://www.keanmiller.com/lawyer-attorney-2001011.html">Andrew Goodman</a>, <a href="http://www.keanmiller.com/lawyer-attorney-1192600.html">Ed Hardin</a>, <a href="http://www.keanmiller.com/lawyer-attorney-1496127.html">Matthew Meiners</a>, <a href="http://www.keanmiller.com/lawyer-attorney-1194126.html">Mark Mese</a> and <a href="http://www.keanmiller.com/lawyer-attorney-1194156.html">Carey Messina</a>.</p>
<p>Click <a href="http://www.keanmiller.com/docs/kean_miller_mergers_and_acquisitions_seminar_-_april_2013_-_updated.pdf">here</a> for the invitation.</p>
<p>If you are interested in attending, please RSVP to <a href="javascript:location.href='mailto:'+String.fromCharCode(114,115,118,112,64,107,101,97,110,109,105,108,108,101,114,46,99,111,109)+'?subject=RSVP'">rsvp@keanmiller.com</a> or 225.389.3753.</p>]]>

</content>
</entry>
<entry>
<title>&quot;Artificially Impaired&quot; Creditors Can Vote on Chapter 11 Plans in the Fifth Circuit</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/bankruptcy-and-business-reorganization-artificially-impaired-creditors-can-vote-on-chapter-11-plans-in-the-fifth-circuit.html" />
<modified>2013-03-12T19:38:54Z</modified>
<issued>2013-03-12T19:27:34Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.371891</id>
<created>2013-03-12T19:27:34Z</created>
<summary type="text/plain"><![CDATA[By J. Eric Lockridge and Benjamin M. Anderson The U.S. Fifth Circuit Court of Appeals dealt a blow to secured creditors in a recent opinion affirming a successful &ldquo;cramdown&rdquo; reorganization plan in a commercial real estate (&ldquo;CRE&rdquo;) case. See In...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Bankruptcy and Business Reorganization</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1193394.html">J. Eric Lockridge</a> and <a href="http://www.keanmiller.com/lawyer-attorney-1496095.html">Benjamin M. Anderson</a></p>
<p>The U.S. Fifth Circuit Court of Appeals dealt a blow to secured creditors in a recent opinion affirming a successful &ldquo;cramdown&rdquo; reorganization plan in a commercial real estate (&ldquo;CRE&rdquo;) case.  <em>See In re Village at Camp Bowie I, L.P.</em>, --- F.3d --- (5th Cir. Feb. 26, 2013), 2013 WL 690497.  The panel opinion in <em>Bowie </em>allowed a debtor in CRE bankruptcy case to intentionally delay paying trade debt that it had cash available to pay and to classify those trade creditors as &ldquo;impaired&rdquo; under Chapter 11 &ndash; thus giving a class of friendly creditors the ability to vote for the debtor&rsquo;s plan of reorganization.  The court expressly rejected the argument that &ldquo;artificially impaired&rdquo; creditors that a debtor could pay in full, like the trade creditors in <em>Bowie</em>, should not be allowed to vote on a Chapter 11 plan.  The result in <em>Bowie </em>was a confirmed plan based on the vote of unsecured creditors owed $60,000 over the objection of the fully secured creditor owed $32 million.</p>
<p>In <em>Bowie</em>, the debtor financed the acquisition and development of land in Fort Worth (the &ldquo;Property&rdquo;) with equity capital and short-term promissory notes (the &ldquo;Notes&rdquo;).  The Notes were secured by a first mortgage on the Property.  The debtor&rsquo;s development of offices and retail did not do as well as planned.  After a series of modification agreements and forbearance agreements to extend the due dates for the Notes, the then-current holder of the Notes initiated foreclosure proceedings on the Property.  The debtor filed its petition for relief under Chapter 11 of the Bankruptcy Code one day before the scheduled foreclosure sale, which stayed the foreclosure proceedings.<br />
&nbsp;</p>]]>
<![CDATA[<p>The debtor filed a reorganization plan that divided its creditors into only two classes &ndash; one for the fully secured creditor, i.e. the owner and holder to the Notes, owed approximately $32,000,000, and one for the debtor&rsquo;s unsecured trade creditors owed approximately $60,000.  Although the debtor had enough cash on hand at confirmation to pay its trade creditors, the plan provided that the trade creditors would be paid over ninety (90) days.  The trade creditors voted to accept the plan while the secured creditor voted against it.  The secured creditor argued that the trade creditors should not be allowed to vote because they were &ldquo;artificially impaired&rdquo; for the purpose of creating an accepting class of creditors.  The creation of an artificially impaired class &ndash; here, the trade creditors that could have been paid from cash on hand &ndash; violates the &ldquo;good faith&rdquo; required of Chapter 11 plans found in 11 U.S.C. &sect;1129(a)(3), according to the secured creditor.   The bankruptcy court overruled the secured creditor&rsquo;s objection and confirmed the plan under the &ldquo;cramdown&rdquo; provision in 11 U.S.C. &sect;1129.</p>
<p>The secured creditor urged its &ldquo;artificial impairment&rdquo; and &ldquo;good faith&rdquo; arguments on appeal to the Fifth Circuit, which had not squarely addressed the issue before.  The Fifth Circuit noted that other circuits are divided over the question of &ldquo;whether &sect;1129(a)(10) draws a distinction between artificial and economically driven impairment.&rdquo;  For example, the Eight Circuit recognizes impairment only to the extent that it is driven by economic need.  <em>See In re Windsor on the Rivers Associates, Ltd.,</em> 7 F.3d 127 (8th Cir. 1993).  Stated differently, a claim is not really &ldquo;impaired,&rdquo; and thus not eligible to vote on the plan, if the impairment is a result of the debtor&rsquo;s discretion rather than economic necessity.  On the other hand, the Ninth Circuit does not distinguish between discretionary and economically driven impairment.  <em>See Matter of L &amp; J Associates</em>, 995 F.2d 940 (9th Cir. 1993).</p>
<p>In <em>Bowie</em>, the Fifth Circuit held that the &ldquo;impairment&rdquo; requirement in 11 U.S.C. &sect;1129(a)(10) does not distinguish between an impairment created at the debtor&rsquo;s discretion and impairment dictated by economic necessity.  The Fifth Circuit expressly rejected the secured creditor&rsquo;s argument and the Eighth Circuit&rsquo;s view of what qualifies as an &ldquo;impaired claim.&rdquo;  As a result, a debtor, in the Fifth Circuit, may purposefully delay paying unsecured creditors for the purpose of creating an accepting &ldquo;impaired&rdquo; class, despite having enough cash on hand to pay them at confirmation.</p>
<p>The <em>Bowie </em>opinion does have something positive for secured creditors dealing with undersecured single asset real estate (&ldquo;SARE&rdquo;) cases.  Footnote 30 to the <em>Bowie </em>opinion states that in a SARE where the creditor is undersecured, the creditor&rsquo;s deficiency claim should be placed in the same class as the debtor&rsquo;s unsecured debt.  Debtors often argue that a lender&rsquo;s deficiency claim is different than other unsecured debt and should be place in its own class, thus improving their chances of having at least one class of creditors vote in favor of a proposed plan.  Footnote 30 in <em>Bowie</em>, however, gives an undersecured creditor good support for the argument that its deficiency claim should be classified with the other unsecured claims, which may give that creditor the opportunity to control the unsecured class&rsquo;s vote on the plan and prevent the debtor from cramming down an unwanted plan under 11 U.S.C. &sect;1129(a)(10).<br />
&nbsp;</p>]]>
</content>
</entry>
<entry>
<title>What&apos;s in a Name?  Classifying Someone as an &quot;Employee&quot; or an &quot;Independent Contractor&quot; Can Have Significant Effects</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-whats-in-a-name-classifying-someone-as-an-employee-or-an-independent-contractor-can-have-significant-effects.html" />
<modified>2013-02-28T15:27:49Z</modified>
<issued>2013-02-28T15:17:41Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.371065</id>
<created>2013-02-28T15:17:41Z</created>
<summary type="text/plain"><![CDATA[By A. Edward Hardin, Jr. &ldquo;What is in a name? That which we call a rose. By any other name would smell as sweet . . .&rdquo; -William Shakespeare, Romeo and Juliet Roses aside, classifying someone as an &ldquo;employee&rdquo; or...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192600.html">A. Edward Hardin, Jr.</a></p>
<p><em>&ldquo;What is in a name? That which we call a rose.  By any other name would smell as sweet . . .&rdquo;</em></p>
<p>-William Shakespeare, <em>Romeo and Juliet</em></p>
<p>Roses aside, classifying someone as an &ldquo;employee&rdquo; or an &ldquo;independent contractor&rdquo; (or rather misclassifying them) can have significant effects.  The misclassification of employees as independent contractors is the focus of a U.S. Department of Labor Wage and Hour Division enforcement initiative.  The DOL and the IRS have joined forces and signed a memorandum of understanding that will allow the sharing of information across the two agencies in an effort to improve compliance.  More importantly, the Louisiana Workforce Commission has likewise entered into an agreement with the DOL to establish &ldquo;a collaborative relationship to promote compliance...&quot;&nbsp; For more information on the enforcement initiative and other states who have signed similar agreements with the DOL click <a href="http://www.dol.gov/whd/workers/misclassification/">here</a>.&nbsp;</p>
<p>The potential cost of misclassification of employees as independent contractors can be high.  For example, the DOL recently obtained a $1.3 million <a href="http://www.dol.gov/opa/media/press/whd/WHD20130066.htm">consent judgment</a> against a technology company that had misclassified employees as independent contractors. So, what is in a name (or classification) can be very important.<br />
&nbsp;</p>]]>

</content>
</entry>
<entry>
<title>A New Definition to &quot;Religious Employer&quot; under the Affordable Care Act</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/health-law-a-new-definition-to-religious-employer-under-the-affordable-care-act.html" />
<modified>2013-02-20T22:30:51Z</modified>
<issued>2013-02-20T22:25:38Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370571</id>
<created>2013-02-20T22:25:38Z</created>
<summary type="text/plain"><![CDATA[By Jennifer J. Thomas On January 30, 2013, the U.S. Department of the Treasury, the Department of Labor, and the Department of Health and Human Services (the &ldquo;Departments&rdquo;) issued proposed regulations to amend to exempt group health plans established or...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Health Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1195346.html">Jennifer J. Thomas</a></p>
<p>On January 30, 2013, the U.S. Department of the Treasury, the Department of Labor, and the Department of Health and Human Services (the &ldquo;Departments&rdquo;) issued proposed regulations to amend to exempt group health plans established or maintained by certain &ldquo;religious employers&rdquo; with respect to the Affordable Care Act (&quot;ACA&quot;) requirement to cover contraceptive services.  The ACA currently requires non-exempt, non-grandfathered group health plans to provide, without cost-sharing by employees, certain preventive health services including contraceptive services, sterilization, and abortion services.  In response to concerns that this requirement violates religious beliefs of employers, the Departments have promulgated proposed amendments to the regulations.</p>
<p>The proposed regulations amend the criteria for the religious employer exemption.  The current definition of &ldquo;religious employer&rdquo; requires that the employer:</p>
<ol>
    <li>Has the inculcation of religious values as its purpose;</li>
    <li>Primarily employs persons who share its religious tenets;</li>
    <li>Primarily services persons who share its religious tenets; and</li>
    <li>Is a non-profit organization described in Section 6033(a)(1)(a)(3)(A)(i) or 			(iii) of the Internal Revenue Code.</li>
</ol>
<p>The proposed regulations revise the definition of &quot;religious employer&quot; to eliminate the first three prongs listed above, but maintain prong number four.  Section 6033 of the Internal Revenue Code refers to churches, their integrated auxiliaries, and conventions or associations of churches, as well as to the exclusively religious activities of any religious order.  The Departments have represented that with the revised definition there will &ldquo;no longer be any question as to whether group health plans of houses of worship that provide educational, charitable, or social services to their communities qualify for the exemption.&rdquo;<br />
&nbsp;</p>]]>
<![CDATA[<p>The proposed regulations also establish accommodations for health coverage established and maintained by &quot;eligible organizations.&quot;  To meet the definition of &quot;eligible organization,&quot; an organization must meet all of the following criteria:</p>
<ol>
    <li>The organization opposes providing coverage for some or all of the contraceptive services required to be covered under Section 2713 of the Public Health Service Act on account of religious objections;</li>
    <li>The organization is organized and operates as a non-profit entity;</li>
    <li>The organization holds itself out as a religious organization; and</li>
    <li>The organization self-certifies that it satisfies the first three criteria.</li>
</ol>
<p>The purpose of the accommodation is to provide women with contraceptive coverage without cost- sharing and without the eligible organization having to contract, arrange, or provide contraceptive coverage.  Instead, the health insurance issuer providing group health coverage maintained by an eligible organization would assume sole responsibility to provide contraceptive coverage without cost-sharing, premium fee, or other charge to plan participants and beneficiaries.  For this accommodation to apply, the eligible organization presents its health insurance issuer with a self-certification specifying the contraceptive services that the eligible organization will not establish, maintain, administer, or fund coverage.  The health insurance issuer will automatically enroll plan participants in separate individual health insurance policies that cover the recommended contraceptive services and assume all costs associated with providing that separate contraceptive coverage.</p>
<p>The Departments are seeking comments to the proposed regulations on or before April 8, 2013.  The proposed regulations are intended to become final before August 1, 2013.<br />
&nbsp;</p>]]>
</content>
</entry>
<entry>
<title>Not Every Boat is a Vessel:  Lozman v. City of Riviera Beach</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/admiralty-and-maritime-not-every-boat-is-a-vessel-lozman-v-city-of-riviera-beach.html" />
<modified>2013-02-19T22:21:38Z</modified>
<issued>2013-02-19T22:10:50Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370470</id>
<created>2013-02-19T22:10:50Z</created>
<summary type="text/plain">By Stephen C. Hanemann Practically speaking, a houseboat is still a vessel. But the same is not true for every floating house. And just when we thought that the highest tribunal in the land had a fast hold on its...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Admiralty and Maritime</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192533.html">Stephen C. Hanemann</a></p>
<p>Practically speaking, a houseboat is still a vessel.  But the same is not true for every floating house.  And just when we thought that the highest tribunal in the land had a fast hold on its commitment to expanding the definition of a vessel, the Supreme Court issues a holding that not only creates confusion by curtailing its existing definition, but also indicates a new method for determining if a floating structure is, in fact, a vessel.<span style="font-size: smaller;">(1)</span>&nbsp;&nbsp; Owners of residences afloat throughout the United States admiralty jurisdiction, now wonder, &ldquo;Is my houseboat a vessel?&rdquo;  Houseboat owners, you are not alone!  Maritime attorneys and judges alike try to answer the same question secondary to the Supreme Court&rsquo;s recent contribution to the ever-developing jurisprudence attempting to define a vessel.</p>
<p>The controversial subject of the Supreme Court&rsquo;s latest vessel status pronouncement arose in 2006 when Fane Lozman docked his 60&rsquo;x 12&rsquo; floating home in a marina owned by the City of Riviera Beach, Florida.  Lozman&rsquo;s abode  &mdash;  equipped with French doors on 3 sides, a sitting room, bedroom, closet, kitchen, and an office  &mdash;  remained at the Riviera Beach Marina until the City, despite the absence of admiralty jurisdiction, filed an <em>in rem</em> suit against the vessel, purchased the home at auction, and destroyed it.  The district court and the 11th Circuit Court of Appeals both found admiralty jurisdiction to exist holding that the home was a vessel.  The Supreme Court reversed the judgment of the Court of Appeals finding that Fane Lozman owned nothing more than a floating house.  <br />
&nbsp;</p>]]>
<![CDATA[<p>The Supreme Court&rsquo;s reasonable observer test led to its conclusion that Fane Lozeman&rsquo;s floating residence was not a vessel.  But the Court did not hold that a houseboat is not a vessel.  The ruling  &mdash;  with the potential to narrow the legal liability for those owning dockside casinos or even floating businesses  &mdash;  does not necessarily spell relief for existing Jones Act employers.</p>
<p>The Rules of Construction Act defines a &ldquo;vessel&rdquo; as including &ldquo;every description of water craft or other artificial contrivance used, or capable of being used, as a means of transportation on water.&rdquo;<span style="font-size: smaller;">(2)&nbsp;</span>&nbsp; The quandary that has befuddled jurists for over 150 years is determining which floating structures fall within the definition.  And because there is no all-encompassing list of items which are vessels, the debate continues.  In fact, even the Supreme Court has reached dissimilar vessel status conclusions for similar structures based on individual characteristics and design.<span style="font-size: smaller;">(3)&nbsp;</span></p>
<p>Justice Breyer&rsquo;s opinion &mdash; alluding to familiar fictional fables &mdash; sets forth obvious examples of artificial contrivances that are not vessels, including Pinocchio&rsquo;s whale, a plastic dishpan, and a wooden washtub.  But here&rsquo;s the rub-a-dub-dub:  a floating structure possessing physical characteristics, which lead a reasonable observer to conclude that it was designed to a practical degree for carrying people or things over water is  &mdash;   in the opinion of the U.S. Supreme Court  &mdash;  a vessel.  The Court&rsquo;s holding, in addition to considering the many non-vessel-like-qualities of Fane Lozman&rsquo;s floating house, focused on the practical possibilities of the structure&rsquo;s use as a means of transportation on water.<span style="font-size: smaller;">(4)</span>&nbsp; But for its ability to float, Lozman&rsquo;s house differed quite significantly from an ordinary houseboat as it had no steering mechanism, no propulsion, a rectangular bottom, and no capacity to generate or store electricity.</p>
<p>And how is the Supreme Court&rsquo;s unexpected narrowing of that which constitutes a vessel going to preserve or alter the maritime&rsquo;s industry vessel status quo?  Certainly, a reasonable observer, looking at a Single Point Anchor Reservoir would not consider it practically designed for transporting people or things over water.</p>
<p>___________________________________________________</p>
<p><em><span style="font-size: smaller;">(1) Lozman v. City of Riviera Beach, Fla., 133 S.Ct. 735 (2013).<br />
</span></em><em><span style="font-size: smaller;">(2)&nbsp; 1 U.S.C. &sect; 3.<br />
</span></em><em><span style="font-size: smaller;">(3)&nbsp; See Evansville &amp; Bowling Green Packet Co. v. Checo Cola Bottling Co., 271 U.S. 19, 46 S.Ct. 379, 70 L.Ed. 805 (1926) (Holding that a floating wharf boat used to transfer cargo was not a vessel); See Also Stewart v. Dutra Constr. Co., 543 U.S. 481, 125 S.Ct. 1118, 160 L.Ed. 2d 932 (2005) (Holding that a floating dredge used to remove silt from the ocean floor was a vessel).<br />
</span></em><em><span style="font-size: smaller;">(4)&nbsp; Stewart, 543 U.S. at 496.</span></em><br />
<br />
&nbsp;</p>]]>
</content>
</entry>
<entry>
<title>EEOC Seeks Public Input On Quality Control Plan</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-eeoc-seeks-public-input-on-quality-control-plan.html" />
<modified>2013-02-19T00:40:19Z</modified>
<issued>2013-02-19T00:36:27Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370370</id>
<created>2013-02-19T00:36:27Z</created>
<summary type="text/plain"><![CDATA[By Zoe Vermeulen The U.S. Equal Employment Opportunity Commission (&ldquo;EEOC&rdquo;) is seeking public input into a Quality Control Plan it is developing as part of its Strategic Plan for the fiscal years 2012-2016. The Strategic Plan provides the framework by...]]></summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-2035641.html">Zoe Vermeulen</a></p>
<p>The U.S. Equal Employment Opportunity Commission (&ldquo;EEOC&rdquo;) is seeking public input into a Quality Control Plan it is developing as part of its Strategic Plan for the fiscal years 2012-2016. The Strategic Plan provides the framework by which the EEOC accomplishes its mission to stop and remedy unlawful employment discrimination. The Quality Control Plan will revise the criteria by which the EEOC evaluates the quality of its investigations and conciliations. Criteria currently used by the EEOC measure whether a charge has been correctly categorized and filed within the agency&rsquo;s data system, but do not measure whether charges are appropriately reassessed on a timely basis, how efficient and timely the investigation has been, what the investigation consisted of, or whether the investigator correctly applied the law to the facts of the charge. The EEOC would like recommendations for criteria to assess the quality of its investigations or conciliations or general recommendations for improving the quality of its intake process, investigations, and conciliations.</p>
<p>Suggestions must be submitted to the EEOC by 5:00 p.m. EDT on Friday, March 1, 2013 and should be submitted electronically to <a href="javascript:location.href='mailto:'+String.fromCharCode(115,116,114,97,116,101,103,105,99,46,112,108,97,110,64,101,101,111,99,46,103,111,118)+'?'">strategic.plan@eeoc.gov</a> or by mail at Executive Officer, Office of the Executive Secretariat, U.S. Equal Employment Opportunity Commission, 131 M Street, NE, Washington, D.C. 20507. Submissions should include a contact e-mail and/or mailing address. Submissions will be reviewed for possible inclusion in a future EEOC Commission meeting in Washington, D.C. and if a submission is selected, the author or a representative will be invited to testify before the Commission.</p>
<p>The EEOC is responsible for enforcing federal laws prohibiting employment discrimination. These laws include Title VII of the Civil Rights Act of 1964, the Pregnancy Discrimination Act, the Equal Pay Act of 1963, the Age Discrimination in Employment Act of 1967, and Title I of the Americans with Disabilities Act of 1990. <br />
&nbsp;</p>]]>

</content>
</entry>
<entry>
<title>OSHA Seeks Public Comment On Proposed Online Whistleblower Complaint Form</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-osha-seeks-public-comment-on-proposed-online-whistleblower-complaint-form.html" />
<modified>2013-02-15T23:13:52Z</modified>
<issued>2013-02-15T22:59:43Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370255</id>
<created>2013-02-15T22:59:43Z</created>
<summary type="text/plain">By Scott D. Huffstetler The Occupational Safety and Health Administration (OSHA) is seeking public comments regarding a proposal for a new online whistleblower complaint form. The form, which would allow whistleblowers to electronically submit whistleblower complaints directly to OSHA, is...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192913.html">Scott D. Huffstetler</a></p>
<p>The Occupational Safety and Health Administration (OSHA) is seeking public comments regarding a proposal for a new online whistleblower complaint form.  The form, which would allow whistleblowers to electronically submit whistleblower complaints directly to OSHA, is part of OSHA&rsquo;s proposal to revise the information collection requirements for handling retaliation complaints filed with OSHA under various whistleblower protection statutes.  The proposal may be accessed electronically <a href="https://www.federalregister.gov/articles/2013/01/17/2013-00866/revision-of-approved-information-collection-paperwork-requirements-for-office-of-management-and">here</a>, and comments are due on or before March 18, 2013.</p>
<p>OSHA is responsible for investigating alleged violations of whistleblower provisions contained in a number of statutes.  These statutes include:</p>
<ul>
    <li>Occupational Safety and Health Act, 29 U.S.C. 660</li>
    <li>Asbestos Hazard Emergency Response Act, 15 U.S.C. 2651</li>
    <li>International Safe Container Act, 46 U.S.C. 80507</li>
    <li>Safe Drinking Water Act, 42 U.S.C. 300j-9(i)</li>
    <li>Federal Water Pollution Control Act, 33 U.S.C. 1367</li>
    <li>Toxic Substances Control Act, 15 U.S.C. 2622</li>
    <li>Solid Waste Disposal Act, 42 U.S.C. 6971</li>
    <li>Clean Air Act, 42 U.S.C. 7622</li>
    <li>Energy Reorganization Act of 1974, 42 U.S.C. 5851</li>
    <li>Comprehensive Environmental Response, Compensation and Liability Act, 42 U.S.C. 9610</li>
    <li>Wendell H. Ford Aviation Investment and Reform Act for the 21st Century</li>
    <li>Corporate and Criminal Fraud Accountability Act of 2002 (Title VIII of the Sarbanes-Oxley Act of 2002)</li>
    <li>Pipeline Safety and Improvement Act of 2002</li>
    <li>National Transit Systems Security Act and the Federal Railroad Safety Act</li>
    <li>Consumer Product Safety Improvement Act of 2008</li>
    <li>Affordable Care Act, 29 U.S.C. 218C</li>
    <li>Consumer Financial Protection Act, Section 1057 of the Dodd Frank Wall Street Reform and Consumer Protection Act, Public Law 111-203</li>
    <li>Seaman's Protection Act, 46 U.S.C. 2114, as amended by Section 611 of the Coast Guard Authorization Act of 2010, Public Law 111-281</li>
    <li>Section 402 of the FDA Food Safety and Modernization Act, Public Law 111-353</li>
    <li>Section 31307 of the Moving Ahead for Progress in the 21st Century Act, 49 U.S.C. 30171</li>
</ul>
<p>The electronic form expands the methods in which a whistleblower may submit a complaint to OSHA under one of these statutes &ndash; either by submitting the form electronically directly through the Internet; or by downloading, completing, and submitting the form to OSHA by fax, mail, or hand-delivery.  The proposed form will enable workers to electronically submit whistleblower complaints directly to OSHA 24-hours a day.  Last year, a record number of whistle-blower cases were filed and resolved by OSHA.  This was after a series of initiatives were launched during the 2012 fiscal year to strengthen OSHA&rsquo;s whistleblower protection programs.  It is believed that the current proposals, if accepted and initiated in 2013, will result in an even greater number of OSHA whistleblower claims being filed.</p>]]>

</content>
</entry>
<entry>
<title>Law Firm&apos;s Cost Advances for Contingency Fee Cases Treated as Loans and not Current Deductions</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/state-and-local-taxation-law-firms-cost-advances-for-contingency-fee-cases-treated-as-loans-and-not-current-deductions.html" />
<modified>2013-02-14T20:10:21Z</modified>
<issued>2013-02-14T20:05:47Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370122</id>
<created>2013-02-14T20:05:47Z</created>
<summary type="text/plain">By Kevin C. Curry In a recent Tax Court case, a law firm was denied a current deduction for litigation expenses advanced on behalf of its contingent fee clients. The Tax Court held that the expenses were in nature of...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>State and Local Taxation</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1190226.html">Kevin C. Curry</a></p>
<p>In a recent Tax Court case, a law firm was denied a current deduction for litigation expenses advanced on behalf of its contingent fee clients.  The Tax Court held that the expenses were in nature of loans, and not ordinary and necessary business expenses that could be deducted when paid (advanced), even if there was low likelihood of reimbursement.   At issue in the case were both expenses for contingency fee cases with individual clients as well as class action cases.  The Tax Court found the cost advances in both types of cases to be loans and not currently deductible.  With respect to the contingency fee cases with individual clients, the taxpayer had a system for classifying cases as high risk vs. low risk and would only deduct the advances on the higher risk cases.  Only the advances for the low risk cases were booked as loans.  The Tax Court found that there was a significant likelihood for reimbursement of the expenses advanced and stated that a low likelihood of recovery does not justify deductibility when advanced.  With respect to the class action cases, the taxpayer argued that advanced expenses in class action cases were not loans and were therefore deductible because expense awards required court approval and/or there was &ldquo;no identifiable obligor&rdquo; until judgment was entered.  The Tax Court rejected this argument on the basis that the taxpayer was entitled to reimbursement of those expenses from class members under common-fund doctrine.</p>
<p><em><span style="font-size: smaller;">(Humphrey, Farrington &amp; McClain, P.C. v. Commissioner, (2013) TC Memo 2013-23, 2013 RIA TC Memo &para;2013-23).</span></em></p>]]>

</content>
</entry>
<entry>
<title>DOL Rolls Out Revised FMLA Regulations</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-dol-rolls-out-revised-fmla-regulations.html" />
<modified>2013-02-13T15:20:11Z</modified>
<issued>2013-02-13T15:13:51Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.370015</id>
<created>2013-02-13T15:13:51Z</created>
<summary type="text/plain">By A. Edward Hardin, Jr. February 5, 2013, the U.S. Department of Labor issued its final rule rolling out new amendments to the FMLA regulations that correspond with military related leaves of absence. The FMLA was amended in 2008 and...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192600.html">A. Edward Hardin, Jr.</a>&nbsp;</p>
<p>February 5, 2013, the U.S. Department of Labor issued its final rule rolling out new amendments to the FMLA regulations that correspond with military related leaves of absence.&nbsp; The FMLA was amended in 2008 and 2010 to provide leave rights for military families.&nbsp; The amended regulations implement changes made to the FMLA.&nbsp; In addition, the prior FMLA regulations included appendices with model forms.&nbsp; The appendices were removed from the revised regulations to allow the DOL&nbsp;greater flexibility to make non-substantive changes to the forms.&nbsp; Although the forms will no longer be in the regulations, they will still be available from the DOL.&nbsp; You may need to amend your current practices, posters, and/or your employee handbooks to comply with the new regulations.&nbsp; The new regulations will take affect March 8, 2013.</p>
<p>&nbsp;</p>]]>

</content>
</entry>
<entry>
<title>NLRB Recess Appointments Held Unconstitutional</title>
<link rel="alternate" type="text/html" href="http://www.louisianalawblog.com/labor-and-employment-law-nlrb-recess-appointments-held-unconstitutional.html" />
<modified>2013-01-28T13:00:18Z</modified>
<issued>2013-01-25T23:43:25Z</issued>
<id>tag:www.louisianalawblog.com,2013://81.368815</id>
<created>2013-01-25T23:43:25Z</created>
<summary type="text/plain">By A. Edward Hardin, Jr. and Erin L. Kilgore Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 In a unanimous 3-0 decision, on January 25, 2013, the U.S. Court of Appeals for the D.C. Circuit Court held that President...</summary>
<author>
<name>Steven Boutwell</name>

<email>steve.boutwell@keanmiller.com</email>
</author>
<dc:subject>Labor and Employment Law</dc:subject>
<content type="text/html" mode="escaped" xml:lang="en" xml:base="http://www.louisianalawblog.com/">
<![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1192600.html">A. Edward Hardin, Jr.</a> and <a href="http://www.keanmiller.com/lawyer-attorney-1348893.html">Erin L. Kilgore</a></p>
<p><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves />
<w:TrackFormatting />
<w:PunctuationKerning />
<w:ValidateAgainstSchemas />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF />
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables />
<w:SnapToGridInCell />
<w:WrapTextWithPunct />
<w:UseAsianBreakRules />
<w:DontGrowAutofit />
<w:SplitPgBreakAndParaMark />
<w:DontVertAlignCellWithSp />
<w:DontBreakConstrainedForcedTables />
<w:DontVertAlignInTxbx />
<w:Word11KerningPairs />
<w:CachedColBalance />
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val="Cambria Math" />
<m:brkBin m:val="before" />
<m:brkBinSub m:val="&#45;-" />
<m:smallFrac m:val="off" />
<m:dispDef />
<m:lMargin m:val="0" />
<m:rMargin m:val="0" />
<m:defJc m:val="centerGroup" />
<m:wrapIndent m:val="1440" />
<m:intLim m:val="subSup" />
<m:naryLim m:val="undOvr" />
</m:mathPr></w:WordDocument>
</xml><![endif]-->In a unanimous 3-0 decision, on January 25, 2013, the U.S. Court of Appeals for the D.C. Circuit Court held that President Obama&rsquo;s three recess appointments to the National Labor Relations Board exceeded his Constitutional authority. &nbsp;</p>
<p>Articles on this decision can be found <a href="http://www.washingtonpost.com/politics/court-says-obama-exceeded-authority-in-making-appointments/2013/01/25/b7e1b692-6713-11e2-9e1b-07db1d2ccd5b_story.html">here</a>, and <a href="http://politicalticker.blogs.cnn.com/2013/01/25/appeals-court-rules-obama-recess-appointments-unconstitutional/?hpt=hp_c1">here</a>.&nbsp;</p>
<p>The decision calls into question all of the Board&rsquo;s rulings and orders issued following the recess appointments.&nbsp; The Supreme Court may ultimately have the last say.&nbsp;&nbsp;Stay tuned.</p>
<p><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" />
<w:LsdException Locked="false" Priority="39" Name="toc 1" />
<w:LsdException Locked="false" Priority="39" Name="toc 2" />
<w:LsdException Locked="false" Priority="39" Name="toc 3" />
<w:LsdException Locked="false" Priority="39" Name="toc 4" />
<w:LsdException Locked="false" Priority="39" Name="toc 5" />
<w:LsdException Locked="false" Priority="39" Name="toc 6" />
<w:LsdException Locked="false" Priority="39" Name="toc 7" />
<w:LsdException Locked="false" Priority="39" Name="toc 8" />
<w:LsdException Locked="false" Priority="39" Name="toc 9" />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" />
<w:LsdException Locked="false" Priority="37" Name="Bibliography" />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" />
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
</style>
<![endif]--></p>]]>

</content>
</entry>

</feed>