 Thank you very much. So for the next session, those of you who saw Heidi's face pop up there, it's because one of our presenters is participating remotely. And so Dan, you're going to be coordinating this group, right? Trying to multitask as well as the overall note taker at the session. I'll take notes. And so the group is moving up there. So this is the exciting, several times alluded to session on novel and disruptive opportunities in genomic medicine. And again, because there was a lot of interest in this session on the organizing committee, they were often also given a little bit longer of a time slot. Dan, turn it over to you. Okay. So thanks for bringing me into this session. Sorry, I couldn't be there in person. So if Qatar and I are going to split the first presentation, I'm going to focus a little bit more around the interpretation side of this session. And so I just wanted to start with kind of the current eMERGE workflow in terms of data delivery. And so those of you who are involved in eMERGE may recognize this sort of diagrammatic figure in the case of eMERGE today with nine sites that are all delivering orders and information to two different sequencing centers that work to harmonize activities and share data into common resources. But then the genetic reports are going back to each of the sites from only one of the two sequencing centers. And each of those deliveries in some ways is being customized in order to bring the genetic information into the electronic health record environment. So there's many custom processes for data integration. In addition, the only data that's actually being brought into those systems are really what's being reported from the sequencing. And that's generally the likely pathogenic and path variant from a limited set of genes and a few SNPs that were chosen. So I think as we think about novel and disruptive approaches, we really want to think beyond this. And you saw a piece of this from Sandy's presentation in the last session. But as we think towards eMERGE 4, although we may or may not think about a core sequencing support for the eMERGE network, I think we also have to embrace that there are external reference labs, internal hospital labs, even direct consumer sources of genetic information that are being brought into the care of patients. And I think we need to think about integrating all of those sources together as a unified genetic source information that can be brought into the EHR. And that may not be directly into the EHR. I saw a lot of us recognize some of the limitations of the existing EHR systems, but certainly ancillary systems that communicate with the EHR thinking about bringing all of those different sources in, including knowledge sources like ClinVar, which is evolving. We also have to think about how to keep patients up to date with that information. And that may include systems to alert physicians to knowledge changes as we bring updated genetic information into the systems and be able to update the information that may come from reference labs, internal labs, direct to consumer, or even research programs. We also have to recognize that physicians who care for patients change over time, yet those patients don't need information to be updated. How do we interact with patients, even the absence of physicians who are still caring for them? So I think the areas of emerge opportunity in terms of knowledge updates are really building on standards for structure reporting and being able to work with all sources of genetic data, ensuring all genetic data is kept in structured forms for us to build on it, as well as determine how and when to update genetic knowledge and alert physicians. And this also is probably an opportunity for ClinGen to partner with Emerge in this setting. Another thing, and I think Mark gave an example in one of his questions in the last session, is how we think about real-time use of genetic information, even information that hasn't yet been interpreted in a particular context. So in the top, you have a patient with who may show up in your office with symptoms or a family history. Can we think about ways to directly engage genomic data in real-time? And I use this sort of traffic light scenario where a physician is concerned about a particular scenario with the patient, and by being able to real-time access that genetic information, they may be triggered to immediately order clinical genetic tests because the system already shows that there's potentially a pathogenic previously interpreted variant in their genome. Or maybe there's a variant that's novel, but suspicious, hasn't been interpreted that might trigger the physician to consider a genetic test with a degree of uncertainty about that genome. Or when the symptoms are mild and the genome says there's nothing in any gene related to this indication, that might prompt them to not worry about genetics. So thinking about how can we in real-time engage with the genome, I think it's something that we really need to start thinking about how to do. So in order to support this, there's a lot more work to improve standardized data models for genomic data, as well as thinking about the quality standards for which variants are brought in. If these are non-confirmed and interpreted variants, they vary in their quality. And I think an opportunity for eMERGE4 is thinking about the details around the standards for how we interact directly with raw genomic sequencing data or variant call files, but then you have to really think about standards. Yeah, go ahead. Sorry for interrupting you. There's some gray box. Do you know what, is it some rocks you can minimize? Well, I keep trying to move it. It's my own video image that's sitting there now. Sorry, trying to get rid of it. There it goes. Okay, thanks. I moved it. And then the other thing is just the decision logic for using uninterpreted data and how do we develop ways to ask questions and have scenarios of dictating clinical care based on the data that's seen. The third scenario that I wanted to talk about is really using the enhancing how we can think about variant interpretation. So the current eMERGE workflow is just like standard genetic testing. We take an order with very limited patient data in from the site, which may only be a overall diagnosis or they are healthy, is our indication for testing really in the laboratories are pulling mostly public knowledge sources. They may be articles published in the literature or data in CUNVAR as our only source of information to interpret those variants. But I think what we would see is a real time integration of population information, perhaps even direct patient data from survey data that access could support performing genetic interpretation. And that will require better common and rare disease phenocytine data in EHR, the ability for patients to contribute to that phenotypic data, as well as infrastructure for labs and clinicians to access aggregate and individual level patient data from many sources. And that would allow us to more richly and thoughtfully interpret genetic data as we deliver that those results back to the patient. So I'm going to stop there and turn it over to the next section.