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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The recommendations <strong>in</strong> this section are derived from the ISO 27799 15 <strong>and</strong> ISO/IEC 27002 16<br />

st<strong>and</strong>ards. Both offer guidance on how best to protect the confidentiality of personal health<br />

<strong>in</strong><strong>for</strong>mation. Reference is made to the UNAIDS <strong>in</strong>terim guidel<strong>in</strong>es. 6 This document, Volume 1 of the<br />

<strong>St<strong>and</strong>ards</strong> <strong>and</strong> <strong>Guidel<strong>in</strong>es</strong> <strong>for</strong> EMR <strong>Systems</strong> <strong>in</strong> Kenya, is limited to def<strong>in</strong><strong>in</strong>g how <strong>in</strong><strong>for</strong>mation security<br />

can be <strong>in</strong>-built <strong>in</strong>to EMR systems.<br />

Requirements<br />

EMR systems must have <strong>in</strong>-built security controls <strong>in</strong>clud<strong>in</strong>g:<br />

1. Access Control<br />

2. Audit Trails <strong>and</strong><br />

3. Back up procedures<br />

Implementation Guidance<br />

Access Control<br />

This is a system of controll<strong>in</strong>g entry <strong>and</strong> use of the EMR system, <strong>in</strong> part or <strong>in</strong> its entirety. Depend<strong>in</strong>g<br />

on one’s assigned roles <strong>and</strong> responsibilities, access can be limited to specific areas such as reports<br />

or the per<strong>for</strong>mance of specific functions, such as view<strong>in</strong>g, edit<strong>in</strong>g or delet<strong>in</strong>g patient data.<br />

· EMR systems must provide a means to authenticate user identity us<strong>in</strong>g a user name <strong>and</strong><br />

password be<strong>for</strong>e enabl<strong>in</strong>g the user to per<strong>for</strong>m any functions. The system should allow <strong>for</strong><br />

the allocation of area-specific access rights. .<br />

· Password length should be a m<strong>in</strong>imum of six characters. Where feasible, 10-12 characters<br />

strengthen password security. The length of the password shall be en<strong>for</strong>ced by the system.<br />

· User account passwords should be changed every n<strong>in</strong>ety days at m<strong>in</strong>imum. The system shall<br />

automatically en<strong>for</strong>ce the regular chang<strong>in</strong>g of passwords.<br />

15 Health <strong>in</strong><strong>for</strong>matics — In<strong>for</strong>mation security management <strong>in</strong> health us<strong>in</strong>g ISO/IEC 27002<br />

16 In<strong>for</strong>mation technology — Security techniques — Code of practice <strong>for</strong> <strong>in</strong><strong>for</strong>mation security management<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 29

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

Saved successfully!

Ooh no, something went wrong!