| Category | Rqmt ID | Title | Originators Request |
|---|---|---|---|
| CROWNWEB | RQMT_140 | Batch and SUI Address Inconsistencies | On July 15, 2009, it was stated in the IV&V meeting that XXXXXX determined that BATCH and SUI requirements would not be required to be the same. It was determined by CMS that this would be put in writing by CMS. The Physical Address in one of the areas where the requirements for Batch are different than the SUI. This needs to be documented. |
| CROWNWEB | RQMT_153 | One-Way Arrow | One Way Arror: CCN, Facility DBA, and the NPI field connection. Modify the KDD to address the correlation between these three fields. In addtion: Primary Type of Dialysis is a one way arrow. |
| CROWNWEB | RQMT_189 | DOB and DOD as Search Criteria | DOB and DOD as Search Criteria in the Patient Module. CMS requested that RCT reseach this post National Release of CROWNWeb (R 1.2) |
| CROWNWEB | RQMT_199 | CSC Contractor Access to Network/Facility Data in CROWNWeb | CSC Contractor Access to Network/Facility Data in CROWNWeb |
| CROWNWEB | RQMT_212 | Report Field Decriptions: Clarify | Request for more robust Report Field descriptions with clarification added to the CROWNWeb Reports page (All Reports). |
| CROWNWEB | RQMT_213 | Edit Primary COD on 2746 Form | Request the ability to edit the Primary Cause of Death directly on the 2746 form. |
| CROWNWEB | RQMT_214 | Perm versus Temp CCN for User Role and Scope | Request to link the QIPS business name to the CW org ID which will not change when the facility profile is edited in CW. |
| BATCH | RQMT_169 | Associate each submitter user ID with a submitting organization | Requirement Definition: The System shall associate each submitter user ID with a submitting organization in CROWNWeb. |
| BATCH | RQMT_176 | Data Provided to Electronic Submitters | Requirement Definition: Data Provided to Electronic Submitters |
| BATCH | RQMT_177 | Provide TBD patient data (e.g., 2728 and 2746) | Requirement Definition: The System shall provide TBD patient data (e.g., 2728 and 2746) to batch submitter users so that their systems are complete. |
| BATCH | RQMT_198 | Prohibit modifying an Admit Reason after a 2728 Form in BATCH and SUI | Request to prohibit CROWNWeb from allowing a patient admit reason to be changed from New to ESRD to transfer in or to any other admit reason even though there is a submitted 2728 form. |
| BATCH | RQMT_170 | Summary Reports of Processed Batch Submission | Requirement Definition: Summary Reports of Processed Batch Submission |
| BATCH | RQMT_171 | Summary reports for CMS and ESRD Network users | Requirement Definition: The System shall
provide the following summary reports for CMS and ESRD
Network users, containing numbers of new admissions, numbers
of discharges and number of updates processed using UI and
batch submission for three time periods (< 30 days; >
30 days < 60 days; > 60 days < 90 days): 1. By Facility 2. By Network (includes all facilities for one Network) 3. By Overall (includes summary for all Networks). |
| BATCH | RQMT_172 | Summary reports for Electronic Submitter users | Requirement Definition: The System shall provide the following summary reports for Electronic Submitter users, containing numbers of new admissions, numbers of discharges and number of updates processed using batch submission by electronic submitters for three time periods (< 30 days; > 30 days < 60 days; > 60 days < 90 days). |
| BATCH | RQMT_173 | Allow batch submitter, Network, and CMS users to view patient data | The System shall allow batch submitter users, Network users and CMS users to view patient data to assist in resolution of patient near-match issues across the scope of all the facilities they are submitting for. |
| BATCH | RQMT_204 | BATCH Discharge Date and DOD work differently than the SUI | Discharge Date and Date of Death Fields are linked by the System, however, BATCH and The SUI work differently and allows the dates to be different when the discharge reason =Death. |
| BATCH | RQMT_205 | Patient Roster: Patient Sort on Name | Request to sort Upper and Lower Case Last Names the same. |
| BATCH | RQMT_196 | SUI - Clinical Data Time Issues | Independent Facililites requesting BATCH capabilities. |
| BATCH | RQMT_231 | For Transient Patient admits, add "other" & "rehab" to drop down list options | User Type Impacted: (Facility Editor) Issue Reported: xxxxxx contacted the CROWN Help Desk with an Enhancement request for the CROWNWeb application. While admitting a Transient patient, user would like to add an additional reason to the transient reason table / drop down list. User would like to add transient reasons of “Other” and “Rehab” to this drop down list. Related Business Requirement/BR 6.3 ID 64 Current Behavior: Currently CROWNWeb does not have Rehab or Other in the reason list. Expected Behavior: CROWNWeb will have Rehab and Other as possible options in the Transient reason dropdown list. |
| BATCH | RQMT_216 | A Facility has no NPI and will never get one | This will allow the capture of ESRD patient data. Currently there is a contractual requirement for networks to capture some patient data where facilities will never have an NPI number. |
| BATCH | RQMT_174 | User Interface for Resolution of Near Matches | Requirement Definition: User Interface for Resolution of Near Matches |
| BATCH | RQMT_175 | Identify potential duplicate patients (near matches) | Requirement Definition: The System shall provide a UI to identify potential duplicate patients (near matches) – as well as avoid duplication of PART, Clinical and Vascular Access data - induced by electronic submission. System validation should error on the side of preventing duplicate patient’s PART, Clinical and Vascular Access data through electronic submission. |
| BATCH | RQMT_182 | PART Report Issues | BATCH uploads are erroneously removing patients from PART who have a system discharge due to a Transient Status. |
| BATCH | RQMT_217 | Acute Patients | If a patient has been discharged as acute the patient should be able to be readmitted into the CROWNWeb System. This patient should not show up as a gap patient, but should be displayed as possible dup during admission of a new patient. |
| BATCH | RQMT_232 | Add "Interruption in service/Resume service" functionality during admit/discharge | User requests to add "Interruption in
Service" and "Resume Service" functionality to
CROWNWeb. Currently CROWNWeb only allows users to transfer out a patient, which forces the facility user to discharge the patient even when they are in the hospital or absent for a non ESRD event. The Facility then must transfer the patient back into their facility. |
| BATCH | RQMT_255 | Submitting Help Desk service request after Acute Patient discharge | Issue Reported: SOP_10: instructs a user of
CROWNWeb to submit a Service request to the CROWN Help Desk
after discharging a patient as acute. The SOP does not
provide guidance to the user in regards to what the specific
request is for and what needs to be done as a result of the
Service Request being opened. Clarification is needed on what
action a user needs to request to have performed on the
service request that the SOP instructs them to open. Related SOP #: SOP_10 Removing Acute or Erroneously Entered Patients from CROWNWeb" Business Need driving request: Facilities and networks do not know what action needs to be performed as a result of opening a service request after discharging a patient as acute in CROWNWeb. |
| Clinical Module | RQMT_222 | Clinical Values to calculate programmatically based on entered clinical data | Request for Clinical Values to calculate programmatically based on entered clinical data. |
| Clinical Module | RQMT_223 | Creatitine Clearance (PD) not required | Request to make the Creatitine Clearance (PD)field not mandatory. |
| Clinical Module | RQMT_238 | Add an option to the Clinical Module for "Not Found/Not Performed" when entering patient data | Reuqest to add a "checkbox" to the clinical
module for "Not Found/Not Performed" so that patients who do
not have lab values for a month would not appear on the
"Missing Clinical Data" report. This will allow patients that do not have any data to input to not appear on the report so that the report only displays patients who actually need data entered. |
| Clinical Module | RQMT_249 | Add 'Albumin' attribute | Add 'Albumin' as an attribute to the Measure field on the Clinical screen |
| Clinical Module | RQMT_47 | CR-909 - Clinical Data entry: Usability Issue | CROWNWeb is not keyboard centric and is not condusive for data entry. |
| Clinical Module | RQMT_125 | Dialysate Volume, Urine Volume, Serum Ferritin, and Pre-Dialysis Weight | The labeling and the KDD elements are in conflict. RCT requests the ability to research these elements to ensure they are (HL7) compliant. The results of this research will determine what change if any should be made. |
| Clinical Module | RQMT_13 | Filter for Post-BUN <= 3 | Request to filter out Patient with a POST BUN of <= 3 as this is due to bad lab draw technique from the CPM Measures. (This is the opinion of the originator however RCT worked with NW7 Clinical Staff who agreed this would be do to a bad lab draw). |
| Clinical Module | RQMT_166 | Weekly Kt/V Field Label is confusing | Request for Weekly Kt/V for PD Label change as this is drawn monthly and is confusing to the users. Therefore, remove the word "Weekly". |
| Clinical Module | RQMT_168 | Dialysate Volume | Request to modify Dialysate Volume to reflect that it is related to the Outflow volume. |
| Clinical Module | RQMT_186 | CPM Adequacy Measures | Request the ability to substitute different adequacy measures when the CMS approved measures are not available |
| Clinical Module | RQMT_57 | CR-892 - Request Field Label Change to spKt/V with RRF | Request to change label to – Single Pool KTV without Residual Renal Function (RRF)for Release 2.0 |
| Clinical Module | RQMT_58 | CR-891 - Request for the PD Weekly Kt/Vurea and Serum Creatinine be required to be collected on the same date. | Request that Kt/V and Serum Creatinine
always be drawn on the same date or should the Serum
Creatinine date be collected at all? |
| Clinical Module | RQMT_59 | CR-890 - Request for Corrected Serum Calcium to be a required field. | Although Corrected Serum Calcium (BR 6.1 KDD element #213) is not a mandatory field in CROWNWeb; it is required for the Mineral Metabolism CPM, therefore request that this field be made mandatory. |
| Clinical Module | RQMT_67 | CR-877 - Request for more robust tracking of these two clinical prescriptions: ESA and Iron. | The DO are requesting an expansion of the Prescription Area of the Clinical Module. This is requested so that a patient's changes in ESA and Iron can be tracked. |
| Clinical Module | RQMT_68 | CR-875 - Request to add RRF to Batch Submissions. | Batch Submitting Organizations requesting a change to the CMS approved CPM Measures to include RRF in the measures. |
| Clinical Module | RQMT_111 | Request the ability to override validation warnings through a check boxes before submit | Request that validation override message appear before the user selects the Submit button in the Clinical Module. |
| Clinical Module | RQMT_117 | Common Lab Test Date | Request to clear the Common Lab Test date after each patient is submitted. |
| Clinical Module | RQMT_179 | Add Save Functionality to the Clinical Module | Request to add Save Functionality to the Clinical Module. |
| Clinical Module | RQMT_181 | Clinical Data From 2728 to Populate to the Clinical Module | Request that the Clinical Data From 2728 Auto Populate to the Clinical Module for the month the 2728 is submitted. |
| Clinical Module | RQMT_230 | Filter out patients if labs not taken | The user has requested that a "checkbox" be added to the clinical module for "Not Found/Not Performed" so that patients who do not have lab values for a month would not appear on the "Missing Clinical Data" report. |
| Clinical Module | RQMT_237 | "Date" for the ESA and IVR be more clearly defined | Request that the "Date" for the ESA and IVR be more clearly defined and that the process not be so "time intensive" for the facilities (having to be updated with each change). The user also stated that the clinical data entry does not keep a record of the changes and only preserves the most recent change, and stated this is not consistent with how facilities perform record keeping. |
| Clinical Module | RQMT_251 | Add 'Description' attribute | Add a free text 'Description' attribute to the Clinical screen |
| Clinical Module | RQMT_38 | Clinical - Old CR_257 | Request from XXXXXXXXXX: The ability to
enter ESA Dose, ESA Unit of Measure, ESA Route, Frequency of
ESA Dose and Iron Dose, Iron Route, Frequency of Iron
Dose. The ability to enter Serum iPTH lab result and Serum iPTH Collection Date must be supported in CROWNWeb as part of a complete clinical perspective of Mineral Metabolism. To ensure continuity of the “12 Elements” requirements, CR #257 and CR #258 have been combined into one change request for clarity and consistency. |
| Clinical Module | RQMT_110 | Maturing Graft Present? | The system requires the user to enter "Yes or No" in the Maturing Graft Present? field when "Graft Not Yet Present" has already been selected. This only occurs when current access type = Catheter Only. |
| Clinical Module | RQMT_115 | Visiting Patient Becomes a Permanent Transfer | NW Kidney Centers reported that one of their patients planned a week vacation. The visiting facility was part of the CROWNWeb Phase I Rollout. The facility entered the patient in the System. CROWNWeb discharged the patient from their primary facility (System Discharge). Because of this, the primary facility could not enter in the patient's clinical data. The facility had to work with the Network to fix this issue, however, the patient's data was overwritten every via BATCH, as the System Discharged the patient over and over again. |
| Clinical Module | RQMT_187 | Fistula with 2 Needles | Fistula with 2 Needles should have the AVG Status Grayed out. |
| Clinical Module | RQMT_188 | Surveillance with Fistulas | Request for surveillance option to be available when the user selects any fistula as the Access Type. |
| Clinical Module | RQMT_194 | The Date Access Type Changed for Patient is too Time-Intensive | The Date Access Type Changed for Patient is too Time-Intensive and has requested the follow: accesses created or revised more than 12 months before the date of entering the data into CROWNWeb (anytime before December, 2008), facilities should be allowed to enter “> 12 months” as the creation/revision date. |
| Clinical Module | RQMT_197 | Incorrect Vascular Access Headers | Request for Vascular Access-Site on the Search Clinical screen to display correct headers. Specifically, AVF Creation Date should be Date Access Type Changed, and AVF Usable Date should either be changed to something else or the correct values should be reflected for patients. For instance, catheter-only patients show a date in this field even though there is NO AVF Usable Date. |
| Clinical Module | RQMT_2 | CR 907 - Request to remove the current validations on the Date Access Type Changed field | Request to use the actual true dates in the
Date Access Type Changed Field. Currently, the date entered
must be after the admit date in CROWNWeb. |
| Clinical Module | RQMT_208 | Date Access Type Changed | Request for the ability to enter "Unknown" in the Date Access Type Changed Field. |
| Clinical Module | RQMT_233 | When entering frequency of Intra-Access Flow measurement, add the option for "At every treatment" | When entering a patients Vascular access
information: If "yes" is selected in the "Surveillance with
intra access flow performed" section, CROWNWeb will then
require the user to select a frequency of intra-access flow
measurement. Would like to have "At every treatment" added to
list of options. Expected Behavior: CROWNWeb will display “at every treatment” as an option for the frequency of Intra-access flow measurement. |
| Clinical Module | RQMT_250 | Add 'Previous Access Type' attribute | Add 'Previous Access Type' attribute to the KDD and Manage Clinical screen on the Vascular Access applet |
| Clinical Module | RQMT_3 | CR 908 - AV Fistula Creation Date | Request the ability to enter the AV Fistula Creation Date, but not mandatory requirement, if Current Access type = 1,2 or 3 (AVF; AVF w/ graft or cath), along with ability to enter this as a prior date; Leave as mandatory the ability to enter AV Fistula Creation Date if Current Access type = 4,5,6,7, or 9 and maturing AVF = Yes. |
| Clinical Module | RQMT_48 | CR-908 - AV Fistula Creation Date | Facilities who know the AV Fistula Creation Date would like to enter the date for those patients whose first access was an AV Fistula. If possible, could CROWNWeb include the ability to enter an AV Fistula Creation Date (available to enter but not mandatory) if Current Access type = 1,2 or 3 (AVF; AVF w/ graft or cath), along with ability to enter this as a prior date; Leave as mandatory the ability to enter AV Fistula Creation Date if Current Access type = 4,5,6,7, or 9 and maturing AVF = Yes. |
| Clinical Module | RQMT_49 | CR-907 - Date Access Type changed field | The following issue was sent to the Crown
Help Desk. Customer XXXXXXXXXX is requesting a change in
the Date Access Type change field in the Manage Clinical data
section of CrownWeb. The customer would like to use the actual or true dates in the Date Access Type change field in the manage clinical, type Vascular, instead of having to enter a false date that is after the patient admit date at their facility. For example, patient A received a fistula 1 year prior to being admitted at their facility in July 08. The system will not allow them to enter the actual or real date the access type changed if it’s prior to the admit date at their facility. They must enter a date that’s really not accurate and they would like this to be changed. |
| Clinical Module | RQMT_64 | CR-880 - Doppler | Requests to change the frequency selections for Doppler Examination Drop Down Field. |
| Clinical Module | RQMT_65 | CR-879 - PrePump Frequency Options | Request for the PrePump Frequency Examination Frequency dropdown selections to be changed to reflect when the facilities actually perform them. |
| Facility | RQMT_15 | Facility Personnel Report | Request for the system to sort Facility Personnel Report by CCN not UPI and reorganize the report layout as it is a useability problem. |
| Facility | RQMT_192 | Transplant Facility Primary Contact | Transplant Facility Primary Contact |
| Facility | RQMT_69 | CR-874 - Advanced Facility Search | Request for the Advanced Facility Search screen to include an option to search by Organizational Affiliation. |
| Facility | RQMT_164 | Hospital CCN Question regarding "23" in the 3rd & 4th position of the field | is unable to add the Medicare Services for the facility, nor the back-up facilities because the Hospital CCN he is entering does not follow the Business Requirement. xxxxxx requested that this issue be submitted for clarification or change as there are Hospital CCN's that do not follow this rule and cannot be populated into Facility Details. |
| Facility | RQMT_18 | Hospital CCN 3rd and 4th position must be 23 | Request for a rationale of why the Hospital
CCN 3rd and 4th position must be 23. |
| Facility | RQMT_203 | Serum Albumin Lower limit as a facility default. | Request to add Serum Albumin Lower limit as
a facility default. |
| Facility | RQMT_239 | Remove Facility Editor's ability to change facility's DBA name | Request to remove a Facility Editor’s
ability to change their facility’s DBA name within
CROWNWeb. Expected Behavior: Remove a Facility Editor’s ability to change a facility’s DBA name and only allow Networks this ability. |
| Facility | RQMT_71 | CR-870 Closed Facility as Back-up | Request for warning messages for the the Closed Facility and the Facility whose back-up becomes a closed facility. |
| Facility | RQMT_73 | CR-851 - Organizational Affiliation | Request to add Organizational Affiliations to the Organizational Affiliations table in CROWNWeb. There are new ones since the onset of the CROWNWeb Release 1.0 and facilities are forced to select "Other". |
| Facility | RQMT_82 | CR-741 - Staff Fields not Implemented | Request for fields necessary to complete the CMS-2744 Report/Form to be implemented in the system, such as: Facility Full-Time Staff, Facility Part-Time Staff, Facility Full-Time Open Positions, Facility Part-Time Open Positions, Facility Hemodialysis Treatments, and Facility Other Treatments. |
| Facility | RQMT_84 | CR-735 - Dx Code Dropdown | Request for a mechanism allowing the user to select the Primary Diagnosis Code field to be a dropdown selection. |
| Facility | RQMT_85 | CR-734 - Page Frames | Request to implement pageframes with tabs to display the facility data instead of one long page. |
| Facility | RQMT_122 | Modify Personnel Business Name | Modify Personnel Business Name to remove "prepopulate with Facility Name" because this is not how the system behaves when a Personnel Record has more than one Business Name associated. |
| Facility | RQMT_123 | Label Changes the Facility Personnel Reports | Request from the Development Contractor to provide the Display Name fields for the Facility Personnel Reports have been requested. |
| Facility | RQMT_132 | Personnel Phone Extension Field | The issue is when an extension number is
entered in the Personnel Phone Number Extension Field, should
the Personnel Phone Number Field be required? |
| Facility | RQMT_19 | Perform any duplicate checking when accepting personnel | Request for Duplicate and Near Match mechanism for Personnel. |
| Facility | RQMT_227 | When to display job code descriptions | Only show Physician Job Codes/descriptions when a UPIN and/or Personnel NPI is populated. |
| Facility | RQMT_136 | Personnel Record Search Criteria | Personnel Record Search Criteria requirement is not provide enough clarity. This will be modified per CMS. |
| Facility | RQMT_88 | CR-658 - Personnel Search | Request to sort by UPIN in the Personnel Search functionality. |
| Global | RQMT_215 | CROWNWeb 1.2 Release not 508 Compliant | CROWNWeb 1.2 Release not 508 Compliant per CMS and CSC |
| Global | RQMT_99 | CR-309 - Sort by CCN - User Managment | Request to sort the facilities by CCN in the Manage Facility User Scope page. |
| Global | RQMT_178 | 15 Minute Time out Warning | Request the 15 minute time out be extended and present a warning message to the user within 60-Second Time before the 15 minute time-out occurs. |
| Global | RQMT_74 | CR-768 - Tab Order | Tab Order (Key-Board) when entering Lab Values is not user friendly and is inconsistent. |
| Global | RQMT_4 | CR 909 - Field Tabbing | Request for the Field tabbing order to be consistent in CROWNWeb: request a Usability Study to ensure tab order is appropriate. |
| Global | RQMT_247 | Add 'Discharge Reason' attribute | Add Discharge Reason attribute to the Patient PART screen |
| Global | RQMT_248 | Add 'Saved' attribute | Add Saved attribute to the Patient PART screen |
| Global | RQMT_62 | CR-881 - PART Enhancement - Extend View of System Discharged Patient to 60 days | Issue Reported: IN the CROWNWeb application, the PART report is displaying patients with a system discharge date of only 30 days prior to the system date. If a patient is on the PART report at the beginning of the month, and then somewhere a mistake is made and the patient is admitted to a different facility as a non-transient and the system discharge date is more that 30 days prior to the system date, the patient will not appear on the PART report. This is makes the patients difficult to track. Enhancement request to raise this 30 day limit to at least 60 days. |
| Global | RQMT_141 | Batch User Role and Scope update | Batch user Role and Scope require modifications. The title is not Batch Editor. |
| Global | RQMT_126 | CMS System Administrator and System Administrator Roles and Scope | Request to analyze the permissable roles that the CMS System Administrator and System Administrator's can assign requires to ensure that the role logic has been appropriately applied. |
| Global | RQMT_210 | Help Desk User Role in CROWNWeb | Request for a new User Role to be added to
the System for the Help Desk Staff that would allow the
application to be seen in a view or edit mode but not perform
any database updates. |
| Library | RQMT_143 | State Table | Change the documentation to indicate that the State will not be abbreviated in all Address fields in the application. This was requested as the Development implementation does not comply with the requirement. CMS has requested that the documentation be changed to match how the System was implemented. |
| Library | RQMT_148 | Country Table | Modify the table to state that the country not the code will display in the dropdown of the UI. |
| Training | RQMT_193 | Remove Limitation of 20 Facilities from all Applicable Reports | Request to remove Limitation of 20 Facilities for all applicable reports so that the user can run reports that include all facilities within their scope. |
| Patient Information | RQMT_139 | Race Code | For the "Race" field on this page, the Race Codes are not displayed and available for selection. The requirement states that the codes should deplay and not the text. This is incorrect. Requirement will be modified. |
| Patient Information | RQMT_201 | PART: Patients appear multiple times on the PART | Request that a patient appear on PART once only regardless of the number of admits/discharges. |
| Patient Information | RQMT_202 | PART Search is confusing | Request for the PART Search selections to be more intuitive. The New Patient Search is not working as expected. |
| Patient Information | RQMT_206 | Print notification the 2728 and 2746 | Request for notification message to display to the user when the user invokes the print button for the 2727/2746 forms in the Systems |
| Patient Information | RQMT_10 | CR 914 - 2728 Lipid Profile Normal Ranges | Request to ensure the 2728 Lipid Profile
Normal Ranges for the following lab values are correct: Total Cholesterol LDL Cholesterol HDL Cholesterol |
| Patient Information | RQMT_100 | Create Supplemental 2728 without an initial 2728 | Created new patient with chronic dialysis
start in December and subsequent "non-functioning" transplant
in January. Was only able to see/process/view the supplemental 2728 once the initial 2728 was completed. If the initial dialysis facility has not done their 2728 the Network cannot do the transplant supplemental 2728...additionally I'm concerned that we will not have accurate data on the supplemental because there is zero ability to edit/complete a supplemental. The supplemental 2728 comes up totally auto filled with data from the initial dialysis facility including the dates the physician and patient signed that first 2728. The supp 2728 does have the transplant surgeon name but the date is from the dialysis nephrologist signature date. Also, if the transplant surgeon/nephrologist does not concur with the patient's diagnosis, there is no way to enter a varying cause...not even in patient attributes. If the dialysis facility does not enter the 2728 within 30 days (the time for which they can view a patient that has left their facility)...how will they be given access to complete their 2728? Related Business Requirement / QC #: BR 4.9.5 Current Behavior: Supplemental cannot be edited or submitted until after the initial 2728 form is completed Expected Behavior: Supplemental cannot be edited or submitted until after the initial 2728 form is completed Steps to Re-Create: 1. Tested in CROWN QA, and supplemental 2728 is not available until after the patients initial 2728 is submitted and after the patient is admitted into the transplant facility. The supplemental form could not be edited. |
| Patient Information | RQMT_103 | Add warning about the "nonfunctioning" status of the graft | Request to add a warning when the user selects non functioning graft on the 2728 CMS Form. |
| Patient Information | RQMT_11 | 2728 - Print Name on 2nd Page Footer | Request for the CMS 2728 OMB forms to display Patient Name on the 2nd Page. |
| Patient Information | RQMT_138 | Non Versus Not for Hispanic or Latino | The entry for "Non-Hispanic or Latino" is incorrectly listed as "Not Hispanic or Latino" in the System correctly according to the CMS-2728 OMB Form. Request to update the requirement. |
| Patient Information | RQMT_147 | 2728 Validation Errors | Analyze the KDD element involved in the 2728 and remove unnecessary field level validations and ensure necessary validations are enforced by the system. |
| Patient Information | RQMT_149 | Co-Morbid Conditions. | Modify the documentation for the Co-Morbid Conditions to be associated with a checkbox beside each of the conditions and remove drop-down selection as the format of the field. |
| Patient Information | RQMT_150 | Co-Morbid = Institutionalized. | If Institutionalized (u) is selected as a
Co-Morbid Condition, then u1, u2 OR u3 must be checked. This
is not the system implementation. Modify documentation based
on the behavior of the system. System does not comply to requirements, however the decision was made to modify documentation to match how the System was implemented. |
| Patient Information | RQMT_151 | Current Medical Coverage Field | The field format "Current Medical Coverage is NOT a Drop-down box but a list of coverages with a corresponding checkbox beside each of the coverages. Modify the documentation to reflect this. |
| Patient Information | RQMT_152 | If patient NOT informed of transplant | The field format of "If patient NOT informed of transplant options, please check all that apply" is NOT a "Drop-down" box but a list of options with a corresponding checkbox beside each option. Modify the documenation to reflect UI implementation |
| Patient Information | RQMT_200 | Warning and Error Messages to display when Saving 2728. | Request for Warning and Error Messages to display when Saving 2728. |
| Patient Information | RQMT_221 | Add Functionality programmatically notify End User when a Patient requires a 2728 or 2746 Form | Add Functionality programmatically notify End User when a Patient requires a 2728 or 2746 Form. |
| Patient Information | RQMT_224 | Waiting periods assiciated with 2728 for re-entitlement | 2728 Form: Request to reduce the 36-month and 12-month waiting periods associated with the option to enter re-entitlement 2728 forms to accomodate when the SSA begins to notify of termination of benefits. |
| Patient Information | RQMT_226 | Patient Date of Birth Validation | Reasess the validations on the age range for patient DOB. |
| Patient Information | RQMT_245 | Request to add a “flag” in CROWNWeb to any CMS-2728 form which is in a "saved" status that a patient has not signed | As part of the “Data Access”
call this afternoon, it became apparent that we need to have
a way to “flag” in CROWNWeb any CMS-2728 form
which is in a ‘saved’ status because the patient
chooses not to sign the form. The concern is that these forms will continue to appear on Missing Forms report for the unit – which is a limitation of the current SIMS report . On the call, we felt that this check-off box would be made available to Network users (not facility users), where the Network would verify that the patient refuses to sign the form. We feel that this is a required component to CROWNWeb as we move forward to the production environment and we develop reporting solutions to handle our contractual and workflow needs. |
| Patient Information | RQMT_41 | CR-914 - Required clinical fields - 2728 Form | I was entering a new patient’s
information and received the following errors – which
is frustrating as I should be able to obtain the physician
signature prior to the patient starting in the chronic
facility - as was truly the case! Also our laboratory
reported the patient’s lipid panel but the range for
the validity will not accept the patient’s actual
value! Also when checking off that physical address was the
same as mailing - it REQUIRED to select the state again!
WHY? These are things I have encountered which I find frustrating and unable to complete and submit 2728 without changing?? Who determined the lipid range and why? COPY of ERROR reading: Minimum required fields are missing or invalid. Please review errors and/or warnings listed and make the necessary changes in order to continue. ! Date Regular Chronic Dialysis Began (24) cannot be after the Physician Signature Date (50). Date Patient Started Chronic Dialysis at Current Facility (25) cannot be after the Physician Signature Date (50). Edit and submit changes to the Admit Date on the admit/discharge page. ! Attending Physician Signature Date (50) cannot be prior to the Date Regular Chronic Dialysis Began [12/11/2008] (24). ! Attending Physician Signature Date (50) cannot be prior to the Date Patient Started Chronic Dialysis at Current Facility [12/11/2008] (25). Edit and submit changes to the Admit Date on the admit/discharge page. Warnings have been identified on this form. Please make any necessary changes to the Warning fields indicated. ! Total Cholesterol (19 e) is not in the valid range (100 - 240). ! LDL Cholesterol (19 e) is not in the valid range (100 - 190). ! HDL Cholesterol (19 e) is not in the valid range (35 - 60). |
| Patient Information | RQMT_6 | CR 906 - 2728 - HbA1c (19d) Lab date 45 days | Request for the system to be consistent with the 2728 Instructions where on the 2728: Field 19d: HbA1c lab date must be taken within 45 days prior to Date Regular Chronic Dialysis Began or the transplant date associated with the 2728. However, the instructions for the 2728 indicate that the HbA1c lab date must be within one year of the prior to the first dialysis treatment or kidney transplant. |
| Patient Information | RQMT_63 | HbA1c date timeframe incorrect | There is a mismatch between the 2728 hardcopy instructions and CROWNWeb 2728 instructions for "HbA1c Lab Date". The hardcopy says the date must be The date must be within 1 year prior to the first dialysis treatment or kidney transplant and CROWNWeb requirements say within 45 days prior to Date Regular Chronic Dialysis Began (KDDRQMT_239) or the transplant date associated with 2728. |
| Patient Information | RQMT_75 | CR-767 - ASHD abbreviation | Request to change the Co-Morbid condition ASHD abbreviation to arteriosclerotic heart disease rather than atherosclerotic heart disease as it is incorrect. |
| Patient Information | RQMT_76 | CR- 766 - Common Lab Date on 2728 | Request to add the Common Lab Date functionality in the Clinical Module to the 2728 functionality. |
| Patient Information | RQMT_77 | CR-764 - Required Fields on 2728 | Request the following fields be required with an asterick on the 2728: #24: Date Regular Chronic Dialysis Began (24) is mandatory#26: Has Patient Been Informed of Kidney Transplant Options (26). |
| Patient Information | RQMT_9 | CR 913 - 2728 Dry Weight | Request for the 2728 Dry Weight Field to be modified to accept decimal point. Currently, it is an integer. Per the CMS - 2728 Instructions, when entering weight in kilograms, round to the nearest kilogram. That being said, we cannot modify the Kg requirement. However, there is not mention of how lbs should be expressed in the instructions. |
| Patient Information | RQMT_37 | GFR Calculation | Request to modify the Glomerular Filtration Rate (GFR) Calculation to allow the end user to select from the original Modification of Diet in Renal Disease (MDRD) study equation or isotope dilution mass spectrometry (IDMS) traceable MDRD study equation. |
| Patient Information | RQMT_106 | add ‘transient’ to the Admit/Discharge summary information | Request to add a field to the Admit/Discharge Page for a patient's transient status. |
| Patient Information | RQMT_116 | Exclude "Recovered Function" as a Discharge Reason for specific Admit Reasons | When a patient's Admit Reason is = 'Dialysis
After Transplant Fails' OR 'Dialysis in Support of a
Transplant' the Discharge Reason choice of 'Recovered
Function' should not be persmissible. |
| Patient Information | RQMT_127 | Reason Table (Admit/Discharge) | Reason Table (Admit/Discharge) requires research to determine if the documentation or the system is correct. |
| Patient Information | RQMT_158 | Reporting Patient Death after Patient Discontinues Therapy | Reporting Patient Death after Patient Discontinues Therapy is addressed incorrectly in CROWNWeb. The DOD Field is tied to the last discharge field which causes errors when submitting the 2746 with the appropriate date of death. |
| Patient Information | RQMT_167 | Interuption in Service | Request from user as to whether the facilities should get data from acute facilities when their patients who have an interuption in service due to hospitalization or otherwise. |
| Patient Information | RQMT_180 | Augment Near Match Criteria | Request an additional near-match
functionality that would render a near match when: a. A patient's SSN is not null, and it is an exact match to another patient in CROWNWeb. b. A patient's HICNUM is not null, and is an exact match to another patient in CROWNWeb. |
| Patient Information | RQMT_185 | Transplant Treatment Type = Deceased Old CR_420 | The Admit/Discharge and Treatment Record for a patient who received a deceased donor Transplant display is confusing. It appears the Patient died and when a patient does die, it displays as though they died twice.(2/14/2008) |
| Patient Information | RQMT_21 | Change order of Name in Data entry | Request to switch the order of the patient's name on the Admission UI to Last Name, First Name. |
| Patient Information | RQMT_40 | CR-586 - Autopopulating fields entered during a patient search | Request to auto-populate patient data with Search entry when creating a new patient record. |
| Patient Information | RQMT_8 | CR 912 - Admit / Discharge Transient Patients | Request to clarify Transient patient in the Gap Area of the Patient Module as Transient Patients are displayed. However, this is an undocumented feature. Therefore, if it is the intent of the GAP to report on Transients, then the BR should be modified. If it is not the intent, then a system change will be required. |
| Patient Information | RQMT_96 | CR-323 - NW # on Admit Record | Request to add the Network # on the Admit/Discharge Summary Page. |
| Patient Information | RQMT_43 | CR-912 - GAP Patients | To Whom it may concern / FMQAI, The following issue has been reported to the CROWN Help Desk: I have a correctly admitted and discharged transient patient that is now showing in the Gap patient report for my Phase 1 facility 382510.Transients shouldn’t show on the gap report because the individual isn’t discharged from their home unit. Isn’t this correct. XXXXXXXXXX Through researching this issue, Per Business Requirement 5.5.11 as provided by FMQAI: The System shall provide the ability for Network users to identify patients that are not currently being treated by a facility (patients that have been discharged from all facilities but are not deceased). (Gap Patients) There is no mention of permanent vs. transient patients. When replying to this email, please include the following thread id (entire line) within the body of your response to expedite routing to the correct office. [THREAD ID:1-50TJC] |
| Patient Information | RQMT_118 | Add second Patient last name field | Request to add a second Patient last name field globally in the system to accomodate hyphenated last names. |
| Patient Information | RQMT_120 | Patient Unique ID be placed in the XSD | Request to add CROWNWeb Patient Unique ID to the BATCH XSD Schema. |
| Patient Information | RQMT_14 | Deceased Patient Record Retention/Archive | Request to determine if this CR should be
moved to future SOPs. Proposed Business Process Rules: 1. The System shall provide a mechanism to maintain all patient data relevant to treatment and clinical information for a period of time no less than one month and 6 years after a patient is discharged with a reason of death. 2. The System shall provide a mechanism to maintain all patient data relevant to treatment and clinical information shall be archived for a period of 4 years after the patient’s data has exceeded the mandatory six year active record status in the CROWNWeb system. |
| Patient Information | RQMT_142 | Plus 4 Zip Code Field | Add a field level validation to KDDRQMT_127 that the field lengh is required to be 4 numeric character field. |
| Patient Information | RQMT_145 | Patient Zip Code (2728) | The Display Name of "Zip Code" is designated as a "Blank" field. The field is labeled as "Zip:" Change Documentation to match label. |
| Patient Information | RQMT_155 | Primary Cause of Renal Failure | Primary Cause of Renal Failure text size restriction to be removed on this field. |
| Patient Information | RQMT_243 | Adjust Field #36 on 2728 form to pre-populate the date given in Field #24 | Request to have field #36 (If Non-Functioning, Date of Return to Regular Dialysis) on a Re-Entitlement 2728 form for return to dialysis after transplant failed pre-populate with the value equal to field #24(Date Regular Chronic Dialysis Began). |
| Patient Information | RQMT_244 | Date on printed 2728/2746 Forms | Change the footer at the bottom a printed
submitted 2728/2746 form to show the date the form was
submitted instead of the date the form was printed. The current footer text states “As of xx/xx/xxxx (which is the printed date), this form is in a Submitted status.” |
| Patient Information | RQMT_246 | Network's ability to view GAP patients that are not currently in a facility | If Network's are only able to view only their patients, it occurred that this could affect "Gap" patients and how they are handled. If they aren't in any facility, they may not be viewable by any Network personnel depending on how scope is handled. This could cause patients to be "lost" in the sytem. |
| Patient Information | RQMT_107 | Merging Patients Process | Request for a programatic patient Merge and Unmerge Process in the System. |
| Patient Information | RQMT_89 | CR-656 - Patient Search Enhancement | Request to add Admit and Discharge Dates to the Patient Search funtionality. |
| Patient Information | RQMT_91 | CR-598 - Facility Sort Order upon Search | Request to add the following sort criteria to the Facility Sort: Open or Closed or All and to have theset fields added to all dropdowns involving facilities. |
| Patient Information | RQMT_92 | CR-541 - Default Hours and Minutes | Request to add the ability to default the Facility's hours of operation in hours and minutes. |
| Patient Information | RQMT_93 | CR-465 - 2728 Form: Patient Idenfier on Each Page | When you print out the 2728, there is no
patient identifier on page 2. In vision, the patient’s
name is in the upper right corner. When I enter a number of
2728’s, it is possible for them to get mixed on my desk
and trying to put page 1 with page 2 can lead to
errors. |
| Patient Information | RQMT_94 | CR-329 - Transplant Facilities | Request to suppress certified number of stations, isolations stations and open times when a facility is a transplant facility. |
| Patient Information | RQMT_228 | Make treatment uneditable after associated with 2746 and/or 2728 | Enhancement request to prevent personnel entries from being edited or deleted in CROWNWeb after the personnel record has been associated with a submitted treatment, 2728 and/or 2746. |
| Reports | RQMT_209 | Facility Search Feature for Faciliites on Reports | Request for a search mechanism for Facilities instead of making the user scroll through a long list a facilities to find the one they are looking for. |
| Reports | RQMT_211 | Clinical Search Report | Request for a report that mirrors the CLinical Search feature. |
| Reports | RQMT_137 | All Audit Reports: Group versus Sort by | All Audit Reports: Group versus Sort by has raised a semantic issue that RCT will address in the next version of the requirements. |
| Reports | RQMT_154 | Audit Report Redesign | RCT will analyze and redesign Audit reports and modify requirements. |
| Reports | RQMT_162 | Audit Report for Saved 2746 and 2728 OMB Forms | Request to add an Audit Report for Saved OMB Forms (2728 & 2746). |
| Reports | RQMT_184 | Audit Reports: Add Time of Modification | Request for a field that indicates the time an action was modified to the report. |
| Reports | RQMT_44 | CR-911 - Reports | I realize this has been discussed many times and many documents have been submitted about CROWNWeb reporting. However, I believe one of the biggest challenges encountered in determining how well Phase I of CROWNWeb is working is the inefficiency of the reporting in CROWNWeb for data validation. In the early phases of CROWNWeb, Networks need access to quality reports. While they are helpful in many aspects – for instance the ability to see who has updated, deleted, or added information and the date of change is very useful, some of the reports are lacking data or have too much data for proper validation. I am including a list of suggestions for the current reports, along with some basic reports I believe would be helpful for data validation in the future. The Audit Forms Report: The audit forms report needs to have an accurate report of forms Submitted. Right now it is counting forms saved/changed as Total forms submitted. Either the heading needs to be changed to “2728s saved or changed” (or whatever this is counting), or the report needs to be expanded to give a true count of forms that have been saved; forms that have been edited; and forms that have been successfully submitted Facility Roster Report: The facility roster report is okay, however it tracks not only who was at a facility but also who left during the date range specified. It would be helpful to have some counts included on this report including the Number of patients on the report along with the Number of discharges on the report. That way a Network/Facility could do the math without having to go through the entire report. Reports not in CROWNWeb that are important Validation Tools for both Networks and Facilities • Admit/Discharge Report that can be filtered by date range: It is cumbersome for Networks and facilities to click on each patient or do a facility-wide patient search to see if an event has been added for their facility. I realize there are both Audit Updates reports and Audit Additions reports that can be run to show what has been added and when. However, this is not effective for a facility and Network to see what a facility reported for a time period. Ex. a facility/Network wants to see quickly in a report who was added and removed for a facility in CROWNWeb for February. They want to enter a date range and pull up this list. The Audit Additions and Audit Update Report would not work because they ask for a date range to see when an admit/discharge was entered, not when it occurred. So if the report date range is February 1 to Feb 28 but the event which took place in February was entered in March, they would not show up on the Audit Additions or Audit Update report. To include this update, you would have to expand the date range to see all Audits and Additions from chosen date to present date which makes an already convoluted report even more difficult to decipher. • Missing Forms Report: Report of 2728 and 2746 forms that the facility needs to submit that have not been submitted or started. It is time consuming for a facility to look up each patient they suspect they have not done a form on. • Missing Clinical Data Report: 1. A simple report that is just a print out that tells who is missing data for a particular month (All patients or by HD/PD/Vasc. Access – similar to search screen). A more detailed report could list actual labs that are missing or could be similar to the search screens). 2. A report that can generate a list like what comes up on patient search: Selection criteria can be Clinical Month; Collection Type and Measure. This would be helpful for facilities that are looking to see what information might be missing (marked by the exclamation point as in CROWNWeb search) – a hardcopy printout the facility staff could take to a patient chart or another computer to gather data. It would also be helpful for Network verification when QIDs are looking at clinical lab data. They would have a hardcopy report where they could make notes for later follow up with the facility, circle/highlight outliers, etc. Report 1 ex. Facility A – Clinical Month January 2009; Collection Type/ Measure HD Anemia Management Patient DOB ESA Rx IV Iron Hgb (g/dl) Ferritin (ng/ml) TSAT (%) ChR (pg) Bob CPM 01/01/1901 Yes No 10.0 60 ! ! Jane CPM 01/01/1921 No No Missing! 500 ! ! Report 2 ex. Facility A – Clinical Month January 2009; Collection Type; Measure HD Adequecy Patient DOB Kt/V (Kt/V Method) Serum Creatinine (mg/dl) Pre Dialysis Weight Post Dialysis Weight BUN Pre Dialysis (mg/dl) BUN Post Dialysis (mg/dL) Mins BUN per Session Sessions Per Week Bob CPM 01/01/1901 1.60 (UKM) 5.6 70 kg 68 kg ! ! ! ! Jane CPM 01/01/1921 1.72 (UKM) 6.8 Missing! ! 60 20 220 3 Note – since the CPM reports aren’t available yet, I’m not sure what those look like so I don’t know if any of this would be similar to that report. |
| Reports | RQMT_7 | CR 911 - Report Deficiencies | Request to address the following Report
Deficiencies: Audit Forms Reports: Display too much extraneous information and not enough useful data. Patient Roster Report does not capture the following necessary data: Patient discharged with a count of the number of patient discharged. Requested Reports: Admit/Discharge Report Missing Forms Report Missing Clinical Data Report |
| Reports | RQMT_134 | Audit Update Report Labeling | The field "Date change was submitted" is
labeled incorrectly as "Change Date" on the Audit Updates
Report. Label is not in compliance with the
requirement. |
| Reports | RQMT_16 | Add Data to Audit Report for Updates | Audit Report for Updates: request to add Personnel Name to the the report. |
| Reports | RQMT_17 | Add Filtering to Audit Report for Updates | Request to add an the ability to sort the data by more than 1 option at a time i.e. multiple sorting, to the Audit Report for Updates. |
| Reports | RQMT_159 | Laboratory KDD elements with no definitions | There are several KDD elements that have never been defined in the KDD. |
| Reports | RQMT_39 | Changes to the FFBI reporting | The purpose of this CR is to provide the
data elements and supporting documentation necessary to
collect and produce the Fistula First Breakthrough Initiative
(FFBI) reports currently in CROWNWeb for evaluation by CMS to
improve the existing FFBI reports. FMQAI has created a Change
Request number CRRQMT_39 which will be used as the reference
number for all work associated with modifications to the FFBI
Reporting in CROWNWeb through the life cycle of this
project. |
| Reports | RQMT_55 | CR-900 - Fistula First Consistency | BR 14 FF Report was not consistent. CVC and Catheter were used and "in use" was not used consistently. |
| Reports | RQMT_195 | Add PAR Report in CROWNWeb | Request for a report in CROWNWeb based on event dates that mimics the monthly PAR. |
| Reports | RQMT_241 | Retain facility's identifying information in the ESRD CPM Summary results | The user requests that if a facility has not entered data for the given month, that the report still contain the basic identifying information for the facility such as the Name, CCN, and NPI, even though the rest of the month will remain blank. |
| Reports | RQMT_242 | Add warning message for patient signatures on 2728 | Add a warning message that displays when a
user attempts to submit a 2728 with a patient signature date
on or after the date of death for a patient that has
expired. The CROWN Help Desk has replicated this issue and concurs that CROWNWeb does allow you to submit both 2728 and 2746 forms on the same date. According to the requirements with the patient signature on the 2728, if the patient is deceased, then the signature is not required. |
| Reports | RQMT_124 | CPM III Adequacy of Dialiysis | The LDOs have requested that CMS reconsider including only patients who dialysis thrice weekly for CPMIII: Minimum Delivered Dose for ESRD HD Patients. |
| Reports | RQMT_98 | CR-312 - Enhanced Sort Criteria | On the Facility Personnel Report Page I am
having trouble searching for multiple facilities. For
instance, if I want a report on all AZ facilities I should be
able to enter "03" in the search bar, expand the options and
select either "starts with any. . . " or (more likely)
"starts with the first. . . " to find all of my AZ units.
Neither choice brings back any results. How would I go about creating a directory of all of my AZ units, or all NW 15 units? The only way I can think of doing it the way the system is set up is to search for one at a time and them print. |
| Reports | RQMT_163 | Reports: Criteria For Facility should be CCN and/or Facility Legal Name | Reports: Criteria For Facility should be CCN and/or Facility Legal Name instead of the Facility DBA Name. This is necessary because the Facilities can change their DBA Name but not the CCN or the Facility Legal Name, so there would be no confusion for the Networks or CMS if they want to execute reports. |
| Reports | RQMT_235 | Patient Events Report | Add a Patient Events Report to
CROWNWeb. Business Need (comments): A Network has requested the ability to run reports within CROWNWeb which will display results similar to the “Patient Events Report” in SIMS. CROWNWeb currently does not have a report which will display all of the 2746s, 2728s, Transfer in, Transfer out and transplant events. |
| Reports | RQMT_72 | CRD-853 - Report Enhancements | Patient History information – The
business need is to be able to run point prevalent reports,
annual report, disaster planning. Annual report tables in
SIMS key off the state as of a point in time. Zip Code history issue: Maintaining history on patients will be accomplished by using the audit tables; history of zip code will not be tracked without additional requirements and programming; zip code tracking for point-prevalent reports needs to be addressed, but this will not be a part of release 1.0. In the audit reports we are showing the difference made between the different fields. In order to store additional history we will need to have additional requirements to say as of what does this store, what fields are kept. |
| Reports | RQMT_135 | Other versus Unknown for Primary Type of Treatment. | In the Treatment Details of the Patient
Roster Report, the Primary Type of Treatment displays as
"DIALYSIS" for every patient, regardless if they are
receiving Hemodialysis, CAPD, CCPD or Other treatment. CMS
determined this would be a future change to provide clarity
on the Patient Roster report. |
| Reports | RQMT_157 | Patient Roster Report: Alert for No Primary Diagnosis Modification | In the Alert Column for the Patient Roster Report, the label is incorrect. Label on Report will change from "No Primary Diag" to "No Primary Dx". |
| Reports | RQMT_95 | Patient Roster Report: Patient's Treatment Location | Request to display the patient's treatment location on the Patient Roster Report. |
| Reports | RQMT_97 | CR-314 - Add CCN to Sort Criteria | Request to add the CCN number on the Patient Roster Report - Criteria Selection page. |