Opposition · USPTO

Opposition 91222076

OtherUSPTO

Opposition 91222076 at USPTO between Quantum Corporation and Plexis Healthcare Systems, Inc., over the mark QUANTUM CHOICE, filed May 26, 2015. Status in the office record: other.

View QUANTUM CHOICEGet this data via the API
Status
Other
Result
Other
Filed
May 26, 2015
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Quantum Corporation

Respondent

Plexis Healthcare Systems, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the QUANTUM CHOICE filing.

  1. QUANTUM CHOICE filed

    Application 85944759 filed at the USPTO.

  2. Opposition filed

    Quantum Corporation started opposition 91222076 at USPTO against QUANTUM CHOICE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
QUANTUM CHOICEContested85944759USPTO
QUANTUMRelied on72327773USPTO
QUANTUMRelied on73127739USPTO
QUANTUMRelied on74242149USPTO
QUANTUMRelied on75052261USPTO
QUANTUMRelied on75387699USPTO
QUANTUMRelied on75552214USPTO
QUANTUMRelied on75601999USPTO
QUANTUMRelied on75604153USPTO
QUANTUMRelied on75608837USPTO
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_1ea68d0d-2422-4d20-93e1-198c25b931fb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1ea68d0d-2422-4d20-93e1-198c25b931fb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91222076",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-05-26",
  "parties": [
    {
      "name": "Quantum Corporation",
      "role": "opponent"
    },
    {
      "name": "Plexis Healthcare Systems, Inc.",
      "role": "respondent"
    }
  ]
}