[CYPRESS-937] Issue with Reason of care Loinc missing Created: 02/14/17  Updated: 05/07/18  Resolved: 03/03/17

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

Type: Question Priority: Moderate
Reporter: ron szmara (Inactive) Assignee: David Czulada
Resolution: Done Votes: 0
Labels: 2016, CQM, cypress

Attachments: JPEG File cms.jpg    
Issue Links:
Relates
relates to CYPRESS-941 CMS2, CMS61 and CMS139 test deck errors Closed
Previous Issue Type: Logic affecting more than 1 eCQM

 Comments   
Comment by Matthew Bianchi (Inactive) [ 02/15/17 ]

Since Cypress 3.1, when exporting patients we follow the instructions in QRDA Cat 1 r3.1 Introductory Material Section 3.4 for a patient that has a Negation Reason for not being treated for anything in that Value Set:

Some cases need to exclude all possibilities, not just that of a single formulation or specific procedure. One example is the general “no Antibiotic Medications for Pharyngitis” compared to the specific “no Amoxicillin 60 MG/ML Oral Suspension”. Another example is the general “no Hepatitis A Antigen Test” compared to the specific “no Hepatitis A virus Ab [Units/volume] in Serum by Immunoassay”.
In such cases, where no code exists in the Value Set Authority Center (VSAC) value set to represent the general concept, use all of the following steps:
    * Use code/[@nullFlavor="NA"]
    * Set code attribute code/sdtc:valueset="[VSAC value set OID]"
   
This section also mentions an "originalText" element that provides a human readable indication that an entire valueset is being negated.  This free text field is currently not implemented in Cypress at the moment. This will not affect your import tests.  Additionally, when evaluating an uploaded QRDA document, Cypress allows for the negation of a single code as well as the negation of an entire valueset.  Therefore, it would be ok for your system to submit the following <code code=”73830-2” codeSystem="2.16.840.1.113883.6.1" displayName="reason" codeSystemName="LOINC" /> to Cypress.

Generated at Sun Sep 21 15:33:01 UTC 2025 using Jira 10.3.9#10030009-sha1:eff8913ed2270ee44ab422c3609af4c4f36536d0.