You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


DateMilestone (M) / Task (T)DescriptionPhaseStatus
2/28/2021MCode deployed to pre-prod for testing.1Complete
3/15/2021 - 3/24/2021TEDIs perform integration testing.1Complete

3/24/2021

MEDIs sign-off on integration testing.1Complete

3/24/2021 - 3/25/2021

TADO prepares for coding deployment.1Complete

3/25/2021

MProduction deployment.1Complete
3/31/2021MProd-Preview environment contains refreshed prod data 2Complete
2/24/2021 - 3/10/2021 TReview of phase 2 codes and finalize list of codes.  Complete
3/11/2021 - 4/30/2021TADO perform coding updates and regression testing - Phase 2 (Patient Codes) 2Complete

4/30/2021

MProd-Preview environment data refresh.2Complete

5/3/2021

MRemaining Phase 2 (Patient Codes) deployed to pre-prod for testing.2Complete

5/4/2021 - 6/1/2021

T

EDIs performs integration testing - Phase 2 (Patient Codes) 
Starting 5/4 - EDIs submit prod file in prod environment and PP2-3.  This should be the SAME file for both environments.  Review discrepancies between the feedback files and validate codes.

2Complete

6/2/2021

MEDIs sign off-on integration testing - Phase 2 (Patient Codes) 2Complete

6/2/2021 - 6/4/2021

TADO prepares for coding deployment - Phase 2 (Patient Codes) 2Complete

6/3/2021

MProduction deployment - Phase 2 (Patient Codes) 2Complete
6/4/2021MPhase 2 (Patient Codes) live in production.2Complete
3/10/2021 - 3/17/2021TReview of phase 3 codes and finalize list of codes.  3Complete
5/12/2021 - 06/08/2021TADO perform coding updates and regression testing - Phase 3 Clinical Codes/27283Complete

6/4/2021

MProd-Preview environment data refresh.
Complete
6/4/2021 - 6/6/2021T

EDIs SHOULD NOT submit any PATIENT files during this time period in production (to ensure same patients are in PP2-3).

3Complete
6/7/2021T

EDIs to drop file into PP2-3 to establish a baseline.

3Complete

6/8/2021

MCode deployed to pre-prod for testing - Phase 3 (Clinical Codes/2728).
Reopening September 2020 to March 2021 Clinical months for submission.
3Complete

6/9/2021 - 7/6/2021

TEDIs 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.

3Complete

7/6/2021

MEDIs sign-off on integration testing - Phase 3 (Clinical Codes/2728).3

Complete

7/7/2021 - 7/11/2021

TADO prepares for coding deployment - Phase 3 (Clinical Codes/2728).3Complete
7/12/2021MPhase 3 (Clinical Codes/2728) live in production.3Complete

7/12/2021

MEDSM Implementation Complete (Phase 1 - 3).n/aComplete

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/aComplete
09/20/2021 - 02/28/2022T

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/2022MThe 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

Admit Reasons

11221, 11222, 11223, 11224, 11225

2/24/2021

3/1/2021

3/24/2021

3/25/2021

2

Patient

Patient Codes


5/3/2021

5/4/2021

6/1/2021

6/7/2021

3

Clinical

Clinical Codes


6/8/2021

6/9/2021

7/6/2021

7/12/2021

3

2728

2728 Codes


6/8/2021

6/9/2021

7/6/2021

7/12/2021

Phase 1 - Admit Reason Codes

Unable to render {include} The included page could not be found.


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}).

ErrorEQP-34463ErrorError

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}).

ErrorEQP-34463ErrorError

11223

Invalid Admit Reason for a dialysis facility admission.

ErrorEQP-34463ErrorErrorAlready turned on in production.

11224

Invalid Admit Reason for a transplant facility admission.

ErrorEQP-34463ErrorErrorAlready 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}).

ErrorEQP-34463ErrorError


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 ReasonAcuteDeathDiscontinueLost to Follow UpRecover FunctionInvoluntaryOtherTransplant In USTransplant Outside USTransferTransplant FailedSystem Discharge
New ESRD Patient (Dialysis)AAAAAAAAAANS
New ESRD Patient (Transplant)NANANNNAANAS
Transfer InNAAAAAAAAANS
RestartNAAAAAAAAANS
Dialysis After Transplant FailedNAAAAAAAAANS
Dialysis in Support of TransplantNANAAAAAAANS
TransplantNANANNNAANAS

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 InRestartDialysis After Transplant FailedDialysis in Support of TransplantTransplant
AcuteAANNNNN
DeathNNNNNNN
DiscontinueNNNANNA
Lost to Follow UpNNAAAAA
Recover FunctionNNNANNA
InvoluntaryNNANNNA
OtherNNAANNA
Transplant in USNNNNAAA
Transplant Outside USNNNNAAA
TransferNNANNNN
Transplant FailedNNNNANA
System DischargeNNAAAAA

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 InRestartDialysis After Transplant FailedDialysis in Support of TransplantTransplant
New ESRD Patient (Dialysis)NNAANNA
New ESRD Patient (Transplant)NNNNAAA
Transfer InNNAANNA
RestartNNAANNA
Dialysis After Transplant FailedNNAANNA
Dialysis in Support of TransplantNNNNAAA
TransplantNNNNAAA


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.


  • No labels