<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Automation on transtorm.ai</title>
		<link>https://transtorm.ai/tags/automation/</link>
		<description>Recent content in Automation on transtorm.ai</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://transtorm.ai/tags/automation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Decision models (1): you don&#39;t need a thousand words to decide</title>
				<link>https://transtorm.ai/blog/decision-models-1-you-dont-need-a-thousand-words-to-decide/</link>
				<pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/decision-models-1-you-dont-need-a-thousand-words-to-decide/</guid>
				<description>For three years, we have been asking models built to write to make decisions. A new family of models does nothing but decide. First part: what a decision model is, with Jev and SemIf.</description>
			</item>
			<item>
				<title>Decision models (2): what speed changes</title>
				<link>https://transtorm.ai/blog/decision-models-2-what-speed-changes/</link>
				<pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/decision-models-2-what-speed-changes/</guid>
				<description>A decision model that answers in a hundred milliseconds is not used the way a language model that answers in ten seconds is. Decision loops, comparing hypotheses, the generator-and-judge pairing, and the return of the small specialized model: the second part of our article on Jev and SemIf.</description>
			</item>
			<item>
				<title>How to Automate a Trading Strategy: Lessons from a 20-Year Backtest</title>
				<link>https://transtorm.ai/blog/automate-your-trading-strategy/</link>
				<pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/automate-your-trading-strategy/</guid>
				<description>We automated a trader&amp;rsquo;s stock-market strategy. This article tells the work the client does not see: what gets taken away from the first figure before anyone dares show it.</description>
			</item>
			<item>
				<title>A Custom-Built Application for an Accurate Patient Journey Audit</title>
				<link>https://transtorm.ai/blog/dedicated-application-accurate-patient-journey-audit/</link>
				<pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/dedicated-application-accurate-patient-journey-audit/</guid>
				<description>Our patient journey audits rested on durations reconstructed from memory. We built an application that follows our existing outline, times the visit as it happens and walks through its checklist before exporting the report.</description>
			</item>
			<item>
				<title>Agenda Sync</title>
				<link>https://transtorm.ai/usecases/agenda-sync/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/agenda-sync/</guid>
				<description>&lt;h2 id=&#34;keep-your-calendars-aligned-without-replacing-your-existing-tools&#34;&gt;Keep your calendars aligned, without replacing your existing tools&lt;/h2&gt;&#xA;&lt;p&gt;In many medical organizations, patient appointments are managed in a legacy business software, while teams use Google Calendar to organize their daily routine: meetings, leaves, on-call shifts, availability, or external interventions.&lt;/p&gt;&#xA;&lt;p&gt;In the field, this separation quickly creates friction: slots blocked on one side but not the other, double bookings, oversights, manual corrections, and wasted time for teams.&lt;/p&gt;&#xA;&lt;p&gt;&lt;span class=&#34;gradient-wave&#34;&gt;transtorm.ai&lt;/span&gt; designs calendar synchronization solutions that connect your existing systems to Google Calendar in a reliable, secure, and traceable way.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Banking Control &amp; Reporting</title>
				<link>https://transtorm.ai/usecases/banking-control/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/banking-control/</guid>
				<description>&lt;h2 id=&#34;automate-bank-reporting-without-losing-oversight&#34;&gt;Automate bank reporting without losing oversight&lt;/h2&gt;&#xA;&lt;p&gt;A regional bank had to regularly produce internal and regulatory reports from multiple systems: legacy banking applications, web portals, and third-party sources.&lt;/p&gt;&#xA;&lt;p&gt;On a daily basis, finance teams manually logged into interfaces, extracted figures, reconciled data across multiple sources, imported PDF or XLS files, and then prepared reports for management or regulators.&lt;/p&gt;&#xA;&lt;p&gt;The process worked, but at the cost of numerous repetitive manipulations, a high risk of error, and insufficient traceability for audit requirements.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Document generator</title>
				<link>https://transtorm.ai/usecases/document-generator/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/document-generator/</guid>
				<description>&lt;h2 id=&#34;produce-your-documents-faster-without-losing-control&#34;&gt;Produce your documents faster, without losing control&lt;/h2&gt;&#xA;&lt;p&gt;A regulatory affairs consultancy had to produce hundreds of compliance reports, certificates, and audit summaries every quarter.&lt;/p&gt;&#xA;&lt;p&gt;Each document had to follow strict templates, include the correct version metadata, and be quickly justifiable in the event of an audit. On paper, the process seemed under control. In practice, a large part of the production still relied on manual handling in Word and Excel.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Kiosk Reception</title>
				<link>https://transtorm.ai/usecases/kiosk/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/kiosk/</guid>
				<description>&lt;h2 id=&#34;context&#34;&gt;Context&lt;/h2&gt;&#xA;&lt;p&gt;In a practice, a patient&amp;rsquo;s arrival sets off a small chain of tasks. The receptionist identifies them, checks their appointment and opens their record, then someone decides which exams to run and adds them. The check-in kiosks on the market handle the start of this chain and stop at the door of the clinical record: adding the exam is still done by hand.&lt;/p&gt;&#xA;&lt;h2 id=&#34;operational-challenge&#34;&gt;Operational Challenge&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;A bottleneck at reception&lt;/strong&gt;: Each check-in takes up about 85 seconds of the receptionist&amp;rsquo;s time. Five patients arriving together means a queue several minutes long.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Information re-entered by hand&lt;/strong&gt;: The type of consultation is almost always the one planned at the previous visit. So it is already in the record, but someone still has to look it up and enter it by hand.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Duplicate records&lt;/strong&gt;: A patient who is not found correctly gets created again, and their history ends up split.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;The language barrier&lt;/strong&gt;: A patient who does not speak the practice&amp;rsquo;s language needs someone to help them.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;solution-architecture&#34;&gt;Solution Architecture&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://transtorm.ai/blog/patient-check-in-kiosk-automated-worklist/&#34;&gt;patient check-in kiosk&lt;/a&gt; recognizes the patient by their appointment time and initials, completed by their year or date of birth: no card, no code, no SMS. It finds the appointment in the practice&amp;rsquo;s calendars, then the patient&amp;rsquo;s record, which it creates if it does not exist yet. It works out the type of consultation from the last follow-up and adds the exam itself, with the right practitioner. By the time the patient sits down, their exam is already on the worklist.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Telegram Assistant</title>
				<link>https://transtorm.ai/usecases/telegram-bot/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/telegram-bot/</guid>
				<description>&lt;h2 id=&#34;offer-quick-answers-on-telegram-without-overloading-your-teams&#34;&gt;Offer quick answers on Telegram, without overloading your teams&lt;/h2&gt;&#xA;&lt;p&gt;More and more organizations are using instant messaging platforms like Telegram to interact with their patients, customers, or partners.&lt;br&gt;&#xA;Users expect simple, fast, and accessible answers: opening hours, appointments, follow-ups, procedures, rescheduling, or practical information.&lt;/p&gt;&#xA;&lt;p&gt;Without automation, these requests quickly pile up. Teams then spend a large part of their time answering the same questions, at the expense of more complex, sensitive, or high-value cases.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How Much Does an Automation Cost? Part 2: Building the Price and Your Guarantees</title>
				<link>https://transtorm.ai/blog/how-much-does-automation-cost-price-guarantees/</link>
				<pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/how-much-does-automation-cost-price-guarantees/</guid>
				<description>Payback within one or two years, a worked example, payment conditioned on acceptance criteria, and code ownership: the second half of our pricing method.</description>
			</item>
			<item>
				<title>How Much Does an Automation Cost? Part 1: Evaluating Your Process</title>
				<link>https://transtorm.ai/blog/how-much-does-automation-cost-project-evaluation/</link>
				<pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/how-much-does-automation-cost-project-evaluation/</guid>
				<description>Price ranges, an audit whose deliverable is yours to keep, and a jointly validated measurement of what your process really costs: the first half of our evaluation method.</description>
			</item>
			<item>
				<title>From web form to signed consent: a fully automated document workflow</title>
				<link>https://transtorm.ai/blog/document-generation-esignature-automation/</link>
				<pubDate>Thu, 23 Jul 2026 00:00:00 +0200</pubDate>
				<guid>https://transtorm.ai/blog/document-generation-esignature-automation/</guid>
				<description>Generate a pre-op file, work out the follow-up dates, get an informed consent signed and archive it: the demo shows a document flow where a human steps in only once, at the entry.</description>
			</item>
			<item>
				<title>How a Reception Kiosk Builds the Clinical Worklist Itself</title>
				<link>https://transtorm.ai/blog/patient-check-in-kiosk-automated-worklist/</link>
				<pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/patient-check-in-kiosk-automated-worklist/</guid>
				<description>How a patient check-in kiosk for an ophthalmology practice goes beyond mere registration: it identifies the patient, infers the consultation type from the last follow-up, and automatically creates the worklist item in the patient record, with a mobile companion, secured by physical presence, on which patients can see how late their doctor is likely to be running, self-hosted and GDPR-friendly. A comparison with Phreesia, Clearwave, Qmatic and the patient kiosk market.</description>
			</item>
			<item>
				<title>Business Process Automation: Our Method for Deploying Reliable Micro-Processes</title>
				<link>https://transtorm.ai/blog/business-process-automation-method-micro-processes/</link>
				<pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/business-process-automation-method-micro-processes/</guid>
				<description>Discover the transtorm.ai method for reliable business process automation: an audit of the real process, human validation on important decisions, complete anonymization of data sent to external resources, robust integrations, and continuous improvement.</description>
			</item>
	</channel>
</rss>
