# Working with Progress Notes

Progress notes follow the general concept of SOAP notes as first proposed by L.L. Weed back in the 1970s.

- Reviewing Progress Notes
  - The EMR Journal
  - The EMR tree browser
- Entering a Progress Note
- Inputting the Reason for and Assessment of Encounter (RFE, AOE)
- Saving (or pausing) a Progress Note
- Multiple notes per enclosing Encounter
- Signing
- Editing, and the Auditing of edits
- Examples

## Reviewing Progress Notes

Different objectives require a different mindset in looking at a situation. The GNUmed progress notes viewers support just that. Currently, there are two of them:

### The EMR Journal

German EMR users (and others, we are sure) will recognize this way of looking at patient data. It chronologically lists clinical data based on when it happened (in nearly all cases this will be when it was entered into GNUmed). Within one date, the data is ordered by its SOAP category. Here are some things users need to be aware of:

- structural elements (encounters, health issues, episodes) are displayed, but are not taken into account for display-ordering
- some clinical data (such as lab data) is stored in the backend in a structured form, instead of as plain text
  - this means it is not shown in its "full glory" in the Journal
  - rather, the relevant data (say, test name, result value and normal range) is extracted from the database
  - nevertheless, the full detail will remain available for display via another viewer (TBA)

This EMR Journal viewer is "read-only".

### The EMR tree browser

This viewer displays clinical data in a tree-like view. The EMR structure forms the trunk and branches while the actual progress notes form the leaves. The left hand side displays the tree structure:

EMR of patient ...

- health issue 1
  - episode 1
    - encounter 1
    - encounter 2
  - episode 2
    - encounter 1
    - ...
    - encounter n
  - ...
  - episode n
- health issue 2
- ....
- health issue n

Single left clicking a tree item causes display of details associated with that item on the right hand pane. Selecting an encounter item will display the progress notes associated with it on the right hand side. They will be selective to the episode the encounter is listed under. Note that one and the same encounter can be listed under several episodes -- namely when the patient attended the clinic with several problems at once.

All Past History Items will appear as first level items in the EMR tree with or without child indicator. Active issues are bold. Sorting is alphabetical, on issue label.

A special "placeholder" health issue, Unattributed, serves by default to group together any and all episodes that had never been, or are presently not, attached to any existing health issue. The sorting algorithm programmatically sorts this Unattributed item at the top, and otherwise sorts issues by name, within which episodes sort by their earliest access time, and encounters by their start time.

Right-clicking on a tree item pops up a context menu, permitting editing of the item's filing data (not the raw data) so as to be able to relocate it under some other tree item or episode.

## Entering a Progress Note

To enter a note you have to follow these steps:

- activate a patient with the patient search box in the top panel
- raise the Notes tab
- type your note – see screenshot
- save it into the EMR
- somewhere along the way, you'll have to decide which episode the note belongs to

Progress note items would be displayed as belonging either to an episode which itself belongs to a health issue, or to a freestanding (Unattributed) episode. For reference, refer to a screenshot generated from gnumed-client 0.4.6-1.

If, within the Active Problems list, you are confident to select an issue or episode with which to associate a new progress note (or progress note portion), double-click that item from the list. You will then be provided a pre-associated progress note editor into which to make your entry. Entries that had been made under health issues will, at the point of saving, prompt you to select (or add) an episode for that issue.

If you do not yet know the associated episode - which often happens with new patients, or new problems in old patients - you can use the pre-opened unassociated progress note editor or open yourself a new one with the appropriate button. Once you realize a good name for the new episode you can type it into the first line of the editor which will suggest episode descriptions from the existing ones or allow you to start a new one. If you haven't typed a name for the new episode but have pressed [save] you will be asked to provide an episode name.

Pressing [save] will save the progress note into the EMR of the currently active patient and close the related progress note editor.

## Inputting the Reason for and Assessment of Encounter (RFE, AOE)

#fixme - anyone please add from this thread on the devel archive.

## Saving (or pausing) a Progress Note

In a paper paradigm, it is possible to partially write a note, and to "pause" an encounter until missing information is obtained (or a quickly-available test performed). During this time, other patients may need to be seen. By holding onto the charts of all involved patients, the doctor has total control over documentation, at the cost of making the charts inaccessible to others. A signature, which can identify the writer, gets added, however the entry may be recognized to have errors, or to be incomplete. Space may or may not permit edits, such as the repair of misspelt words, or the marking of a line through an incorrect word or phrase, or the insertion of additional words but these may be unable to be done clearly, cleanly indicating when these had been done and, in some jurisdictions, are wholly prohibited. Yet corrections which can only live in downstream entries are of dubious adequacy to protect the patient.

In an EMR, progress notes are entered into computer memory, and must at some stage be written and recorded ("committed") into the patient record ("database"). Until the doctor is ready to let the information be saved, the only option for maintaining an uncommitted note is to keep it in memory.

In GNUmed, this means not pressing the progress note "Save" button, and not bringing up a different patient, until you are ready to "Save". The "Saving" of a progress note is prompted by any action, within the running GNUmed session, to activate a different patient, or to exit the session.

GNUmed permits the currently-running session ("instance") to be set aside — "minimized" by your computer system — while you open any number of additional session windows, in which you can manage additional patients concurrently (this is done by just "starting" a second instance of GNUmed, or a third, etc...).

Pausing an entry in this way will work provided the timeout setting of the system is not exceeded. When a consultation with a patient (or chart) needs to be interrupted, for example to send a patient for a test after which the consultation is intended to continue, the provider can choose whether to keep the current progress note paused, or whether to formalize the note (Saving it), and simply make another note after the return of the patient. This scenario enjoyed some email exploration, archived here.

## Multiple notes per enclosing Encounter

It is possible to record two or more progress notes (or notelets) as relating to the same, single encounter. This can be achieved from within a single session at the computer, or from two different sessions. In order to avoid making the user decide every time, GNUmed has put in place configurable encounter interval "thresholds": below the lower one, an encounter is always continued; above the upper one, a new encounter is automatically created; and between the two, GNUmed will ask whether to continue the old one.

## Signing

The GNUmed architecture does not presently provide for unsigned vs signed "state" for progress notes. Progress notes are de facto witnessed by their creators. As such, progress notes are a somewhat different entity from incoming results. For test results and for archived documents, signing is already supported.

A later stage of GNUmed may implement the signing of progress notes. Some of the implications if notes were required to be signed, and if all changes (including trivial) are forced to be brought to everyone's attention, are archived here (1, 2, 3 ).

## Editing, and the Auditing of edits

What if a "Saved" note was incomplete, or contained an error? Clearly, it is always an option to add a new note, to serve as an addendum or supplement. However, in those cases where a prior note should not be left in its existing form, GNUmed will make notes editable. As a result of any editing, a new version of a note will sit on top of all prior versions going back to the original, with all prior versions relocated to the associated "audited" table. Making evident any alteration(s) to a progress note is the project to do list, as is already enabled (in client v 0.3x) for revised test results, as demonstrated at the bottom of this exposed tooltip with associated handling description archived here?. In the meantime, any disputes over record version(s) would be able to be resolved using external tools such as pgadminIII.

## Examples

One or more will be built up over time... see ProgressNoteExamples

Next: Structuring the EMR

%TWISTY{id="topicattachmentslist" mode="div" remember="on" showimgleft="../rsrc/System/DocumentGraphics/toggleopen.png" hideimgleft="../rsrc/System/DocumentGraphics/toggleclose.png" link="Anhänge 1" linkclass="patternTwistyButton"}%

Topic-Anhänge
I | Anhang | Aktion | Größe | Datum | Wer | Kommentar
--- | --- | --- | --- | --- | --- | ---
png | Notes_input_plugin.png | verwalten | 150.1 K | 18 Jul 2011 - 19:20 | JamesBusser | Screenshot of Notes plugin, with explanation (within SOAP) of how it works.

%ENDTWISTY%