Consume the CDS Hooks feedback endpoint to track clinician override reasons and improve hook card quality over time

Verified steps

1. Expose a POST /cds-services/{id}/feedback endpoint that accepts the feedback body with card UUID, outcome (accepted, overridden, ignored), and optional overrideReasons
2. Persist feedback records linked to the original hook request hookInstance for audit and analytics
3. Parse the overrideReasons array to identify coded reasons (e.g., patient-declined, alternative-treatment) for quality improvement analysis
4. Aggregate feedback metrics to compute card acceptance rate per hook type and tune alert thresholds accordingly
5. Return HTTP 200 with an empty body on successful receipt; return 400 only for malformed payloads