Decapolis Systems v. Epic Systems: Federal Circuit Appeal Voluntarily Dismissed
Decapolis Systems, LLC asserted two healthcare information processing patents — US7490048B2 and US7464040B2 — against Epic Systems, Corp. in an infringement action that reached the Federal Circuit. The appeal was voluntarily dismissed by agreement after 302 days, with each side bearing its own costs.
A Federal Circuit healthcare IT patent appeal ends by mutual agreement
Decapolis Systems, LLC filed this infringement appeal at the U.S. Court of Appeals for the Federal Circuit on 16 December 2024, naming Epic Systems, Corp. as defendant. The dispute centred on two patents — US7490048B2 and US7464040B2 — both directed to apparatus and methods for processing and providing healthcare information. Epic Systems is one of the dominant electronic health records vendors in the United States, making it a commercially significant target for healthcare IT patent assertions.
The appeal closed on 14 October 2025 when the parties jointly agreed to dismiss the proceeding under Federal Rule of Appellate Procedure 42(b). The order is explicit that each side shall bear its own costs. The basis of termination is recorded as voluntary dismissal. Notably, the dismissal order does not specify whether it is with or without prejudice, and the public record as available is silent on that distinction — a point of material consequence for any future enforcement action by Decapolis.
The 302-day lifespan of the appeal, from filing to dismissal, suggests the parties engaged in substantive negotiations before reaching their agreement — voluntary Federal Circuit dismissals occurring this far into an appeal cycle are often consistent with a negotiated resolution, though nothing in the public record confirms settlement terms. What remains unknown is whether underlying district court proceedings remain live, whether any licence was exchanged, and whether Decapolis retains the right to refile against Epic on these patents.
Filing to Voluntary dismissal in 302 days
302 days from filing to voluntary dismissal at the Federal Circuit level
Voluntarily dismissed: what the Federal Circuit order means for both parties
Fed. R. App. P. 42(b) dismissal — no merits ruling issued
Rule 42(b) allows parties to voluntarily dismiss a Federal Circuit appeal by stipulation. The court issues no ruling on the merits of the underlying patent dispute. This means the appeal record creates no binding precedent on infringement, validity, or claim construction for US7490048B2 or US7464040B2. The dismissal is purely procedural — it closes this appellate proceeding without adjudicating any substantive question.
No merits adjudicationWith or without prejudice? The public record is silent
A voluntary dismissal with prejudice extinguishes the claim permanently; without prejudice, the asserting party may refile. The dismissal order in this case does not specify either. Federal Rule of Appellate Procedure 42(b) does not automatically impose prejudice — that determination typically depends on the parties’ stipulation. Practitioners should treat this ambiguity carefully: Decapolis’s ability to re-assert these patents against Epic remains an open legal question on the face of the public record.
Prejudice terms unresolved publiclyEpic exits without an adverse ruling — but exposure may persist
Epic Systems obtained dismissal of this appellate proceeding without any finding of infringement and without a merits ruling on validity. No costs were awarded against it. However, because no court has ruled on the underlying patents’ validity or scope, Epic cannot point to this dismissal as a shield against future assertion of the same patents. If the dismissal was without prejudice, the patents remain a potential threat to Epic’s healthcare IT products.
No infringement findingHealthcare IT sector: these patents remain unlitigated on the merits
US7490048B2 and US7464040B2 cover healthcare information processing apparatus and methods — a broad and commercially active technology domain. The voluntary dismissal means neither patent has been invalidated or construed by any appellate court. Other healthcare IT vendors and EHR developers operating in this space should note that these patents theoretically remain enforceable. A freedom-to-operate analysis against both patents is advisable for any product touching healthcare information processing.
Patents remain enforceableFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | DECAPOLIS SYSTEMS, LLC | Company | Healthcare IT patent assertion entity — holder of US7490048B2 and US7464040B2Search in Eureka ↗ |
| Defendant | Epic Systems, Corp. | Company | Epic Systems, Corp. — leading U.S. electronic health records and healthcare software providerSearch in Eureka ↗ |
| Plaintiff counsel | Randall T. Garteiser | Attorney | Counsel for DECAPOLIS SYSTEMS, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Garteiser Honea PLLC | Law Firm | Representing DECAPOLIS SYSTEMS, LLCSearch in Eureka ↗ |
| Defendant counsel | Bryce Loken | Attorney | Counsel for Epic Systems, Corp.Search in Eureka ↗ |
| Defendant counsel | Kristin Graham Noel | Attorney | Counsel for Epic Systems, Corp.Search in Eureka ↗ |
| Defendant counsel | Matthew J. Duchemin | Attorney | Counsel for Epic Systems, Corp.Search in Eureka ↗ |
| Defendant law firm | Quarles & Brady LLP | Law Firm | Representing Epic Systems, Corp.Search in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Court of Appeals for the Federal CircuitSearch in Eureka ↗ |
Official order — verbatim text
The dismissal order is formulaic but legally significant. By invoking Fed. R. App. P. 42(b) — rather than a sua sponte dismissal or a merits ruling — the court confirms this was a consensual exit. The silence on prejudice is the critical gap: without an express ‘with prejudice’ designation, third parties cannot assume Decapolis is barred from future action. The mutual cost-bearing provision suggests neither party extracted a one-sided concession at the appellate stage.
US7490048B2 & US7464040B2 — Healthcare information processing apparatus and methods
US7490048B2 and US7464040B2 are both directed to apparatus and methods for processing and providing healthcare information. The applications were filed as US09/987226 and US09/737348 respectively, placing their priority dates in the early 2000s — a period when electronic health records and clinical data exchange were transitioning from proprietary to networked architectures. The patents sit at the intersection of health informatics, clinical workflow, and data processing, a domain that has grown enormously in commercial scale since original filing.
The strategic significance of these patents lies in their breadth of application to modern EHR platforms. Any system that processes, routes, or presents healthcare information to clinical users could plausibly fall within claim scope — a description that covers a large portion of today’s health IT market. With no claim construction or validity ruling having issued from this litigation, the patents retain their full nominal scope. Competitors to Epic, health data aggregators, and clinical decision support developers should each conduct independent assessments of exposure.
Should your product team run an FTO against US7490048B2 and US7464040B2?
Any organisation developing or deploying software that processes, stores, or presents healthcare information — including EHR systems, clinical data platforms, patient engagement tools, and health information exchanges — should treat these patents as live risk. Neither has been invalidated. Neither has been construed by a court. The voluntary dismissal in this case provides no safe harbour. The relevant question for product and IP teams is whether their implementations fall within the claims as originally granted.
PatSnap Eureka’s FTO Search Agent allows IP and R&D teams to map the claim language of US7490048B2 and US7464040B2 against their own product architecture in minutes. The agent surfaces prior art candidates, identifies design-around opportunities, and flags related Decapolis portfolio patents that may present additional exposure — giving legal and engineering teams a structured basis for risk assessment before product launch or expansion.
Run a freedom-to-operate analysis on US7490048B2 to assess your product’s exposure
Run FTO in Eureka →Similar healthcare IT patent infringement cases at the Federal Circuit
Federal Circuit appeals involving healthcare information processing patents, including EHR and clinical data system infringement actions comparable to Decapolis v. Epic Systems.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedDECAPOLIS SYSTEMS, LLC’s broader IP enforcement history
DECAPOLIS SYSTEMS, LLC’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the healthcare IT patent enforcement landscape
A Federal Circuit appeal ending by mutual dismissal with no cost award raises pointed questions about enforcement strategy and patent risk in healthcare IT.
Voluntary Federal Circuit dismissals often signal off-record resolution
When parties jointly dismiss a Federal Circuit appeal under Rule 42(b) after nearly ten months — with neither side paying costs — it is consistent with a negotiated outcome. Patent attorneys advising healthcare IT clients should monitor whether Decapolis pursues further assertions of these patents, which would clarify whether a broader licence was reached.
No merits ruling leaves patent validity entirely open for the sector
Neither US7490048B2 nor US7464040B2 has been invalidated, construed, or narrowed by this proceeding. Any EHR vendor, healthcare data platform, or clinical information system developer operating in this space inherits full uncertainty as to the enforceability and scope of these patents. An FTO review is the appropriate first step.
Decapolis’s assertion pattern: are other defendants at risk?
Patent assertion entities holding healthcare IT patents frequently pursue multiple defendants sequentially. The dismissal against Epic — without a merits ruling — does not exhaust these patents. Counsel representing other EHR or health data vendors should assess whether similar claims are pending or forthcoming from Decapolis against their clients.
Cost-neutrality as a settlement signal: what it means for future licensing
The explicit ‘each side bears own costs’ language in the dismissal order, rather than a cost award to either party, is consistent with a negotiated exit rather than a clear win for either side. This cost structure may inform expectations in any future licensing discussions involving these patents, particularly in the EHR and healthcare data processing sector.
DECAPOLIS v Epic — key questions answered
The Federal Circuit appeal in Case No. 25-1289 was voluntarily dismissed by agreement of the parties under Fed. R. App. P. 42(b) on 14 October 2025. No merits ruling was issued. Each side bore its own costs. The case involved infringement claims over US7490048B2 and US7464040B2, both covering healthcare information processing apparatus and methods.
Decapolis asserted US7490048B2 (application no. US09/987226) and US7464040B2 (application no. US09/737348). Both patents are directed to apparatus and methods for processing and providing healthcare information. Neither patent has been invalidated or claim-construed by any court in this proceeding.
Not formally. A voluntary dismissal under Fed. R. App. P. 42(b) carries no merits ruling and no finding of non-infringement or invalidity. Epic avoided an adverse appellate judgment, and no costs were awarded against it. However, if the dismissal was without prejudice, Decapolis could theoretically reassert the same patents. The public record does not specify prejudice terms.
The answer depends on whether the dismissal was with or without prejudice — a distinction the public order does not resolve. Fed. R. App. P. 42(b) does not automatically impose prejudice. If no underlying district court judgment or stipulation specifies otherwise, the question of Decapolis’s ability to refile remains legally open based on the publicly available record.
In Federal Circuit appeals, costs may be awarded to the prevailing party. The explicit provision that each side bears its own costs signals that neither party was designated a prevailing party in this dismissal. This cost-neutral outcome is consistent with a negotiated agreement rather than a unilateral concession, though the specific commercial terms — if any — are not part of the public record.
Track healthcare IT patent enforcement risk with PatSnap Eureka
US7490048B2 and US7464040B2 remain valid and unadjudicated on the merits. Run an FTO analysis and monitor Decapolis Systems’ assertion activity to protect your EHR or health data platform from future exposure.
PatSnap Eureka searches patents and litigation data to answer instantly.