Back to top
Top
DERep Home Page

Functional Status Assessment for Total Knee Replacement

CMS Measure ID: CMS66v9    Performance/Reporting Period: 2021    Version: 9    NQF Number: Not Applicable
Description:

Percentage of patients 18 years of age and older who received an elective primary total knee arthroplasty (TKA) and completed a functional status assessment within 90 days prior to the surgery and in the 270-365 days after the surgery

Data Elements and coded QDM Attributes contained within the eCQM

+ Expand all

Direct Reference Code

Constrained to 'Activities of daily living score [KOOS]' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent the Knee Injury and Osteoarthritis Outcome Score for Joint Replacement (KOOS Jr.) total interval score.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Assessment, Performed.
Inclusion Criteria: Includes only relevant concepts associated with the Knee Injury and Osteoarthritis Outcome Score for Joint Replacement (KOOS Jr.) score. This is a grouping of a LOINC code.
Exclusion Criteria: No exclusions.

Constrained to codes in the Assessment, Performed: Knee Injury and Osteoarthritis Outcome Score for Joint Replacement [KOOSJR] value set (2.16.840.1.113883.3.464.1003.118.12.1218)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'Pain score [KOOS]' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'PROMIS-10 Global Mental Health (GMH) score T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'PROMIS-10 Global Physical Health (GPH) score T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'Quality of life score [KOOS]' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'Sport-recreation score [KOOS]' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'Symptoms score [KOOS]' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'VR-12 Mental component summary (MCS) score - oblique method T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'VR-12 Mental component summary (MCS) score - orthogonal method T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'VR-12 Physical component summary (PCS) score - oblique method T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'VR-12 Physical component summary (PCS) score - orthogonal method T-score' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Assessment, Performed"

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references timing for an assessment that occurs at a single point in time.
  • relevant Period references a start and stop time for an assessment that occurs over a time interval
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent a diagnosis of fracture of a bone in the leg or pelvis.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Diagnosis.
Inclusion Criteria: Includes only relevant concepts associated with a diagnosis of fracture of the ankle, ilium, acetabulum, pubis, ischium, epiphysis, femur, patella, leg, tibia, fibula, talus, calcaneus, or metatarsal. This is a grouping of ICD-10-CM and SNOMED CT codes.
Exclusion Criteria: Excludes codes that identify pathological or nontraumatic fractures.

Constrained to codes in the Diagnosis: Fracture - Lower Body value set (2.16.840.1.113883.3.464.1003.113.12.1037)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Diagnosis"

Data elements that meet criteria using this datatype should document the Condition/Diagnosis/Problem and its corresponding value set. The onset dateTime corresponds to the implicit start dateTime of the datatype and the abatement dateTime corresponds to the implicit stop dateTime of the datatype. If the abatement dateTime is not present, then the diagnosis is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for an active diagnosis for the time frame indicated by the timing relationships.

Timing: The prevalencePeriod references the time from the onset date to the abatement date.

Direct Reference Code

Constrained to 'Severe dementia (disorder)' SNOMEDCT code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Diagnosis"

Data elements that meet criteria using this datatype should document the Condition/Diagnosis/Problem and its corresponding value set. The onset dateTime corresponds to the implicit start dateTime of the datatype and the abatement dateTime corresponds to the implicit stop dateTime of the datatype. If the abatement dateTime is not present, then the diagnosis is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for an active diagnosis for the time frame indicated by the timing relationships.

Timing: The prevalencePeriod references the time from the onset date to the abatement date.

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent the most common inpatient encounter types.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Encounter. The intent of this data element is to identify patients who have had an inpatient encounter.
Inclusion Criteria: Includes only relevant concepts associated with SNOMED CT codes representing inpatient encounter.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Encounter Inpatient value set (2.16.840.1.113883.3.666.5.307)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent patients who have had an office or other outpatient visit.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Encounter, Performed.
Inclusion Criteria: Includes only relevant concepts associated with comprehensive history, evaluation, and management of a patient in an office or outpatient facility. Patient can be presenting with problems that are minor to high severity. This is a grouping value set of CPT codes.
Exclusion Criteria: Excludes non-office visits, including telehealth services.

Constrained to codes in the Encounter, Performed: Office Visit value set (2.16.840.1.113883.3.464.1003.101.12.1001)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent patients who have had an outpatient interaction at an office with a member of their medical care team.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Encounter, Performed.
Inclusion Criteria: Includes only relevant concepts associated with comprehensive history, evaluation, and management of a patient in an office or outpatient facility. Patient can be presenting with problems that are minor to high severity. This is a grouping value set of CPT and SNOMED CT codes.
Exclusion Criteria: Excludes non-office visits, including telehealth services.

Constrained to codes in the Encounter, Performed: Outpatient Consultation value set (2.16.840.1.113883.3.464.1003.101.12.1008)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Direct Reference Code

Constrained to 'Postoperative follow-up visit, normally included in the surgical package, to indicate that an evaluation and management service was performed during a postoperative period for a reason(s) related to the original procedure' CPT code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Encounter, Performed"

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent patients receiving hospice care outside of a hospital or long term care facility.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Procedure, Order or Intervention, Order. The intent of this value set is to identify all patients receiving hospice care outside of a hospital or long term care facility.
Inclusion Criteria: Includes only relevant concepts associated with hospice care concepts.
Exclusion Criteria: Excludes concepts for palliative care or comfort measures.

Constrained to codes in the Intervention, Order: Hospice care ambulatory value set (2.16.840.1.113762.1.4.1108.15)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Intervention, Order"

Data elements that meet criteria using this datatype should document a request to perform the intervention indicated by the QDM category and its corresponding value set.

Timing: The time the order is signed; author dateTime.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent patients receiving hospice care outside of a hospital or long term care facility.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Procedure, Order or Intervention, Order. The intent of this value set is to identify all patients receiving hospice care outside of a hospital or long term care facility.
Inclusion Criteria: Includes only relevant concepts associated with hospice care concepts.
Exclusion Criteria: Excludes concepts for palliative care or comfort measures.

Constrained to codes in the Intervention, Performed: Hospice care ambulatory value set (2.16.840.1.113762.1.4.1108.15)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Intervention, Performed"

Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the intervention is performed when the intervention occurs at a single point in time.
  • relevantPeriod references a start and stop time for an intervention that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the intervention begins.
    • stopTime - The time the intervention ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Notes:

  • Timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
     
Direct Reference Code

Constrained to 'Birth date' LOINC code

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Birthdate"

The "Patient Characteristic Birthdate" should document the patient’s date of birth.

Timing: The "Patient Characteristic, Birthdate" is a single point in time representing the date and time of birth. It does not have a start and stop time.

Note: "Patient Characteristic Birthdate" is fixed to LOINC code 21112-8 (Birth date) and therefore cannot be further qualified with a value set.

Value Set Description from VSAC
Clinical Focus: n/a Data Element Scope: n/a Inclusion Criteria: n/a Exclusion Criteria: n/a

Constrained to codes in the Patient Characteristic, Ethnicity: Ethnicity value set (2.16.840.1.114222.4.11.837)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Ethnicity"

Data elements that meet criteria using this datatype should document that the patient has one or more of the ethnicities indicated by the QDM category and its corresponding value set.

Timing: Ethnicity does not have a specific timing. Measures using "Patient Characteristic, Ethnicity" should address the most recent entry in the clinical record.

Value Set Description from VSAC
Clinical Focus: Categories of types of health care payor entities as defined by the US Public Health Data Consortium SOP code system
Data Element Scope: @code in CCDA r2.1 template Planned Coverage [act: identifier urn:oid:2.16.840.1.113883.10.20.22.4.129 (open)] DYNAMIC
Inclusion Criteria: All codes in the code system
Exclusion Criteria: none

Constrained to codes in the Patient Characteristic, Payer: Payer value set (2.16.840.1.114222.4.11.3591)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Payer"

Data elements that meet criteria using this datatype should document that the patient has one or more of the payers indicated by the QDM category and its corresponding value set.

Timing:

The relevantPeriod addresses:

  • startTime – the first day of insurance coverage with the referenced payer.
  • stopTime – the last day of insurance coverage with the referenced payer.
Value Set Description from VSAC
Clinical Focus: n/a Data Element Scope: n/a Inclusion Criteria: n/a Exclusion Criteria: n/a

Constrained to codes in the Patient Characteristic, Race: Race value set (2.16.840.1.114222.4.11.836)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Race"

Data elements that meet criteria using this datatype should document the patient’s race.

Timing: Race does not have a specific timing. Measures using "Patient Characteristic, Race" should address the most recent entry in the clinical record.

Value Set Description from VSAC
Clinical Focus: Gender identity restricted to only Male and Female used in administrative situations requiring a restriction to these two categories.
Data Element Scope: Gender
Inclusion Criteria: Male and Female only.
Exclusion Criteria: Any gender identity that is not male or female.

Constrained to codes in the Patient Characteristic, Sex: ONC Administrative Sex value set (2.16.840.1.113762.1.4.1)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Patient Characteristic, Sex"

Data elements that meet criteria using this datatype should document that the patient's sex matches the QDM category and its corresponding value set.

Timing: Birth (administrative) sex does not have a specific timing.

Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent primary Total Knee Arthroplasty (TKA) procedures.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Procedure, Performed.
Inclusion Criteria: Includes only relevant concepts associated with codes that identify primary TKA procedures. This is a grouping of CPT, HCPCS and SNOMED CT codes.
Exclusion Criteria: Excludes codes for revision or partial knee arthroplasty procedures.

Constrained to codes in the Procedure, Performed: Primary TKA Procedure value set (2.16.840.1.113883.3.464.1003.198.12.1007)

QDM Datatype and Definition (QDM Version 5.5 Guidance Update)

"Procedure, Performed"

Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set.

Two QDM Known Issues has been identified related to this datatype.

  • To see the QDM Known Issue related to QDM Procedure, Performed completion time, please click here.
  • To see the QDM Known Issue related to Differentiating Elective Vs Emergent or Urgent Procedures, please click here.

Timing:

  • relevant dateTime references the time the procedure is performed when the procedure occurs at a single point in time.
  • relevantPeriod references a start and stop time for a procedure that occurs over a time interval. relevantPeriod addresses:
    • startTime - The time the procedure begins.
    • stopTime - The time the procedure ends.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Notes:

  • Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request.
  • The incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • For clarification, see Appendix 6.6 with 2020 guidance about differentiating between successful and unsuccessful procedures.