Opposition 91277821
OtherUSPTO
Opposition 91277821 at USPTO between Apple Inc. and ProMedica Health System, Inc., over the mark GREEN APPLE CLINIC, filed Aug 8, 2022. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 8, 2022
- Marks involved
- 11
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the GREEN APPLE CLINIC filing.
GREEN APPLE CLINIC filed
Application 97168871 filed at the USPTO.Opposition filed
Apple Inc. started opposition 91277821 at USPTO against GREEN APPLE CLINIC.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| GREEN APPLE CLINIC | Contested | 97168871 | USPTO |
| [Design mark] | Relied on | 76426501 | USPTO |
| APPLE | Relied on | 77428980 | USPTO |
| [Design mark] | Relied on | 77648705 | USPTO |
| [Design mark] | Relied on | 78156920 | USPTO |
| [Design mark] | Relied on | 78943482 | USPTO |
| APPLE WATCH | Relied on | 86389914 | USPTO |
| APPLE WATCH | Relied on | 86390028 | USPTO |
| LISTEN ON APPLE PODCASTS | Relied on | 87635733 | USPTO |
| APPLE NEWS+ | Relied on | 88541065 | USPTO |
| APPLE NEWS TODAY | Relied on | 90231151 | USPTO |
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_7b6c6fbd-e1d4-489a-88e4-5ff04d880249
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_7b6c6fbd-e1d4-489a-88e4-5ff04d880249",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91277821",
"status": "other",
"office_code": "US",
"filed_date": "2022-08-08",
"parties": [
{
"name": "Apple Inc.",
"role": "opponent"
},
{
"name": "ProMedica Health System, Inc.",
"role": "respondent"
}
]
}