This week's announcements focused on where AI runs, where data moves and how real-time systems behave. Those questions can feel technical, but they are operational questions for every practice using connected software.
What practices should take from this
Start with the patient or staff action that produces data. Trace each transfer, storage location, model call, log and human review. Add the vendors that operate those components and note which agreements apply.
The drawing often reveals hidden steps: a browser extension, an analytics service, a support portal or a copied output. Each extra hop may be reasonable, but it should be known and controlled.
A useful data-flow review ends with decisions: remove an unnecessary transfer, restrict access, create a fallback or document why the remaining path is acceptable.