<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Activiti for eHealth question in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-for-ehealth-question/m-p/28752#M14623</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi, &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm evaluating Activiti (as the best promising workflow engine around) in an eHealth context of pharmacological theraphy, and I'd like to share some thoughts (hoping they are of general interest).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The medicine prescription workflow is quite straightforward in structure, as it consists (without considering the compensations) of only 4 activities: prescribe (doctor), administer (nurse), don't administer (nurse) and close (doctor).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The biggest modeling issue is that medicine administration tasks need a precise execution timing. Typically, there is a small time window inside which an administration is considered "in time", a slightly larger windows under which the administration is "late" (or "early") but still allowed. Out of these windows an administration work item is not (anymore, or yet) allowed to execute.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Actually, the time specification capabilities of &lt;/SPAN&gt;&lt;A href="http://www.activiti.org/javadocs/org/activiti/engine/task/Task.html" rel="nofollow noopener noreferrer"&gt;Task&lt;/A&gt;&lt;SPAN&gt;, being general purpose, only allows for time requirements like "this task must be due by …"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I need instead is an extension of &lt;/SPAN&gt;&lt;A href="http://www.activiti.org/javadocs/org/activiti/engine/task/Task.html" rel="nofollow noopener noreferrer"&gt;the Task class&lt;/A&gt;&lt;SPAN&gt; for supporting time requirements like "this task must take place at 12:00" (for administration with no duration, like oral theraphy) or as "this task must start at 11:15 and end at 13:30" (for durable administrations, like continuous intravenous theraphy).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Would such an extension be of some value for Activiti in general?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If not, would somebody be so kind to give me some directions on how to develop custom activity types?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sorry for my english, many thanks in advance.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Nov 2010 10:50:30 GMT</pubDate>
    <dc:creator>fbarbon</dc:creator>
    <dc:date>2010-11-12T10:50:30Z</dc:date>
    <item>
      <title>Activiti for eHealth question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-for-ehealth-question/m-p/28752#M14623</link>
      <description>Hi, I'm evaluating Activiti (as the best promising workflow engine around) in an eHealth context of pharmacological theraphy, and I'd like to share some thoughts (hoping they are of general interest).The medicine prescription workflow is quite straightforward in structure, as it consists (without co</description>
      <pubDate>Fri, 12 Nov 2010 10:50:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-for-ehealth-question/m-p/28752#M14623</guid>
      <dc:creator>fbarbon</dc:creator>
      <dc:date>2010-11-12T10:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti for eHealth question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-for-ehealth-question/m-p/28753#M14624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There is indeed no support in the engine yet for such time requirements.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In the future we will add more capabilities to calculate times.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For the moment, you can use a workaround using process variables: create for example a process variable that contains your time and name the variable with the task prefix. In your UI, you can then use these process variables when displaying the task list.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Nov 2010 11:09:37 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-for-ehealth-question/m-p/28753#M14624</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2010-11-19T11:09:37Z</dc:date>
    </item>
  </channel>
</rss>

