Pharmacy Clinical Decision Support Integration

Pharmacy Clinical Decision Support Integration

Introduction

HMIS Pharmacy supports integration with external Clinical Decision Support (CDS) engines to deliver drug-drug interaction alerts, drug-allergy contraindication warnings, and drug-food interaction guidance at the point of prescribing and dispensing. Rather than maintaining an internal interaction database — which requires continuous clinical curation and regulatory updates — HMIS connects to a customer-supplied or third-party CDS service, keeping the alert library current without dependency on the HIS vendor.

How CDS Integration Works

HMIS acts as the CDS client. The CDS engine is an external service purchased and operated by the hospital (or provided as a cloud subscription). At key clinical decision points, HMIS calls the CDS engine's API with the patient's current medication list and the proposed new drug, then displays alerts returned by the engine to the prescriber or pharmacist.

Clinician prescribes drug
        │
        ▼
HMIS sends CDS request:
  - Patient allergy profile
  - Active medication list
  - Proposed drug (AMP/VMP/VTM code)
        │
        ▼
CDS Engine evaluates:
  - Drug-drug interactions
  - Drug-allergy contraindications
  - Drug-food interactions
        │
        ▼
HMIS displays alerts:
  - Severity level (critical / major / moderate / minor)
  - Interaction description
  - Clinical recommendation
        │
        ▼
Clinician acknowledges / overrides with reason

Supported Alert Types

Alert Type	Description
Drug-Drug Interaction	Two or more active medications interact (pharmacokinetic or pharmacodynamic)
Drug-Allergy	Proposed drug matches a recorded patient allergy or cross-reactive class
Drug-Food Interaction	Drug interacts with common foods (e.g., warfarin and vitamin K-rich foods)
Duplicate Therapy	Same drug or therapeutic class already active in the patient's medication list
Contraindication	Drug contraindicated given patient's diagnosis or clinical condition

Compatible CDS Engines

HMIS is designed to integrate with industry-standard CDS engines. Compatible engines include (not limited to):

• First Databank (FDB) — widely used in hospital pharmacy systems
• Multum / Cerner Drug Database
• Micromedex (IBM)
• Lexicomp (Wolters Kluwer)
• Local / national formulary CDS services (e.g., government-run drug interaction databases)

Integration uses standard protocols: HL7 FHIR CDS Hooks, REST API, or the engine's proprietary API. The specific protocol is configured during implementation based on the engine selected by the hospital.

Configuration

CDS integration is configured by the system administrator under:

Main Menu → Administration → Integration → Clinical Decision Support

Settings include:

Setting	Description
CDS Engine URL	Base URL of the external CDS service endpoint
API Key / Credentials	Authentication credentials for the CDS service
Alert Severity Threshold	Minimum severity level to display (e.g., show Major and above only)
Override Requires Reason	Whether clinicians must document a reason to override an alert
Alert Scope	Prescribing only / Dispensing only / Both

Alert Workflow at Prescribing

1. Clinician selects a drug to prescribe.
2. HMIS calls the CDS engine with the drug code and patient context.
3. If alerts are returned, a dialog is shown before the prescription is saved.
4. The clinician must acknowledge each alert (Accept / Override).
5. Override reason is recorded in the prescription record for audit.
6. The prescription is saved with alert acknowledgement metadata.

Alert Workflow at Dispensing

1. Pharmacist opens the dispense screen for a patient.
2. On selecting a drug to dispense, HMIS re-checks against the CDS engine (second independent check).
3. Alerts are displayed. The pharmacist may contact the prescriber before dispensing.
4. Override with reason is recorded against the dispense transaction.

Patient Allergy Profile

Patient allergies recorded in HMIS (allergy entity linked to PatientEncounter) are included in every CDS request. The CDS engine cross-checks the proposed drug against the allergy list using standard drug class codes (e.g., ATC, SNOMED), ensuring cross-reactive allergies are also caught (e.g., penicillin allergy flagged on amoxicillin prescription).

Offline / Fallback Behaviour

If the CDS engine is unreachable:

• A warning banner is displayed to the clinician indicating CDS is unavailable.
• Prescribing and dispensing may proceed (configured per hospital policy — some hospitals require a mandatory hold).
• All transactions during CDS downtime are flagged in the audit log for retrospective review.

Technical Reference

Item	Detail
Integration style	External REST/FHIR CDS Hooks — hospital provides engine
Configuration	Admin → Integration → Clinical Decision Support
Patient allergy source	Allergy records linked to PatientEncounter
Drug code standard	AMP/VMP/VTM codes; maps to ATC / SNOMED ct for CDS engine
Alert acknowledgement	Stored against prescription and dispense transaction
Related	Pharmacy Formulary Management, Pharmacy Dispensing Workflows