Decapolis Systems v. Knight Health & Kindred Health: Dismissed Without Prejudice
Decapolis Systems, LLC asserted two healthcare information processing patents against Knight Health Holdings and Kindred Health Company in the Eastern District of Texas. After 884 days on the docket, plaintiff voluntarily dismissed the case without prejudice before any answer was filed — leaving the door open for future enforcement.
A pre-answer exit: Decapolis preserves its enforcement options
On 18 October 2022, Decapolis Systems, LLC — a patent assertion entity holding US7490048B2 and US7464040B2 — filed an infringement action in the Eastern District of Texas against Knight Health Holdings, LLC and Kindred Health Company, LLC. The asserted patents cover apparatus and methods for processing and providing healthcare information, a foundational category of health IT infrastructure. Both defendants operate in the post-acute and long-term care space, making the technology claims commercially material.
On 20 March 2025, Decapolis filed a Notice of Voluntary Dismissal under Federal Rule of Civil Procedure Rule 41(a)(1)(A)(i), which permits a plaintiff to dismiss without a court order when the defendant has not yet filed an answer or moved for summary judgment. The court accepted the notice and dismissed all claims without prejudice. Each party was ordered to bear its own costs, expenses, and attorneys’ fees, consistent with the default Rule 41 cost allocation.
The 884-day duration before a pre-answer voluntary dismissal is notable — it suggests the parties may have engaged in prolonged negotiation or that Decapolis reassessed litigation strategy following preliminary proceedings. The without-prejudice designation means the patent claims remain viable and could be reasserted against these or other defendants. The public record does not disclose whether any licensing discussions occurred or what prompted the decision to withdraw at this stage.
Filing to Voluntary dismissal in 884 days
884 days on docket — well above the median for E.D. Tex. patent cases that resolve pre-answer
Rule 41 voluntary dismissal: what without prejudice means for both parties
Rule 41(a)(1)(A)(i): plaintiff’s unilateral exit right
Under Federal Rule of Civil Procedure 41(a)(1)(A)(i), a plaintiff may dismiss a case without a court order — and as of right — provided the defendant has not yet filed an answer or moved for summary judgment. Kindred Health had not done either, making this a self-executing dismissal. The court’s role was purely administrative: to accept, acknowledge, and direct the clerk to close the docket.
No merits adjudicationWithout prejudice: claims survive for potential refiling
A dismissal without prejudice does not extinguish the underlying patent claims. Decapolis retains the right to reassert US7490048B2 and US7464040B2 against these defendants or others, subject to any applicable statute of limitations and patent term. This is a meaningful distinction from a with-prejudice dismissal, which would bar refiling. The verdict text explicitly confirms the without-prejudice designation.
Refiling possibleDefendants exit without admissions — but face residual risk
Knight Health Holdings and Kindred Health obtain a clean exit with no liability, no injunction, and no damages award. No answer was filed, so no invalidity or non-infringement positions entered the public record. However, the without-prejudice dismissal means defendants cannot treat this as final resolution. A licensing demand or refiled suit remains a credible scenario, and defendants may wish to build a defensive record on these patents.
No preclusive effectHealthcare IT operators remain exposed to these patent families
US7490048B2 and US7464040B2 cover broadly stated healthcare information processing methods. The voluntary dismissal without prejudice signals that Decapolis has not abandoned its enforcement programme. Other health IT operators — particularly those providing EHR platforms, care coordination software, or patient data processing tools — should treat these patent families as live enforcement risks and consider proactive FTO analysis.
Active enforcement riskFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Decapolis Systems, LLC | Company | Patent assertion entity — holder of US7490048B2 and US7464040B2 in healthcare ITSearch in Eureka ↗ |
| Defendant | Knight Health Holdings, LLC | Company | Knight Health Holdings, LLC and Kindred Health Company, LLC — post-acute care operatorsSearch in Eureka ↗ |
| Co-Defendant | Kindred Health Company, LLC | Company | Search in Eureka ↗ |
| Plaintiff counsel | Christopher A. Honea | Attorney | Counsel for Decapolis Systems, LLCSearch 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 ↗ |
| Presiding judge | Judge N/A | Judge | Texas Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s order reflects a purely procedural acceptance of Decapolis’s unilateral notice under Rule 41(a)(1)(A)(i). Because Kindred Health had not filed an answer or moved for summary judgment, no judicial discretion was required and no merits analysis was conducted. The explicit without-prejudice language is controlling: neither defendant obtained a finding of non-infringement or invalidity, and Decapolis retains the right to refile. The cost-bearing order — each party to bear its own — is the default outcome in this procedural posture and carries no adverse inference for either side.
US7490048B2 & US7464040B2 — Healthcare information processing methods
US7490048B2 and US7464040B2, filed under application numbers US09/987226 and US09/737348 respectively, cover apparatus and methods for processing and providing healthcare information. These patents address foundational health IT infrastructure — specifically the structured handling, routing, and presentation of clinical and administrative healthcare data. Their early application dates place them in the formative era of electronic health record and health information exchange development, giving them potentially broad claim coverage relative to modern implementations.
For health IT vendors, EHR developers, and care coordination platform operators, the asserted scope of these patents is commercially significant. The claims appear positioned to read on core data processing workflows common across post-acute care, telehealth, and hospital information systems. The fact that Decapolis filed in E.D. Tex. — a plaintiff-friendly venue — and pursued defendants in the long-term care sector suggests a targeted enforcement strategy. Companies deploying healthcare information systems should assess whether their architectures fall within the claim scope of either patent before a demand letter arrives.
Should you run an FTO against US7490048B2 and US7464040B2?
Any company building, licensing, or deploying software or hardware for processing healthcare information should treat these patents as live FTO targets. The without-prejudice dismissal confirms Decapolis has not retired these assets. EHR vendors, health data aggregators, telehealth platforms, and post-acute care IT providers are the most directly exposed product categories. An FTO analysis should map your specific data ingestion, processing, and output workflows against the independent claims of both patents.
PatSnap Eureka’s FTO Search Agent can map the claim language of US7490048B2 and US7464040B2 against your product architecture, identify prior art that may support invalidity arguments, and surface related continuations or family members that could present additional risk. Given the breadth of healthcare information processing technology, a structured claim chart review through Eureka can help R&D and legal teams identify design-around options or prior art challenges before any enforcement action is initiated.
Run a freedom-to-operate analysis on US7490048B2 to assess your product’s exposure
Run FTO in Eureka →Similar healthcare IT patent infringement cases in E.D. Texas
Cases involving healthcare information processing patents asserted in the Eastern District of Texas by patent assertion entities against health IT and post-acute care operators.
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 health IT patent enforcement landscape
A without-prejudice exit after nearly 2.5 years suggests unresolved leverage — not abandonment.
Pre-answer dismissals preserve the plaintiff’s full enforcement arsenal
Rule 41(a)(1)(A)(i) dismissals are low-cost exits that reset the clock without forfeiting claim rights. Health IT companies that receive demand letters or are named in suits by patent assertion entities should monitor whether dismissals are with or without prejudice — the distinction determines whether residual risk persists.
884 days pre-answer suggests protracted pre-litigation or negotiation dynamics
The extended docket duration before a pre-answer dismissal is consistent with extended licensing negotiations, parallel proceedings, or a strategic reassessment. Companies in post-acute and long-term care IT should review whether these patent families intersect with their current product architecture before any demand resurfaces.
US7490048B2 and US7464040B2 remain live enforcement tools across health IT
Neither patent was invalidated or challenged to final judgment in this action. Any company deploying healthcare information processing platforms — including EHR vendors, telehealth providers, and care coordination platforms — should assess claim scope against their own implementations before a licensing demand arrives.
E.D. Tex. filing patterns by Decapolis suggest a broader assertion strategy
Filing in the Eastern District of Texas is a consistent strategic choice for patent assertion entities targeting health IT. Monitoring Decapolis’s docket history and related filings in E.D. Tex. may reveal the scope of the broader enforcement campaign and likely next targets in the sector.
Decapolis v Knight — key questions answered
The dismissal without prejudice under Rule 41(a)(1)(A)(i) means Decapolis retains the right to refile infringement claims based on US7490048B2 and US7464040B2 against Knight Health Holdings or Kindred Health Company, or against other defendants. No merits determination was made, and neither patent was found invalid or not infringed. The dismissal carries no preclusive effect for either party.
Decapolis Systems asserted two patents: US7490048B2 (application number US09/987226) and US7464040B2 (application number US09/737348). Both patents cover apparatus and methods for processing and providing healthcare information and/or healthcare-related information, and were filed during the early development period of electronic health record systems.
The public record does not disclose the specific reason for the 884-day gap before voluntary dismissal. The extended duration before a pre-answer exit is consistent with prolonged licensing negotiations, a strategic reassessment of litigation positioning, or developments in related proceedings. The dismissal itself was procedurally straightforward: because no answer had been filed, Decapolis could dismiss as of right under Rule 41(a)(1)(A)(i).
The case was filed in the Eastern District of Texas (Case No. 2:22-cv-00408). E.D. Tex. is a historically plaintiff-favoured venue for patent assertion entities due to its established patent docket, experienced judges, and local patent rules. Filing there is a consistent strategic choice for PAEs asserting healthcare IT patents against national healthcare operators.
Yes. The voluntary dismissal without prejudice means both patents remain enforceable and neither was invalidated or found not infringed in this action. Health IT companies — particularly those in EHR, post-acute care software, telehealth, or health data processing — should treat these patents as active enforcement risks and consider conducting freedom-to-operate analysis against their current product implementations.
Track healthcare IT patent enforcement before the next demand arrives
PatSnap Eureka enables R&D and IP teams to run FTO searches against US7490048B2 and US7464040B2, monitor Decapolis Systems’ enforcement activity, and map claim scope against healthcare information processing products before litigation risk materialises.
PatSnap Eureka searches patents and litigation data to answer instantly.