["Laboratory Test, Performed": "Urine Protein Tests"]
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Laboratory Test, Performed.
Inclusion Criteria: Includes only relevant concepts associated with identifying urine protein tests, including those that look for albumin, microalbumin, and protein.
Exclusion Criteria: Excludes codes that identify urine protein tests that would be taken from a fetus.
Constrained to codes in the Laboratory Test, Performed: Urine Protein Tests value set (2.16.840.1.113883.3.464.1003.109.12.1024)
"Laboratory Test, Performed"
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.
A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.
Timing:
- relevant dateTime references the time the laboratory test is performed when the laboratory test occurs at a single point in time.
- relevantPeriod references a start and stop time for a laboratory test that occurs over a time interval. relevantPeriod addresses:
- startTime - The time the laboratory test begins.
- stopTime - The time the laboratory test ends.
- author dateTime references the time the action was recorded.
- Refer to the eCQM expression to determine allowable timings to meet measure criterion.
Examples:
- Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
- Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.
Notes:
- The time that the result report is available is a separate attribute than the time of the study (specimen collection).
- 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.
relevantPeriod
Relevant Period addresses the time between the start of an action to the end of an action. Each datatype using relevant period defines specific definitions for the start and stop time for the action listed.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatyperelated actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod
result
The final consequences or data collected from the datatype. results can be used in four 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:
- 100mg/dL for a lab test
- 140 mmHg for blood pressure
- as a percentage (actually as a quantity with % as units)
- as a titer or ratio (e.g., 1:4, 1:80)
- A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct reference code
- A result as a dateTime ("Assessment, Performed" and components)