5,814 agents prêts à l'emploi et 15,654 compétences de bibliothèque couvrant 24 secteurs et 12 métiers par secteur — installables depuis le catalogue, connectés à vos systèmes et exécutés à travers la même chaîne de contrôles en échec fermé que tout le reste sur Cortex.
21,511 modèles de bibliothèque dans la matrice du catalogue
Des suites conçues à la main pour les tâches que les entreprises automatisent en premier — chaque collection est livrée gouvernée, politiques et audit inclus.
Recherchez parmi 21,500+ compétences et agents gouvernés, ou filtrez par secteur et par type : chaque résultat s'installe depuis le catalogue et franchit les mêmes points de contrôle.
864 résultats · Healthcare & Hospital Admin
Search approved onboarding knowledge for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft step-by-step guidance for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review checklist for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied feedback for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface recurring points for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare follow-up questions for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved knowledge for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Research & Discovery pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied findings for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Research & Discovery pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a research brief for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Research & Discovery pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved process knowledge for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Process Guidance pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied process context for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Process Guidance pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft next-step guidance for Claims Specialist teams in Healthcare & Hospital Admin, delivered by the Process Guidance pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied request context for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Intake Review & Triage pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess urgency and risk for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Intake Review & Triage pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a review priority for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Intake Review & Triage pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Condense supplied content for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Document Summarizer pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface key points for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Document Summarizer pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Produce a concise brief for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Document Summarizer pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved knowledge for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Q&A Assistant pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a grounded response for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Q&A Assistant pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review-ready answer for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Q&A Assistant pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft from supplied context for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Drafting & Generation pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Follow configured behavior guidance for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Drafting & Generation pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare copy for revision for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Drafting & Generation pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Les agents de la bibliothèque ne sont pas des scripts — ce sont des identités gouvernées. En installer un l'enregistre avec un propriétaire, un budget, des modèles et des actions autorisés, et une place dans le registre d'audit.
Filtrez par secteur et par rôle ; chaque élément indique les systèmes auxquels il se connecte et les compétences qu'il invoque.
Connecteurs, serveurs MCP et imports OpenAPI — cadrés par des listes d'autorisation et le DLP au niveau de la passerelle.
Identité, budget, garde-fous, registre, Control Tower, exécution, garde-fou de sortie — puis un reçu signé dans le Trust Ledger. Sur toutes les formules.
Le générateur visuel de compétences livre de nouvelles compétences sans code — ou dites-nous ce qui manque et nous vous orienterons vers le modèle gouverné le plus proche.