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:  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]
  