Ben Hutton

@sj00coder Hello. Unfortunately, this is not a project where just anyone can contribute. This project is a specification defining a format and a process between specific services that store genetic...

> ...indicate whether the genes in the response were manually curated or computationally curated. ... by the database. I mean, DECIPHER, and assuming others, only know what the user has...

@jxchong This may be the intended use of DECIPHER, however we have had instanced where people have uploaded 40-100 varients for a single patient. In addition, as our API uptake...

I'm not sure if this is needed, however it could be benificial. For some clarification: The related problem in #110 was that a variant had a consequence which was not...

Unless there are any objections, will opt for option 1. I'll create some sample json for this and make a pull request

I'm in favour of allowing multiple consequences and or transcirpts transmitted, but I don't understand the value or use case for including the transcript the consequence was aquired from. Regardless,...

THe DECIPHER API is still under development, but we are seeking feedback from a number of institiutions including Gemics Englaland. As such, I'll email you all the link as opposed...

I would agree option 2 seems more sane. Similar to PhenomeCentral, we don't know if the user is a clinician or researcher, but the majority of time they will be...

Misscommunication! DECIPHER wouldn't collect this information, but if any system wanted to send it, we would could filter it out before displaying. The confusion was over what "recieving" meant. I...

@jxchong We still wouldn't want to get requests from or match on data entered by patients. How that information comes out in the API is not too important, imho. It...