This is a share of our Lead Poisoning Case study presented at the [GOSC DataIO WG Briefing Sessions][1] held on Tue 10 May 2022. The recordings and presentations, including the worked examples, are now available on the [event webpage][2]. Please contact the co-chairs if you would be interested 1) in conducting a Case Study interview; 2) in being an interviewee in relation to a data project, database or service with which you are involved; or 3) if you would like to suggest an interesting subject of a Case Study with which you could connect the WG. In the first instance, the co-chairs will follow up with the existing [GOSC Case Studies][3], but are very keen to hear as soon as possible from other examples which would be useful to the initiative. The previous webinar on [The Emerging Cross-Domain Interoperability][4] was mentioned in Simon Hodson's presentation during the May 10 mtg and in the mtg discussions, because some of the thinking there informs the Case Study Template. If you did not participate in that event, or caught up since, you may be interested in the [recording and presentation from that event][5]. [1]: https://codata.org/initiatives/decadal-programme2/global-open-science-cloud/working-groups/data-interoperability/gosc-dataio-wg-briefings-on-case-studies-tue-10-may/ [2]: https://codata.org/initiatives/decadal-programme2/global-open-science-cloud/working-groups/data-interoperability/gosc-dataio-wg-briefings-on-case-studies-tue-10-may/ [3]: https://codata.org/initiatives/decadal-programme2/global-open-science-cloud/case-studies/ [4]: https://codata.org/initiatives/decadal-programme2/global-open-science-cloud/working-groups/data-interoperability/gosc-dataio-webinar-on-the-emerging-cross-domain-interoperability-framework/ [5]: https://codata.org/initiatives/decadal-programme2/global-open-science-cloud/working-groups/data-interoperability/gosc-dataio-webinar-on-the-emerging-cross-domain-interoperability-framework/