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.
648 résultats · Healthcare & Hospital Admin · Compétences
Summarize a supplied record for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Record Review 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 possible risk for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Record Review 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.
Flag items for human review for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Record Review 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.
Run a parameterized read query for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Data Query & 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.
Summarize returned records for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Data Query & 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 a result-set overview for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Data Query & 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.
Check supplied context against policy for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Compliance Checker 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 potential policy issues for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Compliance Checker 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 review items for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Compliance Checker 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 supplied risk context for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Risk Assessment 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.
Explain assessment drivers for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Risk Assessment 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 human review for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Risk Assessment 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.
Query supplied record data for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief 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 potential discrepancies for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief 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 reconciliation brief for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief 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 a supplied exception for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Exception Review 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 the assessment for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Exception Review 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 follow-up review for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Exception Review 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.
Run an on-demand read query for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights 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 query results for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights 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.
Highlight supplied exceptions for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights 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 supplied context for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Decision Support 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 recommended response for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Decision Support 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 rationale for review for Pharmacy Liaison teams in Healthcare & Hospital Admin, delivered by the Decision Support 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.