Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed. Timing: The Relevant Period addresses: startTime – When the laboratory test is initiated (i.e., the time the specimen collection begins). stopTime – when the laboratory test is completed (i.e., the time the specimen collection ends). Examples: 1) Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – basically a single point in time for many specimen collections. 2) Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection Note – the time that the result report is available is a separate attribute than the time of the study (specimen collection)
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.
The final consequences or data collected from the datatype. Results can be used in five ways, to express: That a result is present in the electronic record but any entry is acceptable. A numerical result is reported directly as a value. Values may be integers or decimal numbers without units, or as a quantity with a value and units – examples: 100 mg/dL for a lab test, 140 mmHg for blood pressure, as a percentage (actually a quantity with % as units), as a ratio (e.g., 1:4, 1:80). Beginning with QDM 5.3 measures use CQL logic to express the mathematical operators to constrain desired results to those above or below a certain threshold. A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct referenced code. A result as a dateTime (Assessment, Performed and components).