[CQM-7117] PC-07 Multiple Births Spec Manual vs. SQL Created: 07/16/24  Updated: 03/10/25  Resolved: 07/19/24

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

Type: EH/CAH eCQMs - Eligible Hospitals/Critical Access Hospitals Priority: Moderate
Reporter: Patricia Diamanti Assignee: Unassigned
Resolution: Answered Votes: 0
Labels: None

Attachments: Microsoft Word Most Recent Documentation OB History.docx    
Solution: Thank you for your question about CMS1028v2 Severe Obstetric Complications.

As noted in the Guidance section of the measure specifications, in case of multiple births, map the first delivery date/time (Baby A) as the delivery date/time for the encounter. The delivery date/time will be noted as the 'LastTimeOfDelivery' which is utilized in other timing calculations down to the minute within the measure such as the FirstLabTestWithEncounterId function and the FirstPhysicalExamWithEncounterId function.
Solution Posted On:
2024 Reporting Period EH/CAH eCQMs:
CMS1028v2
Impact: Multiple birth record validation

 Description   

Hello,

The PC-07 specifications manual states: In the case of multiple births, map the first delivery date/time (Baby A) as the delivery date/time for the encounter. However, our vendor states the SQL is not written based on the specifications manual rather it is written to pull the most recent delivery date/time. Please see attached document.                                                    Baby A delivery date/time is 1/22/2024 1201. Baby B delivery date/ time 1/22/2024 1203. In our validation tool Baby B delivery date/time was pulled.   

Please advise.

Thank you,

Patti Diamanti                                                                                                                        Most Recent Documentation OB History.docx

 Comments   
Comment by Joelencia Leflore [ 07/17/24 ]

Thank you for submitting your question. We will review your ticket and provide a response as soon as possible.

Generated at Fri Apr 04 07:51:05 EDT 2025 using Jira 9.12.16#9120016-sha1:6bee0863f3e6dbb91e4be2d992a3b6761c21c9e0.