anchor.diff:  = Follow up after surgery 
   
   == Background
  +"Norwegian surveillance system for antibiotic use and healthcare related infections" (NOIS) is a registry with data about infection after surgery. 
   
  -NOIS is a registry with data about infection after surgery.
  +Webpage here: https://www.fhi.no/hn/helseregistre-og-registre/nois/[] 
   
  -https://www.fhi.no/hn/helseregistre-og-registre/nois/[NOIS] 
  +One responisibility they have is to follow up patients after surgery to see how much infections there are. This note describes how we would create an openEHR Task Plan to follow up these patients and make sure the relevant data is registered into the system.
   
   The following procedures are included in the registry: 
   
  
positive.code: 
  NOTE: Only hip replacement should be followed up after one year. 
  
  == openEHR Taskplan 
  The follow up for these patients should be a good example for an openEHR taskplan application. So how should we model this?
  
  One xample is the the status after discharge. This task should imply that the surgeon actually takes a look at the patient and examines different parameters. This could be physical examination, anamense, x-rays and perhaps some lab.tests to verify that everything is ok. This means that the status at discharge should not be bound directly to this _taskplan_, that task shuold be bound to a _normal follow up after surgery_ 
  
  And if we then should have a specific Taskplan for infection follow up - the tasks should all be in the same _task_plan_ for the surgeon and the specific patient. 
  
  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. 
  
  === How to start the taskplan? 
  This "taskplan" is mandatory for Patients in the population. The application should be able to start this process automatically if the requirements are fulfilled. 
  
  There should be some kind of a "rule/workflow" engine that gets notified after surgery about what kind of surgery was performed. This agent could have pseudo code like: 
  
  .Pseudo code for "trigger" to start taskplan
  [source]
  
negative.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. 
  
  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"]
  