Parameters
Patient | out | 0 | 1 | Patient |
Inclusion Criteria | out | 0 | 1 | boolean |
Active or In-progress Communication | out | 0 | * | Communication |
Communication Not Done | out | 0 | * | Communication |
Communication Proposal | out | 0 | * | CommunicationRequest |
Do Not Communicate Proposal | out | 0 | * | CommunicationRequest |
Rejected Do Not Communicate Proposal | out | 0 | * | CommunicationRequest |
Is Recommendation Applicable | out | 0 | 1 | boolean |
Data Requirements
Contents
text/cql
library DoNotSendMessage
using FHIR version '4.0.1'
include FHIRHelpers version '4.0.1'
context Patient
/* Recommendation not to greet the patient */
/*
NOTE: This recommendation is dramatically simplified to illustrate the general
pattern for a negative recommendation, with the ability for users to reject
the recommendation, and flexibility in how the recommendation is achieved/documented.
Specifically:
* There is no terminology, any communication request/event on any topic will do
* There is no timing, any communication request/event will do at any time
* There is no reference to participants other than the patient
* There is no relationship to a setting
* There is no relationship to an encounter or episode
* There is no relationship to a care plan
These simplifications allow the example to focus exclusively on the pattern for
not recommending and for accepting/rejecting the proposal, as well as documenting
the completion, or explicit non-performance of the event.
*/
/*
Negative recommendation:
If the activity is planned, in progress, and not documented
If stopping the activity has not been proposed
Propose the planned or in progress activity be stopped
Scenario 1: Event in progress, no proposal to stop, decision support should propose stopping
Scenario 2: Event in progress, accepted proposal to stop, decision support should not propose
Scenario 3: Event in progress, rejected proposal to stop, decision support should not propose
Scenario 4: Event planned, no proposal to stop, decision support should propose stopping
Scenario 5: Event planned, accepted proposal to stop, decision support should not propose
Scenario 6: Event planned, rejected proposal to stop, decision support should not propose
Scenario 7: Negative Event documented, decision support should not propose (nothing to do)
Scenario 8: Event completed, decision support should not propose (nothing to do)
Scenario 9: No event in progress, decision support should not propose (nothing to do)
*/
define "Inclusion Criteria":
Patient.active
define "Active or In-progress Communication":
[Communication] C
where C.status in { 'preparation', 'in-progress', 'on-hold' }
define "Communication Not Done":
[Communication] C
where C.status in { 'not-done', 'stopped' }
define "Communication Proposal":
[CommunicationRequest] R
where R.status in { 'draft', 'active', 'on-hold' }
and not (Coalesce(R.doNotPerform, false))
define "Do Not Communicate Proposal":
[CommunicationRequest] R
where R.status in { 'draft', 'active', 'on-hold' }
and R.doNotPerform
define "Rejected Do Not Communicate Proposal":
[CommunicationRequest] R
where R.status in { 'revoked' }
and R.doNotPerform
define "Is Recommendation Applicable":
"Inclusion Criteria"
and exists (
"Active or In-progress Communication"
union "Communication Proposal"
)
and not exists (
"Communication Not Done"
)
and not exists (
"Do Not Communicate Proposal"
union "Rejected Do Not Communicate Proposal"
)
Content not shown - (
application/elm+xml
, size = 29Kb)
Content not shown - (
application/elm+json
, size = 52Kb)