Hide
Proposed solution
CURRENT LOGIC:
define "Encounter with Atrial Ablation Procedure"
TJC."Ischemic Stroke Encounter" IschemicStrokeEncounter
with ["Procedure, Performed": "Atrial Ablation"] AtrialAblation
such that Global."NormalizeInterval" ( AtrialAblation.relevantDatetime, AtrialAblation.relevantPeriod ) starts before start of IschemicStrokeEncounter.relevantPeriod
PROPOSED LOGIC:
define "Encounter with Atrial Ablation Procedure"
TJC."Ischemic Stroke Encounter" IschemicStrokeEncounter
with ( ["Procedure, Performed": "Atrial Ablation"]
union ["Procedure, Performed": "History of Atrial Ablation Procedure"]) AtrialAblation
such that Global."NormalizeInterval" ( AtrialAblation.relevantDatetime, AtrialAblation.relevantPeriod ) starts before start of IschemicStrokeEncounter.relevantPeriod
The measure developer is looking for feedback as to whether the above changes is most appropriate for how to structure the logic, using the SNOMED-CT codes listed below, or if there is an alternate QDM classification that is more appropriate to apply to SNOMED-CT codes of the 'situation' semantic tag.
Create new value set for "History of Atrial Ablation" including the following SNOMED-CT concepts:
427951003 - History of radiofrequency ablation operation for arrhythmia
429756009 - History of radiofrequency ablation operation on left atrium for arrhythmia
429508000 - History of ablation of atrioventricular node
Rationale for change
There are additional codes to capture a history of an ablation procedure that are not currently applied to the measure's denominator. However, these situation SNOMEDCT codes capture the history of an ablation to the AV node or for arrhythmia, not a procedure as is currently specified in the logic. The measure developer is looking for feedback on what is the most appropriate way to capture this within the technical specification using the Quality Data Model.
Show
Proposed solution
CURRENT LOGIC:
define "Encounter with Atrial Ablation Procedure"
TJC."Ischemic Stroke Encounter" IschemicStrokeEncounter
with ["Procedure, Performed": "Atrial Ablation"] AtrialAblation
such that Global."NormalizeInterval" ( AtrialAblation.relevantDatetime, AtrialAblation.relevantPeriod ) starts before start of IschemicStrokeEncounter.relevantPeriod
PROPOSED LOGIC:
define "Encounter with Atrial Ablation Procedure"
TJC."Ischemic Stroke Encounter" IschemicStrokeEncounter
with ( ["Procedure, Performed": "Atrial Ablation"]
union ["Procedure, Performed": "History of Atrial Ablation Procedure"]) AtrialAblation
such that Global."NormalizeInterval" ( AtrialAblation.relevantDatetime, AtrialAblation.relevantPeriod ) starts before start of IschemicStrokeEncounter.relevantPeriod
The measure developer is looking for feedback as to whether the above changes is most appropriate for how to structure the logic, using the SNOMED-CT codes listed below, or if there is an alternate QDM classification that is more appropriate to apply to SNOMED-CT codes of the 'situation' semantic tag.
Create new value set for "History of Atrial Ablation" including the following SNOMED-CT concepts:
427951003 - History of radiofrequency ablation operation for arrhythmia
429756009 - History of radiofrequency ablation operation on left atrium for arrhythmia
429508000 - History of ablation of atrioventricular node
Rationale for change
There are additional codes to capture a history of an ablation procedure that are not currently applied to the measure's denominator. However, these situation SNOMEDCT codes capture the history of an ablation to the AV node or for arrhythmia, not a procedure as is currently specified in the logic. The measure developer is looking for feedback on what is the most appropriate way to capture this within the technical specification using the Quality Data Model.