report.object
AI agents for hospitals and health systems
Expert-reviewed from public records, platform data, primary sources, and private research beyond AI search. Use /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/sample before purchase, then download PDF, JSON, or Markdown after checkout.
page.markdown
AI agents for hospitals and health systems.md
# AI agents for hospitals and health systems
Hospital AI agents should earn authority from EHR telemetry: source capture, note placement, clinician edits, PHI boundaries, exception queues and downstream coding, inbox or care-coordination rework.
## Object
| field | value |
| ---------------- | ------------------------------------------- |
| report_id | RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS |
| schema_version | 2026-05-28 |
| last_updated_at | 2026-06-02 |
| category | AGENTS |
| sector | Healthcare delivery |
| region | GLOBAL |
| confidence_score | 0.87 |
| source_count | 29 |
| evidence_count | 31 |
## Endpoints
| action | endpoint |
| ------------ | ---------------------------------------------------------------------- |
| summary | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS |
| sample | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/sample |
| schema | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/schema |
| quote | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/quote |
| purchase | /checkout/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS?view=agent |
| versions | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/versions |
| changelog | /api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/changelog |
| monitor | /api/v1/monitors?report_id=RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS |
| mcp_resource | colophon://reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/sample |
## Coverage
| field | value |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| category | AGENTS |
| sector | Healthcare delivery |
| region | GLOBAL |
| topics | hospital AI agents, ambient scribing, EHR integration, clinical inbox, care coordination, revenue cycle, prior authorization, PHI boundaries, algorithm transparency, health system procurement |
| source_classes | regulation, health_it_rule, privacy_security_rule, device_registry, ehr_product_docs, clinical_study, industry_survey, government_data_brief, implementation_guide, vendor_announcement, standard, global_health_guidance, health_ai_assurance, clinical_workflow_study, state_guidance, state_law, vendor_docs, company_filing, vendor_directory |
| update_cadence | Weekly |
## Sample JSON
```json
{
"report_id": "RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS",
"slug": "ai-agents-hospitals-health-systems",
"schema_version": "2026-05-28",
"title": "AI agents for hospitals and health systems",
"abstract": "Hospital AI agents should earn authority from EHR telemetry: source capture, note placement, clinician edits, PHI boundaries, exception queues and downstream coding, inbox or care-coordination rework.",
"category": "AGENTS",
"sector": "Healthcare delivery",
"region": "GLOBAL",
"topics": [
"hospital AI agents",
"ambient scribing",
"EHR integration",
"clinical inbox",
"care coordination",
"revenue cycle",
"prior authorization",
"PHI boundaries",
"algorithm transparency",
"health system procurement"
],
"last_updated_at": "2026-06-02T00:00:00Z",
"source_count": 29,
"evidence_count": 31,
"confidence_score": 0.87,
"web_url": "/r/ai-agents-hospitals-health-systems/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS",
"sample_endpoint": "/api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/sample",
"inventory_endpoint": "/api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/inventory",
"full_endpoint": "/api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/full",
"schema_endpoint": "/api/v1/reports/RPT_HEALTHCARE_DELIVERY_AI_AGENTS_HOSPITALS/schema",
"redaction": {
"status": "sample",
"paid_sections_redacted": true,
"preview_limits": [
"summary",
"table_of_contents",
"evidence_profile"
]
},
"coverage": {
"category": "AGENTS",
"sector": "Healthcare delivery",
"region": "GLOBAL",
"topics": [
"hospital AI agents",
"ambient scribing",
"EHR integration",
"clinical inbox",
"care coordination",
"revenue cycle",
"prior authorization",
"PHI boundaries",
"algorithm transparency",
"health system procurement"
],
"source_classes": [
"regulation",
"health_it_rule",
"privacy_security_rule",
"device_registry",
"ehr_product_docs",
"clinical_study",
"industry_survey",
"government_data_brief",
"implementation_guide",
"vendor_announcement",
"standard",
"global_health_guidance",
"health_ai_assurance",
"clinical_workflow_study",
"state_guidance",
"state_law",
"vendor_docs",
"company_filing",
"vendor_directory"
]
},
"confidence": {
"overall_confidence": 0.87,
"source_quality": 0.89,
"source_recency": 0.88,
"source_density": 0.86,
"claim_verifiability": 0.87,
"geographic_coverage": 0.76,
"known_gaps": [
"Most public workflow evidence is U.S.-heavy because Epic, CMS, ONC and FDA sources are the clearest public record.",
"Ambient documentation studies are better developed than inbox, care-coordination and multi-step clinical agent evidence.",
"Vendor pages show integration shape but rarely publish complete denominator, exception and reviewer-burden data."
]
},
"document": {
"object": "report_document",
"schemaVersion": "2026-05-28",
"title": "AI agents for hospitals and health systems",
"subtitle": "Ambient documentation is the EHR telemetry wedge for hospital agents.",
"abstract": "Hospital AI agents should earn authority from EHR telemetry: source capture, note placement, clinician edits, PHI boundaries, exception queues and downstream coding, inbox or care-coordination rework.",
"category": "AGENTS",
"sector": "Healthcare delivery",
"region": "GLOBAL",
"topics": [
"hospital AI agents",
"ambient scribing",
"EHR integration",
"clinical inbox",
"care coordination",
"revenue cycle",
"prior authorization",
"PHI boundaries",
"algorithm transparency",
"health system procurement"
],
"sources": [
{
"id": "S1",
"label": "CMS - Interoperability and Prior Authorization Final Rule CMS-0057-F",
"publisher": "CMS",
"sourceClass": "regulation",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-and-prior-authorization-final-rule-cms-0057-f",
"publicationDate": "2024-01-17",
"transformChain": [],
"url": "https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-and-prior-authorization-final-rule-cms-0057-f"
},
{
"id": "S2",
"label": "HealthIT.gov - HTI-1 final rule and algorithm transparency",
"publisher": "ASTP/ONC",
"sourceClass": "health_it_rule",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.healthit.gov/topic/laws-regulation-and-policy/health-data-technology-and-interoperability-certification-program",
"transformChain": [],
"url": "https://www.healthit.gov/topic/laws-regulation-and-policy/health-data-technology-and-interoperability-certification-program"
},
{
"id": "S3",
"label": "HHS OCR - HIPAA Security Rule NPRM",
"publisher": "HHS OCR",
"sourceClass": "privacy_security_rule",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/index.html",
"publicationDate": "2024-12-27",
"transformChain": [],
"url": "https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/index.html"
},
{
"id": "S5",
"label": "Microsoft Support - DAX Copilot for Epic",
"publisher": "Microsoft",
"sourceClass": "ehr_product_docs",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://support.microsoft.com/en-us/dax-copilot/epic/get-started-with-dax-copilot-for-epic",
"transformChain": [],
"provenanceNotes": "Vendor-controlled source; use for workflow shape, integration surface and diligence questions, then verify operating claims privately.",
"url": "https://support.microsoft.com/en-us/dax-copilot/epic/get-started-with-dax-copilot-for-epic"
},
{
"id": "S7",
"label": "Ambient AI scribes in clinical practice randomized trial",
"publisher": "PMC",
"sourceClass": "clinical_study",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12768499/",
"transformChain": [],
"provenanceNotes": "Study evidence; verify population, endpoint, workflow and local acceptance fit before using as production proof.",
"url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12768499/"
},
{
"id": "S13",
"label": "NIST - Generative AI Profile for the AI Risk Management Framework",
"publisher": "NIST",
"sourceClass": "standard",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf",
"publicationDate": "2024-07-26",
"transformChain": [],
"url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf"
},
{
"id": "S17",
"label": "JAMA Network Open - AI-generated draft replies to patient inbox messages",
"publisher": "JAMA Network Open / PMC",
"sourceClass": "clinical_workflow_study",
"accessedAt": "2026-06-02",
"status": "verified",
"access": "sample",
"originalUrl": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10955355/",
"publicationDate": "2024-03-20",
"transformChain": [],
"url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10955355/"
}
],
"evidence": [
{
"id": "E1",
"sourceId": "S1",
"claimIds": [
"C2"
],
"summary": "CMS requires impacted payers to implement FHIR APIs for data exchange and prior authorization, with key API requirements generally due by January 2027.",
"status": "verified",
"confidence": 0.9,
"access": "sample"
},
{
"id": "E2",
"sourceId": "S2",
"claimIds": [],
"summary": "HTI-1 adds algorithm-transparency and intervention risk-management expectations for predictive decision support interventions in certified health IT.",
"status": "verified",
"confidence": 0.87,
"access": "sample"
},
{
"id": "E3",
"sourceId": "S3",
"claimIds": [],
"summary": "OCR's HIPAA Security Rule NPRM seeks stronger cybersecurity protections for electronic protected health information across covered entities and business associates.",
"status": "verified",
"confidence": 0.86,
"access": "sample"
},
{
"id": "E5",
"sourceId": "S5",
"claimIds": [
"C1",
"C3"
],
"summary": "Microsoft's DAX Copilot support pages describe an Epic-embedded workflow in which AI-generated summaries can populate Epic notes through configured SmartSections.",
"status": "verified",
"confidence": 0.84,
"access": "sample"
},
{
"id": "E7",
"sourceId": "S7",
"claimIds": [
"C1"
],
"summary": "A randomized ambient-scribe study used DAX Copilot and Nabla integrated with Epic notes and measured documentation time through Epic Signal time-in-note metrics.",
"status": "verified",
"confidence": 0.86,
"access": "sample"
},
{
"id": "E13",
"sourceId": "S13",
"claimIds": [],
"summary": "NIST AI 600-1 identifies generative-AI risks such as confabulation, prompt injection and data poisoning and gives risk-management actions around provenance, testing and monitoring.",
"status": "verified",
"confidence": 0.87,
"access": "sample"
},
{
"id": "E17",
"sourceId": "S17",
"claimIds": [],
"summary": "A patient-inbox draft-reply study reported 20% AI-draft utilization and lower task-load and work-exhaustion scores, but no significant change in reply action time, write time or read time.",
"status": "verified",
"confidence": 0.86,
"access": "sample"
}
],
"claims": [
{
"id": "C1",
"statement": "Ambient documentation is the first measurable hospital agent production lane because it exposes source capture, EHR placement, clinician review, correction and signing telemetry.",
"confidence": 0.86,
"evidenceIds": [
"E5",
"E7"
],
"access": "sample"
},
{
"id": "C2",
"statement": "Revenue-cycle and prior-authorization work is becoming a real agent route because CMS and Da Vinci standards make the data exchange and status workflow more explicit.",
"confidence": 0.86,
"evidenceIds": [
"E1"
],
"access": "sample"
},
{
"id": "C3",
"statement": "The scarce hospital agent control point is the EHR acceptance surface: source context, note placement, reviewer action, audit trace and limited write-back inside the system clinicians already use.",
"confidence": 0.84,
"evidenceIds": [
"E5"
],
"access": "sample"
}
],
"colophon": {
"checkedAt": "2026-06-02",
"latestRevisionAt": "2026-06-02T00:00:00Z",
"reviewStandard": "expert_human_reviewed",
"kinetics": {
"speed": "moderate",
"impact": 0.9,
"momentum": 0.84,
"businessImpact": "Hospital AI is judged by signed work, not drafts: every agent must prove who signs, corrects, escalates and owns rework.",
"rateOfChange": "EHR-native tools, patient-contact rules, model-card guidance and PHI controls are forcing signed-output proof before renewal.",
"from": "innovation pilots measured by draft speed",
"toward": "signed-work loops with correction and escalation telemetry"
},
"watch": [],
"gapAnalysis": "Public evidence is strong for ambient EHR placement and regulatory triggers, but weaker for source-to-signature telemetry across inbox triage, patient outreach, care coordination, write-back, reviewer burden, denials, coding effects and correction cost."
},
"body": {
"sections": [
{
"id": "executive-summary",
"title": "Executive summary",
"access": "sample",
"claimIds": [
"C1",
"C3"
],
"evidenceIds": [
"E5",
"E7",
"E17",
"E13"
],
"blocks": [
{
"id": "executive-summary-narrative",
"evidenceIds": [
"E5",
"E7",
"E17",
"E13"
],
"type": "section_narrative",
"lead": "Ambient documentation is valuable because it is the clearest public EHR-native telemetry lane for source capture, note placement, signer edits, correction burden and downstream rework.",
"body": [
"For CMIO, COO, privacy and procurement owners, use ambient documentation as the default first authority test where it is already in scope: if the hospital cannot see signed work, correction burden and downstream rework there, it should not grant more autonomy to inbox, outreach or write-back workflows.",
"Ambient documentation is the best wedge because it already touches consented capture, EHR placement, clinician review, signing and documentation-time telemetry [E5, E7].",
"Inbox, care coordination, patient outreach and revenue-cycle agents should inherit the same proof burden, not the same evidence. Each workflow needs its own source record, signer, escalation queue, write-back limit and harm or rework denominator. Inbox draft-reply evidence is useful, but it did not show the same time-savings pattern as documentation evidence [E17].",
"The expansion gate combines EHR telemetry and a governance packet. Note acceptance, correction taxonomy and reviewer minutes are the telemetry layer [E7]. Model cards, provenance, red-team testing and incident intake are the governance layer [E13, E15]."
],
"detail": [
"Treat ambient documentation as instrumentation for later agent authority, not as proof that higher-risk workflows are safe.",
"Block autonomous send, write-back or patient contact until local logs show source evidence, signer action, disclosure, escalation quality and downstream rework [E18, E19]."
]
},
{
"id": "board-decision-table",
"title": "The buying decision",
"evidenceIds": [
"E5",
"E7",
"E17",
"E13"
],
"type": "table",
"columns": [
{
"key": "question",
"label": "Question",
"align": "left"
},
{
"key": "answer",
"label": "Answer",
"align": "left"
},
{
"key": "move",
"label": "Action",
"align": "left"
}
],
"rows": [
{
"question": "What is the object of approval?",
"answer": "An EHR handoff record: captured input, note placement, clinician edits, exception queue, PHI boundary and downstream rework.",
"move": "Make signed-output rate, correction minutes, escalation misses, complaint rate, denial movement, rollback audit and stop condition contract deliverables before expanding beyond documentation."
},
{
"question": "Which lane goes first?",
"answer": "Ambient documentation where the hospital can observe signed-output rate, correction burden, coding effects and complaints.",
"move": "Use that telemetry to decide whether inbox, care coordination, patient outreach or revenue-cycle agents deserve authority."
},
{
"question": "What remains blocked?",
"answer": "Autonomous patient contact, unreviewed EHR write-back and workflow expansion without source, signer and rework evidence.",
"move": "Require disclosure, escalation, rollback and harm telemetry before granting higher authority."
}
]
}
]
},
{
"id": "what-changed",
"title": "What changed",
"access": "sample",
"dek": "Public evidence is now structured enough to define private approval tests.",
"claimIds": [
"C2",
"C1",
"C3"
],
"evidenceIds": [
"E5",
"E7",
"E1",
"E2",
"E17"
],
"blocks": [
{
"id": "what-changed-narrative",
"evidenceIds": [
"E5",
"E7",
"E1",
"E2",
"E17"
],
"type": "section_narrative",
"lead": "The trigger is no longer an agent demo. It is whether EHR-native documentation can produce signed-output telemetry that later inbox, care-coordination, prior-authorization and write-back workflows can inherit.",
"body": [
"Ambient documentation is the clearest public production lane because it creates measurable clinician review and signing telemetry inside the EHR [E5, E7]. Use that lane to set a local proof threshold where it is in scope, then approve inbox, care coordination, revenue cycle and write-back separately as authority rises. Prior-authorization API evidence shapes revenue-cycle expansion [E1, E10]. Patient-contact and inbox evidence need separate gates [E17, E18].",
"Use ambient documentation as the instrumentation wedge for later authority. Negotiate logs for source capture, correction taxonomy, reviewer minutes, signed-output rate, governance packet, downstream coding or denial effects and patient complaints; use those numbers to approve or block each later workflow.",
"For high-risk workflows, the approval record has to connect source evidence, accepted output, reviewer action, exception path, outcome signal and retained audit record before volume or staffing claims matter."
]
},
{
"id": "trigger-table",
"title": "Triggers that change approval timing",
"evidenceIds": [
"E5",
"E7",
"E1",
"E2"
],
"type": "table",
"columns": [
{
"key": "trigger",
"label": "Trigger",
"align": "left"
},
{
"key": "why_now",
"label": "Why it matters",
"align": "left"
},
{
"key": "buyer_action",
"label": "Decision use",
"align": "left"
}
],
"rows": [
{
"trigger": "EHR-native ambient products",
"why_now": "The first agent class now sits inside the note, mobile workflow and signer experience [E5, E7].",
"buyer_action": "Use ambient documentation to build the source-to-signature telemetry model before expanding autonomy."
},
{
"trigger": "CMS prior-authorization APIs",
"why_now": "Provider-payer exchange becomes a dated, measurable workflow rather than a portal workaround [E1, E10].",
"buyer_action": "Map revenue-cycle agents to FHIR PAS, payer requirements, denial reasons and EHR work queues."
},
{
"trigger": "HTI-1 algorithm transparency",
"why_now": "Certified health IT now carries a clearer expectation for algorithm information and risk practice [E2].",
"buyer_action": "Require applied model cards, intervention risk controls, workflow-owner sign-off and local monitoring evidence [E2, E16]."
},
{
"trigger": "Patient-contact and high-risk AI rules",
"why_now": "State rules can require patient notice [E18] and discrimination-risk controls [E19] for the same workflow.",
"buyer_action": "Add jurisdiction, disclosure, human-review and discrimination-risk fields before expanding inbox or outreach agents."
},
{
"trigger": "Local privacy and AI governance equivalents",
"why_now": "Non-U.S. and mixed-regime deployments still need local-law mapping before copying U.S. privacy, patient-disclosure, device and procurement controls [E14].",
"buyer_action": "Map each workflow to local privacy, interoperability, device, procurement and disclosure gates [E4, E14]."
}
]
}
]
},
{
"id": "decision-map",
"title": "Decision map",
"access": "sample",
"dek": "Workflow approval changes by authority, source boundary and proof burden.",
"claimIds": [
"C2",
"C1",
"C3"
],
"evidenceIds": [
"E5",
"E7",
"E17",
"E1"
],
"blocks": [
{
"id": "decision-map-narrative",
"evidenceIds": [
"E5",
"E7",
"E17",
"E1"
],
"type": "section_narrative",
"lead": "Hospital AI agents should prove signed-work telemetry before expansion: captured input, EHR placement, accountable signer, exception queue and measured downstream rework.",
"body": [
"The decision map should start with an EHR handoff workflow with captured input, source record, EHR surface, accountable signer, exception queue, write-back limit and downstream telemetry: what source record is read, what output is drafted, who approves it, where it is stored and what event forces reapproval.",
"A system can pass a low-risk support test and still fail production work: source evidence, accepted output, integration state, exception handling, reviewer burden and downstream rework have to hold together.",
"The useful vendor question is whether the system can make the named task inspectable, reversible and measurable inside the operating record."
]
},
{
"id": "route-selection-table",
"title": "Workflow selection",
"evidenceIds": [
"E5",
"E7",
"E17",
"E1"
],
"type": "table",
"columns": [
{
"key": "route",
"label": "Workflow",
"align": "left"
},
{
"key": "accepted_output",
"label": "Accepted work",
"align": "left"
},
{
"key": "gate",
"label": "Approval gate",
"align": "left"
},
{
"key": "buyer_rule",
"label": "Approval rule",
"align": "left"
}
],
"rows": [
{
"route": "Ambient documentation",
"accepted_output": "Signed note, summary, handoff or documentation update with reviewer edits retained in the EHR.",
"gate": "Patient consent, specialty template, source audio handling, SmartSection or chart field, correction taxonomy and signer policy [E5, E7].",
"buyer_rule": "Scale only when signed-output rate rises and correction, coding, complaint and after-hours burden fall together."
},
{
"route": "Clinical inbox",
"accepted_output": "Reviewed draft response, triage label or routed task for clinician approval.",
"gate": "Message type, patient risk, escalation, source chart context, disclosure requirement and audit log [E17, E18].",
"buyer_rule": "Block autonomous send until escalation misses, clinician overrides and patient-contact errors are visible."
},
{
"route": "Care coordination",
"accepted_output": "Follow-up plan, referral task, discharge task or outreach list.",
"gate": "Care-team owner, patient-contact policy, handoff record, discrimination-risk controls and exception queue [E18, E19].",
"buyer_rule": "Pilot on closed-loop tasks with named owners before patient-facing autonomy."
},
{
"route": "Revenue-cycle support",
"accepted_output": "Prior-auth packet, coding query, denial draft or payment-status work item.",
"gate": "Policy source, FHIR or payer-channel path and reviewer queue should map to CMS and Da Vinci evidence [E1, E10]. Accepted-output metrics and appeal economics need revenue-cycle filing evidence [E22].",
"buyer_rule": "Approve by payer and service line, not as a generic back-office bot."
},
{
"route": "Controlled EHR write-back",
"accepted_output": "Reviewed note, task, care-plan update or authorization work item committed to the source system.",
"gate": "Role-based permission, source evidence, reviewer signature, note destination, rollback and downtime route. Oracle and Suki show write-back surfaces; local telemetry must prove operating performance [E20, E21].",
"buyer_rule": "Approve only after read-only and draft workflows prove local correction, escalation and rollback telemetry."
}
]
},
{
"id": "workflow-authority-matrix",
"title": "Write authority changes the proof burden",
"caption": "Use the matrix to decide what proof is required before each workflow becomes accepted work.",
"evidenceIds": [
"E5",
"E7",
"E17",
"E1"
],
"type": "visual_matrix",
"columns": [
"Source path",
"Reviewer gate",
"System action",
"Retest trigger"
],
"rows": [
{
"label": "Ambient documentation",
"note": "Signed note, summary, handoff or documentation update with reviewer edits retained in the EHR.",
"cells": [
{
"label": "Source named",
"detail": "Patient consent, specialty template, source audio handling, SmartSection or chart field, correction taxonomy and signer policy [E5, E7].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Scale only when signed-output rate rises and correction, coding, complaint and after-hours burden fall together.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Signed note, summary, handoff or documentation update with reviewer edits retained in the EHR.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Clinical inbox",
"note": "Reviewed draft response, triage label or routed task for clinician approval.",
"cells": [
{
"label": "Source named",
"detail": "Message type, patient risk, escalation, source chart context, disclosure requirement and audit log [E17, E18].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Block autonomous send until escalation misses, clinician overrides and patient-contact errors are visible.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Reviewed draft response, triage label or routed task for clinician approval.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Care coordination",
"note": "Follow-up plan, referral task, discharge task or outreach list.",
"cells": [
{
"label": "Source named",
"detail": "Care-team owner, patient-contact policy, handoff record, discrimination-risk controls and exception queue [E18, E19].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Pilot on closed-loop tasks with named owners before patient-facing autonomy.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Follow-up plan, referral task, discharge task or outreach list.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Revenue-cycle support",
"note": "Prior-auth packet, coding query, denial draft or payment-status work item.",
"cells": [
{
"label": "Source named",
"detail": "Policy source, FHIR or payer-channel path and reviewer queue should map to CMS and Da Vinci evidence [E1, E10]. Accepted-output metrics and appeal economics need revenue-cycle filing evidence [E22].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Approve by payer and service line, not as a generic back-office bot.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Prior-auth packet, coding query, denial draft or payment-status work item.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Controlled EHR write-back",
"note": "Reviewed note, task, care-plan update or authorization work item committed to the source system.",
"cells": [
{
"label": "Source named",
"detail": "Role-based permission, source evidence, reviewer signature, note destination, rollback and downtime route. Oracle and Suki show write-back surfaces; local telemetry must prove operating performance [E20, E21].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Approve only after read-only and draft workflows prove local correction, escalation and rollback telemetry.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Reviewed note, task, care-plan update or authorization work item committed to the source system.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
}
],
"legend": [
{
"label": "Private eval can start here",
"tone": "success",
"strength": "high"
},
{
"label": "Requires named owner or reviewer",
"tone": "warning",
"strength": "medium"
},
{
"label": "Hard approval gate before scale",
"tone": "blocked",
"strength": "gate"
}
]
},
{
"id": "route-definition-callout",
"title": "Route definition",
"evidenceIds": [
"E5",
"E7",
"E17",
"E1"
],
"type": "callout",
"tone": "neutral",
"body": "Route means the approved path from work to accepted output: the source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger that make an AI result usable."
}
]
},
{
"id": "signature-proof",
"title": "Signature proof",
"access": "locked",
"dek": "The decisive proof is whether the workflow survives evidence, audit and rework.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "signature-proof-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "provider-workflow-landscape",
"title": "Provider lanes",
"access": "locked",
"dek": "Providers should be compared by workflow authority.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "provider-workflow-landscape-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "use-case-route-selection",
"title": "Workflow selection",
"access": "locked",
"dek": "Production starts with the lane where output can be accepted or rejected visibly.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "use-case-route-selection-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "evidence-and-benchmarks",
"title": "Evidence fit",
"access": "locked",
"dek": "Public evidence maps to local accepted work.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "evidence-and-benchmarks-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "private-eval-design",
"title": "Private eval design",
"access": "locked",
"dek": "Public evidence chooses the tests; local cases decide production.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "private-eval-design-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "risks-and-controls",
"title": "Risks and controls",
"access": "locked",
"dek": "The main risk is ungoverned action.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "risks-and-controls-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "operating-model",
"title": "Operating model",
"access": "locked",
"dek": "Production ownership crosses clinical, technical, compliance and finance teams.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "operating-model-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "economics",
"title": "Economics",
"access": "locked",
"dek": "Price the accepted work.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "economics-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "implementation-signals",
"title": "Public claim tests",
"access": "locked",
"dek": "Vendor pages seed diligence; local telemetry supplies operating proof.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "implementation-signals-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "vendor-directory",
"title": "Diligence directory",
"access": "locked",
"dek": "Representative vendors and platform RFI anchors to include in diligence.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "vendor-directory-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "recommended-next-steps",
"title": "Recommended next steps",
"access": "locked",
"dek": "A practical workflow can be approved in phases without pretending the whole market is ready.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "recommended-next-steps-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "known-unknowns",
"title": "Known unknowns",
"access": "locked",
"dek": "These gaps should shape diligence rather than delay all buying.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "known-unknowns-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "source-ledger",
"title": "Source ledger",
"access": "locked",
"dek": "Primary public sources and evidence rows behind the workflow analysis.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "source-ledger-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "glossary",
"title": "Glossary",
"access": "sample",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "glossary-table",
"title": "Terms used in this report",
"caption": "Definitions are reader aids, not separate evidence claims.",
"evidenceIds": [],
"type": "table",
"columns": [
{
"key": "term",
"label": "Term",
"align": "left"
},
{
"key": "meaning",
"label": "Plain meaning",
"align": "left"
}
],
"rows": [
{
"term": "Route",
"meaning": "The approved path from work to accepted output: source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger."
},
{
"term": "API",
"meaning": "Application programming interface: a governed software connection used by an app or workflow to call a model or service."
},
{
"term": "OCR",
"meaning": "Optical character recognition: converting scanned or image text into machine-readable text."
},
{
"term": "SLA",
"meaning": "Service-level agreement: a contractual availability or support commitment, not observed uptime history."
}
]
}
]
}
]
}
},
"gap_analysis": "Public evidence is strong for ambient EHR placement and regulatory triggers, but weaker for source-to-signature telemetry across inbox triage, patient outreach, care coordination, write-back, reviewer burden, denials, coding effects and correction cost.",
"kinetics": {
"speed": "moderate",
"impact": 0.9,
"momentum": 0.84,
"businessImpact": "Hospital AI is judged by signed work, not drafts: every agent must prove who signs, corrects, escalates and owns rework.",
"rateOfChange": "EHR-native tools, patient-contact rules, model-card guidance and PHI controls are forcing signed-output proof before renewal.",
"from": "innovation pilots measured by draft speed",
"toward": "signed-work loops with correction and escalation telemetry"
},
"watch_signals": [],
"sample_findings": [
"Ambient documentation is the instrumentation wedge for hospital agents because it exposes source capture, EHR placement, reviewer correction and signing telemetry."
]
}
```