Hello everyone. My name is Jasmin Smith and I am one of the digital measure programmers here at NCQA. I work with Amenze Okpah and our IG team to develop and maintain the HEDIS implementation guide, of which today I will be giving you all a walkthrough of our HEDIS IG is access by invite only. However, once access is gain, you would create an account on Simplifier darknet, which is the online platform where we author and publish FHIR data models, also known as profiles. I'm going to go ahead and login for you guys. All right. Simplifier is a registry where you can find, view and inspect all FHIR data models in the world. So once you get logged into Simplifier, you will see a list of the implementation guides that you currently have access to. Again, our IDs are accessed by invite only. I have access to all of them, including our development branches. You should currently have access to the main projects for measurement year 2023, 24 and 25. The reason our projects are set up this way is to maintain the level of source control that we require. There's a separate, separate simplifier project for the development branch and the main branch for each measure year version of the IG. The ID that I will be showing you today is for measure year 2025. So upon arrival of the home page of the IG, you will see the version number here at the top. This is here is core version 2025 .1.0. The profiles in this guide build off the US core IG version 3.1.1, which is based on US CDI version one profiles and the canon IG for blue button, version 1.1.0 profiles for clinical data and paired data respectively. For resources that aren't included in either of those IDs or wherever a specific rationale exists. The corresponding HEDIS score profile is going to be derived from the base FHIR R for resource. For example, the claim profile section .1.3 provides a diagram showing how the HEDIS score profile derives from the US core and caring for blue button profiles with the addition of the FHIR R for claim resource. I'm going to go ahead and walk you guys through some of the other sections of the home page. We just have some guidance for future development of this guide. Our contact, as well as our authors, we have included our copyright notice and disclaimer, as well as the terms of use for this implementation guide. The next section I want to show you guys and highlight is the framework section. We have two pages, and first I'll go over our general guidance. The general guidance section describes the requirements of this core that are useful for implementers, and detailed the methods used and decisions made across the complete set of profiles and extensions. A section that I want to highlight for you guys is section 2.1.5, which discusses the use of HEDIS escort Mata tag. This is a core requirement of HEDIS ES quality measures, and classifies the source of each data element to determine how it can be used in measure calculation. There are several methods available in FHIR to support this requirement. In this IG, a data type profile on the standard meta element common to all FHIR resources was chosen. So specifically, this IG requires that the meta tag element must have a value from the HEDIS score. Data source value set HEDIS core leverages a preexisting pattern widely implemented by other IGS, and avoids the creation of an additional extension. For this purpose. Some other things that I'd like to highlight are just a general guidance on must support, and how to indicate important elements in a profile. Referencing target profiles and what to do if your data is missing. The next page I would like to show you guys is our data Modeling guidance page. We have introduced a new page to the framework section of the HEDIS side called the Data Modeling Guidance. This page includes guidance specific to data modeling. We have incorporated some FHIR resources links to our Digital Quality hub here. A guide on how to read the implementation guide, as well as the link to this very video you're watching, which gets updated periodically as we further develop the HEDIS. As IG. Some other things that I'd like to highlight are, guidance on the patient bundle, CDA to FHIR code system mapping, resolving references and bundles, as well as, a new section language Mapping guidance for measure evaluation. So that's just going to give you some more detailed insight on data modeling. The next section that I would like to highlight for you guys is our use cases section, as seen in the use case section of the hillside. We decided to use the breast cancer screening as well as the colorectal cancer screening measures as use case examples. I'm going to give a brief overview of the breast cancer screening measures so you can understand, what that looks like. So when you click on one of these use cases, the first thing that you will come across is an introduction that gives an overview and description of the measure. Next you're going to see the FHIR resource overview. This section includes a first table that shows which resources are supported for that measures. Use case. For each FHIR resource type, you can see the equivalent HEDIS profiles. The second table below shows the resource elements that must be supported. For that measures use case, as well as which section of the measure that it's applied to. And you can see that here. So the next thing I would like to highlight for you guys is our FHIR artifacts. The first thing I'm going to show you is a profile, and I'm going to use our patient profile as an example. All right. So when you land on a profile, in this case the patient profile. The first section on every profile page has a table that shows basic information such as the profile name, the description and the base definition. We also have the status and the URL. The next section is going to be the notes on fields. And this is where profile specific narrative and guidance information can be found. Following that is a formal Views of Profile Content section. This shows the profile structure and multiple views. As you can see there's a differential hybrid snapshot view and examples tab on the differential table view. This includes our edits from the base. This view is the differential statement which describes the differences that we made relative to the structure definition. We're constraining if the parent profile is US core. For instance, the diff view will show the difference between US core, the parent profile and the HEDIS score profile. Next is the hybrid view, which shows a mix between the differential and the snapshot views. That snapshot view is going to show the end result or the information. That is a comprehensive view of what the profile means. Next is this examples tab. And this tab is just going to provide a link to the corresponding test case example for this particular profile that you're on. Let me see here. So yeah in that snapshot view this is also where you can see bindings to different value sets. You have to click inside those actual code systems to see the codes that the element is bound to. And then also the final section on the profile page is going to be the terminal terminology binding section, which also list all the values that's used in this profile along with their path strength and URL. I'm going to go back to the FHIR Artifacts page, just to show you guys a list of the extensions that we use in the helix. In this version of the HEDIS core ID, when a concept required by HEDIS cannot be implemented using existing FHIR resources, we created an extension. They follow the exact same page structures as, the previous profile that I showed you guys. So it still has that same, basic information as well as the differential, hybrid and snapshot views. Next I will show you guys the terminology page. This page lists all the code systems and values that's defined in this guide. All value sets and code systems are listed with their name, their description, and the canonical URL. You can see my code systems. Yep. All right. So next I would love to show you guys are examples page. The following examples are published within this guide. These example instances show what data produced and consumed by systems conforming with this IG might look like. Every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification, nor are they fully representative of real world examples. I will go ahead and show you guys the patient example. Since we went over the patient profile. So this is going to be what each example looks like when you land on the page. There is the Json file here we have the XML view. There's also a tree view. And you can expand each element and see what's populated in those. And then we also have a table view that list them out. I just want to go ahead and highlight once again that meta tag that we talked about before. And that's how it's represented on our test patient. All right. So the next page I'm going to highlight for you guys is the downloads page. The following package files include an npm package file used by many of the FHIR tools. It contains every value set, profile, extension, the list of pages and URLs in the IG, etc. defined as a part of this version of the implementation guide. So that's going to be a list of of all the ECGs that we've published in each of their packages. So let's say we wanted to download this particular versions package. You would click on the package version that you would like to download, and you'll be taken back to simple FHIR. Where those files are actually hosted. From there, you're going to click this download button here at the top in the top right corner to download the actual package. And you can also download snapshots. All right. So I'm going to go back into the guide. And I also want to highlight our change notes page. So the change notes page is going to detail all of the changes made in the current version that differ from the previous version. This is where we document changes such as new profiles, extensions, value sets, content changes, updates to the ECG formatting, and much, much more. And you can see the current changes that we made for this version are highlighted here. And last but not least, I would love to point out, our new community and support page. So we've added this community and support page under the support tab. It covers where you can ask questions, share your implementation experiences and receive any feedback or support as you navigate your digital transformation. One more thing that I'd like to point out before I let you guys go is that at the top of every single IG page, there's a ribbon here in yellow that allows you to contact us through the issues link or through the email address provided. The email address immediately opens a new email, to the given address with your system's default service, and then this issue's link here is going to take you to Simplifier. And it's a dedicated issue tracking system. Here you will be able to sign in, create an issue, and monitor IT status. And I'll kind of just show you what that looks like. So yeah, it'll take you to this page here. And from here you can create an issue. And we will get that notification and be able to help support you. I think that's it for this walkthrough of the IG. And I thank you all so much for your time and support.