Symptom (QDM)

Back to Harmonization of Health Quality Information Models Page
QDM defines Symptom as 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). For a finding, there is either a source of either a temperature-measuring device together with a recorder of the device (electronically) or an individual (healthcare provider, patient, etc.).

QDM Attribute	QI Core Metadata Element	Comment
Symptom	Condition (the .clinicalstatus metadata allows conformance to the specific QDM datatype context)	QDM defaults the status to active and prevalence period provides the evidence of activity.
Prevalence Period	Condition.onset[x]	QDM matched to QI Core / FHIR for start of Prevalence Period
	Condition.abatement[x]	QDM matched to QI Core / FHIR for end of Prevalence Period
Severity	Condition.severity	QDM matched to QI Core / FHIR
Code	Condition.code	QDM matched to QI Core / FHIR
Author dateTime	Condition.assertedDate	FHIR provenance addressed author time, Condition.assertedDate may be closer to the onset of the QDM Prevalence Period. Consider - the software may default assertedDate to the date entered requiring manual editing to enter a different date. Further, does it reflect the date the assertion is made or the date the patient asserted that the condition began? Seeking guidance - due to potential ambiguity, should QDM map to FHIR provenance?
id	Condition.id	QDM matched to QI Core / FHIR
Source	Condition.asserter	QDM matched to QI Core / FHIR