<?xml version='1.0' encoding='UTF-8'?>
			<?xml-stylesheet type='text/xsl' href='https://www.fosterswift-ipblog.com/rss.xsl' ?>
			<rss version='2.0' xmlns:content='http://purl.org/rss/1.0/modules/content/'
					xmlns:atom='http://www.w3.org/2005/Atom'
					xmlns:dc='http://purl.org/dc/elements/1.1/'>
				<channel>
					<title>AI Patent Eligibility Under §101 | How Framing the Right Question can Shape
Outcomes | Foster Swift</title>
					<link>https://www.fosterswift-ipblog.com/ai-patent-eligibility-section-101-uspto-decision</link>
					<atom:link href='https://www.fosterswift-ipblog.com/ai-patent-eligibility-section-101-uspto-decision?rss' rel='self' type='application/rss+xml' />
					<description><![CDATA[The latest updates to AI Patent Eligibility Under §101 | How Framing the Right Question can Shape Outcomes.]]></description>
					<lastBuildDate>Fri, 14 Aug 2026 23:59:23 -0400</lastBuildDate>
					
				<item>
				<title>AI Patent Eligibility Under §101: How Framing the Right Question can Shape
Outcomes</title>
				<dc:creator></dc:creator>
<guid isPermaLink='false'>blogpost-ai-patent-eligibility-section-101-uspto-decision</guid>

					<pubDate>Mon, 18 May 2026 09:00:01 -0400</pubDate>
					<content:encoded><![CDATA[<p><a target="_blank" title="Part 1" rel="noopener" href="https://www.fosterswift-ipblog.com/better-IP-strategy-power-answering-right-questions"><strong>In my last post,</strong></a> I wrote about the importance of asking the <em>right question </em>because the answer you get is only as good as the question you ask. That idea is practically universal, it also shows up in how patent eligibility under 35 U.S.C. &sect;101 is being applied, especially for AI and software.</p>
<p>A recent precedential decision from the United States Patent Trademark Office's (USPTO) Appeals Review Panel, <em>Ex parte Desjardins, </em>is a good example of what happens when the wrong question gets asked and then corrected.</p>
<p><strong>The Wrong Question</strong></p>
<p>For a while now, many &sect;101 rejections, particularly in AI, have effectively started from the same place: <em>Does this involve an algorithm, math, or data processing? </em>If the answer is yes, the rest tends to follow:</p>
<ol>
<li>Abstract idea;</li>
<li>Generic computer components;</li>
<li>Rejection.</li>
</ol>
<p>That framing is efficient, it&rsquo;s also incomplete and it&rsquo;s what happened in <em>Desjardins</em>. The claims were reduced to a mathematical concept implemented on a generic computer, and the analysis largely stopped there.</p>
<p><strong>Asking Differently</strong></p>
<p>On rehearing, the Appeals Review Panel didn&rsquo;t ignore the presence of mathematical operations. It acknowledged them but it stepped back and looked at the claims as a whole.</p>
<p>When viewed that way, the system wasn&rsquo;t just performing calculations. It was doing something more specific; it was training a machine learning model in a way that:</p>
<ul>
<li>Reduces storage requirements,</li>
<li>Reduces system complexity, and</li>
<li>Preserves prior learning when training on new tasks (addressing catastrophic forgetting).</li>
</ul>
<p>That is a change in <strong><em>how</em></strong> the system operates and once the <em>question</em> is framed that way, the answer starts to look different.</p>
<p><strong>Familiar Ground</strong></p>
<p>None of this is new. In <em>Enfish, LLC v. Microsoft Corp.</em> (Fed. Cir. 2016), the Federal Circuit made the same point in a different context, recognizing that many advances in computer technology come from improvements to software itself, not just hardware.</p>
<p>We see that play out every day. The shift from physical media to digital platforms didn&rsquo;t happen just because the hardware changed, it happened because the software did, too. The focus, the court explained, is whether the claims are directed to an improvement in computer functionality, rather than an abstract idea. <em>Desjardins</em> didn&rsquo;t move that line, it <u>reinforces</u> it.</p>
<p><strong>A More Direct Observation</strong></p>
<p>The panel was also candid about the risk of getting this wrong. It noted that the earlier analysis effectively treated machine learning as just an &ldquo;algorithm,&rdquo; with everything else dismissed as &ldquo;generic computer components,&rdquo; without really engaging with what the system was doing.</p>
<p>Taken far enough, it creates a broader issue: if everything gets described at a high enough level of generality, it starts to look abstract and when that happens, the analysis stops reflecting the underlying technology.</p>
<p>The panel didn&rsquo;t frame this as a change in doctrine...it didn&rsquo;t need to. The point was simpler: the framework only works if it&rsquo;s applied with some discipline and a willingness to actually understand what the system is doing. In short, <u><strong>be curious!</strong></u></p>
<p><strong>Will this be a win across the board?</strong></p>
<p>Perhaps...for companies working in AI and software, it at least brings the focus back to how the system actually operates: memory usage, processing behavior, model training, system structure.</p>
<p>For practitioners, it creates a more predictable path: identify the technical improvement, and make sure the claims reflect it. For the USPTO, it shifts the analysis away from high-level labels and back toward the underlying mechanics of the technology.</p>
<p><strong>One Point That Hasn&rsquo;t Changed</strong></p>
<p>Even here, the claims in <em>Desjardins</em> remained rejected under &sect;103. The panel made a point of that. Eligibility is not supposed to do all the work. Novelty, obviousness, and written description are still where most of the real filtering happens.</p>
<p><strong>Closing Thoughts</strong></p>
<p>If there&rsquo;s a common thread <a target="_blank" title="Part 1" rel="noopener" href="https://www.fosterswift-ipblog.com/better-IP-strategy-power-answering-right-questions">between the previous post</a> and this one, it&rsquo;s this: The outcome often turns on the question you start with. In the &sect;101 context, that question isn&rsquo;t:</p>
<ul>
<li>&ldquo;Is there math?&rdquo;</li>
<li>&ldquo;Is there an algorithm?&rdquo;</li>
</ul>
<p>It&rsquo;s: <strong>&ldquo;What is this system actually doing, and does that change how the technology operates?&rdquo;</strong></p>
<p>That <em>has</em> been the standard for a while. <em>Desjardins</em> is a reminder that it still is and that how you ask the question, matters just as much as how you answer it.</p>
<p>Want stronger AI and software patents? Connect with our IP team to ensure your claims highlight real technical improvements and withstand &sect;101 scrutiny.</p>]]></content:encoded>
</item>

			</channel></rss>