Why does the NLM element list for "Face-to-Face Interactions" not contain CPT codes that are included in a posted spreadsheet?

XMLWordPrintable

    • Type: EC eCQMs - Eligible Clinicians
    • Resolution: Referred to External Party for Resolution
    • Priority: Minor
    • Component/s: ValueSet
    • Hide
      The spreadsheet is specific to the PQRS program requirements. If you have additional questions concerning this spreadsheet, please contact the PQRS help desk via the following:

      Phone: 1-866-288-8912
      TTY: 1-877-715-6222
      Email: Qnetsupport@hcqis.org
      Show
      The spreadsheet is specific to the PQRS program requirements. If you have additional questions concerning this spreadsheet, please contact the PQRS help desk via the following: Phone: 1-866-288-8912 TTY: 1-877-715-6222 Email: Qnetsupport@hcqis.org
    • Clarification on why the "Face-to-Face Interactions" encounter element is limited to SNOMED codes in the NLM definition.

      What is the intent of this spreadsheet? It is unclear to us whether it's intended to define the "Encounter, Performed: Face-to-Face Interaction" element in eCQM specs or to define which providers should be considered for reporting PQRS. If it is to define the Encounter, Performed: Face-to-Face Interaction valueset, why are the CPT codes not included in the NLM specifications, which currently contains exclusively SNOMED codes? For example, if a provider was submitting a CPT code included in the face-to-face CPT spreadsheet, but didn't consider it to be equivalent to one of the SNOMED codes from the NLM spreadsheet, should that encounter be included in measure calculation as Encounter, Performed: Face-to-Face Interaction?

      http://www.cms.gov/apps/ama/license.asp?file=/PQRS/Downloads/FacetoFace_Encounter_CodeList_01302015.zip

            Assignee:
            Mathematica EC eCQM Team (Inactive)
            Reporter:
            Eric Barkley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On:
              Comment Posted On: