anchor.diff:  * Kolecystektomi (removeal of gallbladder)
   * Procudes on colon 
   
  -
   NOTE: Some hospitals might include other procedures for the follow up. The set above is the minimal and required procedures defined by national authorities. 
   
  -For each of the procedures there are datasets that should be collected at specific intervals: 
  +If the patient is included in the study the following registrations should be performed to be able to get some statistics about infections: 
   
   .Tasks perfomed to collect the needed data 
   [cols="^1,5,5,15", options="header"]
  
positive.code:  startTaskPlan('FOLLOW_UP_INFECTION_AFTER_SURGERY')
  ----
  
  === The inital task definition 
  First I would try to identify the primary _DEFINED_TASKs_ . 
  
  * Surgeon approves details after surgery 
  
negative.code: 
  NOTE: Only hip replacement should be followed up after one year. 
  
  == openEHR Taskplan for this use-case
  The protocol used to collect the required data is a good example on what to use openEHR Taskplan for. In the following we will lay out some considerations and propose a structure for the _TASK_PLAN_
  
  There are several topics to consider in detail. 
  
  . <<HOW_TO_START>>
  . <<HOW_DETAILED>>
  
  [[HOW_TO_START]]
  === How to start the _TASK_PLAN_? 
  All patient in the population, having surgery with the given procedures, MUST be included in the study. This is why the system/application MUST/SHOULD be able to start the _TASK_PLAN_ automatically if the requirements are fulfilled. 
  
  There should be some kind of a "rule/workflow" engine which gets notified after surgery. The notification should have some info about what kind of procedures where performed or a way to look up data about the surgery. The pseudo-code for this agent could be like the following:
  
  .Pseudo code for "trigger" to start taskplan
  [source]
  