<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Tequio Tech</title>
<link>https://tequio.tech/blog.html</link>
<atom:link href="https://tequio.tech/blog.xml" rel="self" type="application/rss+xml"/>
<description>Voice care, healthcare technology, and the work of community.</description>
<generator>quarto-1.9.37</generator>
<lastBuildDate>Sun, 10 May 2026 07:00:00 GMT</lastBuildDate>
<item>
  <title>Manifesto</title>
  <dc:creator>TODO: author</dc:creator>
  <link>https://tequio.tech/posts/manifesto/</link>
  <description><![CDATA[ 





<p>Healthcare technology should serve the people who carry the weight of care. This is our starting point and our standard.</p>



 ]]></description>
  <guid>https://tequio.tech/posts/manifesto/</guid>
  <pubDate>Sun, 10 May 2026 07:00:00 GMT</pubDate>
</item>
<item>
  <title>Why You Should Use Healthie for Your EMR Platform</title>
  <dc:creator>TODO: author</dc:creator>
  <link>https://tequio.tech/posts/healthie-emr/</link>
  <description><![CDATA[ 





<p>Healthie gives small clinical teams a modern API surface without forcing them into legacy EMR workflows. Here is how we evaluate it in practice.</p>



 ]]></description>
  <guid>https://tequio.tech/posts/healthie-emr/</guid>
  <pubDate>Wed, 15 Apr 2026 07:00:00 GMT</pubDate>
</item>
<item>
  <title>The Healthcare Landscape and Its Voice Care Desert</title>
  <dc:creator>TODO: author</dc:creator>
  <link>https://tequio.tech/posts/voice-care-desert/</link>
  <description><![CDATA[ 





<p>Voice care sits in the gap between ENT, speech pathology, and behavioral health. The result is a coverage desert that affects performers, educators, and clinicians alike.</p>



 ]]></description>
  <guid>https://tequio.tech/posts/voice-care-desert/</guid>
  <pubDate>Sun, 01 Mar 2026 07:00:00 GMT</pubDate>
</item>
</channel>
</rss>
