| Literature DB >> 35949684 |
Shahram Oliaei1, Amirali Karimi2, Ahmadreza Shamsabadi3, Pegah Mirzapour4, Hengameh Mojdeganlou5, Zahra Nazeri6, Amir B Bagheri7,8, Newsha Nazarian9, Reyhaneh Jashaninejad10, Mohammad Qodrati4, Iman Amiri Fard11, Farzaneh Ghanadinezhad12, Arian Afzalian2, Mohammad Heydari13, Esmaeil Mehraeen4,13, SeyedAhmad SeyedAlinaghi4.
Abstract
Background and Aims: Hyperbaric oxygen therapy (HBOT), utilizes 100% oxygen at pressures greater than sea-level atmospheric pressure, for the treatment of conditions in which the tissues starve for oxygen. The Undersea and Hyperbaric Medical Society (UHMS) has granted HBOT approval for the treatment of various conditions. On the other hand, applying informatics registry systems can improve care delivery, ameliorate outcomes, and reduce the costs and medical errors for the patients receiving HBOT treatment. Therefore, we aimed to design, develop, and evaluate a registry system for patients undergoing HBOT.Entities:
Keywords: hyperbaric oxygen therapy; registry; registry systems; system development
Year: 2022 PMID: 35949684 PMCID: PMC9358536 DOI: 10.1002/hsr2.768
Source DB: PubMed Journal: Health Sci Rep ISSN: 2398-8835
Problem rating scale based on Nielsen exploratory evaluation model
| Score = 0 and average intensity = 0–0.5 | Without problem–no problem |
| Score = 1 and average intensity = 0.6–1.5 | Minor problem–no need to correct the problem |
| Score = 2 and average intensity = 1.6–2.5 | Small problem–low priority problem correction |
| Score = 3 and average intensity = 2.6–3.5 | Big problem–high priority problem correction |
| Score = 4 and average intensity = 3.6–4 | Serious problem–high need for problem correction |
Identifying roles of HPIRS users
| No. | User | Roles |
|---|---|---|
| 1 | Specialist physician |
Register into the system Log‐in to the system Record clinical data Demonstrate recorded data and debrief on treatment plan Present medication and laboratory orders Log‐out of the system |
| 2 | Nurse |
Register into the system Log‐in to the system Record admission and clinical data Demonstrate of recorded data and debrief on treatment plan Log‐out of the system |
| 3 | System administrator |
Register into the system Log‐in to the system Control of user access level Edit user profiles Generate reports from the system Log‐out of the system |
Abbreviation: HPIRS, hyperbaric patient information registry system.
Figure 1Use case diagram for the hyperbaric patient information registry system user
The scenario for registration in the HPIRS
| Use case name | Register | |
|---|---|---|
| Scenario | Registration of the user into the system. | |
| Brief description | Through this use case, the user enters and submits their identity information as well as a username and password. | |
| Actors | Specialist physician, nurse, and system administrator. | |
| Preconditions | Users must have been accepted by the system administrator before they were able to login to the system. | |
| Postconditions | The user's identity information, username, and password are saved. S/he is registered into the system. | |
| Workflow | Actor | System |
|
User runs the application. User requests the registration form. User enters identity information, username, and password. User presses the “submit” button. |
The system displays the identity information form. The system checks the entered information. The system saves the user identity information. The message “successfully registered” is shown. | |
| Exceptions |
If the user clicks the “back” button in any step, the system will exit without any changes. If the system encounters a problem saving the information, it will display the message and will exit the form without any changes. | |
Abbreviation: HPIRS, hyperbaric patient information registry system.
Figure 2Architecture of the HPIRS
Identified issues according to the 10 principles of Nielsen heuristic evaluation
| No. | Items | Totla number of identified problems (%) | Mean of severity ratings | Number of identified problems | Severity | ||||
|---|---|---|---|---|---|---|---|---|---|
| E. 1 | E. 2 | E. 3 | E. 4 | E. 5 | |||||
| 1 | Visibility of system status | 7 (10.29) | 0.4 | 2 | 2 | 2 | 0 | 1 | Without problem |
| 2 | Match between system and the real world | 6 (8.82) | 0.5 | 1 | 1 | 0 | 2 | 2 | Without problem |
| 3 | User control and flexibility | 8 (11.76) | 0.2 | 2 | 3 | 2 | 1 | 0 | Without problem |
| 4 | Consistency and standards | 9 (13.23) | 1.31 | 3 | 2 | 1 | 2 | 1 | Partial problem |
| 5 | Help to errors recognize and correction | 8 (11.76) | 2 | 4 | 0 | 1 | 1 | 2 | Minor problem |
| 6 | Error prevention | 5 (7.35) | 1.74 | 1 | 1 | 0 | 0 | 3 | Minor problem |
| 7 | Recognition rather than recall | 6 (8.82) | 1.56 | 1 | 2 | 1 | 1 | 1 | Partial problem |
| 8 | Flexibility and efficiency of use | 3 (4.41) | 0.4 | 2 | 1 | 0 | 0 | 0 | Without problem |
| 9 | Esthetic aspects and simple design | 3 (4.41) | 0.3 | 0 | 0 | 1 | 1 | 1 | Without problem |
| 10 | Help and documentation | 13 (19.11) | 2.9 | 3 | 3 | 4 | 2 | 1 | Major problem |
| Total | 68 (100) | 1.13 | 19 | 15 | 12 | 10 | 12 | Partial problem | |
Abbreviation: E, evaluator.