Why “No Record Found” Does Not Mean Safe

Missing data must be represented as dataset absence, not a clinical all-clear.

Separate database absence from reality

Separate database absence from reality is the first design decision for no drug interaction found. Missing data must be represented as dataset absence, not a clinical all-clear. Write the boundary down before choosing endpoints or drawing clinical-looking UI so reviewers can test the actual promise.

Design precise copy

For no drug interaction found, design precise copy should remain observable rather than becoming hidden adapter behavior. Give resolution, lookup, and interpretation separate states, then decide which failures a user may retry.

Propagate status through clients

Propagate status through clients needs an operational test, not only a happy-path example. Add a bounded timeout, stable error handling, request IDs, privacy-safe logging, and a fixture that proves the no drug interaction found workflow fails closed.