Decision Desk
Review required- Proposed action
- Send a proposed care-plan recommendation
- Configured rule
- Require clinical review before delivery
- Decision owner
- Authorized clinician
- Execution state
- Hold delivery while the clinician reviews
Healthcare
An agent can gather context and prepare a recommendation. Set a review boundary before that recommendation reaches a patient or changes a care record.
Make the proposed action, available context, and applicable rule visible together. A configured approval step holds the governed action for the authorized clinician.
Workflow
KLA evaluates the configured rule at the integrated action boundary. A required approval creates a Decision Request in Decision Desk. The downstream action waits for its authorized outcome.
Explore human approvalEvidence for review
Proposed recommendation, available source references, policy decision, clinical reviewer, rationale, and delivery outcome.
Lineage Explorer connects recorded events. Evidence Room packages collected evidence into a Sealed Evidence Bundle for verification. Evidence integrity establishes whether the recorded material changed; factual accuracy still requires domain review.
Explore execution lineageReview agent-drafted instructions before they reach the patient channel.
Route a proposed update to the responsible clinical team.
Evaluate the agent’s identity and configured data permissions at the governed boundary.
Your team determines the applicable obligations and approval rules for each deployment. Explore Control Mapping.
Choose one care workflow and involve its clinical, technical, and information-governance owners. Agree permitted data, review responsibilities, and the supported integration route before testing.
Discuss an evaluation