This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Condition/Diagnosis/Problem (QDM)"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
  
 
| row1cell1 | Diagnosis
 
| row1cell1 | Diagnosis
| row1cell2 | Condition (the .clinicalstatus metadata allows conformance to the specific QDM datatype context)
+
| row1cell2 | Condition (the Condition.clinicalStatus metadata allows conformance to the specific QDM datatype context)
| row1cell3 | QDM defaults the status to active and prevalence period provides the evidence of activity.
+
| row1cell3 | QDM defaults the status to active and prevalence period provides the evidence of activity. Note: The FHIR Condition resource does not specify a status for Condition.clinicalStatus; however, the QDM datatype Diagnosis default state is "active"; hence, the Condition.clinicalStatus should be constrained to "active". Also, the Condition.verificationStatus should be constrained to "confirmed".
 
|-
 
|-
 
| row2cell1 | Prevalence Period
 
| row2cell1 | Prevalence Period
Line 36: Line 36:
 
|-
 
|-
 
| row2cell1 | Author dateTime
 
| row2cell1 | Author dateTime
| row2cell2 | FHIR Provenance.recorded
+
| 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?
+
| row2cell3 | QDM matched to QI Core / FHIR
 
|-
 
|-
 
| row2cell1 | id
 
| row2cell1 | id

Revision as of 03:56, 28 November 2018

Back to Harmonization of Health Quality Information Models Page

This QDM to QI Core Mapping for the QDM Datatype "Diagnosis" was reviewed by the CQI WG on March 30, 2018 for QDM version 5.3. There are no changes in "Condition/Diagnosis/Problem" in QDM version 5.4.

QDM defines Condition/Diagnosis/Problem as a practitioner’s identification of a patient’s disease, illness, injury, or condition. This category contains a single datatype to represent all of these concepts: Diagnosis. A practitioner determines the diagnosis by means of examination, diagnostic test results, patient history, and/or family history. Diagnoses are usually considered unfavorable, but may also represent neutral or favorable conditions that affect a patient’s plan of care (e.g., pregnancy).

Condition/Diagnosis/Problem

QDM Attribute QI Core Metadata Element Comment
Diagnosis Condition (the Condition.clinicalStatus metadata allows conformance to the specific QDM datatype context) QDM defaults the status to active and prevalence period provides the evidence of activity. Note: The FHIR Condition resource does not specify a status for Condition.clinicalStatus; however, the QDM datatype Diagnosis default state is "active"; hence, the Condition.clinicalStatus should be constrained to "active". Also, the Condition.verificationStatus should be constrained to "confirmed".
Prevalence Period Condition.onset[x], OR Condition.asserted Use whichever is the earlier date. 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
Anatomical Location Site Condition.bodySite QDM matched to QI Core / FHIR
Severity Condition.severity QDM matched to QI Core / FHIR
Code Condition.code QDM matched to QI Core / FHIR
Author dateTime Condition.assertedDate QDM matched to QI Core / FHIR
id Condition.id QDM matched to QI Core / FHIR
Source Condition.asserter QDM matched to QI Core / FHIR