<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>phisiemr Estado - Historial de incidentes</title>
    <link>https://phisiemr.instatus.com</link>
    <description>phisiemr</description>
    <pubDate>Sat, 24 Oct 2026 22:23:43 +0000</pubDate>
    
<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Oct 24, 22:27:43 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Oct 24, 22:23:43 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>22:27:43</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>22:23:43</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 24 Oct 2026 22:23:43 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmvmyu0fh004v07mmc7x6akdm</link>
  <guid>https://phisiemr.instatus.com/incident/cmvmyu0fh004v07mmc7x6akdm</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Oct 24, 01:39:05 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Oct 24, 01:33:04 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>01:39:05</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>01:33:04</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 24 Oct 2026 01:33:04 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmvlq5mdi00x807prgvlfrjke</link>
  <guid>https://phisiemr.instatus.com/incident/cmvlq5mdi00x807prgvlfrjke</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Oct 22, 13:09:07 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Oct 21, 23:13:42 GMT+0 - Supervisando - Phisi EMR v2 Backend se encuentra no disponible por el momento debido a problemas con el proveedor de la nube que se encuentra bajo ciberataque.  
Esta medida se está tomando por precaución y restableceremos el servicio a la brevedad. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>13:09:07</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>23:13:42</var> GMT+0</small><br><strong>Supervisando</strong> -
  Phisi EMR v2 Backend se encuentra no disponible por el momento debido a problemas con el proveedor de la nube que se encuentra bajo ciberataque.  
Esta medida se está tomando por precaución y restableceremos el servicio a la brevedad..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 21 Oct 2026 23:13:42 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmviqaq2000ld07qma2xd6bnw</link>
  <guid>https://phisiemr.instatus.com/incident/cmviqaq2000ld07qma2xd6bnw</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Oct 15, 07:11:59 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Oct 15, 07:09:59 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>07:11:59</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>07:09:59</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 15 Oct 2026 07:09:59 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmv9789c802og07o1cjeh6dvd</link>
  <guid>https://phisiemr.instatus.com/incident/cmv9789c802og07o1cjeh6dvd</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Oct 10, 15:55:21 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Oct 10, 15:51:21 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:55:21</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:51:21</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 15:51:21 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmv2knha000o707rgxx5dyi2k</link>
  <guid>https://phisiemr.instatus.com/incident/cmv2knha000o707rgxx5dyi2k</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Oct 9, 05:27:33 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Oct 9, 05:23:37 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>05:27:33</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>05:23:37</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 9 Oct 2026 05:23:37 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmv0isccu008v07qtxgafgjpg</link>
  <guid>https://phisiemr.instatus.com/incident/cmv0isccu008v07qtxgafgjpg</guid>
</item>

<item>
  <title>Phisi WebPage is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi WebPage
    Sep 30, 07:41:58 GMT+0 - Resuelto - Phisi WebPage is back up. This incident was automatically resolved by Instatus monitoring. Sep 30, 07:36:57 GMT+0 - Investigando - Phisi WebPage is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:41:58</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi WebPage is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:36:57</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi WebPage is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 07:36:57 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmunsnzgr02cn07ne1lfw1amv</link>
  <guid>https://phisiemr.instatus.com/incident/cmunsnzgr02cn07ne1lfw1amv</guid>
</item>

<item>
  <title>Phisi EMR v2 Frontend is back up</title>
  <description>
    Type: Incident
    

    
    Sep 30, 07:40:03 GMT+0 - Resuelto - Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring. Sep 30, 07:36:03 GMT+0 - Investigando - Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:40:03</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:36:03</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 07:36:03 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmunsk3y702p607mnsu1qdr2m</link>
  <guid>https://phisiemr.instatus.com/incident/cmunsk3y702p607mnsu1qdr2m</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Sep 30, 07:41:18 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Sep 30, 07:35:18 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:41:18</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:35:18</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 07:35:18 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmunsj2al039407p7l7cxkh1c</link>
  <guid>https://phisiemr.instatus.com/incident/cmunsj2al039407p7l7cxkh1c</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Sep 22, 03:06:42 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Sep 22, 03:04:53 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>03:06:42</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>03:04:53</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 22 Sep 2026 03:04:53 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmuc3chqa03kp07pbcwz1e6fz</link>
  <guid>https://phisiemr.instatus.com/incident/cmuc3chqa03kp07pbcwz1e6fz</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Sep 18, 19:55:14 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Sep 18, 19:53:34 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>19:55:14</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>19:53:34</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 18 Sep 2026 19:53:34 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmu7dm8pt01ht07pbqvglhzsa</link>
  <guid>https://phisiemr.instatus.com/incident/cmu7dm8pt01ht07pbqvglhzsa</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Sep 5, 18:57:24 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Sep 5, 18:55:23 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>18:57:24</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>18:55:23</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 5 Sep 2026 18:55:23 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmtoqtb9k00qi07pipu0u1e6u</link>
  <guid>https://phisiemr.instatus.com/incident/cmtoqtb9k00qi07pipu0u1e6u</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Aug 8, 00:41:52 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Aug 8, 00:14:28 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>00:41:52</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>00:14:28</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 8 Aug 2026 00:14:28 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmsjmfyy902dl07obki6jsyek</link>
  <guid>https://phisiemr.instatus.com/incident/cmsjmfyy902dl07obki6jsyek</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Jul 4, 18:59:44 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Jul 4, 18:57:56 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>18:59:44</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>18:57:56</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 4 Jul 2026 18:57:56 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmr6q5x0d0005c1kboarha8ok</link>
  <guid>https://phisiemr.instatus.com/incident/cmr6q5x0d0005c1kboarha8ok</guid>
</item>

<item>
  <title>Phisi EMR v1 is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v1
    Jun 21, 01:21:22 GMT+0 - Resuelto - Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring. Jun 21, 01:17:19 GMT+0 - Investigando - Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>01:21:22</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v1 is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>01:17:19</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v1 is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 21 Jun 2026 01:17:19 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmqn3jvot005d0koa9d77nuar</link>
  <guid>https://phisiemr.instatus.com/incident/cmqn3jvot005d0koa9d77nuar</guid>
</item>

<item>
  <title>Phisi EMR v2 Frontend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Frontend
    Jun 8, 11:31:11 GMT+0 - Resuelto - Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring. Jun 8, 11:29:34 GMT+0 - Investigando - Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:31:11</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:29:34</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 8 Jun 2026 11:29:33 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmq54p5d3011tk315xed22ff1</link>
  <guid>https://phisiemr.instatus.com/incident/cmq54p5d3011tk315xed22ff1</guid>
</item>

<item>
  <title>Phisi WebPage is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi WebPage
    Jun 8, 11:30:47 GMT+0 - Resuelto - Phisi WebPage is back up. This incident was automatically resolved by Instatus monitoring. Jun 8, 11:25:58 GMT+0 - Investigando - Phisi WebPage is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:30:47</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi WebPage is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:25:58</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi WebPage is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 8 Jun 2026 11:25:58 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmq54kj43016hnw15zn53c2f6</link>
  <guid>https://phisiemr.instatus.com/incident/cmq54kj43016hnw15zn53c2f6</guid>
</item>

<item>
  <title>Phisi EMR v2 Frontend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Frontend
    Jun 7, 02:24:56 GMT+0 - Resuelto - Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring. Jun 7, 02:22:56 GMT+0 - Investigando - Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>02:24:56</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>02:22:56</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 7 Jun 2026 02:22:56 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmq35qc4j00wfqm15wz8jolj8</link>
  <guid>https://phisiemr.instatus.com/incident/cmq35qc4j00wfqm15wz8jolj8</guid>
</item>

<item>
  <title>Phisi EMR v2 Frontend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Frontend
    Jun 5, 19:31:10 GMT+0 - Resuelto - Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring. Jun 5, 19:27:29 GMT+0 - Investigando - Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>19:31:10</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Frontend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>19:27:29</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Frontend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 5 Jun 2026 19:27:29 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmq1bg7nz0004o315mhvzcpfz</link>
  <guid>https://phisiemr.instatus.com/incident/cmq1bg7nz0004o315mhvzcpfz</guid>
</item>

<item>
  <title>Phisi EMR v2 Backend is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Phisi EMR v2 Backend
    Jun 5, 09:59:51 GMT+0 - Resuelto - Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring. Jun 5, 09:58:07 GMT+0 - Investigando - Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>09:59:51</var> GMT+0</small><br><strong>Resuelto</strong> -
  Phisi EMR v2 Backend is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>09:58:07</var> GMT+0</small><br><strong>Investigando</strong> -
  Phisi EMR v2 Backend is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 5 Jun 2026 09:58:06 +0000</pubDate>
  <link>https://phisiemr.instatus.com/incident/cmq0r3z7b013poc15dxebl568</link>
  <guid>https://phisiemr.instatus.com/incident/cmq0r3z7b013poc15dxebl568</guid>
</item>

  </channel>
  </rss>