[CYPRESS-143] If encounters for patient 'Diabetes Ped B' are coded using SNOMED codes, the patient does not qualify for the IPP for CMS 147 as expected Created: 07/01/13 Updated: 06/20/18 Resolved: 07/23/13 |
|
Status: | Closed |
Project: | CYPRESS Issue Tracker |
Component/s: | None |
Type: | Question | Priority: | Minor |
Reporter: | M Heeke (Inactive) | Assignee: | Renee Rookwood (Inactive) |
Resolution: | Answered | Votes: | 0 |
Labels: | TestData, cypress |
Attachments: | CMS147v1.html Diabetes_Peds_B.html Diabetes_Peds_B.json |
Solution: | Fixed in Cypress 2.3 |
Previous Issue Type: | Logic affecting more than 1 eCQM |
Description |
Patient 'Diabetes Ped B' was built ij our system using SNOMED codes (no CPT codes). The patient does not qualify for the IPP for CMS 147 as expected. The SNOMED codes on the record exist only in the valueset ... Encounter, Performed: Encounter-Influenza" using "Encounter-Influenza Grouping Value Set (2.16.840.1.113883.3.526.3.1252)" ... which qualifies the patient for the denominator only after the IPP has been met. Cypress bundle 2.2 It seems that patient MUST have CPT on the record to qualify for IPP, Is this correct ? Thanks Mary Beth Heeke |
Comments |
Comment by Rob McCready (Inactive) [ 07/23/13 ] |
This bug is still outstanding after Cypress v2.3 The problem is more difficult to fix than originally thought due to semantic interoperability problems with two different code sets (SNOMED and CPT). We will attempt to either force the use of different codes, or potentially modify the clinical attributes on the Cypress patients so that this semantic interoperability problem does not affect the results in Cypress. We are planning on determining the fix to this problem by Cypress v2.4 and have made this a tracked defect on the project site. See http://projectcypress.org/release.html#2.4 |
Comment by Robert Dingwell (Inactive) [ 07/03/13 ] |
This is a problem that was previously reported on the Cpress email list which I believe has been fixed in the patient data for the upcoming 2.3 release but I will need to make sure of that with the team responsible for the test records. |