Informatika | Információelmélet » OASIS duplicate assessment

OASIS Duplicate Assessment The OASIS State System determines that a duplicate record exists if all of the following fields match: HHA System’s Duplicate Assessment Criteria: Duplicate record if all of the following fields match: 1. 2. 3. 4. 5. Header: HHA AGENCY ID (Byte 28 - 43) M0100 Reason for Assessment (Byte 310 – 311) Effective Date Correction Number (Byte 13 – 14) Resident Match on the basis of: M0040 PAT LNAME; M0040 PAT FNAME; M0069 PAT GENDER; M0066 PAT BIRTH DT; AND M0064 SSN HAVEN Duplicate Assessment Criteria • • • • • • M0010 Agency (Provider) ID Number (Byte 124 – 129) (Agency Database) M0020 Patient ID Number (Byte 157 – 176) (Patient Database) M0100 Reason for Assessment (Byte 310 – 311) M0030 START CARE DT (Byte 177 – 184) Effective date Correction Number (Byte 13 – 14) The Patient information for each assessment in the import file is matched against the data in the existing patient database. The software makes the following

comparisons: • • • • Patient ID Number First Name, Last Name, Date of Birth, Gender Medicare Number Medicaid Number Effective Date: 1. Start of care – Further visits planned 2. Start of care – No further visits planned 3. Resumption of care (after inpatient stay) 4. Recertification (follow-up) reassessment 5. Other follow-up 6. Transferred to an inpatient facility – patient not discharged from agency M0030 Start of Care Date M0030 Start of Care Date M0032 Resumption of Care Date M0090 Date Assessment Completed M0090 Date Assessment Completed M0906 Discharge/transfer/death Date 1 7. Transferred to an inpatient facility – patient discharged from agency 8. Death at home 9. Discharge from agency 10. Discharge from agency – no visits completed after start/resumption of care assessment M0906 Discharge/transfer/death Date M0906 Discharge/transfer/death Date M0906 Discharge/transfer/death Date M0906 Discharge/transfer/death Date CORRECTION NUM Front end software

generates a correction number based on the following: For the original submission of a record use 00 (zero, zero) as the value. If correction records are submitted, increment this count with each correction: 01. 2 Resident Matching Criteria The following is the criteria used by the resident row matching Oracle database stored procedure for the resident matching. The arguments for the procedure are: In Facility Internal ID number In Social Security Number varchar 2 In Last Name varchar 2 In First Name varchar 2 In Date of birth date In Gender number Out Resident Internal ID number Out Resident matching criteria number Out Resident change timestamp date Out Row ID Row ID If the information submitted on a resident matches a resident on the database using any one of the following criteria, then the resident internal id, resident change timestamp, and row id of the resident found on the database is returned along with the number of the criteria used for the

match. The resident matching check is done in ascending order of the resident matching criteria. A lower resident matching criteria is considered to be a better match than a higher resident matching criteria. The criteria is called in the following order: 1.) Criteria 1 5.) Criteria 4 2.) Criteria 9 6.) Criteria 5 3.) Criteria 11 7.) Criteria 6 4.) Criteria 3 8.) Criteria 10 Criteria 1: facility, ssn, date of birth, last name, first name, gender Incoming resident Facility internal id Social security number Date of birth = Resident on database Facility internal id Social security number Date of birth 3 Criteria 9: Last name (as all upper case) Last name (as all upper case) First name (as all upper case) First name (as all upper case) Gender Gender ssn, date of birth, last name, first name, gender Incoming resident Criteria 11: Social security number Date of birth Date of birth Last name (as all upper case) Last name (as all upper case) First name (as all upper

case) First name (as all upper case) Gender Gender facility, ssn, gender, last name = Resident on database Facility internal id Facility internal id Social security number Social security number Gender Gender Last Name (as all upper case) Last Name (as all upper case) date of birth, last name, first name, gender Incoming resident Criteria 4: Resident on database Social security number Incoming resident Criteria 3: = = Resident on database Date of birth Date of birth Last name (as all upper case) Last name (as all upper case) First name (as all upper case) First name (as all upper case) Gender Gender ssn, date of birth, gender Incoming resident = Resident on database Social security number Social security number Date of birth Date of birth Gender Gender 4 Criteria 5: ssn, last name, first name, gender Incoming resident Criteria 6: Resident on database Social security number Social security number Last name (as all upper case) Last name

(as all upper case) First name (as all upper case) First name (as all upper case) Gender Gender facility, date of birth (close), last name, first name, gender Incoming resident Criteria 10: = = Resident on database Facility internal id Facility internal id Date of birth (month and year) Date of birth (month and year) Last name (as all upper case) Last name (as all upper case) First name (as all upper case) First name (as all upper case) Gender Gender social security number, date of birth, last name, first name Incoming resident = Resident on database Social security number Social security number Date of birth Date of birth Last name (as all upper case) Last name (as all upper case) First name (as all upper case) First name (as all upper case) 5