Results

RDF/XMLNTriplesTurtleShow queryShare ▶
SubjectPredicateObject
http://purl.uniprot.org/citations/28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/28392550http://www.w3.org/2000/01/rdf-schema#comment"

Purpose

Transition to next generation sequencing (NGS) for BRCA1/BRCA2 analysis in clinical laboratories is ongoing but different platforms and/or data analysis pipelines give different results resulting in difficulties in implementation. We have evaluated the Ion Personal Genome Machine (PGM) Platforms (Ion PGM, Ion PGM Dx, Thermo Fisher Scientific) for the analysis of BRCA1/2.

Materials and methods

The results of Ion PGM with OTG-snpcaller, a pipeline based on Torrent mapping alignment program and Genome Analysis Toolkit, from 75 clinical samples and 14 reference DNA samples were compared with Sanger sequencing for BRCA1/BRCA2. Ten clinical samples and 14 reference DNA samples were additionally sequenced by Ion PGM Dx with Torrent Suite.

Results

Fifty types of variants including 18 pathogenic or variants of unknown significance were identified from 75 clinical samples and known variants of the reference samples were confirmed by Sanger sequencing and/or NGS. One false-negative results were present for Ion PGM/OTG-snpcaller for an indel variant misidentified as a single nucleotide variant. However, eight discordant results were present for Ion PGM Dx/Torrent Suite with both false-positive and -negative results. A 40-bp deletion, a 4-bp deletion and a 1-bp deletion variant was not called and a false-positive deletion was identified. Four other variants were misidentified as another variant.

Conclusion

Ion PGM/OTG-snpcaller showed acceptable performance with good concordance with Sanger sequencing. However, Ion PGM Dx/Torrent Suite showed many discrepant results not suitable for use in a clinical laboratory, requiring further optimization of the data analysis for calling variants."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.org/dc/terms/identifier"doi:10.4143/crt.2017.062"xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/author"Lee M.S."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/author"Lee K.C."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/author"Hwang S.M."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/author"Park K.U."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/date"2018"xsd:gYear
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/name"Cancer Res Treat"xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/pages"255-264"xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/title"Comparison of Ion Personal Genome Machine Platforms for the Detection of Variants in BRCA1 and BRCA2."xsd:string
http://purl.uniprot.org/citations/28392550http://purl.uniprot.org/core/volume"50"xsd:string
http://purl.uniprot.org/citations/28392550http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/28392550
http://purl.uniprot.org/citations/28392550http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/28392550
http://purl.uniprot.org/uniprot/#_A0A0F6TMZ9-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A0F6TN25-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A0F6TN92-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BDS2-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BDS6-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BDT0-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BDU2-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BEU4-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BEV8-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BEW3-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
http://purl.uniprot.org/uniprot/#_A0A068BC92-mappedCitation-28392550http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/28392550
▶