This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Symptom (QDM)"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[http://wiki.hl7.org/index.php?title=Harmonization_of_Health_Quality_Information_models Back to Harmonization of Health Quality Information Models Page]
+
[http://wiki.hl7.org/index.php?title=Harmonization_of_Health_Quality_Information_models Back to Harmonization of Health Quality Information Models Page] <br><br>
 +
This QDM to QI Core Mapping for the QDM Datatype "Symptom" was reviewed by the CQI WG on March 30, 2018 based on QDM version 5.3. There is no change in the structure of "Symptom" in QDM version 5.4. QDM version 5.4 includes the guidance, "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.4 retains the QDM datatype, Symptom, for clarity of expression in the human readable eCQM."<br> <br>
 +
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.).
 +
* Note: Definitions regarding symptom on the FHIR condition resource (http://hl7.org/fhir/condition.html):
 +
# Use the Observation resource when a symptom is resolved without long term management, tracking, or when a symptom contributes to the establishment of a condition.
 +
# Use Condition when a symptom requires long term management, tracking, or is used as a proxy for a diagnosis or problem that is not yet determined.
 +
* The QDM User Group will review the use of the Symptom QDM datatype.  For now, the mapping below, references symptom as an observation (option 1 above).
 +
<br>
 +
__FORCETOC__
 +
==Symptom==
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
| align="center" style="background:#f0f0f0;"|'''QDM Attribute'''
 
| align="center" style="background:#f0f0f0;"|'''QDM Attribute'''
Line 7: Line 16:
  
 
| row1cell1 | Symptom
 
| row1cell1 | Symptom
−
| row1cell2 | Condition (the .clinicalstatus metadata allows conformance to the specific QDM datatype context)
+
| row1cell2 | Symptom maps to Observation [Observation.status]
−
| row1cell3 | QDM defaults the status to active and prevalence period provides the evidence of activity.
+
| row1cell3 | Constrain status as “final”
 
|-
 
|-
 
| row2cell1 | Prevalence Period
 
| row2cell1 | Prevalence Period
−
| row2cell2 | Condition.onset[x]
+
| row2cell2 | Observation.effective(x)
−
| row2cell3 | QDM matched to QI Core / FHIR for start of Prevalence Period
+
| row2cell3 | Observation.effective(x) The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time".  
−
|-
 
−
| row2cell1 |
 
−
| row2cell2 | Condition.abatement[x]
 
−
| row2cell3 | QDM matched to QI Core / FHIR for end of Prevalence Period
 
 
|-
 
|-
 
| row2cell1 | Severity
 
| row2cell1 | Severity
−
| row2cell2 | Condition.severity
+
| row2cell2 | There is no clear observation severity concept in the FHIR observation resource
−
| row2cell3 | QDM matched to QI Core / FHIR
+
| row2cell3 | Consider the value set binding may allow a measure developer to indicate symptom severity as a pre-coordinated concept or set of concepts
 
|-
 
|-
 
| row2cell1 | Code
 
| row2cell1 | Code
−
| row2cell2 | Condition.code
+
| row2cell2 | Observation.code
 
| row2cell3 | QDM matched to QI Core / FHIR
 
| row2cell3 | QDM matched to QI Core / FHIR
−
|-
 
−
| row2cell1 | Author dateTime
 
−
| row2cell2 | Condition.assertedDate
 
−
| row2cell3 | 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?
 
 
|-
 
|-
 
| row2cell1 | id
 
| row2cell1 | id
−
| row2cell2 | Condition.id
+
| row2cell2 | Observation.id
 
| row2cell3 | QDM matched to QI Core / FHIR
 
| row2cell3 | QDM matched to QI Core / FHIR
 
|-
 
|-
 
| row2cell1 | Source
 
| row2cell1 | Source
−
| row2cell2 | Condition.asserter
+
| row2cell2 | Observation.performer
 
| row2cell3 | QDM matched to QI Core / FHIR
 
| row2cell3 | QDM matched to QI Core / FHIR
 
|}
 
|}

Latest revision as of 19:09, 7 June 2018

Back to Harmonization of Health Quality Information Models Page

This QDM to QI Core Mapping for the QDM Datatype "Symptom" was reviewed by the CQI WG on March 30, 2018 based on QDM version 5.3. There is no change in the structure of "Symptom" in QDM version 5.4. QDM version 5.4 includes the guidance, "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.4 retains the QDM datatype, Symptom, for clarity of expression in the human readable eCQM."

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.).

  1. Use the Observation resource when a symptom is resolved without long term management, tracking, or when a symptom contributes to the establishment of a condition.
  2. Use Condition when a symptom requires long term management, tracking, or is used as a proxy for a diagnosis or problem that is not yet determined.
  • The QDM User Group will review the use of the Symptom QDM datatype. For now, the mapping below, references symptom as an observation (option 1 above).


Contents

Symptom

QDM Attribute QI Core Metadata Element Comment
Symptom Symptom maps to Observation [Observation.status] Constrain status as “final”
Prevalence Period Observation.effective(x) Observation.effective(x) The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time".
Severity There is no clear observation severity concept in the FHIR observation resource Consider the value set binding may allow a measure developer to indicate symptom severity as a pre-coordinated concept or set of concepts
Code Observation.code QDM matched to QI Core / FHIR
id Observation.id QDM matched to QI Core / FHIR
Source Observation.performer QDM matched to QI Core / FHIR
Retrieved from "https://wiki.hl7.org/w/index.php?title=Symptom_(QDM)&oldid=157996"