Library-AdministerMedication
Formats: XML, JSON, Turtle
Related Artifacts
depends-on | http://hl7.org/fhir/Library/FHIR-ModelInfo|4.0.1 |
depends-on | http://hl7.org/fhir/Library/FHIRHelpers|4.0.1 |
depends-on | CPG Activity Type |
Parameters
Patient | out | 0 | 1 | Patient |
Medication Proposal | out | 0 | * | MedicationRequest |
Medication Not Proposed | out | 0 | * | MedicationRequest |
Inclusion Criteria | out | 0 | 1 | boolean |
Active or Completed Medication Administration | out | 0 | * | MedicationAdministration |
Medication Administration Not Done | out | 0 | * | MedicationAdministration |
Administer Proposal | out | 0 | * | Task |
Administer Proposal Rejected | out | 0 | * | Task |
Is Recommendation Applicable | out | 0 | 1 | boolean |
Data Requirements
Contents
text/cql
library AdministerMedication
using FHIR version '4.0.1'
include FHIRHelpers version '4.0.1'
codesystem "Activity Type": 'http://hl7.org/fhir/uv/cpg/CodeSystem/cpg-activity-type'
code "Administer medication": 'administer-medication' from "Activity Type"
context Patient
/* Recommendation to administer an existing order for a medication */
/*
Positive recommendation:
If the medication has been ordered but has not been administered
Propose administering the medication
Given a proposal, the user can:
Accept the proposal
Ignore the proposal
Reject the proposal without reason
Reject the proposal with reason
Scenario 1: No event, no plan or proposal, decision support should propose
Scenario 2: No event, incomplete proposal, decision support should not propose
Scenario 3: No event, rejected proposal, decision support should not propose
Scenario 4: Event, no proposal, decision support should not propose
Scenario 5: Event, proposal, decision support should not propose
Scenario 6: Event not done, no proposal, decision support should not propose
Scenario 7: Event not done, proposal, decision support should not propose
*/
define "Inclusion Criteria":
Patient.active
and exists ("Medication Proposal")
and not exists ("Medication Not Proposed")
define "Active or Completed Medication Administration":
[MedicationAdministration] M
where M.status in { 'in-progress', 'on-hold', 'completed' }
define "Medication Administration Not Done":
[MedicationAdministration] M
where M.status in { 'not-done', 'stopped' } // TODO: Is 'stopped' appropriate here?
define "Medication Proposal":
[MedicationRequest] M
where M.status in { 'draft', 'active', 'on-hold', 'completed' }
define "Medication Not Proposed":
[MedicationRequest] M
where M.status in { 'cancelled', 'stopped' }
define "Administer Proposal":
[Task] R
where R.code ~ "Administer medication"
and R.status in { 'draft', 'requested', 'received', 'accepted', 'ready' }
and not Coalesce(doNotPerform(R), false)
define "Administer Proposal Rejected":
[Task] R
where R.code ~ "Administer medication"
and R.status in { 'rejected' }
and not Coalesce(doNotPerform(R), false)
define "Is Recommendation Applicable":
"Inclusion Criteria"
and not exists (
"Active or Completed Medication Administration"
union "Medication Administration Not Done"
)
and not exists (
"Administer Proposal"
union "Administer Proposal Rejected"
)
define function doNotPerform(task Task):
singleton from (
task.extension E
where E.url = 'http://hl7.org/fhir/StructureDefinition/request-doNotPerform'
).value as boolean
Content not shown - (
application/elm+xml
, size = 15Kb)
Content not shown - (
application/elm+json
, size = 28Kb)