J-12_CROWNWeb.docx

Patient Worksheets

CROWNWeb Data Management Guidelines

CROWNWeb Data Management Guidelines

Document Control Document Information

Contributors A special “Thank you” to the following individuals and groups for their contribution to the development of the CROWNWeb Data Management Guidelines:

The work on which this publication is based was performed under Contract Number HHSM-500-2014-00371G, titled “CROWNWeb Outreach, Communication, and Training,” and contains content obtained under the direction of the Centers for Medicare & Medicaid Services, Department of Health and Human Services. Publication Number: FL-OCT-OCT-04152015-01

Table of Contents

Introduction and Background

Introduction On June 14, 2012, the Centers for Medicare & Medicaid Services (CMS) released CROWNWeb—a Web-based data collection system to be used by all Medicare-certified dialysis facilities throughout the United States and U.S. territories to securely report facility and patient data directly to CMS.

Over 20,000 authorized representatives at more than 6,000 Medicare-certified renal dialysis facilities and select renal transplantation centers use CROWNWeb to process and access information that includes facility details, patient admission/discharge data, CMS forms data, and patient lab results. Additionally, other end stage renal disease (ESRD) stakeholders, including ESRD Network representatives, use CROWNWeb to support data accuracy and to provide technical assistance to dialysis facilities and other users.

To help ensure that all data reported via CROWNWeb accurately reflect the quality of patient care it is vital that all CROWNWeb users understand and follow standardized processes when completing specific tasks within CROWNWeb.

This document describes standardized CROWNWeb data management processes created, reviewed, and approved by CMS. CROWNWeb users should reference these guidelines when overseeing CROWNWeb data entry and reporting efforts.

Tasks to be completed by CROWNWeb users and submission timelines are identified in this CROWNWeb Data Management Guidelines document. These tasks fall into three categories:

1. Data Monitoring consists of policies, processes, and practices that address the accuracy, validity, completeness, timeliness, and integrity of data (data quality).

2. Data Quality Measuring quantifies quality of care through comparison to a criterion. Quality measurements typically focus on structures or processes of care that have a demonstrated relationship to positive health outcomes.

3. Data Quality Managing consists of the business processes that ensure the integrity of an organization's data during collection, application (including aggregation), warehousing, and analysis.[footnoteRef:1] [1: Source of definitions: http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_049664.hcsp?dDocName=bok1_049664

CROWNWeb Overview CROWNWeb is a CMS-mandated data collection system that every Medicare-certified dialysis facility must use to input its patient- and facility-level data. Further, select kidney transplantation centers and other ESRD providers voluntarily input data into CROWNWeb.

CROWNWeb is a Web-based data collection system, which means that users are not required to install software onto their computers. The information stored in CROWNWeb can be accessed from virtually anywhere at any time, barring maintenance downtime.

CROWNWeb’s Release The Conditions for Coverage for End-Stage Renal Disease Facilities (http://www.cms.hhs.gov/CFCsAndCoPs/downloads/ESRDfinalrule0415.pdf) published in April 2008 outline the need for CROWNWeb on page 20484:

494.180(h) - Standard: Furnishing data and information for ESRD program administration. Effective February 1, 2009, the dialysis facility must furnish data and information to CMS and at intervals as specified by the Secretary. This information is used in a national ESRD information system and in compilations relevant to program administration, including claims processing and reimbursement, quality improvement, and performance assessment. The data and information must —

(1) Be submitted at the intervals specified by the Secretary;

(2) Be submitted electronically in the format specified by the Secretary;

(3) Include, but not be limited to—

Using CROWNWeb CROWNWeb allows users to enter data, manage data, and generate reports in the following areas:

Patient information (including demographics and treatment and admission records) Facility information (including contact information, hours, and types of services) Personnel information (including current staff members and job titles) Clinical values and vascular access data.

Supporting CMS Goals CROWNWeb supports a multitude of CMS initiatives. Patient admissions and discharges and clinical and vascular access data reported via CROWNWeb back CMS’ goal to optimize health outcomes as part of the CMS Quality Strategy; efforts to promote high-quality patient care through the ESRD Quality Incentive Program (ESRD QIP); and endeavors highlighted as part of the CMS Triple Aim—Better Care for the Individual through Beneficiary- and Family-Centered Care, Better Health for the ESRD Population, and Reduce Costs of ESRD Care by Improving Care.

CROWNWeb Account Maintenance Due to the sensitivity of the data stored in CROWNWeb, all users must complete an identity authentication process in CMS’ QualityNet Identity Management System (QIMS). CROWNWeb users will be appointed roles and scopes by their designated CROWNWeb Facility Administrators once the user successfully completes the QIMS registration process.

What is QIMS?

QIMS is an identity authorization and management system put in place by CMS to manage access to key government information systems, such as CROWNWeb.

QIMS provides tiered levels of account access and management to CROWNWeb users. As part of this process, individuals serving as their facilities’ Security Officials (SOs) and End User Managers (EUMs) authorize and manage other users’ access to CROWNWeb at their facilities via QIMS.

Overview of QIMS roles:

· End User – The individual submitting the request for a QIMS account.

· End User Manager – The individual who must review and approve the information submitted by the account requestor.

· Security Official – The individual who must activate the account.

The following image outlines the process required to request and obtain an End User QIMS account. Visit http://projectcrownweb.org/education/qims-training-videos for step-by-step instructions on completing the QIMS account registration process.SECURITY OFFICIAL

· Specified by End User when applying for access

· Receives reviewed and approved application from End User Manager

· Ensures that End User has taken CMS Security Training prior to activating account

· Activates account in QIMS

END USER MANAGER

· Specified by End User when applying for access

· Receives application electronically

· Reviews and approves application; sends to Security Official for activation

END USER

· Logs in to QIMS system to request access

· Completes all tabs on QIMS screen

· Submits request to End User Manager

· Receives info to log in to CROWNWeb via e-mail, once account is activated by Security Official

Roles and Responsibilities CROWNWeb Roles CROWNWeb has four roles in which a user can serve. CROWNWeb User Role Types:

· Viewer – Views previously submitted data.

· Editor – Enters data into CROWNWeb.

· Batch – Electronically uploads data into CROWNWeb on behalf of facilities within the user’s scope.

· Administrator – Manages CROWNWeb access.

CROWNWeb Data Manager CROWNWeb data entries are overseen by CROWNWeb Data Managers. A CROWNWeb Data Manager is defined as any authorized CROWNWeb user who oversees or assists with promoting data quality by monitoring, contributing to data effectiveness by measuring, and ensuring data reliability by managing accurate and timely data submissions.

There are three tiers of CROWNWeb Data Managers. Each tier encompasses activities that support accurate and timely reporting of data via CROWNWeb. CROWNWeb Data Managers by tiers:

· Tier 1 – Individuals or groups that manually enter patient and facility details directly into CROWNWeb, or those affiliated with an organization that electronically uploads information on behalf of a Medicare-certified facility. Tier 1 CROWNWeb Data Managers include facility-level users and Electronic Data Interface (EDI) submitters.

· Tier 2 – Individuals or groups that provide technical data reporting assistance. Tier 2 CROWNWeb Data Managers primarily monitor data reporting efforts to foster accurate and timely submissions by Tier 1 users. Additionally, Tier 2 CROWNWeb Data Managers input data directly into CROWNWeb to support data reporting requirements. Tier 2 users analyze report data to determine appropriate support activities for improving quality of both data and healthcare outcomes. Tier 2 CROWNWeb Data Managers include ESRD Network-level users.

· Tier 3 – Individuals or groups that support CMS data reporting needs, as well as monitor and analyze CROWNWeb data entry. Additionally, individuals or groups in this classification support Tier 1 and Tier 2 CROWNWeb Data Managers. Tier 3 CROWNWeb Data Managers include CROWNWeb data support contractors such as those responsible for the QualityNet Help Desk, CROWN Data Discrepancy Support (CDDS), and Production Data Management (PDM) and the CROWNWeb Application Development Organization (ADO).

See the next page for an illustration of how CROWNWeb Data Manager Tiers work together.

Tier 1

Tier 2

Tier 3

In their respective roles, CROWNWeb Data Managers:

· Support the third “arm” of the CMS Triple Aim: Reduce Costs of ESRD Care by Improving Care

· Foster timely and accurate reporting by facilities by analyzing data submission and quality using CROWNWeb reports

· Assist with or oversee CROWNWeb data entry for Medicare-certified dialysis facilities, kidney transplantation centers, and Veterans Health Administration (VHA) facilities

· Work to resolve Action List discrepancies generated by the Renal Management Information System (REMIS) or reassigned by another CROWNWeb Data Manager

· Generate, review, and finalize CMS-2744 ESRD Facility Survey submissions in CROWNWeb

· Monitor compliance with ESRD QIP reporting and performance measures

· Assist CMS and other ESRD stakeholders with monitoring, measuring, and managing all CROWNWeb data.

Tasks authorized to be performed by specific CROWNWeb Data Managers are identified in the following sections of these CROWNWeb Data Management Guidelines.

Chapter 1 Data Monitoring

Data Monitoring CROWNWeb has eight tasks that support efforts to promote data quality through data monitoring. CROWNWeb also offers multiple reports and search capabilities that provide users with the means to monitor and audit data entry efforts.

This chapter provides further details about CROWNWeb data monitoring and the timeframes for performing required tasks to support data accuracy.

Facilities Monitor Facility Attestation

· The Facility Attestation submission period in CROWNWeb is January 1–31 of each year.

· Tier 1 and Tier 2 CROWNWeb Data Managers use the system to monitor the attestation statuses of facilities within their scope.

Tier 2 and Tier 3 CROWNWeb Data Managers monitor Facility Attestation completion each week during the month of January and provide completion reminders to facilities.

Figure 1: Example of Facility Attestation Option in CROWNWeb.

Monitor Facility Details

· Information entered on the Facility Details screen supports the ESRD QIP, Dialysis Facility Reports, Dialysis Facility Compare, and the CMS-2744 ESRD Facility Survey.

· Tier 1 and Tier 2 CROWNWeb Data Managers assist with promoting data accuracy by using CROWNWeb to monitor facility details to ensure that the system contains up-to-date information.

Figure 2: Example of Search Results Showing Facility Demographics.

Monitor Saved Facilities

· All facilities submitted in CROWNWeb must have a valid CMS Certification Number (CCN).

· Tier 2 CROWNWeb Data Managers monitor facility status to ensure that “Saved” facilities are updated with required information.

· Patient and facility data cannot be submitted in CROWNWeb for facilities that are in a “Saved” status.

Figure 3: Example of Add New Facility and Saved Facilities Options in CROWNWeb.

Personnel Review Personnel Information

· Personnel entered in CROWNWeb display on other screens, such as:

Facility Attestation

Treatment Summary

CMS-2728

CMS-2746

· ESRD stakeholders utilize personnel data in CROWNWeb for various communication efforts.

· Tier 1 CROWNWeb Data Managers review Personnel Details to ensure that CROWNWeb contains information on current staff members.

Figure 4: Example of Personnel Details in CROWNWeb.

Reports Generate Duplicate Patients Report

· The entry of duplicate patients in CROWNWeb affects the accuracy and reliability of system-generated reports, and the validity of data provided to ESRD research organizations, such as the United States Renal Data System (USRDS).

· Tier 2 and Tier 3 CROWNWeb Data Managers utilize CROWNWeb’s Duplicate Patients Report to identify and work toward resolving duplicate patient entries at facilities within their scope.

Figure 5: Duplicate Patients Report in CROWNWeb.

Generate Missing Forms Report and Saved Status Report

· Tier 2 CROWNWeb Data Managers use CROWNWeb to complete CMS-2728 and CMS-2746 forms for kidney transplantation and VHA facilities.

· CROWNWeb provides all CROWNWeb Data Managers with a means of generating Missing Forms Reports and Saved Status Reports to identify patients whose forms have not been submitted.

· The Missing Forms Report displays all patients currently or previously affiliated with a user’s in-scope facility with a “Due” or “Past Due” CMS-2728 and/or CMS-2746 form.

· The Saved Status Report identifies all CMS-2728 and CMS-2746 forms that were “Saved,” but still require completion or submission.

Note: The CMS form completion process will be covered in the CROWNWeb Data Managing chapter.

Figure 6: Missing Forms Report and Saved Status Report in CROWNWeb.

Generate Transient Patients Report

· A transient patient requires short-term dialysis at a facility other than his/her home facility for less than 30 days or fewer than 13 treatments.

· The Transient Patients Report identifies patients affiliated with two separate facilities and still in a transient status beyond 30 days.

Figure 7: Transient Patients Report in CROWNWeb.

Generate Unverified PART Report

· The PART tool is used by Tier 1 CROWNWeb Data Managers to verify four key pieces of patient information/activity every 30 days:

· Patient census

· Admit/discharge status (including “Transient status”)

· Current treatment information

· Current attending physician

· Tier 2 CROWNWeb Data Managers have the ability to run Unverified PART Reports in CROWNWeb to identify facilities that have not updated their PART data in 30 or more days.

Figure 8: Unverified PART Report in CROWNWeb.

Introduction to CROWNWeb

CROWNWeb Data Management Guidelines Page | 3

Chapter 2 Data Measuring

CROWNWeb has three tasks that support efforts to promote data relevancy through data measuring. CROWNWeb also offers multiple reports and search capabilities that allow users to measure the length of time since data were last updated in CROWNWeb, as well as the ability to determine if specific submission goals were met.

This chapter provides further details about CROWNWeb data measuring and the timeframes for performing required tasks to support CROWNWeb data relevancy.

Reports Generate Clinical Data and Missing Labs Report

· Tier 1 CROWNWeb Data Managers who manage clinical data entries enter the last lab of the month for hemodialysis and peritoneal dialysis patients, or indicate “Not Available” when applicable.

· Tier 2 and Tier 3 CROWNWeb Data Managers are able to measure clinical data reporting compliance.

· The Clinical Data and Missing Labs Report allow Tier 2 and Tier 3 CROWNWeb Data Managers to identify the percentages of patients whose reported clinical lab results fall within, or outside, a specified range, and missing clinical and lab data.

· Tier 2 and Tier 3 CROWNWeb Data Managers can refine the report by selecting a clinical period (Open Clinical Months only), one or more facilities, a treatment type, and the clinical values.

· Values included as part of this report are:

*Indicates hemodialysis clinical values only.

Figure 9: Clinical Data and Missing Labs Report in CROWNWeb.

Generate Open Accretions Report and Open Notifications Report

· CROWNWeb generates Notifications and Accretions on the Action List tab to enable facilities to troubleshoot and correct discrepancies between CROWNWeb and REMIS.

· All CROWNWeb Data Managers resolve Notifications and Accretions within 15 days of when they are issued, unless placed “Under Investigation.”

· Notifications or Accretions placed “Under Investigation” must be resolved within 30 days of when they are issued.

· All CROWNWeb Data Managers utilize CROWNWeb to access the Open Notifications and Open Accretions Reports that measure discrepancies supplied by REMIS.

ACCRETION

ACCRETION

NOTIFICATION

ACCRETION

ACCRETION

NOTIFICATION

NOTIFICATION

NOTIFICATION

ACCRETION

NOTIFICATION

ACCRETION

ACCRETION

ACCRETION

NOTIFICATION

NOTIFICATION

NOTIFICATION

ACCRETION

NOTIFICATION

NOTIFICATION

ACCRETION

ACCRETION

NOTIFICATION

ACCRETION

REMIS

CROWNWeb REMIS gathers information from various CMS databases, and compares that data to data in CROWNWeb.

CROWNWeb receives discrepancy information each night, and assigns Notifications and Accretions to facilities and ESRD Networks.

TO FACILITY XYZ

TO FACILITY ABC

TO ESRD Network 123

Figure 10: The CROWNWeb and REMIS communication process.

Figure 11: Open Notifications and Open Accretions Reports in CROWNWeb.

Introduction to CROWNWeb

CROWNWeb Data Management Guidelines Page | 27

Chapter 3 Data Managing

The following 15 user tasks in CROWNWeb support efforts to promote accurate and timely data submissions through data managing:

Tier 3

*Tier 2 CROWNWeb Data Managers are authorized to complete patient admissions and discharges, and update records for kidney transplantation and Veterans Health Administration (VHA) centers.

**Tier 3 CROWNWeb Data Managers are authorized to delete and modify CMS-2728 forms and to delete CMS-2746 forms.

This chapter provides further details about CROWNWeb data managing and the timeframes for performing required tasks to support accurate and timely data submissions.

Facilities Add New Facility in CROWNWeb

· CROWNWeb allows Tier 2 CROWNWeb Data Managers to add new Medicare-certified dialysis and kidney transplantation facilities with valid CCNs.

· Facilities added to CROWNWeb are active upon submission into CROWNWeb, and appear in CMS’ QIMS system the following day.

Figure 12: Add New Facility Option in CROWNWeb.

Submit Facility Attestations

· Tier 1 CROWNWeb Data Managers manually enter or electronically upload data to the Facility Attestation section in CROWNWeb.

· Tier 1 CROWNWeb Data Managers support the ESRD QIP by working to ensure that accurate Facility Attestation data are reported by CMS-designated submission deadlines.

Figure 13: Facility Attestation Tab in CROWNWeb.

Update Facility Details

· Tier 1 CROWNWeb Data Managers are able to update most fields in CROWNWeb; however, they must work with Tier 2 users to edit disabled fields.

· Changes made to the Facility Details section appear immediately in CROWNWeb.

Figure 14: Edit Facility Option in CROWNWeb.

Patients Admit and Discharge Patients

· Patients who receive a kidney transplant at a Medicare-certified kidney transplantation center must be admitted to a kidney transplantation center in CROWNWeb.

· Tier 1 CROWNWeb Data Managers admit and discharge ESRD patients in CROWNWeb to and from Medicare-certified dialysis facilities within their scope.

· Tier 2 CROWNWeb Data Managers admit and discharge patients to and from kidney transplantation and VHA facilities within their scope.

Tier 2 CROWNWeb Data Managers admit and discharge patients to and from their respective Medicare-certified kidney transplantation and VHA facilities within 2 business days of notification and discharge within 2 business days of last treatment notification.

Visit http://mycrownweb.org/pcw_course/discharging-patient for instructions on how to manage a discharge in CROWNWeb.

*Acute ESRD patients should not be entered into CROWNWeb.

Figure 15: Admit Patient Option in CROWNWeb.

Admit and Discharge Transient Patients

· Tier 1 CROWNWeb Data Managers admit and discharge transient patients upon arrival to and departure from the receiving dialysis facility.

· Change in the patient’s transient status:

Transient Status = “No”

Figure 16: Admit Transient Option in CROWNWeb.

Complete CMS-2728 and CMS-2746 Forms

· CMS-2728 forms are completed and submitted directly to CMS via CROWNWeb. The original signed CMS-2728 is provided to the Social Security Administration (SSA) if the patient is applying for ESRD Medicare benefits.

· A CMS-2746 ESRD Death Notification form is completed when a patient dies.

· Copies of the printed and signed CMS-2728 form and the printed CMS-2746 form are kept in the patient’s medical record.

· Submit Initial CMS-2728 forms within 10 business days of Date Regular Chronic Dialysis Began (field 24 of CMS-2728 form) for ESRD patients at Medicare-certified dialysis facilities, but no later than 45 days.

· Submit CMS-2746 forms within 14 days of the date of death.

Tier 2 CROWNWeb Data Managers:

· Submit Initial CMS-2728 forms within 5 business days of notification.

· Submit CMS-2746 forms for Medicare-certified kidney transplantation and VHA facilities within 5 business days of notification of the date of death.

Tier 3 CROWNWeb Data Managers:

· Support Tier 1 and Tier 2 CROWNWeb Data Managers by deleting and/or modifying CMS-2728 forms within 10 business days of assignment to the Tier 3 Data Manager.

· Support Tier 1 and Tier 2 CROWNWeb Data Managers by deleting CMS-2746 forms within 5 business days of assignment to the Tier 3 Data Manager.

Visit http://mycrownweb.org/pcw_course/completing-cms-2746-form for instructions on how to complete a CMS-2746 form in CROWNWeb.

PART Verification

· CROWNWeb allows Tier 1 users to set a filter of “No PART > 30 Days” to display only patients who still have not been verified in 30+ days.

· The PART tool is used to verify four key pieces of patient information/activity every 30 days:

· Patient census

· Admit/discharge status (including transient status)

· Current treatment information

· Current attending physician

Figure 17: PART Verification in CROWNWeb.

Resolve Gap Patients

· Are not currently associated with a facility and have not been re-admitted after a discharge

· Have no death information associated with them

· For a Gap patient to be resolved, he/she must either be admitted to the proper facility, or the necessary death information must be entered in CROWNWeb.

· Tier 3 CROWNWeb Data Managers support Tier 2 users by providing weekly Gap patient analysis reports.

· Tier 1 and Tier 2 CROWNWeb Data Managers work together to locate and resolve Gap patients.

Tier 2 CROWNWeb Data Managers communicate with Tier 1 CROWNWeb Data Managers weekly by providing Gap Patient Report to resolve Gap patients.

Personnel Add/Edit Key Personnel

· Personnel entered in CROWNWeb display on other screens, such as:

Facility Attestation

Treatment Summary

CMS-2728

CMS-2746

· Tier 1 CROWNWeb Data Managers review and “Inactivate Records” as needed.

· ESRD stakeholders utilize personnel data in CROWNWeb for various communications and approvals.

Tier 2 CROWNWeb Data Managers add/edit key staff members on the Personnel screen of in-scope Medicare-certified kidney transplantation and VHA facilities within 5 business days of notification of staff changes.

Figure 18: Add/Edit Personnel Options in CROWNWeb.

Clinical Manage Clinical

· The CMS Quality Strategy

· The ESRD QIP

· The CMS Triple Aim

· CROWNWeb clinical data include data on management of:

Infection

· Tier 1 CROWNWeb Data Managers report clinical data directly to CMS by either manually entering lab results and other clinical data into CROWNWeb or electronically through batch submission.

· Tier 1 CROWNWeb Data Managers report the last lab of the month for hemodialysis and peritoneal dialysis patients or indicate “Not Available” when applicable.

· Tier 1 CROWNWeb Data Managers report the vascular access type used for each patient during his or her last dialysis treatment during a Clinical Month.

Action List Resolve Action List Notifications and Accretions

· Notifications and Accretions are created when differences are identified between the two databases.

· CROWNWeb has two types of Notifications:

· CROWNWeb has one type of Accretion:

· Notifications and Accretions are:

· Assigned to Tier 1 CROWNWeb Data Managers directly from REMIS or “Reassigned” by Tier 2 users.

· Assigned to Tier 2 CROWNWeb Data Managers directly from REMIS, “Reassigned” by another Tier 2 user, or “Escalated” by a Tier 1 user.

· Tier 2 CROWNWeb Data Managers are responsible for resolving Notifications and Accretions for VHA, kidney transplantation, and closed facilities. Tier 2 CROWNWeb Data Managers are responsible for reassigning or escalating out-of-scope patients or Gap patients in CROWNWeb.

· Assigned to Tier 3 CROWNWeb Data Managers directly from REMIS or “Escalated” by Tier 2 users to reconcile ESRD systems.

Tier 2: Visit http://mycrownweb.org/pcw_course/notifications-accretions-network-role for instructions on how to resolve Action List discrepancies in CROWNWeb.

Figure 19: Actions taken by CROWNWeb Data Managers to Resolve Notifications and Accretions.

Tier 3

Form 2744 Add New CMS-2744A Forms (Dialysis Facilities)

· Treatment trends

· Utilization of services

· Patterns of practice in treating ESRD patients

· CMS-2744A forms are completed for Medicare-certified dialysis facilities that capture facility, treatment, and staffing data for the survey year (January 1 – December 31).

· All patient admissions and discharges and treatment information are entered in CROWNWeb for the survey year.

Tier 2: Visit http://mycrownweb.org/pcw_course/cms-2744-network for instructions on how to complete the CMS-2744 form in CROWNWeb.

Figure 20: Add a New Form 2744 Option in CROWNWeb.

Add New CMS-2744B Forms (Kidney Transplantation Facilities)

· Tier 1 CROWNWeb Data Managers at kidney transplantation centers are authorized to complete CMS-2744B forms for facilities within their scope.*

· Tier 2 CROWNWeb Data Managers complete CMS-2744B forms for kidney transplantation centers that do not have CROWNWeb access.

*Tier 1 CROWNWeb Data Managers at kidney transplantation centers have limited access in CROWNWeb. However, they are authorized to complete the CMS-2744B form in CROWNWeb.

Figure 21: CMS-2744 Completion.

Accept/Reject/Finalize CMS-2744 Forms

· Users must resolve CMS-2744 errors before attempting to “Submit for Acceptance.” The form is complete once it is “Finalized.”

· CMS-2744 forms are “Accepted” or “Rejected” and “Finalized” by Tier 2 CROWNWeb Data Managers.

· Tier 2 CROWNWeb Data Managers attest that all facilities within their scope have completed the CMS-2744 forms by the CMS due date.

Figure 22: CMS-2744 Status Descriptions.

Figure 23: CMS-2744 Workflow

Add New CMS-2744A Forms for Closed Facilities

· Tier 1 CROWNWeb Data Managers ensure that all patient, patient admission and discharge, and treatment information are entered into CROWNWeb before submitting a CMS-2744A form.

Figure 24: Add a New Form 2744 Option in CROWNWeb.

Chapter 4 Tier 3 CROWNWeb Data Management Support

Tier 3 CROWNWeb Data Manager Role Role Defined Tier 3 CROWNWeb Data Managers support CROWNWeb Data Monitoring, Data Measuring, and Data Managing by using the CROWNWeb system to acquire and report necessary data to CMS. Additionally, Tier 3 CROWNWeb Data Managers provide support to Tier 1 and Tier 2 users by providing reports and other documentation that provide an overview of data entries.

Examples of Tier 3 CROWNWeb data management support:

Data Monitoring

Tier 1 and Tier 2 Usage

Research and resolve data discrepancies between CROWNWeb and REMIS

Research and resolve missing clinical data entries

Research and resolve batch submission errors with Tier 1

Appendixes CROWNWeb Facility-Level Reports Facility-Level Reports

Facility Reports

Patient Report

Audit Reports

Clinical Performance Measures (CPMs) Reports

Quality Improvement Reports

Vascular Access Reports

Notification and Accretions Reports

CROWNWeb Network-Level Reports Network-Level Reports

Patient Reports