DOC - Patient Record Summary

🏠Back to Home Page

The Patient Record Summary (file pat102.patient where 102 is the patient's numeric identifier) allows us to navigate through the self-contained components of the patient record. Below, Fig. 1, we see a summary view of the record (tab) for the patient with alias GEORGIOS_ANTONIOY_6998765432. There are buttons to create a NEW CLINICAL CASE and NEW ENCOUNTER as well as buttons for quick access to:

Fig.1 : Patient record summary displays name, age, contact information, the current clinical case, encounters, and various buttons for quick access to the self-contained components of the patient record (profile, medical history, current medication, and a catalogue of medical documents).
Fig.1 : Patient record summary displays name, age, contact information, the current clinical case, encounters, and various buttons for quick access to the self-contained components of the patient record (profile, medical history, current medication, and a catalogue of medical documents).

To display this open file in the Obsidian File Explorer (see Fig. 3). On the upper right side with the title, we click on the file icon (see Fig. 2)

Fig. 2: The icon that opens the Obsidian File Explorer to show us the location of the open file
Fig. 2: The icon that opens the Obsidian File Explorer to show us the location of the open file

Fig. 3: Display of the open file in the patient folder, Patient/100, using the Obsidian File Explorer
Fig. 3: Display of the open file in the patient folder, Patient/100, using the Obsidian File Explorer

There is also another icon, Fig. 4, which displays the open patient record file using the Windows System Explorer (Windows file explorer).

Fig. 4: The icon that opens the Windows System Explorer to show us the location of the open file
Fig. 4: The icon that opens the Windows System Explorer to show us the location of the open file

Also in the patient record summary view there is a link to open the current clinical case as well as a table that shows us all the encounters (with S/N, date and status) that the patient has completed together with the clinical case they are linked to. For example here we can embed the encounters and clinical cases for the patient with alias NICKOLAOS_PAPADOPOYLOS_6945678901:

🏠 ENCOUNTERS

(S/N)3CaseDateStatus
32Friday, August 23, 2024 at 11:30 AMplanned
21Tuesday, August 13, 2024 at 10:26 PMplanned
11Friday, September 15, 2023 at 05:30 PMplanned

  • Linked Notes & Graph View: Obsidian allows you to create connections between notes, forming a "network of information" that can be visualized through the graph view, effectively reflecting synthetic/analytical thinking. Linked notes make it easier to navigate between related topics. In Obsidian MEDILIG, all medical information is interconnected within the patient record folder.

Fig. 5: Network graph representation of the patient record. The patient record summary (`pat100.patient`) serves as the central node, with interconnected standalone files forming the patient record structure. Incoming edges represent key components: medications, medical history, encounters, clinical cases, and medical documents. Additional nodes are visible in the background, connected to the patient record files, representing appointments, physician, administrative secretary, contacts, and multimedia files embedded within the medical documents
Fig. 5: Network graph representation of the patient record. The patient record summary (pat100.patient) serves as the central node, with interconnected standalone files forming the patient record structure. Incoming edges represent key components: medications, medical history, encounters, clinical cases, and medical documents. Additional nodes are visible in the background, connected to the patient record files, representing appointments, physician, administrative secretary, contacts, and multimedia files embedded within the medical documents

Fig. 6: Network graph representation of the patient record. Here all nodes are shown at depth 2, meaning they are two steps (or connections) away from the central node (patient record - summary)
Fig. 6: Network graph representation of the patient record. Here all nodes are shown at depth 2, meaning they are two steps (or connections) away from the central node (patient record - summary)