EHR Benchmark Requirements Document-DRAFT
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
PROJECT: Define a standard of EHRs through a questionnaire that vendors can be required to complete for dentists/schools/DSOs
2
OBJECTIVE: enable dentists/schools/DSOs to make licensing decisions based on pertinent information
3
STRUCTURE: Sections; questions; subquestions - No sub sub questions. Questions have answer formats (e.g., multiple choice, long answer)
4
REQUEST: Please suggest edits to questions from others. NOTE: More thorough is better. Language must be as simple as possible
5
NOTE: This is a high priority project and your expertise is needed. Please contribute. Our product and systems are only helpful if we get them into as many clinics as possible.
6
Please create a new tab for each section (see below) and feel welcome to change the order of the tabs to reflect the suggested order of the sections.
7
Section Title:
SAMPLE
8
Q1
This is a Main question
9
Question TypeMultiple choice
10
ResponsesResponse 1
11
Response 2
12
Response 3
13
Response 4
14
Other (with Text)
15
16
Q 1.1
This is a Sub question. Sub Questions are identified by having the same main number as the main question along with a decimal number in order of the sub.
17
Question TypeLong answer
18
19
There may be many questions in a section
20
There may be many subquestions under each question
21
Each question has a priority level associated with it. Governing Body will determine the absolute Priority 1 items (e.g., security) and will likely leave the prioritization of all other items to the individual client.
22
23
There is a consideration to have some questions identified as mandatory for a system to be considered an Electronic Health Record. For example, a number of the questions in the security area must be answered in the affirmative if the vendor's system is to be considered an EHR.
24
25
Short Stories meant to demonstrate the importance of this project
26
Story 1A prospective client has just taken in a substantial amount of investment capital with the objective of openning a number of dental offices. The internal trainers were familiar with traditional requirements and they focused entirely on front end functions. As such, they pushed their CEO aggressively to select a system that, while it contained interface functions for their office needs and was friendly to use, had no security compliance and had no ability to provide for the warehousing needed by head office for business functions. The limited focus led to an decision that created the highest likelihood of failure for the company due to poor business organization and extreme risk of compliance related fines (also meaning highest risk of data exposure for patients). The sales people were convincing to the trainers and successfully had them focus exclusively on the few static user items.
27
If this document were available, the CEO and trainers could have used it to better understand what to ask and could have required prospective service providers to complete the questionnaire. They could then have made an informed decision and would have taken much less time to make the best decision for them.
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Intro
Introduction
Security
Data Hosting
Use Monitoring/Tracking
Data Migration
Application Information
Customer Support
Charting
Imaging
Forms
Collaborations-Internal
Collaborations-Exernal
Progress Notes
Financials
Administrative Notes
Standardization, Expansion & Integration
Letters
Grading
Insurance
System Configuration
Reporting and Data access
Big Data
Patient Portal
Treatment Planning
Patient Education
Scheduling
Head office functions
Self-Check in
Dispensary