Rank: Guest
|
My firms IT systems are being upgraded and there is going to be an Accident Data Programme which can be interrogated to produce reports etc for information populating the fields.
I have come up with the under-mentioned fields can anyone suggest any others please -
First Name
Surname Name
Male
Female
Date of Accident
Time of Accident
Department
Exact Location
Over 3 days absence
Over 7 days absence
Return to work date
First Aid given
Taken to Hospital
Incident Rates
Yearly comparison
Incidents and Near Misses will be dealt with separately.
Cheers
Rich
|
|
|
|
Rank: Super forum user
|
Severity of Injury
Type of Injury
Investigation carried out by...?
|
|
|
|
Rank: Super forum user
|
Rich
Is this for keeping records of incidents (sorry - accidents in your terms)? In which case you need (added in upper case)
First Name
Surname Name
Male
Female
Date of Accident
Time of Accident
Department
ADDRESS - maybe
Exact Location
INJURY
PART OF BODY
WHAT HAPPENED - quite important!
First Aid / Taken to Hospital - maybe
If you want the information immediately you can't ask how long absent or return date - it will delay.
But if you want to analyse incident rates etc, and the records themselves are kept separately (maybe as a paper form) then you don't need, and shouldn't have, personal details in the database (a reference number connects the two). You may then need additional (investigation & analysis) data such as type of incident, BASIC cause, one-line summary of incident (rather than long winded account), and a risk rating.
Incident rates and comparisons aren't fields as such they are outputs from data.
I have reservations about something like this just being bolted onto an IT system upgrade 'because you can' but I do not know the nature or size of your organisation, or the objectives you have in using the information. It takes time and thought to get the right solution - this query is linked to an recent question about self-contained accident recording software (now locked). It shows there is an interest in such things, and few (if any) stand-alone systems.
|
|
|
|
Rank: Super forum user
|
RIDDOR - note there are other RIDDOR reportable accidents other than over 7 days.
Equipment being used ?
Resulted in a claim ??????
Depends what you mean interrogate, if it is a working system you could have; has there been an investigation yet. You might want to try and classify the accident type, "Slip Trip fall" or "Fall from height" etc
Look at the features of an off the shelf system! And see what they log.
Chris
|
|
|
|
Rank: Super forum user
|
Full list of what I ask for:
Report No
Name
Director
Person Type (Employee, Student, Contractor etc)
Incident Date
Site
Location Type (Lab, Office, Common Internal area etc )
Description of Accident
Severity
Accident Type
Injury Type
Committee
RIDDOR
|
|
|
|
Rank: Super forum user
|
Hi Rich
One of the categories I always included is Occupation-eg Joiner.
This can be followed by Occupation at the time of the event-he or she may have been acting as, say, a forklift driver or even as an electrician [maybe incompetent/untrained/unauthorised at that] which may prove to be one of the causes of the event.
Aside from lax or complicit supervision!
|
|
|
|
Rank: Super forum user
|
We also have 'fields' that deal with both 'immediate' advice/agreed action given and the 'form' is 'rounded off' with further advice/agreed action after discussion at the health and safety committee meeting.
Specified injury?
|
|
|
|
Rank: Super forum user
|
|
|
|
|
Rank: New forum user
|
Hello Rich777
As it's an IT system you need to look at what you need out of the system so that you can define the right inputs. Incident rates need two inputs ie incidents per 100,000 working hours will need someone to enter all incidents and all working hours. The HSE publication HSG245 Investigating accidents and incidents; has some information gathering form examples; from page 29 onwards which might help. I recently worked for an american company and they used a bespoke system to record all this and more .. our guidance was WHO,WHAT,WHERE, WHEN and WHY. the latter being very important as then you could work on a real risk reduction solution. I agree with previous comments on the name being just a code. We used the Personnel Clock number.
Hope this helps
|
|
|
|
Rank: Forum user
|
Hi Rich
Many good answers here, particularly from Clive451.
Think about what you want out of it, then work out which fields are required to achieve that output.
At the same time don't forget the humble form. Often overlooked during the focus on IT (I know this from personal experience!). This has to collect all the data required to be input, otherwise you'll be chasing people for more info.
Hope this helps.
|
|
|
|
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.