Page History

• Introduce Arnie Espartero

Phase 2 Testing Timeline

• 4/30 - Refresh PP2-3 
• Davita can drop their test file in PP2-3 on Monday 5/3.
• ADO will wait for confirmation from Davita before deploying remaining Phase 2 codes.
• 5/3 - Phase 2 Code deployment to PP2-3 early afternoon.
• 5/4 to 6/1 - EDIs perform Phase 2 (Patient Codes) testing.
• 6/2 - EDI Sign off on testing.
• 6/7 - Production deployment.

• Codes highlighted in blue on this page have been deployed to PP2-3 by Mantech.

The codes below will be reverted to errors:

• 13359 - Admission Records created prior to {0} cannot be modified via Batch. Changes to the Admission Data were not processed. Please use the SUI to make any necessary updates.
• 13360 - Admission Records created prior to {0} cannot be modified via Batch. Changes to the Admission Data were not processed. Please use the SUI to make any necessary updates.
• 13561 - Treatment Information on records created prior to {0} cannot be modified via Batch. Changes to the Treatment Information were not processed. Please use the SUI to make any necessary updates.
  
  
• Records submitted via batch where the create date is prior to 5/4/2005, will be rejected and trigger an error message.
• This is to avoid batch files having the ability to update SIMs records.  However, they are able to update via the UI.

Feedback from EDIs

• CROWNWeb used to ignore the date, but accepted the data.  
• EDIs would stress the importance that EDSM and UI function in same way.
• 13561 - For FMC:  70K records triggering warnings in production:
  
  • Admission Records created prior to {0} cannot be modified via Batch. Changes to the Admission Data were not processed. Please use the SUI to make any necessary updates.    Error    13559    Warning    42776
  • Treatment Information on records created prior to {0} cannot be modified via Batch. Changes to the Treatment Information were not processed. Please use the SUI to make any necessary updates.    Error    13561    Warning    72459

• In progress.  Michael is currently working with individual EDIs:  FMC, NRAA, all 18 NW.
• Focused on patient prevalence, admits, discharges, duplicate Medicare status, dupe new to ESRD, dupe patients, secondary merge UPI.
• Working thru Vlad's spreadsheet of approvals.

Error Code 11251 - 

Attending Practitioner is required.

• FMC tested error code 11251 with Michael Kennedy.  
• Slated to be turned on as an error.  Request for reconsideration to make a warning; not an error since there are issues when sending data related to older treatment records.
• During testing - flagged 13,000 records that did not belong to FMC since the attending practitioner on older treatments does not contain a value.
• Currently in EQRS - Not turned on (not as warning or error).  In CROWNWeb, this was a warning.
• Davita posed questions - Leave as an error and review volume during testing phase?
• ADO would not be able change to a warning from an error in time for Phase 2 May 4 testing date.  Would need to know by 5/12 on final decision since there is work needed to change the coding logic.
• CMS will regroup internally to determine next steps.
• Legacy data - CMS decision 5/24/2012 to leave SIMS data untouched in CROWNWeb.  If the code is looking at a create date prior to 1/1/2006, then this could cause additional errors to be triggered since it's looking at even older data than what CW originally took into consideration (5/24/2012.

• FMC to provide feedback on 2728 Codes for Phase 3.