[QRDA-797] How to negate without sdtc:valueSet when code is null flavored? Created: 05/16/19  Updated: 12/22/20  Resolved: 05/29/19

Status: Resolved
Project: QRDA Issue Tracker
Component/s: None

Type: QRDA-I Standard Priority: Moderate
Reporter: Susan Grossenbacher (Inactive) Assignee: Yan Heras
Resolution: Done Votes: 1
Labels: None

Attachments: PNG File image-2019-05-16-12-35-16-194.png    
Impact: Questions on how to implement.

 Description   

In the HL7 Implementation Guide for QRDA I Templates STU 5, it removes the sdtc:valueSet for multiple QDM Elements like Device Applied, Device Order, and Intervention Order just to name a few. my question is how will negation work. Per the eCQM Logic and Implementation Guidance V2, it states:

"In the May 2016 eCQM release, the QRDA Category I Release 3 and CMS QRDA Implementation Guide directed implementers instead to use null values to replace a specific code associated with a value set when describing activities that were negated or “not done.” Thus, providers are not required to specify that they did not perform a specific member from the value set; rather, the recommended approach is that they will indicate what they did not do on any of the items in the value set. This approach is intended for use with all datatypes that use negation to describe activities “not done.” It does not change the expression of negation in the HQMF; however, it does require using an HL7 nullFlavor code instead of a specific code from the value set associated with these activities in the QRDA Category I file.
The intent of the null flavor in this context is to specify that ALL the activities in the value set were intentionally not done, not that a single activity was not done or that it is not known why that activity was not completed. It is not appropriate for users to certify that an activity was not done using negation unless the provider intentionally did not order or perform the activity in question and documented a justification why that was the case."

"In referencing value sets used to negate activities, developers had previously used ingredient-level value sets to group medications for negation because this provided improved usability to providers. Now that the updated approach allows negation of the entire value set, the same detailed value sets used for Medication, Order or Medication, Administered in the measure logic can be used throughout and the logic can be implemented in a more workflow-friendly fashion. Ingredient-level value sets have been retired for negation purposes, but are still used for allergies. This approach also should streamline additional types of negations, such as groups of procedures."

It gives this example of how to null flavor the code with "NA" and negate the value set itself. If the sdtc:valueSet is removed from Device Order, how are we able to specify which value set is being null flavored? There doesn't seem to be a place for a sdtc:valueSet in Reason either. 

 



 Comments   
Comment by Yan Heras [ 05/29/19 ]

Thanks Susan. 

Comment by Susan Grossenbacher (Inactive) [ 05/29/19 ]

You can close this. Thank you for the quick response and explanation. 

Comment by QRDA-ICF [ 05/29/19 ]

Hi sgrossenbacher do you need further explanation or clarification from our team? We will close this ticket in 5 business days. Thank you.

Comment by Yan Heras [ 05/21/19 ]

Hi Susan,

The change described in QRDA I STU5 about removing sdtc:valueSet that you are referring to is applicable to positive scenario only, e.g., medication order, procedure order. It does not affect "not done" scenario such as "medication order not done". To report for "medication order not done", you would still use nullFlavor="NA" and place the value set OID in sdtc:valueSet, the same way as it is shown in Figure 3 that you have attached.

One thing to note is that if the eCQM specification uses direct reference code instead of value set, for example, in CMS26v6, ["Communication: From Provider To Patient, Not Done": "Asthma action plan"] whereas Asthma action plan is defined using a direct reference code not a value set, then you would set negationInd to true, and send the Asthma action plan code directly without using nullFlavor="NA" and sdtc:valueSet, because value set id is not applicable in this case.  

 

 

Comment by QRDA-ICF [ 05/16/19 ]

Thank you for submitting a ticket to the QRDA JIRA Issue Tracker. Our experts are reviewing your ticket and will provide feedback as soon as possible. Thank you for your patience.

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