[CYPRESS-2138] Not able to identify Duplicate Patients from QRDA I (.zip) generated by Cypress tool Created: 10/16/20  Updated: 10/19/20  Resolved: 10/19/20

Status: Closed
Project: CYPRESS Issue Tracker
Component/s: None

Type: Bug/Issue Priority: Critical
Reporter: Manoj R Deriya (Inactive) Assignee: David Czulada
Resolution: Resolved Votes: 0
Labels: DuplicatePatient, Guidance, QRDA-I, QRDA-III, logic

Attachments: Zip Archive CMS165v8_5f6b106863623904f611aaf7.qrda.zip     PNG File Christian Hamilton.PNG     PNG File Loretta Dennis.PNG    
2020 Performance Period EC eCQMs:
CMS165v8/NQFna
Cypress Version: Cypress v5.4.2

 Description   

We are implementing eCQM update year 2020 in our application.
After implementing changes for CMS165v8 measure, we have performed (C2 + C3) test using Cypress v5.4.2 (2019.2.0 bundle).
As per cypress, count for IPOP population is 24, but after importing QRDA1 zip(kindly see the attachment) file, our application displays counts for IPOP as 26.
While looking into the problem we have observed a few things mentioned in below scenarios,
**

1) QRDA1 zip file contains patient's xml of : Lorie Dennis & Loretta Dennis.
As per cypress report, only "Loretta Dennis" patient data should get considered. (kindly see the attachment)
Now, when you look at the xml file data for both patients, you will find Demographic details(like Date of birth, Gender, Race & Ethnicity) and other Patient data are the same for both patients.
Observation: Except the Patient Name, both patients have almost the same data.

 

2) QRDA1 zip file contains patient's xml of : Chris Hamilton & Christian Hamilton.
As per cypress report, only "Christian Hamilton" patient data should be considered. (kindly see the attachment)
Now, when you look at the xml file data for both patients, you will find Demographic details(Date of birth, Gender & Race) and other Patient data are the same for both xml.
Observation: Except the Patient Name & Ethnicity, both patients have almost the same data.

 

Concern : As mentioned in above cases and considering many other demographic details, what would be the closest criteria to be considered to identify duplicate patients?
Also, while other measures testing, we have observed similar kinds of scenarios where only "Patient Names" are different & all the information are the same except (Date of Birth OR Race OR Ethnicity).
Can you please provide us any document or implementation guide link which will help us implement logic to identify duplicate patients while importing QRDA1 Zip files.

 

Thanks in advance.



 Comments   
Comment by Manoj R Deriya (Inactive) [ 10/19/20 ]

Hi David,
Thank you for quick response & addressing the query.
We will apply the changes accordingly. You can close the case.

Thanks,
Manoj Deriya

Comment by David Czulada [ 10/16/20 ]

Manoj

In the two examples, the names differences are common nicknames.

  • Lorie is a common nickname for Loretta
  • Chris is a common nickname for Christian

Below you will find the pattern that Cypress uses when patients are duplicated:

Introduce duplicate files with modifications to a patient’s name and demographics

  • Name differences include: nicknames, initials, misspellings
  • Demographics include discrepancies in: race, gender, ethnicity
  • Discrepancies in Date of birth: missing, different, imprecise
  • The clinical information in the duplicate files will remain consistent
  • The patient address in the duplicate files will remain consistent
  • Note: For reporting, either name or demographic can be chosen

Introduce duplicate files with modifications to a patient’s clinical information

  • Documents will be split one of multiple ways:
    • Temporally (e.g., Jan – June, and July - Dec)
    • Data types (e.g. encounters in one file, lab results in another)
  • Name and Demographics will remain consistent
  • Information in ’split’ files will be additive (i.e., files will not contain duplicate information)
  • Clinical Information will need to be combined to achieve a complete patient record

-Dave Czulada

Comment by Cypress Team (Inactive) [ 10/16/20 ]

Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day

Generated at Sun Aug 31 08:15:41 UTC 2025 using Jira 10.3.8#10030008-sha1:cdaed80cecc964184c5b19b002388d56f96e274e.