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.

Sample EMR System Implementation Models<br />

Different implementation models can be adopted <strong>for</strong> EMR systems’ implementation. Human<br />

resource, <strong>in</strong>frastructural <strong>and</strong> operational requirements will vary depend<strong>in</strong>g on the models selected.<br />

The follow<strong>in</strong>g are examples of models that may be used <strong>for</strong> implementation. These examples are<br />

not conclusive, <strong>and</strong> there<strong>for</strong>e, a facility or implementer may choose to use a different novel model.<br />

These examples give an <strong>in</strong>dication of m<strong>in</strong>imum requirements <strong>for</strong> the implementation of each model.<br />

Additional resources may be allocated depend<strong>in</strong>g on availability <strong>and</strong> complexity of implementation.<br />

Case Scenario 1: Retrospective st<strong>and</strong>-alone EMR system<br />

A facility with a volume of 100 clients per day wishes to implement an EMR to improve their data collection.<br />

The facility manager would like to have a s<strong>in</strong>gle computer runn<strong>in</strong>g the EMR <strong>and</strong> used <strong>for</strong> retrospective data<br />

entry by the data clerk.<br />

Type of Implementation<br />

St<strong>and</strong>alone data entry po<strong>in</strong>t EMR<br />

Workflow Processes<br />

Cl<strong>in</strong>icians enter data manually <strong>in</strong>to patient encounter <strong>for</strong>ms. The<br />

data clerk collects all <strong>for</strong>ms <strong>and</strong> transcribes the data <strong>in</strong>to the<br />

computer. Reports are generated from the computer.<br />

Hardware Requirements<br />

1. A s<strong>in</strong>gle computer complete with CPU, monitor, mouse <strong>and</strong><br />

keyboard<br />

2. Pr<strong>in</strong>ter<br />

3. UPS<br />

Other Infrastructural requirements 1. Reliable power supply<br />

Human Resource Requirements<br />

(recommended personnel required<br />

<strong>and</strong> roles).<br />

Operational requirements<br />

1. Data Entry Clerk<br />

The data clerk should additionally possess the competencies to<br />

do data quality checks, data clean<strong>in</strong>g, <strong>and</strong> m<strong>in</strong>imum data<br />

analysis <strong>for</strong> decision-mak<strong>in</strong>g.<br />

1. Secured physical environment of IT <strong>in</strong>frastructure<br />

2. Daily-automated backups. Data clerk to verify the success<br />

<strong>and</strong> <strong>in</strong>tegrity of backups daily.<br />

3. SLA agreement <strong>for</strong> support or support available on call.<br />

Case Scenario 2: Retrospective dual po<strong>in</strong>t EMR access<br />

A facility wishes to implement an EMR model hav<strong>in</strong>g the receptionist register<strong>in</strong>g <strong>and</strong> retriev<strong>in</strong>g client files <strong>for</strong><br />

the cl<strong>in</strong>icians <strong>and</strong> the data entered retrospectively from paper records <strong>in</strong>to a computer by the data entry clerk.<br />

The receptionist needs to have a computer with access to the patients’ demographic details <strong>in</strong> the EMR.<br />

When a patient visits the cl<strong>in</strong>ic, they give the receptionist their patient card show<strong>in</strong>g their names <strong>and</strong> patient<br />

ID. The receptionist keys <strong>in</strong> the patient ID <strong>in</strong>to the EMR system. The system retrieves the patient’s<br />

demographics <strong>and</strong> displays them <strong>for</strong> confirmation. The system also generates alerts <strong>for</strong> laboratory tests that<br />

are due <strong>and</strong> care plans that are due based on the <strong>in</strong>tegrated decision support features. The receptionist writes<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 78

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

Saved successfully!

Ooh no, something went wrong!