TRV-2026-1564Certified recordPeer-reviewed

Using Sydney Triage to Admission Risk Tool With Artificial Intelligence (START-AI) to Predict Inpatient Admitting Specialty for Emergency Department Patients: Single Centre Deep Learning Analysis

Objective To investigate whether the Sydney Triage to Admission Risk Tool with Artificial Intelligence (START-AI) model could be used to predict specific inpatient admitting teams based on clinical notes. Methods This was a pre-trained language model analysis using electronic medical record data from an inner-city tertiary referral hospital emergency department (ED) in Sydney, Australia. All adult patients who were admitted to an inpatient ward between January 2023 and June 2025 were included. A fine-tuned Bidir…

Health · Good Space — documented gain · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

A fine-tuned clinical language model predicted the correct admitting specialty team from ED case notes with high discrimination in a single Sydney hospital.

What this doesn’t fix

The study was conducted at a single centre, and the authors state that further exploration and validation are needed to assess clinical utility and broader feasibility.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1564, v1: “Using Sydney Triage to Admission Risk Tool With Artificial Intelligence (START-AI) to Predict Inpatient Admitting Specialty for Emergency Department Patients: Single Centre Deep Learning Analysis.” Truvace, 2026-10-16. /record/TRV-2026-1564 (accessed at citation time). sha256 dd6561acfbec7dcf…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1dd6561acfbec…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1564 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.