Welcome to Lesson 2 of this learning activity titled Getting Acquainted with the CATH PCI Registry V5 Dataset. The content in this lesson was developed by Connie Anderson and myself. I am Kate Malish and I will be narrating this lesson. The objectives for the learning activity Getting Acquainted with the V5 Dataset are to discuss the rationale and purpose for the V5 Dataset, locate the coding resources that will support data abstraction, and to identify parameters for coding. All registry resources are identified under the Resources tab on the left navigation bar of the CATH PCI Registry website. Navigate to the Resources home page to find a description of the resources available to support your registry experience. For the purpose of this discussion, our attention will be focused on the resources that are needed for data abstraction. The Learning Center page provides access to recorded lessons and learning activities. The Monthly Case Scenario in particular is a useful resource for getting to know specific data elements in more depth. Real-world patient scenarios are provided and how specific data elements would be coded is reviewed. The Documents page is a place to begin your data abstraction journey. All V5 data collection documents that are needed to support accurate abstraction are conveniently placed under the heading V5 Data Collection Documents. Documents are provided in different formats. Choose your preference, making sure to download the Enhanced Data Collection Form, Data Dictionary Full Specifications, Coronary Artery Segment Diagram, and the V5 Data Dictionary Supplement with Pending Data Element Updates. All of the resources available are very helpful, but I would like to highlight the Enhanced Data Collection Form as a particularly useful document in prioritizing the information that must be documented in the medical record. A key provides how these data elements are used to determine the patient's risk for adverse events and or inform mapping PCI procedures to the appropriate use criteria and should be completed consistently and accurately. With that, all data elements are important and should be completed in the same way. Moving back to the Documents home page, please take the time to familiarize yourself with documents found under the heading User Guide Documents, paying special attention to the Qualitative Quantitative Crosswalk, the DQR Companion Guide, and the Provider Maintenance and Remediation User Guide. These documents will further support your data abstraction efforts. As you can see, there are many resources to support your registry experience, but your familiarity with the content of the Data Dictionary, the V5 Data Dictionary Supplement with Pending Data Element Updates, and the Qualitative Quantitative Crosswalk documents will guide coding individual data elements and ensure the most seamless abstraction experience for you. The most essential documents to support data abstraction have been highlighted. Now let's take a deeper dive into how to apply the directions provided in the Data Dictionary. Here you see the data definition for element 4291, Prior Myocardial Infarction. This data element is found in the History and Risk Factors section of the data collection form and is completed when the patient has at least one documented previous myocardial infarction. Then specifically, the prior MI needs to have occurred at any time between birth and arrival at this facility. Not all data elements have a Notes section, but when they do, the directions included here are applied in addition to the coding instructions and target value. As an example, if patient arrives at Hospital A and is diagnosed with an MI and is transferred to Hospital B for PCI, then they have been diagnosed with a myocardial infarction that occurred between birth and arrival at this facility, Hospital B. This would mean yes is coded for prior MI because the event of MI was documented between birth and arrival at this facility, Hospital B. However, the notes clarify that no should be coded if the patient's only MI occurred at the transferring facility. In this scenario, the patient's MI is the current event for which they are about to receive PCI and should therefore not also be counted as a historical event. If the patient's scenario is altered slightly and the patient arrived at Hospital A, was diagnosed with an MI and treated with PCI at Hospital A, and is subsequently transferred to Hospital B for continued treatment, then the MI which was treated with PCI is considered a historical event. In that scenario, the notes provide that yes is coded when the patient's only MI occurred at the transferring facility because it was treated with PCI prior to arrival at this facility. If the Data Dictionary and other coding resources do not address your specific question, navigate to the FAQ page. This resource includes responses to frequently asked questions of the registry. Begin by entering the data element number or entering a word or phrase and then click search to see the related FAQs. Alternately, all fields can be left blank and clicking on search will render all available FAQs. This concludes Lesson 2 of Getting Acquainted with the CAHPS PCI Registry V5 Dataset. Thank you for your participation.

CATH PCI Registry V5 Dataset

coding resources

data abstraction

Learning Center

Enhanced Data Collection Form