Uploaded image for project: 'eCQM Issue Tracker'
  1. eCQM Issue Tracker
  2. CQM-2275

Elective Delivery PC-01 Timing of performing Gestational Age vs Time of Delivery

XMLWordPrintable

    • Icon: Annual Update Annual Update
    • Resolution: Done
    • Icon: Minor Minor
    • Guidance
    • None
    • Hide
      Thank you for your question. Your interpretation of the measure logic is correct, the gestational age must be known prior to proceeding with elective delivery. The eCQM logic evaluates the day of delivery as "Day Zero" and will allow documentation the day of delivery up to the minute prior to the time of delivery, on the same day of delivery.
      Show
      Thank you for your question. Your interpretation of the measure logic is correct, the gestational age must be known prior to proceeding with elective delivery. The eCQM logic evaluates the day of delivery as "Day Zero" and will allow documentation the day of delivery up to the minute prior to the time of delivery, on the same day of delivery.
    • Verification of intent of Logic

      Denominator Logic: I am reading this as the Physical Exam for Gestational Age starts < 1 Day before the Start of the Physical Exam: Time of Delivery (that starts during the Inpatient Encounter). I am reading this as they need to know the gestational age is >=37 weeks and < 39 weeks, before they proceed with the Elective Delivery in order to meet the Denominator Criteria. Some may be interpreting this differently because of the Guidance Section at the top that says: "Whenever the gestational age is mentioned with relative timing to the delivery, the intent is to capture the estimated gestational age on the day of delivery." This would mean that it could be on the day of delivery and after the time of delivery. So, it doesn't match the logic and we need clarification for a customer. Thank you.

            JLeflore Joelencia Leflore
            megbutler Margaret Butler
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: