<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-source IT for small behavioral health and psychiatric practices. on Lintra</title><link>https://lintra.cloud/</link><description>Recent content in Open-source IT for small behavioral health and psychiatric practices. on Lintra</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lintra.cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Is Nextcloud HIPAA-compliant for a small practice?</title><link>https://lintra.cloud/posts/is-nextcloud-hipaa-compliant-small-practice/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><guid>https://lintra.cloud/posts/is-nextcloud-hipaa-compliant-small-practice/</guid><description>&lt;p&gt;If you run a small behavioral health or psychiatric practice and you&amp;rsquo;ve started
looking at what it would cost to keep paying Microsoft or Google forever, you
have probably found Nextcloud. It does what you need — files, sharing, document
editing, calendars, desktop and mobile sync — and it&amp;rsquo;s free.&lt;/p&gt;
&lt;p&gt;Then you hit the question that stops everything: &lt;em&gt;can I legally put patient
records in it?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The short answer is yes, and I&amp;rsquo;ll show you the configuration. But there&amp;rsquo;s a
specific piece that nearly every self-hosting guide gets backwards, and it&amp;rsquo;s the
piece that would actually hurt you in an audit. That&amp;rsquo;s most of what this post is
about.&lt;/p&gt;</description></item><item><title>About</title><link>https://lintra.cloud/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lintra.cloud/about/</guid><description>&lt;p&gt;I&amp;rsquo;m Matthew Wells. I build and run open-source IT infrastructure for small
behavioral health and psychiatric practices, out of Little Rock, Arkansas.&lt;/p&gt;
&lt;!-- TODO (Matthew): replace this paragraph with your actual background — where
 you've worked in healthcare IT, how long, what you were responsible for,
 any certifications. This is the single highest-value paragraph on the site.
 In this niche the person IS the credibility, and it's the one thing I can't
 write for you. Keep it plain and specific: "I spent N years doing X at Y"
 beats any adjective. --&gt;
&lt;h2 id="why-this-exists"&gt;Why this exists&lt;a class="heading-anchor" href="#why-this-exists" aria-label="Link to this section"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Small practices get a bad deal on IT, and it&amp;rsquo;s structural rather than anybody
being villainous about it.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://lintra.cloud/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lintra.cloud/contact/</guid><description>&lt;p&gt;Email is the fastest way to reach me, and it goes straight to me rather than a
queue.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="mailto:mwells@lintra.cloud"&gt;mwells@lintra.cloud&lt;/a&gt;&lt;/strong&gt;
· &lt;a href="tel:+16622923217"&gt;(662) 292-3217&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Useful things to include if you&amp;rsquo;re inquiring about the service: roughly how many
clinicians and staff, how many workstations, what you&amp;rsquo;re running now, and
whether you&amp;rsquo;re migrating or starting fresh. None of it is required — &amp;ldquo;can we
talk&amp;rdquo; is a perfectly good email.&lt;/p&gt;
&lt;p&gt;Questions about a post are welcome too, and I don&amp;rsquo;t treat those as sales leads.&lt;/p&gt;</description></item><item><title>Services</title><link>https://lintra.cloud/services/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lintra.cloud/services/</guid><description>&lt;p&gt;I build and run the complete IT stack for small practices using open-source
software, on cloud infrastructure dedicated to that practice alone.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s the same set of things a Microsoft 365 subscription plus a traditional MSP
would give you — file storage, document editing, single sign-on, password
management, security monitoring, remote support, backups — with two differences.
You aren&amp;rsquo;t renting per-seat licences you can never stop paying, and your data
sits on infrastructure you could take custody of tomorrow if you wanted to.&lt;/p&gt;</description></item></channel></rss>