<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a66a86a3320543f39047421484a6690b&quot; frameborder=&quot;0&quot; width=&quot;1668&quot; height=&quot;1251&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1251</height><width>1668</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1251</thumbnail_height><thumbnail_width>1668</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a66a86a3320543f39047421484a6690b-e7fb13cd72dae9af.gif</thumbnail_url><duration>108.139</duration><title>OSTI Prevents Mismatched Referral Approvals</title><description>This Loom explains how OSTI protected a clinical referral workflow by enforcing correct patient context and one-time approvals. Dr. Lin opened Maya Patel’s chest pain referral, then switched to Jordan Rooks while Maya’s workflow continued in the background. A red banner indicated a clinical context mismatch; OSTI restored Maya and also opened a sanitized engineering incident for the vendor. The cardiology referral to UCSF was drafted, then reviewed and signed with an exact one-time approval that was invalidated due to the destination changing, prompting restoration and revalidation. A duplicate submission was rejected, with decisions recorded for two approvals and one execution.</description></oembed>