Short answer: Use staged retrieval with explicit collections, bounded queries, and source context that survives reranking; a healthcare appointment assistant should not promote a result that an operator cannot trace to a URL or document ID. Choose the product only after writing that retrieval contract, its timeout budget, and its deletion procedure.
That order matters in B2B healthcare SaaS. A plausible appointment answer delivered from stale or untraceable context is harder to review than an empty result. The ranking layer has two jobs: improve relevance and preserve the evidence needed to inspect the answer later. Relevance alone isn't the acceptance criterion.
What retrieval architecture and ranking signals should a healthcare appointment assistant use?
Use three stages: retrieve from a named collection, reject candidates that violate the contract, then rerank the remaining bounded set. The contract should require a source URL or stable document identifier on every candidate.β¦