Turning to FIG. 4, a further exemplary electronic health record system 400 is illustrated including the use of an integrated third party information provider application (e.g., a hook application to hook information and notifications). In particular, the example of FIG. 4 illustrates a system 400 for a using an application such as CDS Hooks, but the disclosure is not limited to such and could be applied to various other third party information providers. It is noted that in the particular example of CDS Hooks, user activity inside an electronic health record (EHR) system, such as the system 402 (also 200 as shown in FIG. 2), will trigger the CDS Hooks application in real-time. As an example, the system 402 may include a third party hook application, API, manager, or circuitry 404 that is configured to be triggered by events occurring in the system 402. In particular, the third party hook application 404 may monitor a system processor 406 or a workspace manager circuitry 408, as examples, for various events occurring in the system 402. When the event occurs, the third party hook application 404 may access a database 410 that includes clinical decision notification related to the various events occurring. In an aspect, database 410 may be separate or merely a part of the system database as illustrated by lines 412 and/or communicatively coupled to another database 414, which may be the database for system 402. The application 404 is configured to pull data, information, or notifications (termed “CDS cards” for the CDS Hooks application, in particular). Additionally, the database 410 may receive updated third party information directly from a network 416, which may be the internet as an example, or via the system 402 accessing proprietary information via the internet as illustrated by a dashed line communicative coupling from the system 402 to the network 416. Information obtained with application 404 is sent either to the processor 406 or the workspace manager 408, which in turn send the information or notifications to system devices 418 (e.g., device 202 in FIG. 2).