Development Roadmap

This section links to material on the changes and new functionality planned or underway for BRCA Exchange development.

This page is updated quarterly. To get the most recent roadmap, please see our Waffleboard.

---

Big Picture

• Here are notes from a brainstorming meeting on upcoming development priorities.

---

Portal Development

• Mobile app (Faisal)

• Restructure the help pages. Here is a prototype page for background information targeted to a BRCA testing patient. And here is an outline of questions to ask of stakeholders such as patient advocates (Amy).

• Reporting on Beacons of all variants. This code was developed by Audrey, and has not yet been integrated into the pipeline.

• Literature search: currently refining the method for production (Audrey).

• Implement BRCA Exchange News (see the wireframes). (Unassigned)

• Expand the suite of unit tests (Collin)

---

Collecting and presenting variant-level evidence

Splicing and prediction of truncation

• Team Splicing is gathering the ingredients for computing the splicing prior, including predicting truncating variants (Tyler, Melissa M, Luis). These documents describe respectively the method and the data.

Gathering and presenting allele frequency data

• Adding subpopulation data from ExAC:

  • The BRCA Exchange output data now includes allele counts, allele numbers, homozygous counts and allele frequencies for the seven ExAC subpopulations: AFR, AMR, EAS, FIN, NFE, OTH, SAS.

  • Prototype allele frequency graphs are under development (Joe)

• Incorporating data from gnomAD: Awaiting the release of "gnomAD minus TCGA" (Sam)

---

Collecting case-level evidence

• See the draft specification of forms of evidence by analysis type.

Analysis Types

• Co-occurrence

  • See the draft specification for the data needed for co-occurrence (Melissa).

• Summary family history

  • See the UCSC IRB exemption for the ENIGMA pilot

Data collection issues

• Parsing text data from images of reports

  • OCR methods (Chloe).
  • We have some scans of blank test order forms here

• Managing redundancy: one-way cryptographic hashes (Johnnie)