Skip to content

NDP Services Architecture Review

Healthcare Professional & Software Architecture Perspective

Critical Issues Identified

1. MISSING CRITICAL SERVICES

❌ D2D (Drug-Drug Interaction) Service - CRITICAL

Status: Listed as "Planned" but this is ESSENTIAL for patient safety Healthcare Impact:

  • Drug-drug interactions cause 20% of adverse drug events
  • Can be FATAL (e.g., Warfarin + NSAIDs = bleeding risk)
  • Required BEFORE prescribing, not after

Fix: Must be integrated INTO Prescription Service validation, not separate

❌ Insurance/Coverage Verification Service - MISSING

Healthcare Reality:

  • Egypt uses Universal Health Insurance System (UHIS)
  • Need real-time eligibility checking
  • Copayment calculation
  • Prior authorization workflows

❌ Notification Service - Underspecified

Current: Generic "SMS/Email/Push" Healthcare Needs:

  • Patient: Prescription ready, refill reminders
  • Prescriber: Alerts for high-risk interactions
  • Pharmacy: Stock availability alerts
  • MOH: Public health alerts (drug recalls)

2. PRESCRIPTION SERVICE ISSUES

Issue: Partial Dispensing Logic

Current: Mentions support but not detailed Healthcare Reality:

  • Chronic medications: Often 30-90 day supply
  • Insurance may cover only 30 days at a time
  • Pharmacy may not have full quantity
  • Need: Track cumulative dispensed vs prescribed

Fix Needed:

typescript
interface PrescriptionItem {
  quantityPrescribed: number;
  quantityDispensed: number;      // Total dispensed
  remainingQuantity: number;       // Calculated
  dispensingEvents: DispenseEvent[]; // History
  allowPartialDispensing: boolean;
  maximumDispenses: number;        // e.g., 3 refills
  dispensesRemaining: number;
}

Issue: Prescription Validity Rules Too Simple

Current: "30-90 days" Healthcare Reality:

  • Controlled substances: 7-30 days max
  • Chronic conditions: 90-180 days
  • Antibiotics: No refills allowed
  • Psychiatric medications: 30 days, monthly review

Fix: Category-based validity rules

Issue: Missing Clinical Decision Support

Current: Basic validation only Healthcare Needs:

  • Allergy checking (CRITICAL)
  • Renal dosing adjustments
  • Hepatic dosing adjustments
  • Age-based dosing (pediatric/geriatric)
  • Pregnancy/lactation warnings
  • Duplicate therapy checking

3. MEDICINE DIRECTORY ISSUES

Issue: Missing FHIR Medication Resource

Current: Custom data model Standard: Should use FHIR R4 Medication resource Impact: Interoperability with international systems

Issue: Missing Essential Drug Data

Healthcare Needs:

  • Therapeutic equivalence (generic substitution rules)
  • Bioequivalence data
  • Storage requirements (refrigeration, etc.)
  • Administration routes
  • Dosage forms mapping
  • Unit conversions (mg/ml/units)

Issue: Drug Classification Too Simple

Current: Single category Healthcare Reality needs:

  • ATC (Anatomical Therapeutic Chemical) classification
  • Egyptian Drug Schedule (I, II, III, IV, controlled substances)
  • UHIS formulary status
  • Hospital vs community only
  • Requires prior authorization

4. PATIENT REGISTRY ISSUES

Issue: Missing Clinical Data

Current: Demographics only Healthcare Needs:

  • Allergies (CRITICAL - cross-service)
  • Chronic conditions
  • Pregnancy status
  • Renal function (CrCl)
  • Hepatic function
  • Weight/BMI (for dosing)

Security: This is PHI - needs encryption at rest AND in transit

Healthcare Reality:

  • GDPR-like consent for data sharing
  • Consent for specific providers
  • Consent for research
  • Right to be forgotten
  • Audit of who accessed data

5. HPR REGISTRY ISSUES

Issue: Missing Prescribing Authority Details

Current: Boolean "canPrescribe" Healthcare Reality:

  • Controlled substance DEA-like number
  • Specialty-specific permissions (e.g., only oncologists prescribe chemotherapy)
  • Facility-specific privileges
  • Temporary vs permanent license
  • Supervision requirements (residents)

Issue: Missing Facility Capabilities

Current: Basic facility data Healthcare Needs:

  • Emergency department?
  • ICU capability?
  • Specialty services
  • Formulary restrictions
  • Insurance contracts

6. DISPENSE SERVICE ISSUES

Issue: Missing Inventory Integration

Healthcare Reality:

  • Pharmacy needs real-time stock check
  • Reserve medication on prescription creation
  • Expiry date tracking (FIFO)
  • Batch/lot number tracking (for recalls)

Issue: Missing Insurance Adjudication

Current: Basic payment info Healthcare Reality:

  • Real-time insurance claim
  • Prior authorization check
  • Copayment calculation
  • Rejected claims workflow
  • Patient assistance programs

7. AUDIT SERVICE ISSUES

Issue: Audit Data Model Too Generic

Healthcare Compliance Needs:

  • HIPAA/GDPR-like requirements
  • "Break the glass" emergency access
  • Minimum necessary access principle
  • Data retention: 7-10 years
  • Tamper-proof storage

8. MISSING SERVICES

A. Clinical Decision Support Service (CDSS)

Purpose:

  • Drug-drug interactions
  • Drug-allergy checking
  • Dosing calculators
  • Clinical guidelines
  • Drug recall alerts

B. Insurance/Coverage Service

Purpose:

  • Eligibility verification
  • Prior authorization
  • Copayment calculation
  • Claims processing
  • Coverage rules

C. Analytics & Reporting Service

Purpose:

  • Public health surveillance
  • Drug utilization review
  • Antibiotic stewardship
  • Opioid monitoring
  • Prescribing patterns

D. Master Data Management Service

Purpose:

  • ICD-10 diagnosis codes
  • LOINC lab codes
  • SNOMED CT clinical terms
  • Unified code mapping

ARCHITECTURAL ISSUES

1. No FHIR Compliance

Current: Custom APIs Healthcare Standard: HL7 FHIR R4 Impact: Cannot integrate with international systems, EMRs

Fix: Map all services to FHIR resources:

  • Prescription → MedicationRequest
  • Dispense → MedicationDispense
  • Patient → Patient resource
  • Provider → Practitioner resource

2. Missing External Integrations

Healthcare Reality Needs:

  • EDA (Egyptian Drug Authority) - real-time drug database
  • MOH - public health reporting
  • UHIS - insurance eligibility
  • International drug databases (FDA, EMA for imports)
  • SMS gateways (for patient notifications)
  • Payment gateways (for copayments)

3. Security Architecture Gaps

Missing:

  • End-to-end encryption for PHI
  • Data masking for non-clinical staff
  • Role-based access control (RBAC) details
  • Audit of all data access
  • Automatic session timeout
  • Two-factor authentication for prescribers
  • Digital signature for prescriptions

4. Missing Workflows

Prescription Modification Workflow

Healthcare Reality:

  • Prescriber wants to change dose
  • Can't edit - must cancel and create new
  • Need: Amendment workflow with audit trail

Drug Recall Workflow

Healthcare Reality:

  • EDA issues recall
  • Need to: Identify affected prescriptions
  • Notify prescribers and patients
  • Provide alternatives

Prior Authorization Workflow

Healthcare Reality:

  • High-cost drugs need insurance approval
  • Prescriber submits justification
  • Insurance reviews
  • Approval/denial with alternative

5. Performance & Scale Issues

Current Resource Estimates Too Low

Healthcare Reality:

  • Egypt: 100M+ population
  • 200K+ prescribers
  • 30K+ pharmacies
  • Expected: 100M+ prescriptions/year
  • Peak: 500K prescriptions/day

Current Estimates:

  • Prescription Service: 1000 req/s
  • This is only 86M/day - INSUFFICIENT

Realistic Needs:

  • 5000 req/s sustained
  • 10000 req/s peak
  • Need caching, read replicas, sharding

6. Data Consistency Issues

Missing Distributed Transaction Handling

Problem:

  • Prescription created in Prescription Service
  • Patient data from Patient Registry
  • Drug data from Medicine Directory
  • What if Patient Registry is down?

Need: Saga pattern or event sourcing

RECOMMENDATIONS

Immediate (P0 - Safety Critical)

  1. Integrate D2D checking INTO Prescription Service

    • Cannot prescribe without checking
    • Blocking validation
  2. Add Allergy Checking

    • Patient allergies in Patient Registry
    • Cross-checked on prescription creation
  3. Add Consent Management

    • GDPR compliance
    • Patient data access control
  4. Add Insurance Service

    • Real-time eligibility
    • Cannot dispense without coverage check
  5. Enhance Audit Service

    • Healthcare-specific compliance
    • Immutable, tamper-proof

High Priority (P1)

  1. Add Clinical Decision Support Service
  2. FHIR Compliance Layer
  3. Add Notification Service with templates
  4. Add Analytics Service
  5. Enhance security architecture

Medium Priority (P2)

  1. Add Master Data Management
  2. Add Prior Authorization Workflow
  3. Add Drug Recall Workflow
  4. Performance optimization

Documentation Priorities

  1. Update Prescription Service - Add D2D, allergies, clinical validation
  2. Create Insurance Service doc - New service
  3. Create CDSS Service doc - New service
  4. Update Patient Registry - Add clinical data, consent
  5. Update Medicine Directory - FHIR compliance, extended data
  6. Create Analytics Service doc - New service
  7. Update all services - FHIR mappings