From: Technical requirements framework of hospital information systems: design and evaluation
 | Item | Delphi | Evaluation | |
---|---|---|---|---|
Mean Score | Yes | No | ||
1 | Using standard databases | 3.86 | 16 (100) | – |
2 | Handling the standard Persian language | 3.84 | 16 (100) | – |
3 | Handling an unlimited number of clients | 3.78 | 14 (87.5) | 2 (12.5) |
4 | Availability of standard templates for output and input information | 3.76 | 13 (81.2) | 3 (18.8) |
5 | Installing the client and server easily and standard form. | 3.73 | 16 (100) | – |
6 | Upgrading through the server easily and automatically | 3.73 | 14 (87.5) | 2 (12.5) |
7 | Employing standard programming languages | 3.71 | 15 (93.8) | 1 (6.2) |
8 | Compatibility with the international standards for client-server operating systems | 3.71 | 11 (68.8) | 5 (31.2) |
9 | Exporting data to different types of statistical programs | 3.71 | 11 (68.8) | 5 (31.2) |
10 | Generating customized reports | 3.68 | 9 (56.2) | 7 (43.8) |
11 | Application of server’s date and time rather than client’s date and time in the software | 3.63 | 13 (81.2) | 3 (18.8) |
12 | Execution of routines as services instead of manual execution | 3.55 | 12 (75) | 4 (25) |
13 | Being run in a network-connected mode using the client-server method | 3.52 | 13 (81.2) | 3 (18.8) |
14 | Providing predicted and routine reports | 3.52 | 14 (87.5) | 2 (12.5) |
15 | Adopting appropriate solutions to server connection among different units | 3.5 | 11 (68.8) | 5 (31.2) |
16 | Application of external devices and other devices in the system | 3.5 | 15 (93.8) | 1 (6.2) |
17 | Providing functional independence for clients of certain operating systems and platforms | 3.47 | 7 (43.8) | 9 (56.2) |
18 | Application of supported standards | 3.47 | 8 (50) | 8 (50) |
19 | Reporting through the Web Service | 3.44 | 7 (43.8) | 9 (56.2) |
20 | Providing all the technical specifications, relationships among tables, ERD, routines and among software classes as UML as well as other technical features of the database in writing and based on the RUP methodology for large projects or XP for small projects | 3.44 | 4 (25) | 12 (75) |
21 | Recording all the modifiable data and procedures in the database and avoiding storing them in the program code | 3.39 | 9 (56.2) | 7 (43.8) |
22 | Availability of a multilayer enterprise architecture for the design | 3.34 | 6 (37.5) | 10 (62.5) |
23 | Compatibility with the Web | 3.28 | 6 (37.5) | 10 (62.5) |
24 | Employing the procedures by using Commit and Rollback | 3.28 | 5 (31.2) | 11 (68.8) |
25 | Recording and editing data through the Web | 3.23 | 4 (25) | 12 (75) |
26 | Using open-source tools in the system design and production | 3.07 | 6 (37.5) | 10 (62.5) |
27 | Visibility of database contents and non-coding information | 3.02 | 8 (50) | 8 (50) |
Total | 3.53 ± 0.37 | 283 (65.5) | 149 (34.5) |