throbber
From:
`To:
`Cc:
`
`Subject:
`Date:
`
`John West
`Richard Chen
`Russ B. Altman; Gemma Chandratillake; Russ Altman; Mark Pratt; Christian Haudenschild; Carol Tillis; Sarah
`Garcia
`Re: Name instead of "Exome+"
`Friday, January 11, 2013 6:00:01 PM
`
`This is good. While you all are on a roll, the new name for VariMed would be ___ ?
`
`John
`
`On Fri, Jan 11, 2013 at 5:10 PM, Richard Chen <richard.chen@personalis.com> wrote:
`We could use MINTdb as our new name for MendelDB, in that case MINT =
`Mendelian INheriTance DB
`
`On Fri, Jan 11, 2013 at 4:14 PM, Russ B. Altman
`<russ.altman@stanford.edu> wrote:
`> I won't push this hard because it's just an idea:
`
` Medically INTerpretable Genome = MINT Genome
`
`>>
`
`>>
`
` Medical = is what we do at 30K feet, e.g. we are not consumer. Research and care both
`are medical.
`
`>>
`
` Interpretable = we imply that we decide what is interpretable and we use genome because
`I think Exome is too limiting, and predict that MINT Genome will grow significantly
`(exclusively) over the years in the area of non-Exomic sequences.
`
` MINT = connotes new, fresh, accurate (coinage), green like our logo (minty fresh).
`
`>>
`
`>>
`
` MINT Genome v1.0 can be what we are doing now, and then we can have MINT Genome
`v2.0. I think we should move away from exome, because in light of ENCODE papers, and
`science movement in general (e.g. where variants are being found that matter) the exome is
`not as exciting. It is certainly included in the MINT Genome v1.0 but I don't think we
`should stress it.
`
`>>
`
` Of course, people will then read the details to understand exactly what we mean, but I like
`that this telegraphs our serious, accurate, fresh approach to medical genomics.
`
` That's it from me!
`
` Russ
`
`On Jan 11, 2013, at 1:41 PM, Gemma Chandratillake <gemmac@personalis.com> wrote:
`
`> Russ,
`>>
`>> Just a thought about names incorporating "medically interpretable"
`
`>>
`
`>>
`
`>>>
`
`>>
`
`Personalis EX2117.1
`
`

`

`exome/genome.........I've heard people make reference to this sort of thing in conferences
`and they usually use it in the context of a subset of the exome/genome e.g. HGMD genes
`(since not all of it is currently considered medically interpretable) so I'm not sure whether it
`conveys greater coverage/content than standard exomes/genomes......it could sound like less
`coverage/content given the current common use of these terms.......
`>>
`>> Just a thought,
`>>
`>> Gemma
`>>
`>> On Fri, Jan 11, 2013 at 12:57 PM, Richard Chen <richard.chen@personalis.com> wrote:
`>> Ok, cc'ing Russ on this thread since he may have some fresh ideas :)
`>>
`>> On Fri, Jan 11, 2013 at 12:23 PM, John West <john.west@personalis.com> wrote:
`>> > I really like the ACE acronym. Can we fold in the "Accuracy" theme here in
`>> > addition to content / coverage ?
`>> > "Accuracy & Content Enhanced" exome / genome ?
`>> >
`>> > John
`>> >
`>> >
`>> > On Fri, Jan 11, 2013 at 11:53 AM, Gemma Chandratillake
`>> > <gemmac@personalis.com> wrote:
`>> >>
`>> >> In the context of exome, it's nice that the E in ACE can stand for exome
`>> >> but I agree with Mark that, taking a longer term view, if we go for ACE, it
`>> >> would be great to be able to use ACE in front of products generally and
`>> >> therefore E would need to stand for something other than exome.
`>> >>
`>> >> I'd also like to stay away from any "seq" references that everybody else
`>> >> is ripping of from Illumina.....
`>> >>
`>> >> Gemma
`>> >>
`>> >>
`>> >> On Fri, Jan 11, 2013 at 11:36 AM, Mark Pratt <mark.pratt@personalis.com>
`>> >> wrote:
`>> >>>
`>> >>> Great idea Rich. We need to make ACE work for the marketing value alone.
`>> >>> Further, we should define it in the prefix sense, eg ACE genome, ACE exome,
`>> >>> ACE panel, etc
`>> >>>
`>> >>>
`>> >>> Sent from my iPhone
`>> >>>
`>> >>> On Jan 11, 2013, at 11:10 AM, Richard Chen <richard.chen@personalis.com>
`>> >>> wrote:
`>> >>>
`>> >>> > Hi John, do you think that "medically supplemented exome" is too
`>> >>> > limiting in the sense that it more than just medical content (includes
`
`Personalis EX2117.2
`
`

`

`>> >>> > regulatory regions, also increased coverage for existing exome)
`>> >>> >
`>> >>> > Other ideas are:
`>> >>> >
`>> >>> > Personalis Extended Exome
`>> >>> > Personalis Extended Clinical Exome
`>> >>> > Personalis Exome ACE (Personalis Exome with Augmented Coverage and
`>> >>> > Content Extensions)
`>> >>> > Personalis ACE Technology (ACE = Augmented Content and Coverage Exome)
`>> >>> >
`>> >>> >
`>> >>> > On Fri, Jan 11, 2013 at 10:35 AM, John West <john.west@personalis.com>
`>> >>> > wrote:
`>> >>> >>
`>> >>> >> All,
`>> >>> >>
`>> >>> >> We can't use "Exome+" as the name for our product as others already
`>> >>> >> use
`>> >>> >> this. Since we are now working to complete the content for our new
`>> >>> >> web
`>> >>> >> site, we need to address this. I tend to think of our product as a
`>> >>> >> "Medically Supplemented Exome". This is a bit of a mouthful, but it
`>> >>> >> does
`>> >>> >> get at the fact that our additions are focused on the two main
`>> >>> >> improvements
`>> >>> >> needed for medical use of an exome: Accuracy and Content (including
`>> >>> >> both
`>> >>> >> finished genes and content outside the exons). This would also set us
`>> >>> >> up to
`>> >>> >> later offer a "Medically Supplemented Genome". I did a quick Google
`>> >>> >> search
`>> >>> >> on these and did not find any hits.
`>> >>> >>
`>> >>> >> Any thoughts on this as a name, or alternatives you prefer ? I would
`>> >>> >> be
`>> >>> >> completely happy to have something more succinct, if any of us can
`>> >>> >> come up
`>> >>> >> with it.
`>> >>> >>
`>> >>> >> Thanks,
`>> >>> >>
`>> >>> >> John
`>> >>> >>
`>> >>> >>
`>> >>> >>
`>> >>> >>
`>> >>> >>
`>> >>
`>> >>
`>> >>
`
`Personalis EX2117.3
`
`

`

`>> >>
`>> >> --
`>> >> Gemma Chandratillake, MPhil, PhD, MS, CGC
`>> >> Genomic Counselor, LGC
`>> >> Personalis, Inc.
`>> >
`>> >
`>>
`>>
`>>
`>> --
`>> Gemma Chandratillake, MPhil, PhD, MS, CGC
`>> Genomic Counselor, LGC
`>> Personalis, Inc.
`>
`
`Personalis EX2117.4
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket