3:26-cv-05050
Evidium Inc v. BMJ Publishing Group Ltd
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Evidium, Inc. (Delaware)
- Defendant: BMJ Publishing Group Limited (United Kingdom)
- Plaintiff's Counsel: Fenwick & West LLP
- Case Identification: 3:26-cv-05050, N.D. Cal., 05/28/2026
- Venue Allegations: Venue is asserted on the basis that Defendant is an alien corporation, has engaged in business activities directed at the judicial district, and that the court has personal jurisdiction.
- Core Dispute: Plaintiff alleges that Defendant's "BMJ Clinical Intelligence" AI platform infringes three patents related to computational medical evidence technology, which Plaintiff claims Defendant misappropriated during a prior business relationship to create a competing product.
- Technical Context: The technology at issue involves using artificial intelligence, specifically knowledge graphs, to transform unstructured narrative medical text into a computable format to improve clinical decision support systems.
- Key Procedural History: The complaint alleges a history of business collaboration starting in April 2020, during which Plaintiff shared its confidential and proprietary technology with Defendant. Following the launch of Defendant's allegedly competing "Clinical Intelligence" product, Plaintiff sent notices of infringement for the '674 patent in December 2024 and for the '882 and '883 patents in April 2026. The complaint also notes that the '882 and '883 patents were allowed after amendments adding limitations related to Application Programming Interfaces (APIs) to overcome patent eligibility rejections under 35 U.S.C. § 101.
Case Timeline
| Date | Event |
|---|---|
| 2020-04-XX | Business discussions between Evidium and BMJ begin. |
| 2021-06-01 | Parties execute "Best Practice Agreement". |
| 2021-10-01 | Parties execute "Technology Licence Agreement". |
| 2022-04-15 | Earliest Priority Date for '674, '882, and '883 Patents. |
| 2024-01-09 | U.S. Patent No. 11,869,674 issues. |
| 2024-03-XX | Defendant BMJ allegedly launches its "Clinical Intelligence" product. |
| 2024-11-XX | Plaintiff Evidium learns that Defendant had introduced its "Clinical Intelligence" product. |
| 2024-12-XX | Plaintiff provides Defendant with notice of infringement of the '674 patent. |
| 2026-01-06 | U.S. Patent No. 12,518,882 issues. |
| 2026-01-06 | U.S. Patent No. 12,518,883 issues. |
| 2026-04-08 | Plaintiff provides Defendant with notice of infringement of the '882 and '883 patents. |
| 2026-05-28 | Complaint is filed. |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 11,869,674 - "Translation of Medical Evidence Into Computational Evidence and Applications Thereof"
- Patent Identification: U.S. Patent No. 11,869,674, "Translation of Medical Evidence Into Computational Evidence and Applications Thereof," issued January 9, 2024.
The Invention Explained
- Problem Addressed: The patent's background describes that medical knowledge is predominantly locked in narrative, document-based formats Compl., Ex. A, col. 1:36-40 This form is difficult to scale, slow to disseminate, and not suitable for computational reasoning, leading to clinical inefficiency, diagnostic errors, and clinician burnout Compl., Ex. A, col. 1:25-35
- The Patented Solution: The invention is a platform and method for making medical evidence "computational" Compl., Ex. A, col. 2:39-40 It achieves this by extracting clinical concepts from text sources and representing them as "elemental factors" and "investigations" in a structured graph database Compl., Ex. A, abstract Compl., Ex. A, col. 2:56-63 This structured format allows software applications to query the evidence and map it to patient data for purposes like clinical decision support Compl., Ex. A, col. 2:41-44 The '674 patent's Figure 2 illustrates this translation process, showing how input text is processed by an NLP engine to create clinical concepts that are then grouped and stored in a graph database Compl., Ex. A, FIG. 2
- Technical Importance: This approach is presented as a solution to make vast amounts of medical knowledge AI-ready and deployable at scale, enabling more advanced and reliable AI applications in healthcare Compl., Ex. A, col. 4:31-36
Key Claims at a Glance
- The complaint asserts independent claims 1 and 12 Compl. ¶74
- Independent Claim 1, a method claim, includes the following essential elements:
- Inputting medical evidence as text containing a medical condition and at least one diagnostic factor.
- Transforming the text into a "diagnostic factor data structure" that includes a name, synonym, and a unique identifier linked to a medical ontology.
- Creating a graph database with the data structure as a node.
- The graph database also includes nodes representing medical conditions, with links from the condition nodes to the diagnostic factor node.
- The complaint does not explicitly reserve the right to assert dependent claims but makes general allegations of infringement.
U.S. Patent No. 12,518,882 - "Translation of Medical Evidence Into Computational Evidence and Applications Thereof"
- Patent Identification: U.S. Patent No. 12,518,882, "Translation of Medical Evidence Into Computational Evidence and Applications Thereof," issued January 6, 2026.
The Invention Explained
- Problem Addressed: As a continuation, the '882 patent addresses the same problems as the '674 patent: the limitations of narrative, document-based medical evidence Compl. ¶38 Compl., Ex. B, col. 1:25-51
- The Patented Solution: The '882 patent claims a computer system that implements the solution of translating medical evidence into a computational form Compl. ¶32 A key aspect of the claimed system is the creation of a cross-linked graph database and, critically, the establishment of "one or more application programming interfaces (APIs)" that allow an external application to integrate with and access the database to generate a healthcare determination Compl., Ex. B, claim 1
- Technical Importance: The system is described as a specific technological improvement over abstract data organization by enabling programmatic integration and reasoning, a feature the complaint highlights was key to overcoming a patent eligibility rejection during prosecution Compl. ¶45
Key Claims at a Glance
- The complaint asserts independent claim 1 Compl. ¶84
- Independent Claim 1, a system claim, includes the following essential elements:
- A computer system with one or more processors and memory.
- Instructions to receive electronic text from medical evidence sources.
- Instructions to retrieve diagnostic factors from the text.
- Instructions to create and store a cross-linked graph database of diagnostic factors and medical conditions.
- Instructions to establish one or more "application programming interfaces (APIs)" allowing an application to integrate with the graph database to access its entries and generate a healthcare determination.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 12,518,883 - "Translation of Medical Evidence Into Computational Evidence and Applications Thereof"
- Patent Identification: U.S. Patent No. 12,518,883, "Translation of Medical Evidence Into Computational Evidence and Applications Thereof," issued January 6, 2026 Compl. ¶35
- Technology Synopsis: The '883 patent, which shares a common specification with the other asserted patents, claims methods and systems for translating medical evidence into computational elements Compl. ¶¶35, 38 The complaint notes that prosecution of this patent involved adding a limitation for "outputting, responsive to said medical query, an output to said software application" to overcome a § 101 rejection, suggesting a focus on the query-response functionality of the system Compl. ¶46
- Asserted Claims: Claim 23 Compl. ¶95
- Accused Features: The complaint alleges that Defendant's "Clinical Intelligence" product and related services that use the BMJ knowledge graph infringe claim 23 Compl. ¶96
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are Defendant's "BMJ Clinical Intelligence" platform and other AI product offerings that rely on or relate to the "BMJ knowledge graph" Compl. ¶¶63-64
Functionality and Market Context
- The complaint alleges that BMJ Clinical Intelligence is a platform designed to "deliver[] computable evidence at scale" Compl. ¶62 It is marketed as providing "high-quality computable guideline recommendations" that are "coded and converted into computable form in a knowledge graph" Compl. ¶63
- The platform's architecture is described by BMJ as a "dynamic knowledge graph" that is "relationship-based" and serves as a "foundational infrastructure for AI-enabled clinical reasoning systems" Compl. ¶65 The platform allegedly derives its underlying database from BMJ's "Best Practice" data, which is converted into a computable form via natural language processing Compl. ¶63
IV. Analysis of Infringement Allegations
The complaint references claim-chart exhibits that are not provided Compl. ¶¶75, 85, 96 The infringement theory is summarized below in prose.
'674 Patent Infringement Allegations
The complaint alleges that BMJ's Clinical Intelligence platform directly infringes at least claims 1 and 12 of the '674 patent Compl. ¶74 The theory of infringement is that BMJ's process for creating its "knowledge graph" performs the steps of the claimed method. This allegedly involves taking medical evidence (BMJ's Best Practice content), transforming it into a structured, computational format, and storing it as nodes and links in a graph database, thereby meeting each limitation of the asserted claims Compl. ¶63 Compl. ¶75
'882 Patent Infringement Allegations
The complaint alleges that BMJ's Clinical Intelligence system directly infringes at least claim 1 of the '882 patent Compl. ¶84 The infringement theory posits that the accused platform is a computer system that creates and uses a graph database as claimed. The complaint specifically highlights that BMJ's architecture supports APIs, which maps to the key API limitation in claim 1 that was added to overcome a § 101 rejection during prosecution Compl. ¶45 Compl. ¶65 Compl. ¶85
Identified Points of Contention
- Scope Questions: A primary legal question may be patent eligibility under 35 U.S.C. § 101. The complaint argues the claims are a "technological solution" and not abstract Compl. ¶44 However, a court may need to determine whether the claims, despite their technical framing, are ultimately directed to the abstract idea of organizing medical information, a central issue given the prosecution history cited in the complaint Compl. ¶¶45-46
- Technical Questions: A key factual question for infringement will be whether BMJ's process for creating its "knowledge graph" is technically equivalent to the claimed methods. The analysis may turn on whether BMJ's platform creates a "diagnostic factor data structure" with the specific attributes required by the claims and whether its system architecture provides "APIs allowing an application to integrate" in the manner claimed by the '882 patent.
V. Key Claim Terms for Construction
"diagnostic factor data structure"
(from '674 Patent, Claim 1)
Context and Importance
This term defines the fundamental unit of "computational evidence" at the heart of the invention. Its construction is critical because infringement will depend on whether the data elements within BMJ's "knowledge graph" meet this definition.
Intrinsic Evidence for Interpretation
- Evidence for a Broader Interpretation: The specification describes the underlying concept broadly as "representing clinical concepts as elemental factors and investigations that are computational useful" Compl., Ex. A, col. 2:56-59 This could support an interpretation covering any structured data element representing a clinical concept.
- Evidence for a Narrower Interpretation: Claim 1 itself requires the structure to include a "name, at least one synonym... and a unique identifier to a link in a medical oncology" Compl., Ex. A, claim 1 This specific recitation of components could support a narrower definition that requires all these elements to be present.
"application programming interfaces (APIs) allowing an application to integrate with said graph database to access said separate entries"
(from '882 Patent, Claim 1)
Context and Importance
Practitioners may focus on this term because the complaint states it was added to overcome a § 101 patent eligibility rejection Compl. ¶45 Its construction is therefore central to both validity and infringement, as it represents the purported "inventive concept."
Intrinsic Evidence for Interpretation
- Evidence for a Broader Interpretation: The term could be interpreted broadly to cover any standard programmatic interface that allows software to query a database, a common feature in software architecture.
- Evidence for a Narrower Interpretation: The complaint cites the applicant's argument during prosecution that the API is a "software construct that a human cannot practically perform" and "allows the software application to integrate with the graph database to access the entries" Compl. ¶45 This suggests a specific type of functional integration beyond simple data retrieval, which could support a narrower construction tied to enabling a healthcare determination.
VI. Other Allegations
Indirect Infringement
The complaint alleges inducement of infringement for all three patents, asserting that BMJ is aware of the patents and "encourages or enables its customers to use" the accused products in the United States Compl. ¶76 Compl. ¶86 Compl. ¶97 For the '882 and '883 patents, contributory infringement is also alleged, on the basis that BMJ's platform is a material part of the invention, is known to be especially adapted for an infringing use, and is not a staple article of commerce Compl. ¶87 Compl. ¶98
Willful Infringement
Willfulness is alleged for all three patents. The complaint pleads pre-suit knowledge based on notice letters sent to BMJ regarding the '674 patent in December 2024 and the '882 and '883 patents in April 2026 Compl. ¶79 Compl. ¶90 Compl. ¶101 The complaint further alleges that BMJ knew of Evidium's technology and monitored its patent portfolio Compl. ¶79
VII. Analyst's Conclusion: Key Questions for the Case
A threshold issue will be one of patent eligibility: will the claims be found valid under 35 U.S.C. § 101, or will a court determine they are directed to the abstract idea of organizing medical information without a sufficient inventive concept, a question made acute by the prosecution history that is detailed in the complaint?
A central claim construction question will be the definitional scope of the API limitations added to secure the '882 and '883 patents. Will "APIs allowing an application to integrate" be interpreted broadly as any programmatic data access, or will it be narrowly construed, in light of the prosecution history, to require a specific functional integration that distinguishes the claims from abstract data manipulation?
A key evidentiary question will be one of technical implementation: does the accused "BMJ Clinical Intelligence" platform, which allegedly converts existing "Best Practice" content, actually perform the specific "transforming" and "cross-linking" steps required to create the claimed "diagnostic factor data structures," or is there a fundamental mismatch in the technical operation between the patented method and the accused system?