[QRDA-420] The CMS HQR_IQR Combined IG states that UTC Offsets are required for the birthTime element (if used elesewhere), but since birthTime is specific to the day (unless it is required for a newborn), a UTC offset is not appropriate for birthTime in most cases. Created: 12/22/16 Updated: 12/22/20 Resolved: 09/05/17 |
|
Status: | Resolved |
Project: | QRDA Issue Tracker |
Component/s: | None |
Type: | Certification | Priority: | Moderate |
Reporter: | David Sundaram-Stukel (Inactive) | Assignee: | QRDA-ICF |
Resolution: | Placed in Long-term Storage | Votes: | 0 |
Labels: | cypress |
Impact: | We are unable to successfully submit files for the HQR program for the 2017 Reporting Year. |
Solution: | If UTC offsets are being sent for times within a QRDA document, then the birthTime element should only require a UTC offset if it is being sent for a newborn, where the time of birth needs to be captured. In the normal case, where CONF:1198-5300_C01 specifies that birthTime "SHALL be precise to day", a UTC offset is not appropriate (i.e. A UTC offset is meaningless for dates. It is only well-defined for a time accurate to at least hours and minutes) |
Description |
When submitting documents to Cypress for HQR programs for the 2017 Reporting Year, we receive the following CMS HQR_IQR Combined IG error:
We are sending UTC offsets everywhere in the document except for the reportingParameters/effectiveTime and the birthTime. We are getting the conformance error for the birthTime element in all test documents we submit. The CMS HQR_IQR Combined IG specifies that the reportingParameters/effectiveTime element is an exception to the UTC rule since it is specific to the day. birthTime should also be an exception, since at other locations in the IG, birthTime is specifies to be precise to the day (unless a newborn's time of birth is needed for a measure. This is stated as the following:
Since a UTC offset isn't well defined for a date, the conformance statement CONF: CMS_0121 should only be applied to the birthTime element in the rare cases where this element contains a time specific to the minute. birthTimes specific to the day should not require UTC offsets. The 2 conformance statements in the IG seem to contradict each other, and make it impossible to successfully submit files to HQR programs for the 2017 Reporting Year. UIt |
Comments |
Comment by Yan Heras [ 03/13/17 ] |
Thanks for pointing out the issue. Your feedback has been taking into consideration for the development of the IG for the 2018 reporting period. We hope to provide an update soon about the 2017 reporting period. |
Comment by QRDA-ICF [ 12/27/16 ] |
Your ticket is being reviewed by our experts. We will provide you feedback as soon as possible. Thank you for your patience. |