\n \n \n \n library DoNotSendMessage\n\nusing FHIR version '4.0.1'\n\ninclude FHIRHelpers version '4.0.1'\n\ncodesystem \"Task Codes\": 'http://hl7.org/fhir/CodeSystem/task-code'\n\ncode \"fulfill\": 'fulfill' from \"Task Codes\" display 'Fulfill'\n\ncontext Patient\n\n/* Recommendation not to greet the patient */\n\n/*\nNOTE: This recommendation is dramatically simplified to illustrate the general\npattern for a negative recommendation, with the ability for users to reject\nthe recommendation, and flexibility in how the recommendation is achieved/documented.\n\nSpecifically:\n* There is no terminology, any communication request/event on any topic will do\n* There is no timing, any communication request/event will do at any time\n* There is no reference to participants other than the patient\n* There is no relationship to a setting\n* There is no relationship to an encounter or episode\n* There is no relationship to a care plan\n\nThese simplifications allow the example to focus exclusively on the pattern for\nnot recommending and for accepting/rejecting the proposal, as well as documenting\nthe completion, or explicit non-performance of the event.\n*/\n\n/*\nNegative recommendation:\n\nIf the activity is planned, in progress, and not documented\n If stopping the activity has not been proposed\n Propose the planned or in progress activity be stopped\n\nScenario 1: Event in progress, no proposal to stop, decision support should propose stopping\nScenario 2: Event in progress, accepted proposal to stop, decision support should not propose\nScenario 3: Event in progress, rejected proposal to stop, decision support should not propose\nScenario 4: Event planned, no proposal to stop, decision support should propose stopping\nScenario 5: Event planned, accepted proposal to stop, decision support should not propose\nScenario 6: Event planned, rejected proposal to stop, decision support should not propose\nScenario 7: Negative Event documented, decision support should not propose (nothing to do)\nScenario 8: Event completed, decision support should not propose (nothing to do)\nScenario 9: No event in progress, decision support should not propose (nothing to do)\n*/\n\ndefine \"Inclusion Criteria\":\n Patient.active\n\ndefine \"Active or In-progress Communication\":\n [Communication] C\n where C.status in { 'preparation', 'in-progress', 'on-hold' }\n\ndefine \"Communication Not Done\":\n [Communication] C\n where C.status in { 'not-done', 'stopped' }\n\ndefine \"Rejected Task\":\n [Task] T\n where T.code ~ \"fulfill\"\n and T.status = 'rejected'\n\ndefine \"Communication Proposal\":\n [CommunicationRequest] R\n without \"Rejected Task\" T\n such that R.id = Last(Split(T.focus.reference, '/'))\n where R.status in { 'draft', 'active', 'on-hold' }\n and R.doNotPerform is not true\n\ndefine \"Communication Prohibited\":\n [CommunicationRequest] R\n without \"Rejected Task\" T\n such that R.id = Last(Split(T.focus.reference, '/'))\n where R.status in { 'draft', 'active', 'on-hold' }\n and R.doNotPerform is true\n\ndefine \"Communication Prohibited Rejected\":\n [CommunicationRequest] R\n with \"Rejected Task\" T\n such that R.id = Last(Split(T.focus.reference, '/'))\n where R.status in { 'active' }\n and R.doNotPerform is true\n\ndefine \"Is Recommendation Applicable\":\n \"Inclusion Criteria\"\n and exists (\n \"Active or In-progress Communication\"\n union \"Communication Proposal\"\n )\n and not exists (\n \"Communication Not Done\"\n )\n and not exists (\n \"Communication Prohibited\"\n union \"Communication Prohibited Rejected\"\n )\n
\n | \n
\n \n \n \n