Data_management.
Acknowledge contributions Identify content contributers and organisations
Assess value Give each asset an identifier, rank its value to the department so that backup procedures can be targeted
Assimilate_content. Capture best practice, useful data, Word, Powerpoint, webpages
Assist co-operation Get experts to help others, networking, web blogs
association ../medicine/clinical_coding.
association ../university/course_performance.
association Data Protection
Back_up Copy data regularly and secure in a different site
CAMIS, Clinical_and_management information_system http://www.heis.co.uk/camis/camis.htm
Central_patient_repository http://www.heis.co.uk/camis/central_patient_repository.htm
Clarify_responsibilities Control and direct resources to meet overall objective
Consideration Is ethical approval required ?
Consideration Use data at patient level or aggregated ?
De-commission redundant parts Extract useful content and links
Encourage Flexibility, attention to detail, problem solving, planning, training, innovation
Get feedback Complaints, comments
Good management ../management/index.
is_type_of Task.
Keep costs down Monitor where time spent
Metrics Measure success for key objectives
Objective Gain maximum value from the data, extract associations
Patient_records ../medicine/patient_records.
Peer review Peers decide the position and order of links
Possible gains Ontology_benefits.
Possible metrics Ontology_success_metrics.
Privacy Anonomise data where possible
Rationalise Identify the assets the department owns and centrally manage backups of them, e.g. a graphics library of useful jpegs, gifs, animated gifs
Reduce complexity De-skill the maintenance burden
Resource allocation Concentrate resources at key times and knowledge areas
Stimulate creativity Encourage linking of authors homepages
Talk to experts Knowledge_capture.
Task team Use temporary teams for mini-projects
   
 
Vr.156, July 2011     Readme      List of Objects ..