The building blocks of being a health informatician – part 2 of 3 (Course review)

Previously, I have written about the first part of The building block of being a health informatician trilogy. Then, during the first two blocks, we learned how to understand the context and user needs and how to engineer the requirement. In this second part, I will tell you my review on the third block where we learn how to evaluate various health informatics project.

Block 3 – Evaluation

How can someone know whether the health informatics solution met the user’s need or comply with the requirement or fulfill its original aim to solve a certain identified problem? Yes, as you thought, by evaluating it. Here we learned several methods of evaluation depending on the type of the project. So, there is no ‘one size fits all’ method. And as the previous block, we worked in a group.

Evaluation is a basis for improvement. Image by Tumisu from Pixabay

We were also assigned to write an evaluation plan on a health informatics project. My group chose a project which allows the patient to consult his/her condition to the artificial intelligence and get some recommendations and booking time for a real doctor visit. While on the other side of the system, the doctor could get the initial data previously inputted by the patient prior to the visit within the electronic health record. The solution could also act as a clinical decision support system, helping the doctor in establishing a diagnosis and providing recommendations. My group decided to plan an evaluation on how the acceptance and satisfaction level of the patient regarding using this solution.

Block 4 – Finishing touch?

The intense two weeks, of course, brought the students to its final week where the students were assigned with a real-world problem. But then, each student was on his/her own for this assignment. Each should apply the knowledge gathered during the previous blocks into developing the solution to solve the problem. Starting from planning how to acquire the user need and designing based on the required specification until planning the evaluation of the desired solution. The assignment could feel challenging if we did not pay much attention to the previous blocks. On the other hand, it seemed like a memory refreshing to the more active students. Another practice before jumping into the health informatician’s shoes.

The final exam is (almost) always the finishing touch. Image by StockSnap from Pixabay

But apparently, this block is not the end. In the next part, I will review the next course where we learned the more practical skills about standardization in the health informatics. So, stay tuned for the culmination of the trilogy.


LinkedIn: Winner Ng



Related posts