Opposition · USPTO

Opposition 91300791

OtherUSPTO

Opposition 91300791 at USPTO between Helix, Inc. and Helix Virtual Medicine, Inc., over the mark HELIX VIRTUAL MEDICINE, filed Aug 4, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 4, 2025
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Helix, Inc.

Respondent

Helix Virtual Medicine, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the HELIX VIRTUAL MEDICINE filing.

  1. HELIX VIRTUAL MEDICINE filed

    Application 97245481 filed at the USPTO.
  2. Opposition filed

    Helix, Inc. started opposition 91300791 at USPTO against HELIX VIRTUAL MEDICINE.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
HELIX VIRTUAL MEDICINEContested97245481USPTO
HELIXRelied on78311374USPTO
HELIXRelied on87539083USPTO
HELIXRelied on87539089USPTO
HELIXRelied on87539101USPTO
HELIXRelied on87573883USPTO
HELIXRelied on88134331USPTO
HELIXRelied on88950481USPTO
HELIXRelied on88950502USPTO
HELIXRelied on88950523USPTO
HELIXRelied on88950541USPTO
HELIXRelied on88950556USPTO

+7 more marks in this case

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 /v1/proceedings/{id}
ID=prc_223911e8-6763-484f-83f4-2bb73adf3c72
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_223911e8-6763-484f-83f4-2bb73adf3c72",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300791",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-08-04",
  "parties": [
    {
      "name": "Helix, Inc.",
      "role": "opponent"
    },
    {
      "name": "Helix Virtual Medicine, Inc.",
      "role": "respondent"
    }
  ]
}