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

More documents

Recommendations

Info

Functional areas Attributes Components to be evaluated Measurements methods Indicators reporting calculated indicators (age, BMI etc) % of missing fields when compared to the paper system (num = # of missing fields; denom = total # of fields) Presence of a quality control system Does data entry staff feel the EMR system is useful to them? Staff survey Data validation % of patient records that are entered into the EMR (num = # of records entered into EMR; denom = total # of records) Acceptability % of data entry staff who feel the system is adaptable to all of their needs (num = # of providers who state system is adaptable; denom = total # of providers surveyed) How long does it take to enter patient data? Time-flow analysis Length of time following visit for data to be entered. Staff survey Average time for data entry per patient file. Timeliness % of data entry staff who feel they have adequate time to enter data into the EMR (num = # of staff who state they have adequate time; denom = total # of staff surveyed) Stability / Availability How many unscheduled power outages occur per week? How many times per week do the computers malfunction? Staff Survey Number of unscheduled power outages per week. Number of times per week that computers malfunction. % of staff who rely primarily on the EMR (num = # of staff who state they rely primarily of the EMR; denom = total # of staff surveyed) Reports Usefulness Are reports used by MOH officials for policy decisions? Are reports used by clinic staff for program decisions? MOH Survey Staff Survey Does MOH staff use the EMR to make policy decisions? Does clinic staff use the EMR to make program decisions? Type of reports generated. How many national / recommended reports are generated? Simplicity Does clinic staff find the Staff survey % of clinic staff who find the reports Standards and Guidelines for Electronic Medical Records Systems in Kenya 111
Functional areas Attributes Components to be evaluated Measurements methods Indicators reports useful and easy to understand? Does clinic staff find the reports easy to generate? useful and easy to understand (num = # of staff who state reports and useful and easy to understand; denom = total # of clinic staff surveyed) % of clinic staff who find reports easy to generate (num = # of staff who state that reports are easy to generate; total # of clinic staff surveyed) Flexibility Can the information in reports and the format of reports be altered? EMR Information and report format are modifiable Data Quality Are data in reports correct? Data validation Presence of a quality control system Acceptability Do staff feel the EMR report generating system is useful to them Staff Survey % of staff who feel the reports make their job easier to do (num = # of staff who state the reports make their job easier; denom = total # of staff surveyed) % of staff who use the reports (num = # of staff who state they use the reports; denom = total # of staff surveyed) Timeliness How long does it take to generate a quarterly report? Are the reports received on time? Time flow analysis Staff survey Submission validation Time it takes to generate a quarterly report % of reports received on time (num = # of reports received on time; denom = total # of reports received) Average delay in reporting Stability / Availability Is there a back-up paper report? Staff survey Number of paper reports printed and filed at the clinic Standards and Guidelines for Electronic Medical Records Systems in Kenya 112
Page 1 and 2:
Ministry of Medical Services Minist
Page 4 and 5:
Acknowledgements This initial publi
Page 6 and 7:
Change Management Process .........
Page 8 and 9:
Architecture Enterprise Architectur
Page 10 and 11:
and without the ability to share pa
Page 12 and 13:
Purpose of this document This docum
Page 14 and 15:
Globally, several organizations hav
Page 16 and 17:
will be reviewed by the technical w
Page 18 and 19:
Section Introduction The section de
Page 20 and 21:
The above listed documentation requ
Page 22 and 23:
Clinical Decision Support This refe
Page 24 and 25:
H = Requirements. These items tare
Page 26 and 27:
4.3. System has the capability to r
Page 28 and 29:
10.2. System has the capability of
Page 30 and 31:
16. Children’s Health 16.1. Syste
Page 32 and 33:
The recommendations in this section
Page 34 and 35:
Backup Backup is the procedure for
Page 36 and 37:
Case Example: Building an EMR syste
Page 38 and 39:
o Date medically eligible to start
Page 40 and 41:
o Height o Blood pressure o BMI Whe
Page 42 and 43:
· Form 711 - Cross-sectional quart
Page 44 and 45:
Section Introduction Within the hea
Page 46 and 47:
Data Transmission Protocols There a
Page 48 and 49:
i. EMR systems ii. Patient Identifi
Page 50 and 51:
Summary Primary Actor Secondary Act
Page 52 and 53:
Use Case Title Summary Primary Acto
Page 54 and 55:
Business Rules Pre-condition(s) Cor
Page 56 and 57:
Section Introduction The implementa
Page 58 and 59:
Requirements 1. Servers and worksta
Page 60 and 61:
informatics skills in order to effe
Page 62 and 63:
competencies will be of greater use
Page 64 and 65: esponsible for utilizing the inform
Page 66 and 67: expertise, this cadre is also likel
Page 68 and 69: Data Quality and Confidentiality Id
Page 70 and 71: Demonstrate use of mouse functions
Page 72 and 73: Health facility management plays a
Page 74 and 75: A locally stored backup log should
Page 76 and 77: · User related issues could also b
Page 78 and 79: Upgrade Scheduling The EMR system n
Page 80 and 81: Monitoring is an ongoing, continuou
Page 82 and 83: down these alerts on a notification
Page 84 and 85: Hardware requirements Other infrast
Page 86 and 87: System Costs, Ownership and Sustain
Page 88 and 89: their health records upon request o
Page 90 and 91: A. Sample EMR Implementation Plan E
Page 92 and 93: deployment of the EMR (i.e. change
Page 94 and 95: C. EMR Readiness Assessment Checkli
Page 96 and 97: Is there a computer at each point o
Page 98 and 99: D. Security Policy Template Documen
Page 100 and 101: 1.9 Employees shall not access, sto
Page 102 and 103: E. Information Asset Inventory Name
Page 104 and 105: G. Sample Service Level Agreement T
Page 106 and 107: • Determine appropriate incident
Page 108 and 109: H. Sample EMR Monitoring and Evalua
Page 110 and 111: Strongly agree Agree Disagree Stron
Page 112 and 113: Functional areas Attributes Compone
show all

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

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

Delete template?

Save as template?