“… • In an EHR, providing overview of the patient data is of vital importance [ 8 , 27 ] • It should be possible to link problems and interventions, as problems are not always treated one at the time, to prevent fragmentation of the patients data [ 8 , 10 , 12 , 13 ] • The problem list should represent the patient data in a coherent and logical order, so it provides a cornerstone of the EHR, preventing errors due to missing information [ 11 , 15 , 18 , 21 , 25 , 36 ] • If well maintained and structured, a problem list can assist a multi-disciplinary approach [ 10 , 13 , 16 , 36 ] • Policy should help with constructing the overview of patient data, providing guidelines for adding or leaving problems of the list reducing confusion and preventing missing information [ 14 ] | Quality of care The definition of quality of care is used in the broadest sense of the term, all which can influence the care of the patient. | • If all patient information is related to problems and the problem list is often updated it allows for an evaluation of the efficacy of the treatment [ 7 , 13 , 15 , 22 , 33 ] • Communication and coordination between health professionals is supported by the problem list [ 7 , 10 , 15 , 18 , 21 , 22 ] • Clear policy on what to put on the problem list and for the users clear structure is essential [ 9 , 10 , 14 , 18 , 19 , 27 , 29 ] • The problem list is a valuable tool to get overview of the data of (unfamiliar) patients [ 7 , 8 , 11 , 12 , 14 ... |
…”