Date | Milestone (M) / Task (T) | Description | Phase | Status |
---|---|---|---|---|
2/28/2021 | M | Code deployed to pre-prod for testing. | 1 | Complete |
3/15/2021 - 3/24/2021 | T | EDIs perform integration testing. | 1 | Complete |
3/24/2021 | M | EDIs sign-off on integration testing. | 1 | Complete |
3/24/2021 - 3/25/2021 | T | ADO prepares for coding deployment. | 1 | Complete |
3/25/2021 | M | Production deployment. | 1 | Complete |
3/31/2021 | M | Prod-Preview environment contains refreshed prod data | 2 | Complete |
2/24/2021 - 3/10/2021 | T | Review of phase 2 codes and finalize list of codes. | 2 | Complete |
3/11/2021 - 4/30/2021 | T | ADO perform coding updates and regression testing - Phase 2 (Patient Codes) | 2 | Complete |
4/30/2021 | M | Prod-Preview environment data refresh. | 2 | Complete |
5/3/2021 | M | Remaining Phase 2 (Patient Codes) deployed to pre-prod for testing. | 2 | Complete |
5/4/2021 - 6/1/2021 | T | EDIs performs integration testing - Phase 2 (Patient Codes) | 2 | Complete |
6/2/2021 | M | EDIs sign off-on integration testing - Phase 2 (Patient Codes) | 2 | Complete |
6/2/2021 - 6/4/2021 | T | ADO prepares for coding deployment - Phase 2 (Patient Codes) | 2 | Complete |
6/3/2021 | M | Production deployment - Phase 2 (Patient Codes) | 2 | Complete |
6/4/2021 | M | Phase 2 (Patient Codes) live in production. | 2 | Complete |
3/10/2021 - 3/17/2021 | T | Review of phase 3 codes and finalize list of codes. | 3 | Complete |
5/12/2021 - 06/08/2021 | T | ADO perform coding updates and regression testing - Phase 3 Clinical Codes/2728 | 3 | Complete |
6/4/2021 | M | Prod-Preview environment data refresh. | Complete | |
6/4/2021 - 6/6/2021 | T | EDIs SHOULD NOT submit any PATIENT files during this time period in production (to ensure same patients are in PP2-3). | 3 | Complete |
6/7/2021 | T | EDIs to drop file into PP2-3 to establish a baseline. | 3 | Complete |
6/8/2021 | M | Code deployed to pre-prod for testing - Phase 3 (Clinical Codes/2728). Reopening September 2020 to March 2021 Clinical months for submission. | 3 | Complete |
6/9/2021 - 7/6/2021 | T | EDIs performs integration testing. Starting 6/9 - Re-drop same file from 6/7/2021 into PP2-3. Review feedback files from PP2-3 and validate codes. | 3 | Complete |
7/6/2021 | M | EDIs sign-off on integration testing - Phase 3 (Clinical Codes/2728). | 3 | Complete |
7/7/2021 - 7/11/2021 | T | ADO prepares for coding deployment - Phase 3 (Clinical Codes/2728). | 3 | Complete |
7/12/2021 | M | Phase 3 (Clinical Codes/2728) live in production. | 3 | Complete |
7/12/2021 | M | EDSM Implementation Complete (Phase 1 - 3). | n/a | Complete |
7/12/2021 - 9/15/2021 | T | Resubmission of Clinical Data Files (September to December). Open July 12, 2021 at 5 a.m. Pacific (8 a.m. Eastern) and close September 15, 2021 at 11:59 p.m. Pacific Daylight Time 9/15/2021 is the official closure date for the clinical months of September, October, November, and December 2020. CMS highly recommends completing large data submissions prior to the official clinical closure date. | n/a | Complete |
9/15/2021 | M | Data fully submitted and ready for measure and scoring calculations. | n/a | Complete |
09/20/2021 - 02/28/2022 | T | Submit January-September 2021 EQRS Clinical Data, ICH CAHPS Attestations, and Clinical Depression Screening and Follow-Up Plan reporting in EQRS. Additionally, all subsequent months in 2021 will open for data submission on the first day of each month (i.e., October opens October 1; November opens November 1; and December opens December 1). | n/a | |
02/28/2022 | M | The clinical closure date for all months in 2021 is February 28, 2022 at 11:59 PM PT. | n/a |
Data Submission (Errors & Warnings) Milestone Dates - By Phase
Phase No. | File Type | Code Bucket Name | Codes | ADO Completion Date | LDO Testing Start Date | Testing Completion Date | Production Date |
---|---|---|---|---|---|---|---|
1 | Patient | 11221, 11222, 11223, 11224, 11225 | 2/24/2021 | 3/1/2021 | 3/24/2021 | 3/25/2021 | |
2 | Patient | 5/3/2021 | 5/4/2021 | 6/1/2021 | 6/7/2021 | ||
3 | Clinical | 6/8/2021 | 6/9/2021 | 7/6/2021 | 7/12/2021 | ||
3 | 2728 | 6/8/2021 | 6/9/2021 | 7/6/2021 | 7/12/2021 |
Phase 1 - Admit Reason Codes
Admit Reason Codes
The following codes will be turned on as error validation codes:
Error ID | Error Description | Error/Warning | JIRA Ticket | EDSM | UI | Comments |
---|---|---|---|---|---|---|
11221 | Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the next admission record's Admit Reason ({0}). | Error | EQP-34463 | Error | Error | |
11222 | Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the previous admission record's Admit Reason ({0}). | Error | EQP-34463 | Error | Error | |
11223 | Invalid Admit Reason for a dialysis facility admission. | Error | EQP-34463 | Error | Error | Already turned on in production. |
11224 | Invalid Admit Reason for a transplant facility admission. | Error | EQP-34463 | Error | Error | Already turned on in production. |
11225 | Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the previous admission record's Discharge Reason ({0}). | Error | EQP-34463 | Error | Error |
Patient Admit Discharge Reason Rules
The following are the admit discharge reason logic combination that are allowed or not allowed. These scenarios should be part of use case testing.
Discharge Reasons Rules Codes =
Discharge Reasons A=Allow N=Not Allow S=System Generated | ||||||||||||
Admission Record Admit Reason | Acute | Death | Discontinue | Lost to Follow Up | Recover Function | Involuntary | Other | Transplant In US | Transplant Outside US | Transfer | Transplant Failed | System Discharge |
---|---|---|---|---|---|---|---|---|---|---|---|---|
New ESRD Patient (Dialysis) | A | A | A | A | A | A | A | A | A | A | N | S |
New ESRD Patient (Transplant) | N | A | N | A | N | N | N | A | A | N | A | S |
Transfer In | N | A | A | A | A | A | A | A | A | A | N | S |
Restart | N | A | A | A | A | A | A | A | A | A | N | S |
Dialysis After Transplant Failed | N | A | A | A | A | A | A | A | A | A | N | S |
Dialysis in Support of Transplant | N | A | N | A | A | A | A | A | A | A | N | S |
Transplant | N | A | N | A | N | N | N | A | A | N | A | S |
Previous Discharge - Next Admit Allowed = 11225
Admission Reasons A=Allow N=Not Allow | |||||||
---|---|---|---|---|---|---|---|
Previous Admission Record Discharge Reason | New ESRD Patient (Dialysis) | New ESRD Patient (Transplant) | Transfer In | Restart | Dialysis After Transplant Failed | Dialysis in Support of Transplant | Transplant |
Acute | A | A | N | N | N | N | N |
Death | N | N | N | N | N | N | N |
Discontinue | N | N | N | A | N | N | A |
Lost to Follow Up | N | N | A | A | A | A | A |
Recover Function | N | N | N | A | N | N | A |
Involuntary | N | N | A | N | N | N | A |
Other | N | N | A | A | N | N | A |
Transplant in US | N | N | N | N | A | A | A |
Transplant Outside US | N | N | N | N | A | A | A |
Transfer | N | N | A | N | N | N | N |
Transplant Failed | N | N | N | N | A | N | A |
System Discharge | N | N | A | A | A | A | A |
Previous Admit - Next Admit Allowed - 11221 / 11222
Next Admission Record Admission Reasons A=Allow N=Not Allow | |||||||
---|---|---|---|---|---|---|---|
Previous Admission Record Admit Reason | New ESRD Patient (Dialysis) | New ESRD Patient (Transplant) | Transfer In | Restart | Dialysis After Transplant Failed | Dialysis in Support of Transplant | Transplant |
New ESRD Patient (Dialysis) | N | N | A | A | N | N | A |
New ESRD Patient (Transplant) | N | N | N | N | A | A | A |
Transfer In | N | N | A | A | N | N | A |
Restart | N | N | A | A | N | N | A |
Dialysis After Transplant Failed | N | N | A | A | N | N | A |
Dialysis in Support of Transplant | N | N | N | N | A | A | A |
Transplant | N | N | N | N | A | A | A |
Note: This table is used to validate an admission's Admit Reason in 2 instances: | ||||||||
1. When adding an admission that occurs prior to an existing admission (based on Admit Date) with the same Transient Status. | ||||||||
2. When adding an admission that occurs after an existing admission (based on Admit Date) with the same Transient Status and the previous admission does not have Discharge Information. |