Document: MedCheck User Guide
Audience: Doctors and Nurses
Version: 1.0
Updated: 18 May 2026

MedCheck: Smart Prescription Interaction and Clinical Safety Scanner

MedCheck is an asynchronous, real-time safety engine that evaluates each prescription item during entry. It cross-references active ingredients against patient history, allergy records, and retainership rules, then presents clear risk indicators so clinicians can act quickly and safely.

Real-time ingredient checks Allergy and interaction detection Retainership compliance validation Supervisor-audited override protocol

1) Module Overview and Value Proposition

During electronic prescription entry, MedCheck starts safety evaluation automatically after each medication line update. This allows the prescriber to see risks while still in the e-Rx drawer, without waiting for post-submit checks.

What MedCheck Cross-References

  • Active target ingredients against current active medication profile.
  • Ingredient classes against documented clinical allergens.
  • Total prescription burden against corporate retainership caps and exclusions.
  • Contextual dosage concerns where risk labels are available.

Clinical Safety Velocity Impact

  • Faster risk visibility at point-of-entry rather than after submission.
  • Reduced avoidable back-and-forth between prescribing and nursing teams.
  • Traceable clinical decisions with structured safety context.
  • Higher confidence in high-pressure prescribing moments.
Safety Layer Validation Logic Expected Indicator Outcome
Drug Interaction Layer Ingredient-to-active-medication conflict and severity map Green, Amber, or Red based on interaction grade
Allergy Layer Ingredient class matching against allergy matrix Amber for caution class, Red for severe known allergen
Retainership Layer Coverage restrictions and cap consumption checks Amber for restricted or partially covered cost events

2) Step-by-Step Prescription Workflow

2.1 Populate the e-Rx Drawer

  1. Open patient encounter and launch Add Prescription.
  2. Enter medication line item (drug, strength, route, frequency, duration).
  3. Observe MedCheck HUD updates as each field is entered or edited.
  4. Review risk tier, recommendation, and supporting warning text.
  5. Proceed with save when status and context are clinically acceptable.
Trigger behavior: MedCheck evaluates asynchronously at item-change events. Clinicians can continue typing while checks complete, and indicators refresh in near real time as scan results return.

2.2 [UI Wireframe Box] e-Prescription and MedCheck HUD

2.3 [Status Flag Indicator Component Block]

GREEN - Safe / Clear
  • No major interaction found.
  • No known severe allergy conflict.
  • No retainership restriction breach.
  • Action: Save prescription normally.
AMBER - Caution / Restriction
  • Non-critical interaction or policy warning.
  • Retainership cap or exclusion impact identified.
  • Action: Acknowledge warning and continue with documented rationale.
RED - Hard Blocker / Severe Allergy
  • Severe allergy or high-risk contraindication detected.
  • Save path is safety-locked by default.
  • Action: Start emergency override protocol with supervisor authorization.

3) Overriding a Safety Lock

Use Emergency Override Bypass only when immediate clinical judgment indicates that patient benefit outweighs flagged risk, and an authorized supervisor is available to review and approve.

Emergency Override Bypass Protocol

  1. Open flagged medication row and select Request Override.
  2. Review risk statement with patient-specific context.
  3. Enter structured clinical justification and mitigation plan.
  4. Supervisor authenticates and records approval decision.
  5. If approved, submit prescription within override validity window.

Supervisor Audit Trail Elements

  • Requesting clinician ID and timestamp.
  • Approving supervisor ID and role.
  • Risk class and flagged rule identifiers.
  • Entered clinical rationale and planned monitoring action.
  • Final outcome: approved, denied, or expired.

3.1 Override and Audit Sequence (Illustrative Workflow)

Compliance note: Every override should include a concise risk-benefit statement, a mitigation action (for example, monitoring instruction), and the approving supervisor identity. This preserves legal and operational traceability.