-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommendation 10 updates for look-back period and 2022-compliant response #343
base: master
Are you sure you want to change the base?
Conversation
… reasoning to the documentation
…ing up the PlanDefinitions and CQL
else if GetNegativeScreeningsCount(Screenings) > 0 then | ||
'<br />*Positive for ' + Type + ': ' + | ||
Combine(GetPositiveDates(Screenings), ', ') + | ||
' (' + ToString(GetNegativeScreeningsCount(Screenings)) + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 way more readable, thanks for making that a more generic definition!
if isScreeningRecommended | ||
then 'Consider the benefits and risks of toxicology testing to assess for prescribed medications as well as other prescribed and nonprescribed controlled substances.' | ||
else if "Applicable Because of Unexpected Results" | ||
then 'Patient May Have Unexpected Toxicology Test Results' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 way more readable, thanks for making that a more generic definition!
and MR.medication is Reference or (MR.medication in "Opioid analgesics with ambulatory misuse potential" | ||
and not (MR.medication in "Non-synthetic opioid medications")) | ||
and MR.medication is Reference or (MR.medication in "Opioid Analgesics with Ambulatory Misuse Potential" | ||
and not (MR.medication in "Nonsynthetic Opioid Medications")) | ||
else |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just for myself to know: is this naming convention of capital starting letters documented anywhere?
"code": [ { | ||
"system": "http://terminology.hl7.org/CodeSystem/observation-category", | ||
"code": "laboratory" | ||
} ] | ||
} ] | ||
}, { | ||
"type": "Observation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
original observation
"code": [ { | ||
"system": "http://terminology.hl7.org/CodeSystem/observation-category", | ||
"code": "laboratory" | ||
} ] | ||
} ] | ||
}, { | ||
"type": "Observation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
first copy
"code": [ { | ||
"system": "http://terminology.hl7.org/CodeSystem/observation-category", | ||
"code": "laboratory" | ||
} ] | ||
} ] | ||
}, { | ||
"type": "Observation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2nd copy
} ] | ||
} ] | ||
}, { | ||
"type": "Observation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4x identical observations added in addition
"path": "category", | ||
"code": [ { | ||
"system": "http://terminology.hl7.org/CodeSystem/observation-category", | ||
"code": "laboratory" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also here, many identical data requirments of type Observation.
"code": [ { | ||
"system": "http://terminology.hl7.org/CodeSystem/observation-category", | ||
"code": "laboratory" | ||
} ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also here, many identical data requirements of type Observation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! The only thing that I have noticed is that there is duplicated dataRequirement definitions for the resource type "Observation" of type laboratory in the following files:
- plandefinition/opioidcds-10.json
- library/OpioidCDSREC10.json
- plandefinition/opioidcds-10-patient-view.json
- plandefinition/opioidcds-10-order-sign.json
…lement with updated strategy
… positive results
…g and fixed issue with opiate screening referencing incorrect value set
Note: this PR requires an enhancement in the cqf-ruler to be approved and merged before it will pass testing (or use the following cqf-ruler branch for testing)