Welcome to our first educational opportunity for version 3.0. In this learning activity, we will address data elements that are common to all procedures with a focus on new or updated data elements. Version 3 will capture four transcatheter procedures, TAVR, transcatheter aortic valve replacement, TMVr, transcatheter mitral valve repair, which is a CLIP procedure, TMVR, transcatheter mitral valve replacement, or TTVP, transcatheter tricuspid valve procedures. This will include both valve replacement and valve CLIP. Please take note that mitral CLIP procedures will be referred to as capital TMVr or capital TMVr. With the launch of version 3.0, we would like to introduce the opportunity to capture a basic data set or a full data set. They are not separate documents, rather the elements contained in the basic data set are highlighted in yellow and must be answered. Data elements that are not highlighted are part of the full data set. These are examples of the basic data set contained within the full data set. We would like to call to your attention a few important points regarding the basic and full data sets. For the basic data set, the data elements are highlighted in yellow and must be completed. Your facility will receive results on all metrics. Your facility will also receive available detail lines in the outcomes report. Because the basic data set has less data elements than the full data set, completing the basic data set will lessen abstraction burden. For the full data set, your facility has the ability to answer all data elements or has the ability to answer additional data elements above the basic data set that are specific to your facility without answering all data elements in the full data set. Your facility will receive available detail lines in the outcomes report and will receive all results from the metrics. Sequence 3050, admitting provider's last name, is a new data element and may be voluntarily entered at the discretion of your facility. NCDR will use the data to provide reporting at the physician level, which may assist physicians with demonstrating value-based care as well as support your facility's engagement in quality improvement efforts. The admitting provider's first name, middle name, and NPI number are also voluntarily entered. Please keep in mind that when entering Sequence 3052, admitting provider's middle name, if the provider does not have a middle name, please leave this blank. Sequence 10070, discharge provider's last name, is also a new data element and may be voluntarily entered at the discretion of your facility. This data element is located in the Discharge section of the Data Dictionary. The discharge provider's first name, middle name, and NPI number are also voluntarily entered. And as with our previous slide, if the provider does not have a middle name, please leave this data element blank. Sequence 4625, tobacco use, is a parent field. The registry definitions for Sequence 4625, tobacco use, have been aligned to industry standard definitions to support data capture directly from EMRs and to align with meaningful use. This data element indicates the frequency that patients have or have not used a tobacco product. Please code FORMER for Sequence 4625 every time the data definition is met, indicating that the patient has smoked at least 100 cigarettes during his or her lifetime but does not currently smoke. Sequence 4626, tobacco type, is the child field of Sequence 4625, tobacco use. If the patient currently uses tobacco products, then the tobacco types child field will populate that allows CITE to indicate all tobacco types the patient uses, including cigarettes, cigars, pipe, and smokeless tobacco. These cigarettes and vaping products are not captured in this data element as they are nicotine delivery devices, not tobacco. Additionally, marijuana is not included in this data element. The condition history, Sequence 12903, takes the place of individual data elements for past medical conditions and risk factors. The condition history list will enable coding of many past medical conditions. Explanations of patient conditions have been provided in the data dictionary where further explanation is necessary. Not every condition in the condition history list will need abstracted for every procedure. As an example, cardiomyopathy is not captured in the TAVR pathway, however, it is captured in both of the mitral pathways and the tricuspid pathway. Lastly, please pay close attention when abstracting in the data collection tool, as coding YES for certain data elements will require further coding of child fields, which we will demonstrate on the next slide. When YES is coded for cardiomyopathy, the user must then indicate the type or types of cardiomyopathy in Sequence 4570, Cardiomyopathy Type. Users can now select all that apply as stated in the notes section of the coding instructions in the data dictionary. Similar to the condition history, the procedure history, Sequence 12905, is a list with a number of procedures to use in coding the patient's past procedural history. Definitions have been provided in the data dictionary where further explanation is necessary. For some data elements, a date for the past procedure is asked to be provided. Sequence 7000, Procedure Start Time, was previously Sequence 6041 in Version 2.1. The Procedure Start Time definition has changed. Instead of capturing the first injection of anesthesia or first incision in Sequence 6041, for Version 3.0, Sequence 7000 states to capture the time that the skin incision, vascular access, or its equivalent was made in order to start the procedure.

Version 3.0

transcatheter procedures

basic data set

tobacco use

Procedure Start Time