ecqm.dataelement

Below Normal Follow Up Order

Description:

Clinical Focus: The purpose of this value set is that the provider documents a follow-up plan for those with a below normal BMI that indicates a patient is underweight.

Data Element Scope:

Inclusion Criteria: This value set includes lifestyle modification, dietary and nutritional education, or interventions as documented in the medical record by a provider as a follow-up plan to increase BMI or support weight gain.

Exclusion Criteria:

Subject constrained to the Below Normal Follow up

QDM Datatype: InterventionOrder

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

Used By:

• CMS69v7

QDM Attributes

Subject.Statement

Defined in Activity

DataType

Constrained in BelowNormalFollowUpOrder

BelowNormalFollowUp

AuthorDatetime

The time the data element was entered into the clinical software. Note, some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.

NegationRationale

Indicates the reason that an action was not performed. Only QDM datatypes that represent actions (e.g., performed, recommended, communication, order, dispensed) allow the “negation rationale” attribute. The intent is to indicate a justification that such action did not happen as expected. This attribute specifically does not address the presence or absence of information in a clinical record (e.g., documented absence of allergies Vs lack of documentation about allergies). The syntax in the human readable HQMF is address in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, “Procedure, Performed not done.” QDM 5.0 DRAFT uses the syntax, “Procedure, not Performed.” Note: Some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.