You are on page 1of 3

INDIANA BLOOD CENTER

INDIANAPOLIS, INDIANA 46208


STANDARD OPERATING PROCEDURE (SOP)

S.O.P. #: 16,376
Page 1 of 3

DEPARTMENT NAME:

Training and Development

EFFECTIVE DATE:

PROCEDURE NAME:

Data Entry of Initial Training Documentation

07/01/00
REVISED: 11/17/08

Written by:
Scope:

dma

Typed by:

dma

AC
DT
RL

BR
HL
RM

CP
HR
TD

CS
IT
TL

DM
LB

DP
MM

DR
PS

DS
QA

AN
LF
TH

AV
MB
WB

BC
MI

CL
MU

EB
MV

EV
NB

IM
NE

KO
SB

Approved by:
Approved by:
Approved by:
Annual Review by:
Annual Review by:
Annual Review by:
Annual Review by:
Annual Review by:
Annual Review by:

PROCESS FLOW
I n it ia l t r a in in g
o c c u rs

T r a in e r s e n d s
c o m p le t e d t r a in in g
d o c u m e n t a t io n t o
T r a in in g
C o o r d in a t o r

A s s o c ia t e c o m p le t e s
t r a in in g

T r a in e r d o c u m e n t s
e x e m p t io n f r o m
t r a in in g

Y es
T r a in in g
C o o r d in a t o r
v e r if ie s a ll t r a in in g
d o c u m e n t a t io n
r e c e iv e d

M is s in g
t r a in in g
r e q u ir e m e n t s ?

N o
R e c o r d s e n t e r e d in t r a in in g
d a ta b a s e

D o c u m e n t a t io n
f i le d i n a s s o c i a t e
t r a i n i n g f il e

N o
T r a in in g t o b e
c o m p le t e d ?

Y es

T r a in i n g p a c k e t
r e t u r n e d t o t r a in e r

Date:
Date:
Date:
Date:
Date:
Date:
Date:
Date:
Date:

INDIANA BLOOD CENTER


INDIANAPOLIS, INDIANA 46208
STANDARD OPERATING PROCEDURE (SOP)
DEPARTMENT NAME:
PROCEDURE NAME:

Training and Development


Data Entry of Initial Training Documentation

S.O.P. #: 16,376
Page 2 of 3
EFFECTIVE DATE:
07/01/00
REVISED: 11/17/08

I.

PURPOSE:
To provide instructions for entering completed initial training records into the training software.

II.

MATERIALS REQUIRED:
A. Job Duties/Procedures Manual
B. Associate training file
C. Completed training documentation
Team Training Checklist
Process Training Checklist
Policy/Process Training Checklists
Procedure Training Checklist
Learning activities, etc.

III.

EQUIPMENT REQUIRED:
PC with training database

IV.

FORMS/JOB AIDS/CATS/SAMPLES REQUIRED:


N/A

V.

DETAILS OF PROCEDURE:
A.

Processing completed training documentation


1. Trainer
a. Verify completeness of training documentation.
b. Send documentation to the Training Coordinator.
2. Training Coordinator
Refer to Job Duties/Procedures Manual for clerical steps
a. Verify completeness of training documentation.
b. Enter training documentation into training database. If any records are missing,
proceed to Step V.B.1.
c. File training documentation in associate training file.

INDIANA BLOOD CENTER


INDIANAPOLIS, INDIANA 46208
STANDARD OPERATING PROCEDURE (SOP)
DEPARTMENT NAME:
PROCEDURE NAME:

Training and Development


Data Entry of Initial Training Documentation

S.O.P. #: 16,376
Page 3 of 3
EFFECTIVE DATE:
07/01/00
REVISED: 11/17/08

B.

Processing missing training requirements


1. Training Coordinator
After verifying missing training documentation, return entire training packet to
trainer for completion.
2. Trainer
a. Upon receipt of returned documentation, research why the documentation is
missing.
b. Is the requirement to be completed?
If yes, train associate on missing documentation.
If no, provide documentation supporting why associate will not be trained.
This can be documented on the training checklist or by separate memo.
c. Return documentation packet to the Training Coordinator.
3. Training Coordinator
Upon receipt of the returned training packet, the Training Coordinator will
follow the steps found in V.A.2.

VI.

REFERENCE VALUES:
N/A

VII.

VIII.

SPECIAL NOTES:
A.

VTA history reports will be generated when requested for external audits.

B.

The Training Notes section of a training file contains documentation regarding team
requirement exemptions, changes in training, etc. This is for history only and may be
superceded.

C.

Typically, training exemptions are not entered into the training software. They are
documented on the Team Training Checklist or separate memo. Training exemptions
will be documented in training software when appropriate.

REFERENCES:
N/A

You might also like