Training and Facilitation Guide

Revisi per 18 Februari 2014 12.45 oleh Angus (bicara | kontrib) (Marked this version for translation)

Suggested program for kabupaten level training

Preparation on arrival

By the kabupaten coordinator and an experienced user such as a Champion or a coordinator visiting from an iSIKHNAS active area.

  • Staff should be pre-registered to use the system before the start of the training to avoid time losses in the registration process. Website registrations should include,
    • Mobile phone number/s and email
    • Registered work location to desa level, could also add infrastructure as additional work location if desired
    • User type set with care because many permissions are dependent on user type.
    • Area of responsibility established
    • Permissions set
    • Alert switches set
  • Infrastructure is checked and entered if not already listed – abattoirs, dinas offices, labs, and others
  • Location codes for the area are checked – names, kecamatan, kabupaten. Adjustments will have to be noted for later – when the interface is able to handle making changes of this type. Local location code list should be created and printed for staff training. See attached
  • Drugs used in the Kabupaten checked against iSIKHNAS drug list. Local list created using Wiki, cut and paste into Excel and editing. Print prior to training.
  • Discussion about protocol, standard operating procedures, decisions, responsibilities etc.
  • Monitoring – error log, user performance, response rates, case follow up, communication and decision making shortfalls, help desk service, questions redirected.

Introductory meeting with senior staff and Kepala Dinas

Minimum 4 hours suggested

  • Introductions and thanks
  • Introduction to iSIKHNAS
    • History and development of the system,
    • Founding principles, goals, philosophy,
    • roles and responsibilities of staff/users – introduction to user types, including pelsa
    • The importance of good service, communication and strongly positive community relations
    • functions, information access
    • additional tools – website (www.isikhnas.com), email, apps, IM (data capture, chat and photo share via internet based instant messaging program), XM (data capture and push via excel and email)
    • management model,
    • vision for future
  • Video presentation of key areas of interest for staff
  • Outputs
  • Administration
    • management,
    • oversight,
    • monitoring using data, tools, outputs,
    • agreement on adoption strategy – which components to come first and the plan for roll out within the kabupaten for specialised purposes

Suggested training model

Suggested timing

  • Half day: Generic introduction to iSIKHNAS and how it works
  • Approximately half day per message set with practice
  • Half day: Review and evaluation

Basic model for SMS message training

  • Set up prior to start of training
    • Set up training point scoring tool with participants names
  • Training model for each message set
    • Presentation of message set: Show video and discuss
    • Draw out main purpose/importance
    • Who is responsible/involved in the use of this message set
  • Training model for each individual message within a message set
    • Contextualised presentation of message function and its purpose/role
    • Presentation: Message format
      • Rules for ensuring correct format – commas, spaces, order
      • Mandatory and optional parts of message
      • Sequencing within messages, if available for multiple entry
      • Determine the Codes required
    • Demonstration: Open class scenario to send test message
    • Controlled practice: Show response on phone to check and enforce
    • Reduced control practice: receive a few more example scenarios on cards
  • Special skills development
    • Signs vs Syndromes vs Disease lists and Differential diagnosis vs “opinion”
      • All Pelsa and Dinas staff (using appropriately chosen examples and signs lists). Signs recognition and code matching activity using specially selected numbered photo slides and video clips. Participants put code to photo number on a sheet as the photos roll over. Discuss their answers/swap papers with neighbour and run through photos and answers together to share ideas. Run through photos again as a whole class and come to agreement about sign and code.
      • Disease recognition and differential diagnosis

Training resources/equipment required

  • Internet connection either WIFI or tethered telephone connection
  • Projector
  • Necessary files and documents – powerpoints, photo files, scenario cards, videos
  • USB stick
  • At least one laptop computer
  • Microphones / voice amplification where possible
  • Whiteboard, pens and erasers /Flipchart paper, large clips and pens
  • Blank cards/paper
  • Participant name lists
  • Writing paper and pens for participants
  • Smart cards/user manuals for users
  • Signs recognition and code matching activity using numbered photo slides. Participants put code to photo number on a sheet as the photos roll over. Discuss their answers/swap papers with neighbour and run through photos and answers together to share ideas. Run through photos again as a whole class and come to agreement about sign and code.
  • Printed code lists
    • Priority syndromes
    • General signs codes
    • Disease codes
    • Drugs codes
    • Location codes for the area
  • Printed scenario cards in the following message sets with adjustments made to ensure locations and case IDs are accurate for the area undergoing training.
    • Disease reports: U and P
    • Disease response reports: R, OB, LAB and PK
    • Administration functions: LOK, H, N, D,
    • System query functions: CKL, CKO, CKP, CKT, LAPD, LAPK, KODE, [Message code], Q
    • Disease investigation (PDSR): AI, SRAB, LTL
    • Slaughterhouse reports: RP
    • Movement reports: LSK, SK, VSK, KSK
    • Special activities: SUR, VAK, POP
    • Insemination reports: IB series
  • Training competition point scoring tool {optional}
  • Facilitator’s guide – agenda, checklist, message training points, activity set up, etc
  • Smart cards
  • Prizes
  • Training videos

Example training schedule

Indicative only: Dependant on agreed message sets to be introduced in the induction training

DAY 1

  • 08.00-08.30 Opening
  • 08.30-09.00 Training overview and staff introductions
  • 09.00-09.30 General introduction to ISIKHNAS, Coordination, administration, User types; roles and responsibilities compared
  • 09.30-10.00 iSIKHNAS SMS Reporting 101: How the system works, Areas of responsibility, Unique case IDs
  • 10.00-10.15 COFFEE BREAK
  • 10.00-12.00 How the message formats work – the ‘rules’ for reading them, Sending a message, receiving a reply, Correct data, codes, SMS messages U, P(and PNEG for Pelsa) - presentation, demonstration and practice
  • 12.00-13.00 LUNCH
  • 13.00-14.15 SMS query messages for CKL,DKL,LOK – presentation, demonstration and practice
  • 14.15-14.30 COFFEE BREAK
  • 14.30-17.00 SMS R,OB,PK,LAB - presentation, demonstration and practice

DAY 2

  • 08.00-09.00 Review U,P,R,PNEG, OB, LAB, PK. Scenario card game – controlled practice and review
  • 09.00-10.00 SMS for Special Activities - POP, SURV, VAK – presentation, demonstration and practice
  • 10.00-10.15 COFFEE BREAK
  • 10.15-12.00 SMS for Movement – LSK, SK, VSK, KSK – presentation, and demonstration
  • 12.00-13.00 LUNCH BREAK
  • 13.00-15.00 SMS for movement – practice with scenario activity cards Or Competitive activity to practice all new messages
  • 15.00-15.15 COFFEE BREAK
  • 15.15-16.00 Review, comprehension check and discussion.

DAY 3

  • 08.00-09.00 Review
  • 09.00-10.00 Good relations, good communication, providing additional service, SMS case queries LAPD,LAPK.
  • 10.00-10.15 COFFEE BREAK
  • 10.15-12.00 Scenario card competition
  • 12.00-13.00 LUNCH BREAK
  • 13.00-14.30 Question time. Where to get help. Resources
  • 15.00-15.30 Evaluation
  • 15.30-15.45 COFFEE BREAK
  • 15.00-15.30 Closing ceremony

Final meeting with senior staff and Kepala dinas

Wrap up regarding administration, operating procedures, internal policy, standard operating procedures and outcomes from training.

  • Thanks to all participants, senior staff, kepala dinas etc for their participation and cooperation
  • Staff feedback from the training.
  • Changes required/requested in response to training
  • Identify parts that still aren't clear, those topics that were difficult, which activities worked and which didn't
  • What they thought of the materials
  • Discussion about issues raised during training. Problems, confusions clarified.
  • Policy issues of significance
    • Movement
    • Drugs – traditional, non-registered can be added, later to be able to be searched by components etc
    • Location codes – future changes will be able to be made via website by provincial and kabupaten coordinators
    • Additional data usually recorded but not being captured
    • Procedures for communicating changes, updates, etc
  • Outputs
    • Reports through the web interface
    • Emailed reports
    • Requesting new outputs
    • Downloading data to use in Excel or other software
    • Mapping – to come soon
  • Where to go for help and advice and to give feedback
    • Resources – web, wiki, apps, chat, xm
    • Human expertise – coordinators, champions
  • Support training to come in the future to help staff strengthen their skills in various important areas
    • Disease investigation with emphasis on examination skills, signs recognition, diagnostic process, determining appropriate lab work necessary and recommended treatments
    • Field Epi and Surveillance for para-vets, and vets
    • Budget Advocacy
    • Data analysis for decision makers
    • GIS
  • Feedback welcome at all times. The system is for all users and the guiding philosophy is that iSIKHNAS should provide a useful service to ALL users at ALL levels.