Okay. So, hello everybody. Hello guys. Welcome you. I would like to welcome you on today's session. Unified networking for VMs and containers in OpenStack on Kubernetes. My name is Artur Korzenewski. I'm working as software engineer at Intel. My name is Wadi Meriderman. I am working as software engineer and deployment engineer at Merenties. Yeah, we have prepared some research about how to connect VMs in one environment, networking environment. So, for our purposes, we defined unified networking as VMs and containers being in the same network that can reach each other using IP or L2 or L3 technologies. So, maybe first question to the audience, who is already familiar with technologies like Courier, Kubernetes, Galico, I guess a few. I'm seeing that there's also an expert of Galico and Courier, so it's good. So, why even do we want to join these two technologies, containers and VMs into one single, let's say, network? It's because microservices and containers are gaining popularity and also all the workloads are run inside data center in VMs, so it would be good to have them connected somehow in the networking layer. We can imagine use cases like front-end stateless services deployed in container and background like database services deployed inside VMs. And also, what's nice about having unified networking is have one single API, which will be like OpenStack Newton API for managing all the workloads in your cloud. So, our assumptions are we are using OpenStack on top of Kubernetes cluster, so every service is containerized and we can leverage features from Kubernetes like failovers, resilience, and so on. And like OpenStack is very popular and has stable APIs. It's good to use this API to manage both VMs and containers' networking layer. So, Kubernetes is very reliable, funded by Google, and has proven container-on-crestation engine techniques, and OpenStack on Kubernetes is bringing us ease of deploy, fine-grained control over the placement of services, of OpenStack control plane, and the ability to do the rolling upgrades and self-healing services. And today, we will concentrate on Bermeter containers, which is... We're not talking about Magnum and nested containers that are running inside VMs for security and other reasons. And, like I said, we have chosen two technologies, like KaliCut and Kooded Plus OVS for L3 and L2 connectivity purposes. Of course, there are other technologies like OVN, OVN, Flanner, Wave, and Romana, which is doing the same, but we didn't have time to cover all of them in this presentation. Speaking about Bermeter containers, there is a big OpenStack installation. There are many points for the employers which we are facing too. First of all, we need to make some multi-tenancy technology for big network, and there is actually not such a big variance of options. There is L2 segmentation with VLAN. Tunnels is growing, and VXLan and Ginev and GRE is all the way to segment data, data tenant traffic, and with KaliCut and all the technologies, like Romana, we have another option to segmentate tenant traffic using L3 segmentation, where either firewalling, like in KaliCut case, either IP namespacing, like Romana case, is using to segmentate traffic inside the data center network. For HAP services, in data center cases, we have also not so much of options, because either we need to install a lot of balanceries using IPvase, a bunch of HAP rocks behind the very repeat, or either we bought some expensive hardware which serve 10 geeks or more of traffic. So for designing big data centers, we frequently need to invent some options to terminate traffic on many boxes and we frequently start using OSPF or BGP endpoints to make multi-pass routing and Kubernetes on bare metals and KaliCut uses BGP as pretty helpful for this. Also, for exposing services to the Internet, we need to somehow terminate all this traffic, not only inside the cluster, like Kubernetes does with their cluster APIs, but terminate traffic to the Internet, so we can somehow make a filtration and fair warning of this traffic. Next button. So speaking about Kubernetes model of networking, Kubernetes doesn't really care about how the networking is working behind the stack. It implies that we can communicate it without any other port, without any nut, and it gets the same IP address inside the net name space and outside the net name space, but Kubernetes container somehow detects the IP address and sends it to configuration server, so another port could communicate with this IP address. And Kubernetes afflows all the communicating between ports to their CNI plugins, so Kubernetes doesn't really care about how the networking is working. So CNI driver handles how the VTH pair is set up, how to connect it to some networking gear like bridges in a career case or like routing setup in Calico case, and also it's a type of underlying infrastructure if it exists. Also, Kubernetes implies multi-tenancy models, so every port has a label with a attribute which namespace it runs belongs to and networking technologies that provides some firewalling between namespaces could leverage this labeling to set up multi-tenancy isolation between tenancies. So Calico is providing not only routing for VMs, but also multi-tenancy isolation. So, for example, you could set up Calico policies to firewall traffic between ports so you can communicate between ports of different namespaces. Another hard part of Kubernetes on bare metal is how to set up external access to Kubernetes. Basically, Kubernetes provides two proxy mechanisms that set up kind of load balancer using IP tables and it's set up virtual IP on every node and port could communicate to service which is a set of port using a well-known IP address which is built into service and it could be accessible so every Kubernetes node. This mechanism also could be used to make access to service from outside for implementing this you can set up external IP to the services but there is also a problem because as the IP tables is using stateful node, you need to somehow synchronize your state of node in case of your service IP will be set on different nodes. So if traffic goes to the next node, for example, it's that multi-pass routing for a data center, IP tables on the second node will not be known how to send the traffic and you possibly get your traffic to another port and your TCP flow will be broken. Another case to solve this is using Kubernetes not port technology where Kubernetes sets not for virtual IP address but for port on some of the node and you set the load balancer behind of your infrastructure to somehow balance traffic between your Kubernetes nodes or dedicated network nodes for this. But this requires another part in your infrastructure another single point of failure. So actually the point is Kubernetes on bare metal still have no any clues how to expose services. They try to cover this case with Ingress L7 proxies which could use as a programmatic router to HTTP services or every service which is right now can be proxied by Ingress but the problem is still the same. Nginx is still the Kubernetes port and it still requires to somehow handle balancing for them. Either you could put Nginx to the hostnet mechanism and somehow configure VRP to share the same IP address. So right now Kubernetes for bare metal is handled well on the internal port network using Kaliq or other technologies but still couldn't be used well to handle external traffic. So to have a good view how OpenStack networking can be mapped into the Kubernetes abstraction into OpenStack networking model. I would like to show what's the data abstraction for Neutron. Neutron has ports which has this connectivity information for single endpoint, single VM, single port and subnets which defines IP address ranges, delivers gateways, DHCP and DNS configurations options and networks which holds subnets and ports inside one bucket so every port on the same network should have equal connectivity. Security groups for managing their access control to the endpoints to the VMs, setting up the firewall like in IP tables and so on and so forth like IPs which provides external public irritable IP addresses or in data center use case some accessible IP address that is inside the corporate network range and for how the services are designed are placed on the computer network node the VMs on compute node connected with tap interface with firewall bridge, Linux bridge when you are using the hybrid firewall inside OVS and integration bridge with all VHD interface connected with the Linux bridge then the outside traffic is handled by tunneling bridge or VLAN bridge it depends on your use case and tenant network's configuration and on the network node you have the tunneling or VLAN bridge with integration bridge connected with Vrouter name spaces where the routing is taking place so in usual scenario the legacy scenario when you have centralized network node the traffic being recruited from one VM to the other VM in other tenant network should go through the network node so it's like when even two VMs are on the same node they will need to connect each other using the network node of course if you are not using the DVR and then it will be routed on the compute node and also in both cases DVR and legacy scenario network node is handling the source node so for fixed IPs reaching the outside internet access Okay, but Mkallika network is designed very differently than OpenStack network which provides a big IP segment to all of your cluster which is then segmented to small subnets like 26 for this case and each of this subnet is set on every of Minion and pod gets an address from this name spaces on every node and to make this platform networking works Mkallika propagates every of these small raw prefixes using BGP protocol so for example first node gets the raw name space of second node use BGP that is set by Mkallika internals also BGP could be used to integrate with data center span leaf or L3 top of the rack with routing capabilities or even closed apologist to propagate all the IP routers that are set on every node so you don't need to set up any nuts and internals you just push your routing information from the node to your network infrastructure and it erodes your IP packets like usual without any special processing also Mkallika provides isolation for every node so for every pod or every other kind of workload you set by setting up endpoint firewall like OpenStack does with their security groups so you can stop fine grained firewalling using somehow the same terminology that we familiar with security groups so you can filter traffic by ports, by source addresses and also by belonging to another workloads so you kind of erode traffic from one name space and forbid traffic from other name spaces it's not updated and I can show this so I talk about external network node to make Mkallika working with external traffic you can set up the Kubernetes proxy on every node erode traffic for every of these nodes but another case you can build for made-up installations is dedicate some of Kubernetes proxy node which is running on the Q proxy component and then either distribute routing to your gateway using BGP or just set up common address address around the C for every of your service using either manual setup of Carp, ERP name or using some of Kubernetes helpers that are already designed to set up ERP using a Kubernetes API this case will provide you with much more fine grained control of how the traffic flows by not using or routing to Kubernetes external IPs and using common address redundancy could run into a case where the traffic could get on the node where the IP table state doesn't share it So the second use case is using Qtir to manage connecting VMs and containers So what is Qtir? Qtir is OpenStack BigTent project that aims to provide nodes for networking into the containers So it's already supporting Dockerlib network and Kubernetes support is under development as we speak and as I prepared this presentation one month ago and it was still evolving so some kind of information can be updated in the master branch that may be already available So what does Qtir do is provide the CNI driver for the QBLET on the worker node and the CNI driver and API water which was called Raven You can see this, yes So it's working like in a manner when you start containers inside the Kubernetes CLI Raven is performing crude operations on OpenStack Neutron server creating ports, subnet, or subnet are already created inside Neutron and when the pod is placed on the node the Qtir CNI driver is asking for the connectivity details For example, when you're starting pod Raven will ask for Neutron server to create the port like it's for the VMs like Nova is doing Then return back to Kubernetes API with annotations details Inside annotations there are details how to connect and what's the port created for this new started pod and then on the worker node CNI driver will ask for the annotations from the Kubernetes API server and then connect the pod with VATH pair with the obvious integration bridge As you can see on the screen there's also VMs connected to the same obvious and in this case you can have the L2 connectivity between VMs and containers So the worker layout is networking services on worker node is that you have containerized Qubelet CNI driver, containerized Nova compute and Neutron L2 agent and obvious is also containerized here and for the connectivity like I said the VATH pair is connected also with Linux bridge and the courier driver is doing that setting up the port inside the integration bridge and connecting it to the pod It's similar what Nova compute does which is setting up the tap interface and plumbing it into the integration bridge and with these two ports Neutron L2 agent is responsible for wiring it up with port details from Neutron server What should be the local VLAN if it's the same network on that already existing or on any other and also connecting it to the tunneling bridge So on the network node you can see that it can be done twice So when you install courier it can create default subnet for workload and service service IP and it can be like I've seen that in current in master branch you can specify that don't create new one you can use already existing ones in Neutron but you need to map it before you can start Raven because the IP API watcher is asking for subnet and workload subnet for workload and service cluster IP creation and as well you have this Neutron L3 agent, DHCP agent, L2 agent metadata and so on obvious service containerized So this is kind of when you start up and your courier and Kubernetes plus Neutron you will get this kind of layout when you will start new pod with for example two replicas it will be spawned on network, sorry on worker nodes like I've talked on previous slide and there will be load balancing you can use load balancing instead of Kube Proxy for creating the HA Proxy instance and expose the service like it's designed in Kubernetes networking scheme so every pod can access each other using this workload subnet and as well using the service cluster IP subnet and you will be having access to both of them and this 10.10.223 and it will roundtrob in the request for the pod or any other load balancing mechanism you will set up inside the HA Proxy for example and when you will start VM you can use the same workload subnet so it can be spawned using the same subnet and you can gain the connectivity between the pods and VMs like on L2 level and as well using the router VM can also reach the service cluster IP subnet and the load balancing mechanism and so when you want to expose your service to the internet you need to connect it with floating IPs that you have defined and have the pool for your usage so I have done it manually but I'm not sure how about current status in master branch for courier because you can use the same API that you are creating the floating IPs for VMs and then connect it into the HA Proxy load balancing port so you can define that in some kind in external subnet this load balancing 4.3 IP address is connected to the load balancer and then you can gain access to these two pods underneath the load balancer so it's kind of double routing the mechanism because you will access the load balancer first it will redirect you to the pod currently to serve your request and so there's more the model mapping as I said it's important so the namespace is connected is mapped to network in OpenStack from Kubernetes namespace to OpenStack network and the cluster subnet is mapped to subnet pool because in Kubernetes use case you can have the slash 24 or any other subnet connected to each compute node so you can map it to this cluster subnet and service cluster IP range like I've talked is HA Proxy so it's virtual IP address inside this load balancing subnet external subnet is mapped to floating IPs and port is of course port so it holds the default information about IP and MAC address and the service itself is mapped to load balancing mechanism inside OpenStack terminology so what's the pros and cons about using Courier it's like it's big tent project it has good community and it's have simple architecture and taking advantage of the CNI pluggable architecture in Kubernetes also Courier can support other technologies, networking technologies it's not only of yes but it can take advantage of Open or any other so it's using Newton API so it's what we wanted to achieve single API for all the workloads management system for the VMs and containers so the VMs and containers of course gets its L2 connectivity and you can get the security groups applied for both VMs and containers so I forgot to mention about Raven Raven is also creating security group inside the Newton API and Newton security groups so you can apply the same security groups for both containers and VMs and what cons that I name it next steps it's that it's not ready yet like it wasn't released maybe it will be in short period of time some time ago it was working only on Python 3 but I've seen that there's already merge changes that it port the Asyncio library into EventNet into Python 2.7 and so like I presented the Kube proxy have to be replaced with some other load balancing mechanism and for better scalability and high throughput workloads and what's the bigger disadvantage of using Courier it can be used only for overlay networks so for the workloads and when you will install Courier you need to provide all the Kubernetes and OpenStack containers working in some kind of networking scheme so it's like I've seen that some team has used Flannel for setting up the OpenStack on top of Kubernetes and then we had added Courier or you can add Courier for the workload mechanism to reuse the networking created already in OpenStack yes so the last point is that I've seen that it should be already addressed on master branch in Courier that you can reuse the existing networking created inside Neutron to create pods on Kubernetes site so this is kind of resources that we used for these presentations and I guess legal notice Q&A I can leave the resources page so do you have any questions? I've got a microphone here so if anyone would like to ask a question sorry you need to turn it on I forgot hello so couldn't you use Courier with Calico? Calico has a Neutron yeah yeah so it's also possible because of the Courier we'll be using it's already using OSVF to connect the interfaces it can be plug-inable to use it with other networking drivers not only OVS it has the plug-in for Calico as well right? actually Calico could be used as a Neutron backend but if you use Courier to connect container workloads using Calico as a backend it may be a chicken and a proble and you may prefer to use Calico natively to the containers in CNI and using networking Calico plug-in for Neutron ML2 to connect UVMs to Calico thank you you can use also Calico for the underlying networking so you can set up Calico as networking for OpenStack services and then use Courier for workloads there so you can have also that kind of mix any other questions? if not then thanks thank you very much thank you for attending


All right, why don't we go ahead and start? Again, thank you everyone for tuning in this afternoon or this morning or whatever time it may be where you're at. My name is Bob Trug. I'm the director of the Center for Bioethics at Harvard Medical School. And this is a part of our series on contemporary books in bioethics. And today we are really excited to have Dr. Stephanie Green discussing her recent book, This Is Assisted Dying. Let me give you a little bit of background on her from her bio. After obtaining her medical degree at McGillnate University in 1993, Dr. Stephanie Green completed a residency in family medicine and then fellowships in palliative care and infant and maternal health. After more than 20 years in practice and in conjunction with a change in federal law in Canada, Dr. Green began working in medical assistance in dying or what we call made in June of 2016. She is co-founder and president of the Canadian Association of Made Assessors and Providers. Not sure how you pronounce the acronym. Cam app. Cam app, cam app. Okay, thank you. You got it. Cam app, cam app. Medical advisor to the British Columbia Ministry of Health and made oversight committee, moderator of cam apps, national online community of practice and as hosted three national conferences on the topic. The book, This Is Assisted Dying is a memoir of her first year providing assisted dying in Canada and it is her first book. Just a word of logistics here. As I'm sure almost all of you are familiar, you've got two functions down there at the bottom, the chat box and the Q&A. We're gonna be using the Q&A box exclusively in terms of what we'll be monitoring and looking at. So you can put things in the chat box, but there's no guarantee that any of us will see them. But please do put your questions in the Q&A. I'll be keeping an eye on that and we'll have a few minutes at the end to get to those. But for now, why don't we go ahead and get started and Dr. Green, thank you for joining us. Thanks for that. I'll just take a moment to set this up properly. Great, you're seeing my slides, I hope. Yes, we are. Great. Thanks. Good afternoon, everybody. And thanks for that introduction, Bob. It's a real pleasure to be here with you today. I've taken this opportunity, of course, to display the cover of my new book. Unlike today's slightly more academic presentation, this book is a narrative memoir. It's more of a personal journey through my first year of providing assisted dying and it explains what it is and how it works and how it feels as a physician to administer the drugs that will end a person's life. I'd like to suggest that it's a worthy companion to today's talk. But today I actually want to give you a different type of overview. I want to speak to you more as colleagues and peers, as medical students, professors and interested guests. So what qualifies me to give this talk? Well, as you've just heard, I spent 20 years in maternity and newborn care before I changed my focus to assisted dying in 2016. And oddly, because 90% of my clinical work now is based around this care, I have become one of the more experienced providers of Maid in Canada. I flag two potential conflicts with today's talk just to mention briefly. And while I'm tremendously proud to say that I'm the co-founder and president of the Canadian Association of Maid Assessors and Providers, that is CAMAC, please note that nothing I say today is on behalf of that organization, should be taken as a reflection of that organization and all thoughts and comments, of course, are strictly my own. And of course, I have recently published a book and while I'd like to think that it would be insightful and of interest for you, you certainly don't need to buy it or read it. So in the next short hour, in about 30 to 40 minutes, I'm gonna just, in very broad strokes, I wanna first define what it is that I'm gonna be talking about and I'm gonna contextualize it so we can understand why we're talking about assisted dying and how it might be relevant to your world in Boston in 2022. I'm briefly gonna share some data. I'm gonna highlight some practical implications of the work. I'm gonna touch on the role that clinicians have played in the evolution of assisted dying in Canada and I'm gonna end with a few lessons that I think are relevant to anyone in a jurisdiction that's considering assisted dying legislation and of course make sure to leave time for questions and answers at the end, which I think can be the most interesting time. This is not, of course, a scoping review of the topic, it simply can't be, I would need more time for that, but I do hope it's relevant to the audience today. I hope it's informative and maybe challenging and if we can dispel some myths and misinformation, that would be all the better. So what exactly am I talking about? Well, depending on what you read and who wrote it, maybe who published it or what year that happened, you might come across quite a bit of different or even confusing terminology. So that may be very clear from the beginning what I mean by my terms. So assisted suicide or physician assisted suicide, these are terms that are still used quite often in the United States. They're meant to describe the situation when lethal medications are prescribed by a healthcare practitioner, but that they're self-administered by the patient and often without the clinician being present. So it's usually a drink, usually a mixture of foul-tasting barbiturates to be precise and the person usually holds it and needs to drink it themselves. So the modern understanding of the term euthanasia by contrast is defined as the administration of the lethal medication by the healthcare professional. So it's always at the explicit request of a competent adult and it's with the goal of relieving further pain and suffering. So it's also the preferred term that's used for assisted dying in Europe today. So the key difference between assisted suicide in euthanasia simply is who administers the medication, the patient or the healthcare professional. Now Canada consciously chose to use a different term that of medical assistance in dying or made. So we don't talk about assisted suicide or euthanasia in Canada. In part, that's to avoid negative connotation. So outdated phrasing, such as someone committed suicide implies that maybe a crime was involved or it could. And opponents sometimes invoke the term euthanasia in order to specifically conflate assisted dying with the repugnant history of Nazi use of the word during World War II when it was used euphemistically for the killing campaigns. So not only does the term made avoid these associations, but it's also designed to be an umbrella term because in Canada, we have both self-administered and clinician-administered assisted dying. So Canada is one of only four jurisdictions in the world where that is possible, where both of these options are legally available and the Netherlands, Belgium and Luxembourg, of course, are the other three. So no one ever talks about Luxembourg. And everywhere else you might hear about assisted dying in film or in books or in lectures, everywhere like Switzerland or Australia and in some United States, these only allow a self-administered form of care. So for greatest clarity, I'm just going to simply use the term assisted dying to refer to any and all forms of this compassionate healthcare that I'm talking about today, although I will probably lapse into using the term made because I'm so accustomed to it in my own work. So that said, I do wanna just point out that when I began working in assisted dying in 2016, there were five American states that already allowed some form of this care and six countries outside of the US that allowed some form of made. So six years ago, you could say there were 11 jurisdictions globally offering some access to assisted dying to basically about 180 million people. Now, today, there are 25 jurisdictions that allow some form of this care and they include 11 regions in the US alone, as well as the entire country of Canada, of course, and it grants access to over 475 million people worldwide. So it's more than doubled. In fact, just since 2019, assisted dying has been newly legislated, implemented or offered in three United States, in New Jersey, in Maine, and in New Mexico, most of Australia, all of New Zealand, Spain, Austria, and is currently being debated in the House of Lords in England, in the Irish legislature, in the courts of Italy and Portugal, and in a complex mix of professional and legal environments in Germany, just to name the most active. As for a detailed overview of the current situation in the US, I cannot and will not cover that today in any great detail, but I do think that this map might be helpful to visualize the current landscape in the US, where the green-colored states demonstrate where assisted dying is already legalized and the year in which that became true. The light kind of salmon-colored highlights are the states that are considering legislative change, including Massachusetts, and the birch-orange-colored states are regions where there's no current intent or interest in doing so. And I'll just thank Death with Dignity, a national advocacy organization for the basis for this map, and Mara Bookbinder, a medical anthropologist down at UNC Chapel Hill for her work to update and add to the map, and of course, her permission to share it with you today. So as for the various variabilities among the state laws with respect to eligibility or procedural safeguards that are in place, I'm gonna just refer you to this article by Thaddeus Pope. Please note, though, that changes continue to happen at a pretty rapid pace, and therefore this article from 2020 is already slightly out of date. But by way of example, even less than two weeks ago, you may know that an important court challenge over residency requirements reached settlement in the states. So until now, you had to prove residency in the state before you could be found eligible for an assisted death. And that residency requirement was recently challenged in the state of Oregon, and less than two weeks ago, it's no longer required. So this is likely gonna spur similar challenges in other states with similar residency requirements, and there may be more changes coming. And of course, I would be remiss if I didn't recognize that the topic of assisted dying might be of special relevance to today's audience. Of course, as Massachusetts highest court is hearing the appeal of Dr. Roger Klegler, a physician and a patient who's asking the courts to allow physicians to prescribe lethal medications for terminally ill patients who want to end their lives. I understand that the state's attorney general is arguing that doctors who prescribe such medications could actually be prosecuted for manslaughter, and that in her opinion, the issue is one for lawmakers and not the courts to address. But lawyers for Klegler, of course, argue that the court shouldn't act because the lawmakers haven't. And I suspect you're also familiar with the fact that voters narrowly rejected a 2012 end of life ballot question in Massachusetts, and that multiple end of life bills have not progressed through the state legislature, but that recently a new end of life act was introduced in 2021. And there's actually a suggestion that there's gonna be a potential vote on the matter in 2022 in your region. I also actually understand that just last week, your state's attorney general was quoted as saying she's now open to working with the medical community and with patient advocacy groups to consider changes in the law. So it sounds like things are moving in Massachusetts. So that said, in that context in place, I do wanna take a few moments to just describe some basics of the assisted dine model that I work in in Canada. I think it'll inform the rest of our discussion later on and probably help with the Q and As. So bear with me as I take a few minutes to explain how this came to be and how assisted dine works in the Canadian model because I do believe it is somewhat unique. So in an effort not to get too deep into the Canadian weeds, suffice it to say, because I could get very deep in those weeds. I suffice to say that in 2011, two women and their families challenged the blanket prohibition of assisted dine that previously existed in all of Canada.  So Kate Carter, it needs to be noted was an 89-year-old woman suffering from spinal stenosis. So a progressive, painful, non-terminal condition that caused her intolerable suffering. So she ultimately chose to go to Switzerland and receive an assisted death in 2010. And Gloria Taylor was suffering from ALS, it's a cruel and as you know, a relentlessly progressive neurologic condition which would of course ultimately be disabling and fatal. So appealing to the Canadian Charter of Rights and Freedoms, the Carter lawsuit argued that the prohibition of assisted dying violated certain patients' equality provisions and their rights to life, liberty and security of persons. Patients like Carter and Taylor who were what was termed grievously and irremediably ill. So basically very sick and incurably so. Interesting, there we go. Now I am not a legal scholar and I will not go into the really interesting legal arguments that I've come to understand. But Justice Lynn Smith, a constitutional expert I'm told, wrote the original trial decision and she agreed. She also considered a tremendous amount of evidence and she concluded that A, clinicians are indeed capable of assessing people for the uncoerced capacity that's required to make requests like this, meaning clinicians know how to do their jobs. And that B, that data does exist that shows rigorous models of care that can be implemented or that there were in fact international models and evidence of such examples and that they appear to balance the respect for individual autonomy while also reasonably safeguarding the most vulnerable in society. So it was an important decision. And the original trial victory was overturned on appeal but eventually it was unanimously upheld by the Supreme Court of Canada. So practically speaking, the court had carved out this blue square from within the black box, the circumstances under which the provision of an assisted death would no longer be criminal. And that was when it was requested by a capable adult who was suffering intolerably from a grievous and irremediable condition. You will please note that Canadian law did not change because voters demanded it or because government felt like it was a good idea but because patients demanded it based on their constitutional rights. And that was a unique basis for assisted dying globally at that time. So our whole model of care then is rights-based and completely patient-centered. You might also note that nowhere in this decision is there a requirement that the person be terminally ill or even near end of life. So that invalidity of the criminal code provisions, that was suspended to allow the government time to act. And then in 2016, 16 months later, the federal government enacted legislation that was however more restrictive than the conditions outlined in the original court's decision. So it's represented by the smaller green pentagon. So specifically, while the courts didn't require a person to have a terminal illness, the new government legislation required a person to have what was termed a reasonably foreseeable natural death, a term that nobody understood. But eventually we did come to understand that it meant that death was reasonably predictable really in kind of medical speak and that it had no specific timeframe imposed around that however. So that could mean it was temporarily related to death. There's a temporal proximity to death that someone might be dying soon, that death was coming soon, say a person with stage four pancreatic cancer or that death might be predictable because of the person's combination of known medical condition and the potential sequelae. So maybe a diagnosis of ALS or significant heart disease or significant lung disease. So again, no timeframe around that but just on a trajectory to work that predictable path. The story didn't end there.  And in 2021, so very recently, just a year ago really Canadian legislation was amended so that that requirement of a reasonably foreseeable death was removed and it took the federal legislation a significant step closer to the original Supreme Court decision which we refer to this change as C7, it was the bill. This is important to understand because sometimes opponents will talk about slippery slopes and suggest that Canadian law has been expanding rapidly since it began. But the truth is we had a court decision that was much more open. We had initial legislation that was much more restrictive and we now have something in between. So without all in mind and for reference as much as anything else, I just wanna demonstrate that we're not so grossly different than most jurisdictions. I'm gonna tell you that current Canadian law now states that to be eligible for an assisted death you need to be A, an adult over 18 years of age. You need to be eligible for Canadian government funded healthcare services. So you don't have to be a citizen but you need to be eligible for our healthcare. So essentially tourists can't come to Canada and pay privately for this. That is not legal and I don't expect that we'll ever change. Patient needs to make a voluntary request for this care. They can't be coerced into this by any other person or something internally or externally has to be an uncoerced voluntary request. Patient needs to have capacity to make the request for made and give informed consent. Essentially they need to understand their illness. They need to understand their treatment options and the pros and cons of them and the possibility of palliative care and what they can offer them. They need to understand and appreciate the ramifications of their decision for themselves and their loved ones and to articulate that request. So that's all involved in the capacity and the giving of informed consent. And of course they need to have what we've called the grievous and irremediable condition. And that is currently defined actually in the criminal code of our country. You can see this is quite rigorous. Currently the definition of a grievous and irremediable condition implies that the patient has a serious and incurable illness that has put them in an advanced state of irreversible decline and function essentially and that they're enduring a suffering that is intolerable to them and cannot be relieved by any means acceptable to them. So I know I went through that very quickly. A little asterisk is there for me to remember to tell you that with our current legislation if a mental health disorder is your sole underlying reason for applying for made you are currently excluded from accessing this care but that exclusion will automatically sunset out of our law, out of our legislation in March of 2023 and that will actually become available. So that's the quick run through of a lot of material. So if you meet all the eligibility criteria you can potentially have an assisted death in Canada but how you get there depends and I promise I won't go through all of this for you just to say that there are also a number of procedural safeguards that are required and our newly amended law created two tracks or two pathways to assisted dying. What determines which track you're on? One track is a little bit more straightforward than the other. What determines what track you're on is whether your death is reasonably foreseeable. So very unfortunately the government kind of recalled decided to use a recently discarded terminology. So track one, if your death is reasonably foreseeable there's a straightforward number of safeguards like you have to make a written request that need to be a witnessed written request you need to see two different clinicians pretty straightforward. If your death is not reasonably foreseeable you would follow track two you need to have all the same safeguards as track one plus there are more of them which makes sense of course because these are people who aren't on a trajectory towards death so deserve a more rigorous assessment and more rigorous safeguards. So knowing all of this, what is actually happening? What kind of data are we seeing in the Canadian model of care? So all this information comes from the second annual report on medical assistance and dying from 2020 all this data is from 2019. So just very briefly we are seeing a steady annual increase in assisted deaths in Canada. I would add that this is not surprising nor should it be alarming. It's still relatively new. People are still not yet fully aware of its existence which is surprising to me because I live in a made bubble of course and as the idea penetrates into the public sphere and we've seen Canadians embrace this type of medical care it is not surprising to see this kind of access really growing. It's essentially a new end of life option available to Canadians but better yet to maybe contextualize it. So in Canada in 2019, 2.5% of all annual deaths were attributable to assisted dying. You can see the range between our different provinces there is the variation amongst us but the Canadian average is 2.5%. Now comparing that to Oregon next to that it's a region with 20 years of experience but where access is limited to those with terminal illness and those who have to self-administer so not surprisingly the rates are lower and in fact they are significantly under 1%. But comparing that to the Netherlands where the model of care is much more similar to the Canadian model, terminal illness is not required clinicians can administer care. A lot of our model is based on the Dutch model and there consistently the percentage of annual deaths attributable to assisted dying is consistently between four and 4.5% depending on the year you look at. So after only three years of legalization for Canada to be sitting at 2.5% seems exactly as might be expected. Very quickly then in Canada we're seeing both male and females accessing care in almost equal numbers. The age range of those receiving assisted deaths is quite wide, the highest prevalence is between 55 and 80 with the average age being 75. You can see the oldest the youngest recorded. I personally the youngest person I've ever assisted was 27 with a terribly metastatic breast cancer and the oldest person I have personally helped was 105 with heart disease. And regarding underlying diagnoses by far the most common underlying illness leading to an assisted death is cancer that's consistent with other jurisdictions. We see neurologic conditions and end stage organ failure and stage heart disease and stage lung disease and stage liver disease in almost equal measure after that. As for where it's happening there are some centers in Canada large centers where hospital-based programs tend to be the more robust programs and there are other centers where home-based programs seem to be more robust. But overall, if you look at the whole Canadian data it's almost equal between home and hospital but as I like to say made can be provided anywhere that's safe and legal. I personally have provided made in hospitals in people's homes which is by far the most common what I do but in palliative care settings and seniors residences and assisted living facilities. I've helped people in hotel rooms in backyards on patios on beach. I have a colleague who's helped someone in a funeral home that's kind of new and I am aware of one that actually happened in the camper van. So we have lots of diverse locations for sure but primarily home and hospital. So I've explained all of this to you in order to highlight some of the few important differences between the Canadian system and some of the US states and to look at some of their practical applications. So first and foremost as I keep saying in Canada it's not required that a patient have a terminal illness to qualify for an assisted death. Now, this is actually not so odd or shocking as it may seem at first. So the Dutch for example, they emphasize the eligibility requirement of unbearable suffering in their list of mandatory criteria. And the Belgians focus on the presence of what they call medically hopeless situation. The Swiss, the only jurisdiction that allows foreigners to access this type of care requires only that the medication be self-administered and that there be no selfish motivation in the one who's actually doing the assisting. So none of these assisted dying programs is designed to be used exclusively at end of life. And as in Canada, they are instead focused on autonomy, on patient suffering and on irremediability as the key factors in determining eligibility. Of course in the US the very first state to enact legislation was Oregon in 1997 with the death dignity act which did require terminal illness defined as an expected death within six months and as an eligibility requirement, excuse me, and as other states decided to mimic that legislative success almost all the other US jurisdictions require this. And in fact, the Oregon model has been the blueprint for other legislative successes in Australia, New Zealand, probably in Spain, all of which also require terminal illness to be present. And this may make some sense in theory but I can report to you from the front lines. And we all know that clinicians are terrible at prognosticating and we all know that suffering can occur without being within six months of end of life. So when I'm in a middle-aged woman suffering from something like multi-systems atrophy or super nuclear palsy or severe heart disease or severe lung disease or even full men in Parkinson's disease, I am grateful that it doesn't matter if I cannot guess exactly how much longer she might survive with her condition. Our law allows the person themselves to decide when they have reached the point of intolerable suffering and to ask for an assisted death at that point as long as they meet all the other eligibility criteria. Secondly, as I've pointed out, clinician administration of medication is permitted in Canada. And you might be interested to know that in any and every jurisdiction where clinician administrative made is allowed, it is greatly favored by the patients. And in fact, in Canada, we've recorded over 20,000 assisted deaths in the past five or six years. And there have been less than 20 that have been self-administered. So 99.999% of ours are clinician-administered. And that's consistent with data from the Netherlands where approximately 96% of all assisted deaths are in fact, clinician-administered as well. So why is that? Well, in a self-administered assisted death, a person usually needs to be able to sit up to hold the glass, to be able to swallow, to digest. And these are things that are often no longer possible at end of life. So quite clearly this discriminates against those who are paralyzed, those who can't swallow, or those with maybe pathology in their GI tract. I mean, what about the gentleman with end stage esophageal cancer, for example? What can be done? And if the clinician isn't present, well, I'll just say that some complications have certainly been reported. Now to be fair, some creative thinking has occurred around this issue in the US. And in California, for example, the word in the legislation is ingest. A person must ingest the medication. So this has been taken to mean that any use of the GI tract is allowable. And that interpretation has led to the permissible use of feeding tubes right into the stomach, or even rectal tubes. But it still needs to be achieved by the patients themselves. So what do you do if your ALS patient can no longer swallow or push a plunger? So right now in California, the current requirement of self-administration is actually being challenged. And arguing that it is in fact discriminatory, and especially against those that are physically disabled. So I've been highlighting some differences, but there's also in fact, something that all jurisdictions seem to have in common. And that's the reasons why people ask for help. So in every case of assisted dying in Canada, it has to be reported and monitored by federal agency, by Health Canada. They generate an annual report, which provides much of the data that I'm presenting you today. And practitioners are actually required to report on how the person who's requesting made describes their own suffering. So we actually have to write that down and report that federally. So the most commonly cited descriptions that patients tell us of their suffering is that they are suffering from the loss of ability to engage in meaningful activities. And that's followed very closely by the loss of ability to perform their activities of daily living. In the state of Oregon, there's also of course annual reports and in it the most common end of life concerns, as they're called, are expressed by the patients who are requesting an assisted death. They're very, very similar. Again, a decreasing ability to participate in activities that make life enjoyable or meaningful is the number one answer. Excuse me, and the loss of autonomy is the second. So very similar. Okay, one other element I do wanna discuss very briefly is the level of involvement of clinicians in this work and its evolution, especially in Canada, but in general. So as uncertain, many of you are aware, the American Medical Association has a stated policy opposing assisted dying, although the report of their own counsel, judicial and ethical affairs outlines both positions, both for and against a physician participation. The Canadian Medical Association, by contrast, the CMA, has been statedly neutral on the topic since 2015, since right before the Carter decision. And it was done in an almost impossible effort to try to advocate on behalf of all of the CMA membership, which is about 90,000 physicians who of course hold divergent views on the subject. But it does, this statedly neutral stance does allow the CMA to more fully and purposefully participate in the ongoing public debate around the topic and to liaise and relate and consult with government, for example. So there's an important difference in the role of our National Medical Associations, I think. That said, let me be clear, our federal legislation explicitly recognizes, allows and respects conscientious objection to the practice. No clinician has ever been forced to provide this care or ever could be. It's true, however, that our professional licensing bodies do require some form of non-abandonment of the patients who are making this choice. Essentially, you can't fire a patient over their decision to seek this care and you have to still care for them in all other respects. So in fact, professional standards require an effective referral of care to alternative resources for the patient to help them address their request. So there's professional standards that are in place. Interestingly, however, there's no similar respect for what I call conscientious participation. The term I more recently learned and I quite like for when a clinician feels compelled to be available to offer this care to eligible patients. So we do have some situations where clinicians want to offer this care to qualified eligible patients but that they're affiliated, the patients are affiliated with facilities that forbid them to do so. So primarily these are faith-based institutions. So we see doctors and nurses within those facilities that may not be able to answer questions that patients pose to them about this care while they're inside that facility, for example. And it's led to a number of odd situations. So for example, I've done assessments for made outside those facilities in cafes, on park benches, in odd places. But the most important way that I think that clinicians have been involved assisted dying in Canada has been, you know, through the Canadian Association of Made Assessors and Providers. You have to remember when our law changed, when it did so, assisted dying sort of became suddenly legal or suddenly non-criminal. And there was no training. There was no guidance documents. There were no medical standards. It was very little help. It was left to clinicians to kind of do the work to sort out what it meant to determine if the law was met and how to apply the mandated safeguards. So some clinicians therefore stepped in to help set those standards and to create that training and to learn from each other and to learn from those who had gone before us and other jurisdiction. And from that very small group, few clinicians who were willing to take on the work in the very earliest of days came this organization. And this organization's mission, of course, is to support those who do the work of assisted dying. And let's be clear, there was no other professional association that could do that because we came from such a wide variety of backgrounds. We are primarily family physicians, nursing nurse practitioners, internists, neurologists, anesthesiologists, psychiatrists. So we needed a new association that could represent us in our new field of work. A lot of what we do is we educate about made, about what it is about what it isn't, especially do so to the healthcare community. And we are hopefully a leading voice trying to become a leader in the setting of the highest of medical standards for this new field of care. This is all achieved through things like an established and active community of practice online, but there's daily interactions between colleagues across the country. We run training workshops for clinicians who are interested in doing the work or coming to the work. We've developed clinical guidance documents, national case sharing webinars, educational conferences, all kinds of projects, but fairly unique organization in its founding. I like to think we were able to inspire others elsewhere, including a very similar American group which now exists called the American Clinicians Academy on Medical Aden Dine, and I urge you to check them out if you're remotely interested. So in my last few minutes, I do wanna highlight just three or four lessons that have been learned and then turn this over to an open Q&A. So very briefly, as might be obvious by now, I work in a system that did not allow for much preparation. If you want to learn what it was like to try to understand what to do, how to function in a brand new system without formal training, how to take more than a few big blind steps, potentially criminally liable steps at that, my book candidly tells the story of my first year providing this care, and I do hope you find it illuminating and insightful. But the Australians, for example, were wise and learned from us and others, and they first passed legislation in the state of Victoria, and then they mandated an 18 month preparation time. If you ever find yourselves in a state with pending new legislation on assisted dying, I urge sufficient preparation for the clinicians who are interested in participating. Some people argue that patients only ask for assisted dying due to lack of access to quality palliative care. I'd point out that the data does not support this. Data from Canada's 2020 report states that of all the patients who received made in Canada in 2019, 83% of them were already receiving palliative care at the time of their death, and of those who were not receiving palliative care, another 17%. 88% of them did have access palliative care services if they had one of them. So I routinely provide made to patients already receiving outstanding palliative care on palliative care wards, people being supported by palliative care at home, in hospice units, so routinely. So my experience assisted dying is not due to a failure of palliative care, nor is it due to access issues where I live. Of course, we can always do better on a strong supporter of increased funding for palliative care, for greater access to palliative care. I also recognize that I live in a center in a region that's fortunate enough to have good access to high quality palliative care, not everybody does. So there is that, but the data is fairly clear. Next, I do wanna share with you that when I tell someone that they're eligible for an assisted death, almost every time, I see an immediate physical change in them, right? A relaxing of the shoulder, sometimes a little smirk, almost always an expression of relief and gratitude for the near possibility. Some find this confirmation of eligibility, it reduces their suffering enough that they actually choose to live a little longer. And you might know the data from Oregon that suggests only 65% of those were given a prescription for an assisted death in Oregon, actually ever use it. So I found that allowing for the option is actually empowering to the patient and therapeutic in and of itself. And finally, yes, it's not all sunshine and roses. I have encountered angry families, people who disagree with what's going on. I do always try to facilitate discussions between the different parties. I try very much to encourage the patient to be the one to explain what they're asking for and why, if they're able to do so. I think it's important that everyone be heard in a respectful manner, that solutions and closure are very much worth seeking. And that can either be done with my facilitation or with professional counselors, of course. But in the end, do know the law and I do take my cues from the patient. Family and loved ones deserve to be heard but they have no legal standing where I work. I won't be bullied and I won't allow my patients to be bullied. We do hear opponents who often talk about coercion and a fear of having people coerced into making this decision to end their lives. That's not something I have actually really ever seen. It was one case I was concerned about. They did not proceed in all my years. But I have seen more than a handful of cases where patients were seemingly coerced out of making this choice or where they felt that they would be letting their families down or letting a loved one down or disappointing somebody if they did proceed despite their own clear desire to do so. If I have a parting message for you, it would be that somewhat to my surprise maybe or to the surprise of others, I don't find this work more gross or morbid or untenable as a physician. I consider it a physician's role to help people. I think that's why we all went into medical school why we went into medicine. And sure, sometimes we can diagnose issues and sometimes we can even treat them or cure them. But I don't think that's the majority of our work. Certainly as a family physician, I don't really think so. People have come to see me during some of the most challenging times in their lives. And sometimes I can treat them and sometimes I can help them, but not always. So the expression goes, right? Sometimes to treat sometimes, to care often but to comfort always, right? I found my work in assisted dying to not be so different than my role as a physician in any other part of my career. And in general, I find that to be invited into that intimate time with patients and their families to help them facilitate what are essentially their final wishes. I have found that to be profoundly meaningful work to be honest. So I've only scratched the surface on the topic today but according to the pigeons here, it's at least a way to avoid misunderstanding or misinterpretation. So I certainly welcome your questions. Stephanie, thank you so much for that really concise talk that covered so much territory. And I've been taking notes out of the Q&A and I'm gonna try to synthesize some of the questions. Maybe one though is that I know that your book, as you said, is more of a memoir. And at the very end, you spoke a little bit about your personal experiences, but some of the comments are, what has it been like for you personally to be involved in this? What, yeah, what has that been like? Yeah, I think, yeah, I appreciate the question actually. So having spent 20 years in maternity care and adoring my practice, I spent much of my time feeling quite grateful to be able to be invited into that sacred space, into that space with families who are having this tremendous change, that tremendous transition. And I find a lot of similarities with end of life actually. I find that in both of those situations, there's a lot of intensity, there's a lot of emotion involved, there's a lot of family dynamics involved. There's a lot of my, my role is supposed to be guiding and be knowledgeable, helping people through these challenging times, but it's extremely obvious to me in both of these situations, and especially at end of life, that I am not the most important person in that room, right? You know, it's my job to guide the situation to some extent, but there's a lot of paradox in this work. But there's a lot of, there's to be sadness, there can be tragedy sometimes, someone's life is ending, but at the same time, I have been witness to some extraordinary moments of beauty, of people saying goodbye to each other, of finding closure with each other, of finding peace at the end of their life, of having this opportunity to take the time to finalize and say goodbye and tell the people they love. I kind of witnessed this journey with patients. I find it really extraordinary work and I found it very, very meaningful. And patients have been incredibly grateful for this care. I've been a little bit overwhelmed by that, to be honest. You mentioned that terminal illness is not a requirement. And forgive me if I miss this and taking notes, but many people are just concerned about psychiatric disease in general. And a lot of debate here around physician aid and dying, for example, with patients with eating disorders. And when do you decide that something is no longer treatable? It seems to be such an area of uncertainty. How do you manage that? Well, it's a very pertinent question to us. We're about to be grappling with that very, very practically here. So just to be clear, in the original legislation in Canada, there was no particular exclusion of mental health patients from accessing made, but there was a requirement that their death be reasonably foreseeable. So essentially 99% of mental health patients couldn't access made because of that requirement. There was actually an exception for a patient with anorexia who did qualify and proceed. With our change in law, when we remove that requirement, that kind of end of life requirement, that reasonably foreseeable requirement, the government recognized that that would then open the door for mental health patients to then have access without that kind of stop gap. And that's why they inserted the blanket exclusion of those patients before they could really sink their teeth into how to do this. I mean, that exclusion means to be lifted. The Senate enforced that it needed to be coming out because of constitutional rights. You couldn't discriminate against a patient simply because of their diagnosis. That wasn't going to be allowed to happen. The courts weren't going to allow that. And the government recognized this is a complex topic. And so we have a national advisory committee that's actually about to report, I think within the next month, on this very topic and give recommendations on how we can more accurately, more carefully assess patients with mental health disorders to decide whether their illness is irremediable or not in this big debate within the community, but whether that's even possible or not, whether that's even true or not ever and how we can maybe apply some more safeguards. In March of 2023, this will be on my doorstep, at my door. These patients will be in my office. So I am very much looking forward to those recommendations and talking about this a lot further. I don't have those answers for you yet. Questions about dementia and advanced directives. Can people request made via an advanced directive? And if not, and they become demented and then they're not able to consent. You can see the issues there. And three sentences or less. So that is the question I'm asked the most in every single talk that I give. And it could be an entire lecture into itself, but I think I would just tell you the basis are like this. In our original law, it was clear that if you met all the eligibility criteria, you could have an assisted death. And at first, we weren't clear what that meant with dementia patients, did they need to have physical ailments, but it became clear that a purely cognitive decline could actually meet the criteria. I have personally assessed and helped people with dementia apply for and access medical assistance and dying. These are complex patients, not all of them do. There's a model of care that we use that allows us to follow these patients closely over a long period of time. And we call it the 10 minute to midnight. If people lose capacity to make this decision, they can't, of course, access made, but they also need to be an advanced state of decline. There are some patients that would be called 10 minutes to midnight, right before they're about to lose capacity, right before that happens. They can, if the stars align, they can actually meet all the criteria. So dementia patients can access made in Canada as long as they can give consent or on the day of. Now, can there be an advanced request where a patient says, I've got Alzheimer's, when A, B, and C are true, I would like you to end my life? That's an advanced request. We do not have that in Canada. That is not currently legal. That is the topic that most Canadians want to be discussing, have asked to make legal, that we have not yet sunk our teeth into. I think primarily because we are currently mired in the mental health debate, which has been thrust upon us by the current law, we're going to have to deal with that first. Canadians really want to be dealing with advanced requests. We do have, just to say, we do have a new loophole where some patients can give consent in advance of losing capacity. It's a very special subset of patients and some dementia patients can fit into that. But the overall comment is, dementia patients can access made sometimes in Canada, but not through an advanced request. Thank you, it is a complicated topic. Rather straightforward question, what about life insurance? Yeah, great question. We got asked that a lot. Life insurance is not affected by the all beneficiaries are paid out. The National Life Insurance folks have a statement on that. All the insurance companies have policies and assisted dying. In six years, I've never seen anybody have a problem with that. Okay. Some of the comments had, what about when you know that a person does not want to be a burden on their family? And that is their primary reason for requesting made. And the family may say, no, no, no, we will take care of you. But the person says, no, I just do not want to be a burden. How do you deal with that? Yeah, that's always tough. I think it causes some distress. I actually, personally, what I do is I pop that bubble. I tend to throw that back at patients and say, I'm not going to be that doctor that's going to lie to you and say, you're not a burden. In fact, you are. I mean, this is a burden. It's burdensome to take care of someone. But let's put the shoe on the other foot. If your wife was the one in bed and you were the one taking care of her, would you do that? And would you consider that burdensome? Well, you might consider it burdensome, but you'd also be willing to do it. My bet is because you've been together for 52 years and this is what you do for your partner. So that's not really, that's not a reason. That's not the reason. Our law does require the patient to be suffering. Could they be suffering significantly and intolerably by the concept of burdening their loved ones? I suppose that's a subjective debate we could maybe have. But generally speaking, because you feel you're a burden on someone is not really a reason to have made. So we'd have to explore that a little bit more. Sounds like a lot of the discretion really does come to the provider. And you obviously are very thoughtful about this.  Well, I have developed very large and broad shoulders doing this work. There's a lot of responsibility. My experience, I'm in touch with colleagues across the country with my work in CAMAP. I have to tell you, the clinicians I work with, the clinicians I know, they take this pretty seriously. We have a criminal liability, right? If we don't do this right, we're liable for 14 years in jail.  That's not what we're seeing. People are cautious. And the organization CAMAP is specifically there to help standardize care, to help, you know, help colleagues bring some up, pull others in so that we have a person in Nova Scotia who's got a particular situation, someone in Manitoba, they have the same type of approach to care, the same standard of care. It's really important that we do that. Now, not every clinician needs to be a member of our organization. I can't say that there's a quality control out there for every single clinician, but it has certainly not been my experience that there are, that anybody would sign off these papers with, you know, with just a quick glance. This is rigorous stuff that people take pretty seriously. You talked a little bit about palliative care and how you in Canada have fairly good access to palliative care. I know some of my friends when this last came to a vote in Massachusetts voted against it because they thought it had too great of a risk of allowing governments and insurance companies to take their foot off the gas around providing palliative care, that it was a cheaper and easier way out and that the only way to really maintain our focus on the need for good palliative care was to not have physician aid in dying. Of course, you know, that's not your situation in Canada, and I hesitate to have you comment on the United States experience, but I mean, I think for many people that's a big area of concern. And I think that there is a good example.  In every jurisdiction where aid in dying has been legalized, we've seen a concurrent increase in palliative care funding and access if you look at the global data. So I think that the fears are legitimate, but have so far been unfounded. I think you can also create a situation or legislation that links the two. So that ensures that both come up together. I think that's probably essential. I mean, everybody who does assisted dying works wants the best palliative care possible for our patients because if that's satisfactory, they won't need this care, right? That would be ideal. We know that palliative care isn't the answer to everything and that despite good palliative care, people will still choose to have an assisted death, but it certainly makes us feel better to know they've had palliative care first. So I think you can link the two and I don't think that you should hold certain care or certain patients hostage to care system failings, right? I mean, it's not really, just because the resource isn't resourced, it doesn't mean you shouldn't offer something else. I think you need to do both at the same time. I think I really think that's the answer. All right, so let me comment here. Lachlan Farah who chaired our Massachusetts task force on end of life care asked the following. He says Massachusetts has been grappling with legislation on this, which has largely been a near copycat of the 30 year old Oregon statute. And we have learned a lot since then. Question is, what would be the ideal process for engaging diverse voices in creating legislation that can pass? And is there a state in the United States that you think has done this best? And do you have any suggestions about best sources of model legislation that we should review and possibly adopt? Great questions. I think I will be bold enough to say the answer to the first part of that question, the best way to engage and learn from others. I do think you need to look outside the borders. I do think there are, there's a number of jurisdictions with good data. The Australians got two and a half years of data. Canadians have five years of data. The Belgians, the Dutch, there's 20 years of data. There are other models that should be looked at. I've had international folks come and approach us in Canada to ask for our experience to seek that input. I do think there are good centers that you can contact and do that. I think it's very important you point out that we've got 23 years of experience. I do think we've learned a lot. I don't know the minutiae of the variations within the states. I am aware that in Mexico, one of the most recent states has been a little bit more forward thinking. I mean, at the very basics, they don't only allow physicians to do this, advanced practice and nurse practitioners can do this in New Mexico. I think that's the kind of thing that we've learned. Seeing in other jurisdictions have data on showing that it's safe and it's within scope of practice and now could be implemented based on that learning. New Zealand's done the same. I think with issues like clinician administered care, I think I would be a really tough one perhaps in the states, but there's really good data why it's a good idea. So I think engaging those outside of the US is important. Within the US, I wouldn't deem to answer which is the best state legislation to look at. That's out of my scope. But that is what could probably tell you that answer. To be honest. So here's a question. I guess it's about disabilities and about the deep bias we have around not valuing people who have disabilities and that there's no quick and easy way to just chuck that box and say, oh, we took that into account. We're not, that wasn't a factor here. How do you deal with that as a much deeper social problem about the worth of people with disabilities and their perceived worth and how they even perceive themselves? Yeah, it's a really good question. I think a couple of things. First and foremost, let me just say that, and this is not a cop out, but it's probably offensive to people, whether they're disabled or not, to think that they could be coerced into a decision by someone else, right? I mean, this care has to be explicitly requested and consented to by the patient themselves. So the idea that someone could convince them to do this, I think is offensive to a lot of people. That said, obviously society has certain views and they're not always so positive. I think also I would point out that there is a wide diversity, heterogeneity of the thought on assisted dying from within what we call the disabled community. I mean, I'm not even sure how you define this disabled community anymore, but there's, in fact, in Canada, much of our legislation, much of our court challenges have come from those with obvious physical disabilities who were arguing for the right to access to this care that they felt discriminated against because of their disability, they couldn't access this care. So I think it would be naive to think that there's one voice coming there and that's really opposed to this. It's quite not the case. So I would point that out. Having said that, it's now been a year where we have legislation where those who don't need to be anywhere near end of life can now access this care. And we are facing really challenging situations where people have come to us and asked for care because they are literally suffering for want of better resources that aren't available to them in the community, mental health resources, disability resources, social housing, things that I can't control and that I can't even find for them even if I wanted to. So what do I do when the patient meets all the eligibility requirements, tick, tick, tick, but it's because I see that it's for lack of resources. That's a situation that I can tell you providers are not comfortable with. We're not seeing those patients going forward, not necessarily because they don't meet the law, but because things are feeling a lot of moral tension around that. And while I say, it's easy to say, we need to work on both at the same time. And I think we are pushing for that. And I hope that assisted dying like with palliative care has brought palliative care to the conversation and brought into the headlines and brought more finance and funding the palliative care. I hope assisted dying will do the same for disability resources and mental health resources. I think it's one of the powers that this talk and this conversation, this topic can do. We can raise awareness of all of these issues. But practically speaking at the front of the line at the end of the day, I'm not so sure I'm comfortable, providing assisted dying for someone in that situation. I haven't done that yet. I'm not sure what I would do in that situation. It's a big, a big complication for sure. Dr. Green, we're in the last few seconds of our webinar here. Any last messages for, what did you call us earlier? The great behemoth to the south? The great behemoth to the south, yes. Our friendly southern neighbors. Any last comments for us? Advice, thoughts of wisdom? So many, but related to this topic. Yeah, no, I think keeping an open mind, keeping curious about what others have done that have gone before you. I think having the debate is important. I think having the conversation is the most important. I think that as clinicians, I think doing this work is not so far out of our wheelhouse. And I really feel strongly about that. I think you can get a better sense of that through my book. And I would only just say two things that clinicians that do this work are very, very conscientious about doing it, like everything else we do in medicine, right? We're conscientious about, before we cut into someone, we are also before this. And I can just reemphasize the work I've been overwhelmed with the gratitude from patients and families to have this possibility given to them. And the work has been very, very, very meaningful. So don't close your eyes to it. Thank you very much. It was a wonderful presentation today. We're very grateful to you for taking the time to do this. Thanks, Bob. Bye everyone, and thank you for being here with us.


Hello again friends, and welcome to another evening edition of the astrophlog Tomorrow will be two weeks for us here in Self-isolation I think considering two young children and all the panic in the world. It's gone quite well I'm really happy to report that all four of us appear really healthy We've gone for some long walks in our neighborhood, which is pretty quiet And I think the actual highlight of this time so far has been how excited my three-year-old has been about the free little Libraries if you haven't seen these before they're amazing you put them up in your front yard And people can just come by and take books or leave books We found six of these things so far within 20 or 30 minute walk of our house tonight on the astrophlog I'm just gonna tell you a short story over six years ago at the end of 2013 I created a Twitter bot called mock twain And it was a really good way to learn a bit of Python programming and how to interact with things on the web The actual coding of the Twitter robot was only maybe a day or two of effort There were lots of examples on the internet of how to build these Python based Twitter robots What really took a while was designing what the bot should do now a Twitter robot can do anything It can tell you about the weather it could interact with you it could answer questions in my case I wanted my Twitter bot to read an entire book. I thought Mark Twain was a good subject matter since his writing is kind of funny It's very American I was really interested in mixing these mediums of taking the experience of reading a book and Putting that into the short form content of Twitter And so mock twain was born to tweet an entire book over the course of a year why a year I don't know a year is a good time scale to do things But I think the project really found its niche when my friend Jake Vanderblas came back from a conference and gave me a Piece of the free swag that he had a raspberry pie. This is a tiny computer So I wrote my little Python code and I set this little machine off to run for a year But I thought about where am I going to put this little computer that it's gonna be safe and stable for an entire year It came with a little plastic case and it could just sit on my desk for a year But that somehow didn't seem quite fitting for Mark Twain or certainly not from Mock Twain And so I took a little trip to the bookstore and I picked up this copy of The Mississippi writings which included the book that I was going to tweet which was the adventures of Tom Sawyer The plastic case was not good enough. This would be our vehicle The project I think was a huge success within a week or so It had almost five or six hundred followers people seem to be enjoying the idea at least But I quickly learned a few lessons number one a Book is not a good case for a computer even a tiny little computer like the raspberry pie Well, this is a pretty low power operation It does produce heat and this book got hot hot enough In fact the poor raspberry pie shut down after about four days So the book had to sit open to let it breathe the second take away and maybe this was obvious from the beginning This is not a good way to read a book. I don't think it's a matter of reading the book too slowly I think it's the fact that Twitter is so ephemeral that if you don't catch the messages when they happen You might miss days worth of the story and before you know it It's on to another chapter and you have no idea what's going on But I will say some tweets generated lots of interaction Sometimes there are funny lines or memorable moments and those will get a lot of engagement now after its year of tweeting 10 times a day with a few power outages and overheating Mock Twain completed its journey and read the entirety of The Adventures of Tom Sawyer and the project is over the bot was shelved And I haven't really done anything with it in the last six years But the experience of building a Twitter bot was really instructive for when I wanted to spin up a new Twitter bot called Apollo 11 mission which tweeted out in nearly real time the entire mission logs of the Apollo 11 mission using the code from Mock Twain and a little bit of work getting the logs into the right format I was able to get this bot booted up and running in like a day instead of tweeting with a regular schedule over a year This bot had to tweet based on the timestamp of every entry of the mission log So there'd be long stints where nothing was happening because the astronauts slept and then there'd be very high activity when they were Radioing back and forth say during during key moments of the mission and it was here that I learned some more valuable lessons in terms of building Twitter bots You need to really understand the limitations of the Twitter program interface Specifically the limitations on how often you can tweet during the landing the actual descent of the lunar module Onto the surface of the moon all three astronauts are talking constantly to mission control and mission control back to them There's messages going on every few seconds and a lot of them are exactly the same like the astronauts just saying okay, Roger Okay, and right as the astronauts were about to touch down something like a hundred feet from the surface really rapid cadence of very short Very similar messages caused Twitter to think that my bot had turned into a spam robot and put it in Twitter timeout for about four hours So it should have been the highlight of the entire project the eagle has landed turned out to be massively embarrassing Frustrating so some rapid changes were made. I was able to group some messages together Make some small changes so that messages didn't seem exactly the same as they came out in rapid fire And when the next milestone for the mission the actual walk on the surface, that's one small step for man The bot did not crash and we managed to get that if you're interested in building these kinds of bots There's a ton of resources on the web I'll try to put a couple of links down in the description below And there's actually a really phenomenal textbook called Twitter bots by Tony veal and Mike cook I've read it. It's really good And I've actually used the textbook as a outline for a course that I'd like to teach on how to build Twitter bots So there you go friends a little late night story time I hope that you're all doing well that you're staying safe You're staying inside and away from other people and that I see many of you soon


Hey, everybody, what's up? It's Rob Dodson, coming at you live from the Chrome Dev Summit. We are here at the SF Jazz Center. We're just sort of lurking in the stairs. I'm joined by Sam Saccone. Sam, you just gave a talk on application performance, and in particular, like load time and things like that, time to interactive. For folks who haven't seen the talk yet, what are some of the sort of the troubling hotspots that you saw in sort of your forensic analysis of apps and how they could do time to interactive better? Good question, Rob. I think that a lot of websites just ship a lot of JavaScript today. And that JavaScript that they're shipping, this takes up so much time on the main thread on a phone that it basically locks out the page from being interactive. I mean, that paired with the amount of resources that people are loading on the page, we're talking about web pages that load super slow for most users. Now, I know one of the things that people have been kind of raving about potentially is like H2 push. Like H2 push is going to save the world and things like that. And I know you looked into that as well. So what were your findings related to H2 push and how it affects performance? Yeah, I found that, well, H2 push is very useful for getting resources to the browser faster, but it's not like a golden bullet for performance. What works really well is actually link rel preload. Think of link rel preload as the first step in switching to H2 push. Link rel preload lets you download resources faster than they're discovered. So like with Polymer or HTML imports, it lets you put the dependent resources way up in the discovery tree so that the browser shoots off those requests so that when they're finally discovered, it's already there in the browser. So it's great. Now, for someone who maybe doesn't know much about preload, is there a resource someplace where you know where they can go to learn more about that? Yeah, so if you just type that into Google, the first three results are all excellent. So there's a W3 spec article and then there's a few blog posts, one on Smashing Mag that are super great and explain all the details and how you can get a big win out of them. All right, right on. Sam, thank you so much for being with us today. If you haven't done so yet, definitely catch Sam's talk on the YouTube channel. Be sure to subscribe to the Chrome developers YouTube channel. We got a lot more content coming at you and don't forget we got an entire second day of the Chrome developers summit. So definitely check out the live stream tomorrow as well. Again, I'm Rob Dodson coming at you from beautiful San Francisco. Stay with us.


Using the social networking service TikTok, fans of K-pop music disrupted science for President Trump's June rally in Tulsa. They also trick social media algorithms to slow the spread of anti-black lives matter hashtags. These examples illustrate how powerful social media has become in digital activism, says Michigan State Associate Professor Anjana Susarla. First, social media gives an opinion-making role to a few influencers with large followings. Secondly, people tend to engage with like-minded people on social media, a phenomenon known as homophily. Together, these mechanisms enable a video or a tweet to go viral, creating a situation that's impossible for the targeted companies or individuals to ignore. K-pop fans may have also flooded the Trump campaign with bad data, which could interfere with their voter turnout models and targeted online advertisements. The success of the TikTok teens campaign also shows how it's relatively easy for a group including foreign actors to interfere in the political process by using social media.