anchor.diff:  
   Both the Surgeon and the Patient needs an agent to be able to follow up the registration. There might also be som additional observations and evaluations to be done to be able to complete the _forms_ 
   
  +[[DEFINE_DECISION_POINTS]]
   === Define decisions points
   There are a few decisions points here: 
   
   . Is Patient in the population (the included procedures)? 
   . Is Patient included in 1 year follow up? 
   
  -=== Generic Task Plan 
  +[[CREATE_GENERIC_TASK_PLAN]]
  +=== Create a generic _TASK_PLAN_
   In the following there is an inital example on how to make a Task Plan (skeleton) of this protocoll
   
   [source, json]
  
positive.code: * 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: 
  
  .Tasks perfomed to collect the needed data 
  [cols="^1,5,5,15", options="header"]
  
negative.code:  startTaskPlan('FOLLOW_UP_INFECTION_AFTER_SURGERY')
  ----
  
  [[HOW_DETAILED]]
  === How detailed shuold the _TASK_ITEMs_ be? 
  
  To discuss the details we will look into the second task; _the status after discharge_. This task should imply that the surgeon actually takes a look at the patient and examines different parameters. I.e. perform a physical examination, take up some history, look at some X-ray images, check blood status (lab results). The purpose of this is of course to verify that everything is ok. 
  
  In turn this tells us that the _task_ for the clinician is not specific for this infection follow up. The task is a _normal follow up after surgery_. It could be some extra steps, _TASK_ITEMs_ needed which is specific for the infection follow up. They should be added to the overall _TASK_PLAN_ .
  
  Perhaps the modelling of this specific "guideline" should be modelled as reusable _TASK_GROUPs_ that might be added into other _TASK_PLANs_ ? I think this makes sense. As the patient trajectory goes on there will be new _TASK_ITEMs_ added to the complete list of _TASKs_. Some items will be added from protocols like this, and they might have strict rules for the sequence and timing. 
  
  All _TASK_ITEMs_ added must have a "source" or, put another way, a reason why they where added. The minimum _source_ must be one openEHR INSTRUCTION . The specification should also support orders (order set) with several openEHR-INSTRUCTION and the correlation with the inital order must be taken care of. 
  
  
  == Model the Task plan 
  To model this task plan I will go through the following steps: 
  
  . <<LIST_TASKS>>
  . <<DEFINE_DECISION_POINTS>>
  . <<CREATE_GENERIC_TASK_PLAN>>
  
  [[LIST_TASKS]]
  === Listing of all the tasks in the protocol
  First I would try to identify the primary _DEFINED_TASKs_ . 
  
  * Surgeon approves details after surgery 
  