[QRDA-718] Lack of clear guidance on which specific Value element to use for the Result in the Assessment Performed QDM element Created: 08/03/18  Updated: 12/22/20  Resolved: 09/17/18

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

Type: QRDA-I Standard Priority: Moderate
Reporter: Manish Parekhji Assignee: Yan Heras
Resolution: Answered Votes: 0
Labels: None

Attachments: Microsoft Word JIRA-AssessmentPerformed.docx    
Impact: Potential for confusion and incorrect information being exchanged because of ambiguity in the Implementation Guide regarding which specific Value element to use for the Result in Assessment Performed QDM element. This could lead to inaccurate eCQM calculations.

 Description   

Attached document provides the details of the issue.
This could affect at least the following Eligible Hospital eCQM measure calculations - VTE-1, VTE-2, PC-01 and PC-05.



 Comments   
Comment by Yan Heras [ 11/26/18 ]

matt.hardman Thanks for pointing this out. My apologies!

Please note the following CORRECTIONS to the previous comment regarding the mapping of the Assessment Performed result attribute:

  1. For the 2018 reporting period, the contained Result (V3) template (instead of the observation/value element) is used for the Assessment Performed result attribute.
  2. For the 2019 reporting period: the result attribute will be mapped to the Assessment Performed's observation/value element as specified in the HL7 QRDA I STU 5. 

 

 

Comment by Matt Hardman (Inactive) [ 11/20/18 ]

yanheras - Are the years flipped in this previous comment?

"Added clarifications below to specify which reporting period:

****

Thanks for raising this issue. Yes, this is a known issue with this template. Both the receiving systems for the CMS HQR programs and The Joint Commission have been aligned according to the following:

1. For the 2018 reporting period, the result attribute will be mapped to the Assessment Performed's observation/value element.

2. For the 2019 reporting period: it will be using the contained Result template (instead of the observation/value element) for the Assessment Performed result attribute."

Comment by Manish Parekhji [ 11/13/18 ]

Hi Yan,

I'm wondering why this item has been closed. I do not believe a resolution has been provided. The last update from you stated

"...there are some discussions among TJC and CMS happening currently to discuss this further for the 2019 reporting period, including Assessment Performed. We will keep you posted once there is a clear decision/guidance made. .."

Is this being tracked with some other ticket? If so could you add a reference to it here?

Thanks for your consideration.

 

Comment by Matt Hardman (Inactive) [ 09/27/18 ]

yanheras is there a place where we can track known issues with templates for 2018 reporting periods? It would be helpful if we could know ahead of time and proactively address these issues instead of not finding out until we submit test submissions. Thanks

Comment by Yan Heras [ 09/18/18 ]

Hi Manish, there are some discussions among TJC and CMS happening currently to discuss this further for the 2019 reporting period, including Assessment Performed. We will keep you posted once there is a clear decision/guidance made. Thanks.

Comment by Manish Parekhji [ 09/17/18 ]

Thanks Yan.

It will surely be helpful to get more definitive guidance. The way is stands right now depending on how someone interprets this, they could use a combination of code and value elements which can lead a lot of issues downstream. I'm still not clear which code and value element to use in CY2019 for a single question assessment.

Also in regards to your clarification above about CY2019, where you mentioned we need to use the contained Result template, I'm assuming you meant the contained "Component" template, correct? I did not see a contained Result template in Assessment Performed in QRDA CAT I STU 5.

Thanks again for your comments and taking on this issue for further clarification.

Comment by Yan Heras [ 09/17/18 ]

Hi Manish,

Please note that clarifications are added above to indicate which reporting period for further clarifications. 

It looks like that you are referring to the QRDA I STU 5, which will be used for the 2019 reporting period. The Component is expected to be used when an assessment has multiple components that need to be reported. If it is single question assessment, then use observation/code directly. Agree that the IG does not provide guidance clearly on this. We will take this issue for discussions with both CMS and TJC as well as HL7 and to provide more definitive guidance on this.

Thanks.

 

Comment by Manish Parekhji [ 09/17/18 ]

Hi Yan

Thanks for the clarification on the <value> element.

Does the same apply to the <code> element?

One can provide a Code for the Result in 2 locations as shown below -
a. Entry/observation/code OR
b. Entry/observation/entryRelationship/observation/code (where entryRelationship is for the Component identified by template ID - 2.16.840.1.113883.10.20.22.3.149)

What is the expectation here as to where the Code should be provided?

And should the code be the exact same between the 2 locations for a singe question assessment i.e. assessments that do not have more than one component? What do we do if the codes are different?

Thanks in advance for your guidance.

 

Comment by Yan Heras [ 09/17/18 ]

Added clarifications below to specify which reporting period:

****

Thanks for raising this issue. Yes, this is a known issue with this template. Both the receiving systems for the CMS HQR programs and The Joint Commission have been aligned according to the following:

1. For the 2018 reporting period, the result attribute will be mapped to the Assessment Performed's observation/value element. 

2. For the 2019 reporting period: it will be using the contained Result template (instead of the observation/value element) for the Assessment Performed result attribute.

 

 

Comment by Matt Hardman (Inactive) [ 08/24/18 ]

I would also like clarification on this.

Generated at Fri Mar 14 09:17:57 EDT 2025 using Jira 9.12.16#9120016-sha1:6bee0863f3e6dbb91e4be2d992a3b6761c21c9e0.