Cardiac Anesthesia Hemodynamic Constraint Evaluation Dataset

#Constraint verification #Clinical plan evaluation #Conflict detection #Escalation trigger identification #Cardiac anesthesia #Perioperative monitoring #Hemodynamic management #Clinical AI safety evaluation

5460
0.3GB
JSON
CATL
MOBIUSI INC

Updated:2026-11-03

AI Analysis & Value Prop

This JSON dataset presents cardiac anesthesia patient and procedural contexts, individualized hemodynamic targets and boundaries, and candidate monitoring and management plans for evaluation. Annotations identify conflicts with case-specific constraints, omitted escalation triggers, and the overall assessment. It supports evaluation of models that validate patient-specific constraints, detect plan inconsistencies, and identify important omissions; it is intended for research and model safety testing, not as a substitute for clinical judgment.

Dataset Insights

Sample Examples

{}

Technical Specifications

Field	Type	Description
file_name	string	File name
rationale	string	Concise evidence-based rationale supporting the evaluation result.
candidate_plan	object	Proposed monitoring and management plan supplied for evaluation.
patient_context	object	Patient and procedural information provided as an input source.
conflict_detected	boolean	Whether any part of the candidate plan conflicts with the patient-specific constraints.
conflict_findings	array	Specific conflicts identified between the candidate plan and the case constraints.
overall_assessment	string	Overall result of evaluating the plan against the case constraints.
hemodynamic_constraints	object	Patient-specific hemodynamic targets, boundaries, and escalation criteria supplied as an input source.
missing_escalation_triggers	array	Specified escalation triggers that are not adequately addressed in the candidate plan.

Compliance Statement

Authorization Type	Proprietary - Commercial AI Training License (No Redistribution)
Commercial Use	Requires exclusive subscription or authorization contract (monthly or per-invocation charging)
Privacy and Anonymization	No PII, no real company names, simulated scenarios follow industry standards
Compliance System	Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs

Frequently Asked Questions

What does the dataset contain?: Each record includes patient and procedural context, patient-specific hemodynamic targets or boundaries, and a candidate monitoring and management plan. Annotations cover constraint conflicts, supporting findings, missed escalation triggers, and an overall assessment.

What format is provided, and which capabilities can it evaluate?: The data is provided in structured JSON and can evaluate whether models verify constraints, detect conflicts between a plan and case-specific requirements, identify escalation triggers that are not adequately addressed, and produce a reasoned overall assessment.

How can I obtain the data, and what are the licensing terms?: Check the dataset product page for available download or access options, licensing terms, permitted uses, and redistribution conditions. The terms published on the page govern access and use.

Can this dataset be used to make clinical decisions?: It is intended for research, model development, and clinical AI safety evaluation. It should not be used as an independent basis for care or as a replacement for judgment by anesthesiology and other qualified clinical professionals.

Can't find the data you need?

Post a request and let data providers reach out to you.

Get this Dataset

Verified for Enterprise Use

Cite this Work

@dataset{Mobiusi2026,
  title={Cardiac Anesthesia Hemodynamic Constraint Evaluation Dataset},
  author={MOBIUSI INC},
  year={2026},
  url={https://www.mobiusi.com/datasets/c60ff68258b01749b4e7cc601ed9b710?dataset_scene_id=4},
  urldate={2026-10-26},
  keywords={cardiac anesthesia dataset,hemodynamic evaluation,clinical constraint verification,anesthesia plan assessment,medical AI evaluation,patient-specific constraints,clinical safety assessment,JSON medical data},
  version={1.0}
}

Using this in research? Please cite us.

placeholder

Scene

Domain

Modality

Task