Tuesday, 5 January 2021

Colorectal Somatic MLH1 case

 

Colorectal Somatic MLH1 case

This document presents a discussion centered around a real case wherein my supervisor was tasked with verifying whether a deletion variant was not identified in the NGS (Next-Generation Sequencing) data of a test conducted three years ago. The purpose of this discourse is educational. In the following text, I will outline the process utilized to analyze the NGS data, the conclusions derived from this examination, and a draft of what my response would be (via email) if I were in charge of this verification. The discussion will conclude with an exploration of the current developments regarding the patient in question.


Background

The patient in question was diagnosed with well-differentiated adenocarcinoma of the bowel at the age of 38. Family history includes his father's diagnosis of colon cancer and his sister's diagnosis of colorectal polyposis. In December 2017, the patient underwent germline testing for the MLH1, MSH2, MSH6, and PMS2 genes, but no pathogenic variant was identified. Subsequently, in February 2018, an immunohistochemistry (IHC) analysis revealed a loss of MLH1 and PMS2, and normal MLH1 promoter methylation status. Additionally, a tumor pathology sample was screened for variants in a 13-gene panel associated with inherited predisposition to colorectal cancer. The variant c.2169_2175del p.(Leu724HisfsTer57) was found in 30% of sequence reads, along with a loss of heterozygosity (LOH) across multiple SNV markers in the MLH1 region. This particular variant, MLH1 c.2169_2175del p.(Leu724HisfsTer57), is a stop-loss variant that extends the protein by 23 amino acids. It has been assessed as likely pathogenic (ACGS Class 4) according to published guidelines. My supervisor has been tasked with verifying that this variant was not detected in the original germline test. I have seized this opportunity to draft this document, detailing the procedure, interpretation, and conclusions derived from this case.

Procedure to analyse the absence of the variant c.2169_2175de


The first step has been to access the folder where the NGS data is stored, this step has been carried out by using IRIDIS4.

The steps needed to open ivg with this terminal are:

[mdb1c20@cyan01 ~]$ cd /scratch

[mdb1c20@cyan01 scratch]$ cd WRGL/

[mdb1c20@cyan01 WRGL]$ cd 000000_M01875_0303_000000000-B394W_RPT/

# For patient confidentiality, the last folder show is not real

[mdb1c20@cyan01  000000_M01875_0303_000000000-B394W_RPT]$ cd 1142149020

[mdb1c20@cyan01 1142149020]$ module load igv/2.3.88

[mdb1c20@cyan01 1142149020]$ igv  000000_M01875_0303_000000000-B394W_RPT_1142149020.bam 3:37092042
# After the name of the bam file, the coordinates of the variant can be specified.

 

A screenshot in which it can be seen the output provided by igv is shown below.



The alignment representation for the coordinates at chromosome 3, location 37,092,042 is depicted in the last figure. This specific region of the genome displays approximately 415 reads, indicating that there is no evidence to support the occurrence of a deletion within this chromosome segment. In DNA sequencing, a "read" refers to an inferred sequence of base pairs that corresponds to part of a single DNA fragment. In this particular instance, it corresponds to the aforementioned location. As there is a certain degree of uncertainty between the true DNA molecule and the final set of reads, multiple reads are necessary to minimize this uncertainty. A count of 400 reads surpasses the required number to deem the quality of this region acceptable, thereby eliminating the quality of the analysis as a contributing factor to the existence of this variant. This confirms that the variant is not present in the data. A potential response to the email received by my supervisor could be as follows: --- Dear Clinical Scientist, I have conducted an analysis on the NGS data (1142149020/W1702270) specifically targeting the region of the mentioned variant (c.2169_2175del, Chr3(GRCh38):g.37050551_37050557del, NM_000249.2(MLH1):c.2169_2175del). I can confirm that the NGS test performed in 2017 reveals NO evidence to support the presence of a deletion at this position. Below, you will find the nucleotides located between the positions 37092037 to 37092052, along with their respective frequency. Please let me know if you require further details or clarification.




Positions

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

Nucleotides

A

A

A

G

C

C

T

T

G

C

G

C

T

C

A

C

Counting

C

1

0

1

0

414

413

0

0

1

433

0

440

0

455

1

459

T

0

0

0

2

0

0

416

418

2

1

1

0

440

0

0

0

G

0

0

0

414

0

0

0

0

418

0

432

0

0

0

0

0

A

405

404

403

0

1

0

1

0

0

0

2

0

0

0

455

0

Total count

406

404

404

416

415

413

417

418

421

434

435

440

440

455

456

459



















I have also checked that this sequence corresponds with the reference genome by using Mutalizer.

CTGTGGAACACATTGTCTATAAAGC CTTGCGC TCACACATTCTGCCTCCTAAACATT

CTGTGGAACACATTGTCTATAAAGC ------- TCACACATTCTGCCTCCTAAACATT


As you can see, in the table the region when the variant is located (marked in blue color) and their closest nucleotides show a regular pattern of readings where the frequency of one amino acid always predominates over the other three. We can see also that this region was coverage sufficiently in the variant location. The quality of this region confirms that according to this data there is no reason to think that there is a deletion in the mentioned coordinates. A drop in the number of amino acids counted is NOT observed in the variant location so according to this data, we can confirm that there is not a deletion between the position 37092042 to 37092048.


With this analysis and with the data provided in the report you provide me in your email I interpret that this variant is not in the germ line and this mutation has occurred in the patient's tumor cells. 


Do not hesitate if you require any further information.


Regards


Manuel

Patient-centered approach

This has been my inaugural real-case scenario, allowing me to engage in detailed discussions with my supervisor about aspects related to this patient's pathology. The email inquiry received by the genetic counseling department stems from the necessity to ascertain whether the identified variant (c.2169_2175del) is of germ-line origin or if it's a mutation specific to the colon cancer cells. The patient's medical history, marked by two instances of colon cancer (the patient and his father) and a third family member with polyps, suggests a possible inheritance pattern. However, the genetic tests conducted thus far have not confirmed any somatic origin variants. This verification carries significant implications not only for the patient but also for their family members. Firstly, confirming a somatic origin would reduce the likelihood of a Lynch syndrome diagnosis, possibly leading to alterations in future treatment strategies. As a bioinformatician, my familiarity with clinical criteria is limited, yet it seems likely that if a somatic origin is confirmed, additional measures such as screening the offspring or other close relatives (e.g., the patient's sister) would be undertaken. Considering the lack of evidence to corroborate the somatic origin of variants explaining this pathology, my supervisor and I have delved into the underlying reasons for the high incidence of colon cancer within this family. Our discussion has been constrained by the limited information about the family, as the necessary details were not provided in the reports we had access to. Several unanswered questions linger, such as whether these three medical cases are merely a result of unfortunate coincidence or if they could be attributed to inheritable factors that remain undetected due to current limitations. Personally, I'm uncertain whether this is a common occurrence or an exceedingly rare case where family members develop a pathology that hints at an inheritance pattern without any supporting evidence. Presuming that this is not an isolated incident, and possibly stemming from my novelty in the field, I find myself grappling with additional questions. These include the sensitivity of current techniques (the true positive rate) in the diagnosis of causative variants and the frequency with which existing variants may go undetected in patients subjected to current testing methodologies. These questions underscore the complexity of the issue at hand and the challenges faced in the field of genetic diagnostics.


Feedback of supervisor:

I would advise against including a comprehensive table like the one you're contemplating. While it might seem like a thorough approach, it's not particularly clear and might be cumbersome for the reader. Many people seek professional opinions precisely to avoid sifting through complex data themselves. The key point to remember is that they're requesting not just raw information but your professional insight. When you confirm that the coverage and/or quality is good, they will likely trust your judgment, as interpreting the data is within your expertise. Should the email you send become part of the patient's record in Starlims, providing a brief summary of the average coverage along with a comment on data quality should suffice.

In the same vein, the direct comparison between the observed sequence and the variant sequence may be an overextension. While it could be helpful, it's generally more relevant if you're referring to a variant that's actually present in the data. For better readability, I suggest using a monospace font like courier or consolas for alignments. This will ensure that the two sequences align perfectly, even if one has gaps. For example:

Using monospace:

```
CTGTGGAACACATTGTCTATAAAGC CTTGCGC TCACACATTCTGCCTCCTAAACATT
CTGTGGAACACATTGTCTATAAAGC ------- TCACACATTCTGCCTCCTAAACATT
```

vs.

```
CTGTGGAACACATTGTCTATAAAGC CTTGCGC TCACACATTCTGCCTCCTAAACATT
CTGTGGAACACATTGTCTATAAAGC ------- TCACACATTCTGCCTCCTAAACATT
```

This presentation is undoubtedly clearer!

As you gain more experience, I believe you'll grow more confident in your interpretations, feeling less compelled to include exhaustive copies of items, though screenshots can sometimes be highly beneficial. For now, if including extra information brings you peace of mind, it's a good practice. It's preferable to have too much information rather than too little.

Lastly, your observation regarding the read distribution was spot on and precisely what you'd expect to see. I suggest examining how some capture kits (e.g., Nextera, SureSelect) operate, and we can discuss why you might observe this pattern during our meeting on Thursday.

Monday, 4 January 2021

NHS Constitution and Patient-centred. An approach from a bioinformatic and a nurse

As evidence of my knowledge and skills relevant to achieving the Professional Practice (PP) competency, I find it pertinent to delve into part of my professional background. My journey into the professional world commenced in Spain, where I completed a three-year nursing degree in 2011. This was followed by four years of valuable service at a 220-resident nursing home, a semi-private institution that housed private residents as well as homeless individuals or those without family support. This period was instrumental in shaping my nursing foundation, enriching me with 1500 hours of rotational practice across various wards, including A&E and operating rooms. Simultaneously, my role in the nursing home first as a newly-qualified nurse, and later as head of nursing, armed me with crucial insights into patient care, emphasizing traits such as kindness, compassion, understanding, honesty, and courtesy. This early stage of my career was not only pivotal in nurturing my skills in specialized pharmacology, the medical conditions of the elderly, and leadership, but it also forged a profound connection with my patients. Through countless pleasant conversations and deeply personal interactions, I cultivated a unique patient-carer perspective that resonates with me both professionally and personally. I learned that socio-emotional conditions often weighed more heavily on health than medical conditions. This realization reinforced my belief that patients, rather than diseases, should be the focal point of care. Tailoring care to individual needs and preferences became my guiding principle. Two years into my role at the nursing home, I was promoted, opening new vistas in my career. As I grappled with responsibilities like audits, local guidelines, and compliance with legislation, I came to appreciate the delicate balance between management and hands-on patient interaction. Striving to maintain quality care, I found that enhanced communication among healthcare professionals could bridge the gap. This realization led me to champion regular multidisciplinary meetings, allowing for more individualized patient care. My insatiable thirst for science and a desire for fresh perspectives steered me towards a second degree in Biology and then a master's in Bioinformatics. These academic pursuits, blended with part-time and full-time positions, forged another formative phase in my career. A particularly memorable experience was my year in A&E in Kent, where I encountered diverse patient backgrounds. A recurring case of an elderly and blind patient taught me a profound lesson in patient care. His repeated early departures from the hospital due to religious concerns (he was a Jehovah’s Witness) were finally addressed by ensuring his involvement in care decisions and bringing in the chaplain to offer support. His case exemplified three key aspects of PP competency: understanding and respecting patients' rights, involving patients in medical decisions, and enhancing patient autonomy through health education. Over the past decade, these values have seamlessly transitioned into my new role as a bioinformatician in an NHS clinical genomics laboratory. Though I no longer interact with patients face-to-face, I'm acutely aware that my work continually strives to enhance the quality of people's health. Below are some of the bibliography consulted and readings that assisted me in penning this document: - Kiely, J. R. (2018) ‘Plan to restrict procedures goes against the NHS constitution’, BMJ, 362, p. k3706. - [No title] (no date). Available at: [Link](https://www.nhs.uk/NHSEngland/aboutnhs/Documents/NHS_Constitution_interactive_9Mar09.pdf) (Accessed: 4 January 2021). - OECD (2020) ‘More effective and patient-centred care’. doi: 10.1787/b36d9264-en. - Tingle, J. (2019) ‘The role of the NHS Constitution in balancing the care equation’, The British journal of nursing, 28(3), pp. 206–207. - Titchener, J. (2020) ‘Providing patient-centred care’, Diabetes Management, pp. 77–85. doi: 10.4324/9780429326196-12.

Sunday, 20 December 2020

Notes taken in the 2020 ACGS NHS Bioinformatics meeting

On the 18th of December, the ACGS celebrated the annual 2020 NHS bioinformatician meeting remotely in Cardiff. Below are some highlighted notes from this significant event. **Opening and Introduction**: The conference kicked off with a formal introduction about the committees and the collaborating organizations involved in this event, including BMGS, CGS, FGG, CGG, and AGNC. An announcement was also made about the next ACGS conference, planned for 2021 in Birmingham. Communication regarding the organization of this upcoming event and other matters will be disseminated via Slack and Github. **First Presentation: Genomic Partnership of Wales (GPW)**: Tom Connor from Public Health Wales started the meeting by detailing the services supported by GPW and its collaborations with other NHS departments (such as epidemiology, microbiology, and IT infrastructure) as well as entities outside the NHS like academic bodies and private sector companies. He continued to discuss GPW's work related to COVID-19. Since sequencing the first Welsh SARS-Cov-2 genome in March 2020, GPW sequenced over 15,000 genomes by December. This effort allowed for genomic analyses to trace the virus's ancestry, identify transmission across the country, and study variants from different nations. For instance, Spain was identified as the predominant source of cases from February to March. This presentation was particularly enlightening for me, offering insights into the direct applications of bioinformatics in current clinical and societal challenges. Tom emphasized how the government used this genomic data to make informed decisions about travel restrictions based on the origin of new cases. **Second Presentation: Wales Infants and Children’s Genome Service (WINGS)**: Joseph Halstead from All Wales Medical Genomics Service provided a technical overview of WINGS, a new service for rapid diagnostic testing in critically ill children with unexplained rare disorders. Though quite technical and sometimes beyond my comprehension, this speech shed light on areas where I should deepen my focus. **Update from The University of Manchester**: Andrew Devereau updated us on the challenges faced by The University of Manchester, revealing that the second semester would be conducted entirely online. Despite this, most feedback has been positive. **Short Presentations by STP Trainees**: The second half of the conference featured four brief presentations by STP trainees. For example, Maria Lock introduced MosaicMiner, a new bioinformatics pipeline for low-frequency variants detection, while Laura McCluskey discussed an innovative NGS pipeline to detect fusion in RNA. These presentations were quite inspiring for my STP development and provided ideas for potential research projects. **Conference Closing Discussion**: The conference concluded with a brief discussion on various topics, though limited participation constrained the content. The subjects covered included: 1. **Adapting to Training during COVID-19**: Adriana reported on a remote training event for STP Trainees in Cambridge using Zoom and Slack, highlighting positive feedback. Also mentioned were theme-based meetings for trainees and training officers, providing opportunities to discuss managing training during the pandemic. 2. **Somatic Bioinformatics Best Practice Guidelines**: Progress on this work has stalled, and the speaker expressed a desire to expand the team working on this topic. The meeting served as a valuable platform for sharing information, updates, and ideas among professionals in the field of bioinformatics. While some presentations were highly technical, the overall experience provided key insights and inspiration, underscoring the importance and adaptability of the field during these unprecedented times.

Monday, 14 December 2020

Good Scientific Practice

        "An expert is a person who has made all the mistakes that can be made in a very narrow field"

                -- Niels Bohn


Today, I want to explore a topic a bit different from the ones I usually address in this blog, but one that's incredibly vital to my profession: Good Scientific Practice (GSP). Specifically, I aim to offer a reflective thought on personal values, principles, and assumptions, and how these can influence personal judgment and professional behavior—all in relation to GSP. In this post, I will summarize what I believe are the significant principles and values underpinning the good practices conducted by a clinical bioinformatician.


I define GSP as a set of values and standards applied throughout the career of any professional involved in healthcare science. Healthcare professionals come from diverse fields, so these values must be contextualized for each particular role. However, a core ethos can be applied universally at any level of practice. In this brief document, I'll mention and explain this set of shared values before focusing on those especially pertinent to a clinical bioinformatician.


Clinical scientists often deal with patient care, and patient well-being is our foremost concern. Even though, as a bioinformatician, I don't interact with patients directly, I always keep in mind that each patient is an individual whose dignity and confidential data must be treated appropriately. To achieve this, several key elements need to be performed:


- Maintain up-to-date professional, technical, and scientific knowledge and skills to make sound judgments.

- Recognize your personal competence limits and consult or seek advice if unsure.

- Develop skills to work effectively as part of a multi-disciplinary team.

- Foster a friendly environment where colleagues are comfortable.

- Be proactive and seek to bring out the best in your team.

- Contribute to the education of colleagues, recognizing that each member has a unique background.


**Personal Experience**: Working in Cambridge, I recall a technician who was neither a leader nor a manager but was considered a key person in the group. For reasons unknown, this individual's absence for a few weeks caused the group to lose cohesion.


Since clinical scientists also engage in scientific pursuits, good practice includes not only research reliability but also technical excellence, quality, innovation, and development. Inherent principles of scientific method—such as objectivity, impartiality, fairness, credit attribution, and the responsibility to impart knowledge and train future scientists—must be maintained.


Science, especially genomics, is in constant flux, advancing rapidly. To be effective professionals, we must stay abreast of the latest developments in our field. Since much of our work involves diagnosis, treatment, screening, prognosis, and monitoring, it's vital to know the latest strategies and procedures to ensure quality and safety.


Good scientific practice also requires solid technical practices. This domain can be challenging to define, particularly in the context of a clinical genomics laboratory. Good technical practices involve principles designed to assure the quality and reliability of services. This includes adhering to methodologies, handling measurements and analysis, and managing risks associated with hazardous substances.


In clinical laboratories, ensuring a high level of quality and standardization is crucial. We must assess and evaluate new technologies in collaboration with peer laboratories, participate in quality assurance programs, develop standard operating procedures, and continuously seek improvement through effective audit trails.


In conclusion, this post represents a synthesis of ideas I've gleaned from my experiences, supplemented by additional research. Other important factors may exist that I've either forgotten or am not yet confident enough to discuss, such as those related to leadership and management. Nonetheless, the principles and practices I've outlined here provide a foundational understanding of the essential aspects of GSP in the field of clinical bioinformatics.