Why should you care?

Clinicians need speed; hospitals need safety — assistant accelerates lookup without autonomous treatment decisions.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Api/Controllers/HospitalAssistantController.cs
[ApiController]
[Route("api/hospital/assistant")]
[Authorize(Roles = "ClinicalStaff")]
public sealed class HospitalAssistantController(IHospitalAssistant svc) : ControllerBase
{
    [HttpPost("triage")]
    public async Task<TriageSuggestion> Triage([FromBody] TriageRequest req, CancellationToken ct) =>
        await svc.TriageAsync(req, ct);

    [HttpPost("protocol-search")]
    public async Task<ProtocolSearchResult> SearchProtocols([FromBody] ProtocolQuery q, CancellationToken ct) =>
        await svc.SearchProtocolsRagAsync(q.Text, ct);
}

What happened?

• HospitalAssistantController exposes triage and RAG protocol search under ClinicalStaff role.
• Service applies redaction and output filters internally.

Practice next

1. build IHospitalAssistant with AllergyPlugin and Qdrant RAG.
2. Require MFA for clinical roles in Entra ID.
3. Display disclaimer and require nurse acknowledgment in UI.
4. Add bilingual protocol templates for Spanish-speaking units.
5. Integrate push notification for critical triage scores.

Remember

Hospital assistant exposes triage and protocol RAG to clinical roles. PHI controls, filters, and human acknowledgment mandatory. RAG over approved protocol index only.

ED nurse workflow

Nurse queries fever protocol while triaging pediatric patient.

Outcome: RAG returns cited protocol section; nurse applies clinical judgment — not auto orders.