Transcript INITIATIVES TO IMPROVE ACCURACY OF MDS DATA

INITIATIVES TO IMPROVE
ACCURACY OF MDS DATA
• Enhanced edits and rejections
• New mechanism to correct
errors in the MDS database
ENHANCED EDITS WILL
REJECT RECORDS WITH:
• Out of Range
Values
• Certain
Inconsistencies
• Impossible Date
Relationships
NEW MECHANISM TO CORRECT
ERRORS IN THE MDS DATABASE
• Inactivation of spurious records
• Modification of errors in records
NEW CORRECTION
REQUEST FORM
• Identify a record in error
• Identify reason for error
• Specify request for Modification
or Inactivation
• Correction sequence number
• Attest to accuracy of correction
NEED TO CORRECT RECORDS IN
DATABASE SHOULD BE RARE
• The need for corrections should
decrease as a result of stricter
edits and enhanced rejections
• Fewer records with
errors will be
accepted by the
database
Records will be rejected for errors that
were not in fatal in the past
• Facilities
should pay
close
attention to
Final
Feedback
Reports
• The facility submission
schedule should allow for timely
correction and resubmission of
rejected records
2 MAIN COMPONENTS OF
CORRECTION REQUEST FORM
• Prior Record Section
• Correction Attestation
Section
PRIOR RECORD SECTION
Identifies the erroneous
record so that it can be
located in the State
database
ATTESTATION SECTION
• Sequence number of the correction
request
• Modify vs. Inactivate
• Reason correction is needed
• Attestation
• The correction request
form does NOT include
identification of specific
items in error
DOCUMENTATION
REQUIREMENTS
• Retain signed, hard
copy of Correction
Request Form
• Retain copy of
corrected MDS form
• Documentation
substantiating
accuracy of
corrected
information on the
INACTIVATION
• Record should not have been submitted
• Facility submits Correction Request
Form, requesting inactivation
• State “inactivates” but does not delete
• Inactivated record not used in system
applications, but remains in history file
MODIFICATION
• Record in the database has error(s)
• Facility submits Correction Request
Form requesting “modification” AND
a corrected copy of the record
• State “replaces” erroneous record in the
database with it’s corrected version
AND
• Stores erroneous version in history file