15.11.2013 Views

Standards and Guidelines for Electronic Medical Record Systems in ...

Standards and Guidelines for Electronic Medical Record Systems in ...

Standards and Guidelines for Electronic Medical Record Systems in ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

It is important to have a pre-def<strong>in</strong>ed process <strong>for</strong> mak<strong>in</strong>g requests <strong>for</strong> changes to the EMR<br />

system. Any request <strong>for</strong> changes to the EMR should then go through this change management<br />

process.<br />

A change management process would <strong>in</strong>clude the procedure <strong>for</strong>:<br />

1. request<strong>in</strong>g the change, to whom the request is to be made;<br />

2. how requests will be reviewed;<br />

3. criteria <strong>for</strong> requests to be approved or denied;<br />

4. how the approved requests are prioritized <strong>for</strong> implementation based on criteria such as<br />

importance, impact, <strong>and</strong> complexity of the request; <strong>and</strong><br />

5. How the request is processed <strong>for</strong> implementation.<br />

Most change management processes <strong>in</strong>volve the organization of a group that is responsible <strong>for</strong><br />

receiv<strong>in</strong>g <strong>and</strong> process<strong>in</strong>g the request. This group can be health facility management, or another<br />

designated group of stakeholders, such as a technical work<strong>in</strong>g group (TWG).Once prioritized, an<br />

agreement needs to be <strong>in</strong> place between the facility or group <strong>and</strong> the EMR development team <strong>for</strong><br />

process<strong>in</strong>g that request, <strong>in</strong>clud<strong>in</strong>g acknowledgment of request, estimation of development<br />

timeframe, deployment of request, <strong>and</strong> system documentation updates.<br />

In addition to the development team mak<strong>in</strong>g the change, tra<strong>in</strong><strong>in</strong>g teams also need to be made<br />

aware of the change <strong>in</strong> order to determ<strong>in</strong>e the impact <strong>and</strong> plan <strong>for</strong> the tra<strong>in</strong><strong>in</strong>g strategy <strong>for</strong> the<br />

modification to the system (<strong>in</strong>clud<strong>in</strong>g notifications to users, retra<strong>in</strong><strong>in</strong>g users, etc).<br />

Acceptance <strong>for</strong> System Modifications<br />

It is imperative that there is a process <strong>for</strong> acceptance of any system modifications prior to<br />

deployment of those modifications. Bug fixes <strong>and</strong> m<strong>in</strong>or changes may be considered an “express<br />

change” <strong>and</strong> may be decided by the change management group to not require review by anyone<br />

other than the development team. The types of changes that qualify as an express change should be<br />

explicitly decided on by the change management group be<strong>for</strong>e the EMR system is implemented <strong>in</strong><br />

the facility. Larger feature enhancements that require a change <strong>in</strong> workflow <strong>and</strong> user tra<strong>in</strong><strong>in</strong>g may<br />

require larger stakeholder acceptance be<strong>for</strong>e proceed<strong>in</strong>g with deployment.<br />

<strong>St<strong>and</strong>ards</strong> <strong>and</strong> <strong>Guidel<strong>in</strong>es</strong> <strong>for</strong> <strong>Electronic</strong> <strong>Medical</strong> <strong>Record</strong>s <strong>Systems</strong> <strong>in</strong> Kenya 74

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!