Opposition · USPTO

Opposition 91238423

OtherUSPTO

Opposition 91238423 at USPTO between HealthPartners, Inc. and Virtual Health Partners, Inc., over the mark VIRTUAL HEALTH PARTNERS, filed Dec 15, 2017. Status in the office record: other.

View VIRTUAL HEALTH PARTNERSGet this data via the API
Status
Other
Result
Other
Filed
Dec 15, 2017
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

HealthPartners, Inc.

Respondent

Virtual Health Partners, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the VIRTUAL HEALTH PARTNERS filing.

  1. VIRTUAL HEALTH PARTNERS filed

    Application 87109224 filed at the USPTO.

  2. Opposition filed

    HealthPartners, Inc. started opposition 91238423 at USPTO against VIRTUAL HEALTH PARTNERS.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
VIRTUAL HEALTH PARTNERSContested87109224USPTO
HEALTHPARTNERSRelied on74476983USPTO
HEALTHPARTNERSRelied on74476997USPTO
HEALTHPARTNERSRelied on74476998USPTO
VIRTUWELLRelied on77855527USPTO
HEALTHPARTNERSRelied on85872812USPTO
HEALTHPARTNERSRelied on86141969USPTO
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_bf47e19b-811d-48dd-96bd-f579c7c13a43
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bf47e19b-811d-48dd-96bd-f579c7c13a43",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91238423",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-12-15",
  "parties": [
    {
      "name": "HealthPartners, Inc.",
      "role": "opponent"
    },
    {
      "name": "Virtual Health Partners, Inc.",
      "role": "respondent"
    }
  ]
}