Clinical Practice Guidelines
2.0.0 - STU2 International flag

This page is part of the Clinical Guidelines (v2.0.0: STU2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Library: Document Medication Library (Experimental)

Official URL: http://hl7.org/fhir/uv/cpg/Library/documentmedication-library Version: 2.0.0
Active as of 2024-11-26 Computable Name: DocumentMedicationLibrary
Other Identifiers: OID:2.16.840.1.113883.4.642.40.48.28.6

Logic for an example recommendation to document a medication

Generated Narrative: Library documentmedication-library

Related Artifacts

Depends OnCode System Activity TypeCPG Activity Type Code System

Parameters

Patientout01Patient
Medication Orderout0*MedicationRequest
Inclusion Criteriaout01boolean
Active or Completed Medication Statementout0*MedicationStatement
Medication Statement Not Takenout0*MedicationStatement
Document Proposalout0*Task
Document Proposal Rejectedout0*Task
Is Recommendation Applicableout01boolean

Data Requirements

Type: MedicationRequest (MedicationRequest)
Type: MedicationStatement (MedicationStatement)
Type: MedicationStatement (MedicationStatement)
Type: Task (Task)
Type: Task (Task)

Contents

text/cql

library DocumentMedication

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-cs'

code "Document medication": 'document-medication' from "Activity Type"

context Patient

/* Recommendation to document an existing order for a medication */

/*
Positive recommendation:

If the medication has been ordered but has not been documented
  Propose documenting 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 request, decision support should propose
Scenario 2: No event, active 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, active 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 Order")

define "Active or Completed Medication Statement":
  [MedicationStatement] M
    where M.status in { 'active', 'completed', 'intended', 'on-hold' }

define "Medication Statement Not Taken":
  [MedicationStatement] M
    where M.status in { 'not-taken', 'stopped' } // TODO: Is 'stopped' appropriate here?

define "Medication Order":
  [MedicationRequest] M
    where M.status in { 'draft', 'active', 'on-hold', 'completed' }
      and M.intent = 'order'
      and M.doNotPerform is not true

define "Document Proposal":
  [Task] R
    where R.code ~ "Document medication"
      and R.status in { 'draft', 'requested', 'received', 'accepted', 'ready' }
      and doNotPerform(R) is not true

define "Document Proposal Rejected":
  [Task] R
    where R.code ~ "Document medication"
      and R.status in { 'rejected' }
      and doNotPerform(R) is not true

define "Is Recommendation Applicable":
  "Inclusion Criteria"
    and not exists (
      "Active or Completed Medication Statement"
        union "Medication Statement Not Taken"
    )
    and not exists (
      "Document Proposal"
        union "Document Proposal Rejected"
    )

define function doNotPerform(task Task):
  singleton from (
    task.modifierExtension E
      where E.url = 'http://hl7.org/fhir/StructureDefinition/request-doNotPerform'
  ).value as boolean

Content not shown - (application/elm+xml, size = 40Kb )

Content not shown - (application/elm+json, size = 73Kb )