Opposition · USPTO

Opposition 91306559

PendingUSPTO

Opposition 91306559 at USPTO between Health Catalyst, Inc. and John Wiley & Sons, Inc., over the mark CATALYST, filed Apr 13, 2026. Status in the office record: pending.

View CATALYSTGet this data via the API
Status
Pending
Filed
Apr 13, 2026
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Health Catalyst, Inc.

Company trademarks
Respondent

John Wiley & Sons, Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the CATALYST filing.

  1. CATALYST filed

    Application 98606318 filed at the USPTO.

  2. Opposition filed

    Health Catalyst, Inc. started opposition 91306559 at USPTO against CATALYST.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
CATALYSTContested98606318USPTO
HEALTH CATALYSTRelied on85749769USPTO
HEALTH CATALYSTRelied on85749802USPTO
HEALTH CATALYSTRelied on87748726USPTO
HEALTH CATALYST IGNITERelied on98604008USPTO
HEALTH CATALYST IGNITE SPARKRelied on99161360USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_2858f557-0c76-42e5-a15b-55c56d3d958c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2858f557-0c76-42e5-a15b-55c56d3d958c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306559",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-04-13",
  "parties": [
    {
      "name": "Health Catalyst, Inc.",
      "role": "opponent"
    },
    {
      "name": "John Wiley & Sons, Inc.",
      "role": "respondent"
    }
  ]
}