<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Topics on transtorm.ai</title>
		<link>https://transtorm.ai/tags/</link>
		<description>Recent content in Topics on transtorm.ai</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://transtorm.ai/tags/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>AI</title>
				<link>https://transtorm.ai/tags/ai/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/ai/</guid>
				<description>&lt;p&gt;We use language models for the parts of a process that resist rules, such as summarising a CV or drafting a first answer. The model never writes to the record on its own. A person reviews and validates the output, and the pages below show what that looks like in practice.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Compliance</title>
				<link>https://transtorm.ai/tags/compliance/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/compliance/</guid>
				<description>&lt;p&gt;Compliance is easier to build in than to add afterwards. We decide early what a process may store, what it must anonymise and what it has to be able to prove later. These pages show how those constraints shaped real systems, from pseudonymised exports to self-hosted infrastructure.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Decision support</title>
				<link>https://transtorm.ai/tags/decision-support/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/decision-support/</guid>
				<description>&lt;p&gt;Decision support earns its place when it makes the expert faster without hiding the reasoning. We encode the rules the practitioner already applies, expose the thresholds so they stay adjustable, and present a cautious result rather than a verdict. These pages describe the simulators and planners built that way.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Healthcare</title>
				<link>https://transtorm.ai/tags/healthcare/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/healthcare/</guid>
				<description>&lt;p&gt;Clinical software fails when it costs the practitioner time. We start from the existing consultation and remove the steps that do not need a human, from check-in to the structured record. These pages gather the healthcare systems we have deployed and what changed for the teams using them.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Self-hosted</title>
				<link>https://transtorm.ai/tags/self-hosted/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/self-hosted/</guid>
				<description>&lt;p&gt;Hosting a tool yourself is a decision about control rather than about price. It keeps the data on infrastructure the client owns, removes the per-seat pricing that punishes growth, and leaves the door open to migrate later. These pages describe the internal tools and open-source stacks we deploy that way.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Jev</title>
				<link>https://transtorm.ai/tags/jev/</link>
				<pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/jev/</guid>
				<description>&lt;p&gt;Jev does not generate text. It reads a question and a list of options, then gives the probability of each one in about a hundred milliseconds. TypeSafe AI offers it as a hosted service and has not published the weights. These pages explain what this kind of model changes and how we use its open replicas.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Ophthalmology</title>
				<link>https://transtorm.ai/tags/ophthalmology/</link>
				<pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/ophthalmology/</guid>
				<description>&lt;p&gt;Ophthalmology is the field we know best, and it is unforgiving for generic software. Everything happens per eye, follow-up is a curve rather than a value, and the vocabulary is specific. These pages cover the retina registries, the refractive planning tools and the clinical workflows we built around those constraints.&lt;/p&gt;</description>
			</item>
			<item>
				<title>SemIf</title>
				<link>https://transtorm.ai/tags/semif/</link>
				<pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/semif/</guid>
				<description>&lt;p&gt;SemIf reads the probability a language model assigns to each option instead of letting it write an answer. It runs on the model already installed on the server, so the data never leaves the building. These pages describe how we use it and what it gives on real cases.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Automation</title>
				<link>https://transtorm.ai/tags/automation/</link>
				<pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/automation/</guid>
				<description>&lt;p&gt;Automation only pays off when it survives contact with real operations. The pages below cover the micro-processes we deploy for our clients, the checks that keep a person in the loop, and the numbers we measure once the process is live.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Ops</title>
				<link>https://transtorm.ai/tags/ops/</link>
				<pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/ops/</guid>
				<description>&lt;p&gt;Operational work is repetitive, unglamorous and expensive when it stays manual. We move that back office onto processes that run on their own and only ask for a human when something is genuinely ambiguous. These pages cover the reporting, support and scheduling systems we run for clients.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Workflow</title>
				<link>https://transtorm.ai/tags/workflow/</link>
				<pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/workflow/</guid>
				<description>&lt;p&gt;A large process is hard to automate and harder to fix. We cut it into micro-processes that each do one thing and can be tested on their own, then orchestrate them. These pages explain that method and show the worklists and business processes we rebuilt with it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Clinical data</title>
				<link>https://transtorm.ai/tags/clinical-data/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/clinical-data/</guid>
				<description>&lt;p&gt;A clinic that records its activity in free text cannot query it afterwards. We build structured entry around controlled vocabularies, so the same data serves the consultation, the follow-up curve and the export. These pages describe the registries and clinical workflows we have built on that principle.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Documents</title>
				<link>https://transtorm.ai/tags/documents/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/documents/</guid>
				<description>&lt;p&gt;A document workflow usually breaks at the seams, between the form, the template, the signature and the archive. We connect those steps so a single entry produces the finished, signed and filed document. These pages cover the generators, the e-signature flows and the archiving that follows.&lt;/p&gt;</description>
			</item>
			<item>
				<title>HR</title>
				<link>https://transtorm.ai/tags/hr/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/hr/</guid>
				<description>&lt;p&gt;We rebuilt our own hiring process before selling the idea to anyone else. Interviews follow a fixed grid, scores are weighted and visible live, and the AI summaries stay under human validation. These pages cover that tooling and the roles we are currently recruiting for.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Integration</title>
				<link>https://transtorm.ai/tags/integration/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/tags/integration/</guid>
				<description>&lt;p&gt;Most teams do not need another application. They need the ones they already run to talk to each other. We connect calendars, messaging platforms and business software so data stops being re-entered by hand. These pages describe those connections and what they removed from the daily routine.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
