QDM Datatype (QDM Version 5.5 Guidance Update):
Data elements that meet criteria using this datatype should document the symptom and its corresponding value set.
- The prevalencePeriod references the time from the onset date to the abatement date.
- 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 null, then the symptom is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for whether the symptom was active for the time frame indicated by the timing relationships.
QDM Category (QDM Version 5.5 Guidance Update)
Symptom represents an indication that a person has a condition or disease. Some examples are headache, fever, fatigue, nausea, vomiting, and pain. Also, symptoms are subjective manifestations of the disease perceived by the patient. As an example to differentiate symptom from finding, the patient's subjective symptom of fever is distinguished from the temperature (a finding). A finding could reference a temperature-measuring device and a recorder. The recorder could be the device (with electronic data capture) or an individual (healthcare provider, patient, etc.). Note that while many symptoms are entered as findings as part of assessments and, therefore, may not be included in a specific EHR "symptom" section, QDM 5.5 retains the QDM datatype, "Symptom", for clarity of expression in the human readable eCQM.
Data Elements defined by this QDM Datatype: