`Carol Tillis; Richard Chen; Christian Haudenschild
`Product naming decisions from staff meeting today
`Monday, January 14, 2013 6:33:57 PM
`
`From:
`To:
`Subject:
`Date:
`
`All,
`
`These are my notes from our discussion at the staff meeting today. The issue is that we have
`to make some firm decisions for product names since we are about to finalize the content for
`our new web site.
`
`For the products we have been calling Exome+ and Exome++, we will use ACE Exome
`(Acuracy & Content Enhanced Exome). Carol will explore filing for a trademark on this for
`our field of use.
`
`For the other names, we have decided to leverage the Personalis name. Specifically, we will
`refer to:
`
`The Personalis Pipeline version x.x, built on the HugeSeq pipeline originally created at
`Stanford.
`
`The Personalis Mendelian Database (this will not be referred to as being built on MendelDB
`from Stanfrd, since we really started over from scratch.)
`
`The Personalis Common Disease Variant Database, built on the VariMed database originally
`developed at Stanford.
`
`The Personalis Pharmacogenomic Database, built on the PharmGKB database, originally
`developed and still being advanced at Stanford.
`
`It turns out that some of the other names we considered are already being used by others:
`
` ACE db is a c. elegans related database
`
` Mint is a database of molecular interactions
`
`Unless there is some last minute reason we need to change the choices above, we will begin
`implementing them in our material for the web site. In the future when we have a full time
`marketing group, we may consider additional brand names, but for now we want to start with
`this fairly simple approach (and one for which we have already investigated the trademark
`issues) - Personalis.
`
`Thanks,
`
`John
`
`Personalis EX2119
`
`
`
`Personalis EX2119
`
`Personalis EX2119
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
