[QRDA-1007] For CMS529v1.3, should Physical exam performed element utilize Relevant Datetime or Relevant Period Created: 08/30/21  Updated: 09/08/21  Resolved: 09/08/21

Status: Resolved
Project: QRDA Issue Tracker
Component/s: Reporting/Attestation

Type: Question/Guidance Priority: Moderate
Reporter: Dherya Sahni (Inactive) Assignee: Yan Heras
Resolution: Resolved Votes: 0
Labels: None

Attachments: PNG File image-2021-08-30-16-43-53-149.png     PNG File image-2021-08-30-16-45-47-306.png    

 Description   

Hi Team, 

For the Reporting period 2021, as per the Hybrid measure CMS 529v1.3 logic, only the Relevant Date time should be considered for evaluation. But it is observed that when we are providing Relevant period for the Physical Exam performed, it is still evaluating in the Cypress and considering it as a result evidence. Please find the attached screenshot for the reference. 

 

 

 

 

 

 

Also, as per the resolution provided for Jira QKI-2for the Hospital measures calculation, "When a relevantPeriod is reported and a relevantDatetime is needed for evaluation, the low value will be used unless not provided, then the high time will be used". Please help us understand if the same behavior is expected for Hybrid measure as well and will providing Relevant Period for Physical Exam performed is accepted for submission?

 

Thank you.

 Comments   
Comment by QRDA-ICF [ 09/01/21 ]

Hi Dherya Sahni,

Does this solution answer your question?

If you have no follow up questions, this ticket will be considered resolved and closed on Wedneday, September 8 .

Thank you.

Comment by Yan Heras [ 08/30/21 ]

Hi Dherya,

The guidance provided in QKI-2 applies to the hybrid measure submission as well. Providing relevantPeriod for Physical Exam Performed is accepted. 

Comment by QRDA-ICF [ 08/30/21 ]

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 Sep 21 15:30:30 UTC 2025 using Jira 10.3.9#10030009-sha1:eff8913ed2270ee44ab422c3609af4c4f36536d0.