The Concepts used in the GNUmed EMR

Synopsis

If you know what this is all about, you can stop reading here, and jump to StartingGnumed.

What it All Means

The Encounter

An encounter is a one-off contact of a patient with the health care system. In a GP setting most encounters start when the patient enters the building and usually end when the patient leaves the building. Contact with a doctor may or may not have taken place. An encounter need not end on the day it started, eg when care is given over midnight the encounter will span a date boundary. Likewise there may well be two or even three encounters in one day (think of patients you see in the practice in the morning, send home but have to admit to hospital in the late evening).

Technically, in GNUmed an encounter need not always include human interaction. So over and beyond the usual patient-provider consultation the following situations are considered encounters, too:

Problem-Oriented Documentation of Care

This means that all recorded clinical data is associated with an explicitly stated problem suffered by a patient. Problems need not be diagnoses. They need not be hard scientific facts. They can be syndromes, they can be findings, they can be history items. Over time they are likely to merge and consolidate into well-founded diagnoses. Or they may not. That is the beauty of GP level healthcare.

Note that during one single encounter, several problems with the patient's health can be dealt with.

The SOAP Schema

In 1964 Lawrence L Weed introduced the SOAP structuring of progress notes in medical records. This concept roughly says that all clinical data associated with giving care to a patient is to be grouped into the categories Subjective, Objective, Assessment, and Plan. Various criticisms have been put forth as to where this classification lacks sophistication or falls short of properly capturing clinical information. However, setting aside academically-proper validation and evaluation, most clinical data at the GP level can be grouped into one of:

Each problem will, in GNUmed, have its own, dedicated, SOAP-structured data.

The Episode of Care

In the course of possibly several encounters a few health problems will be worked on. The time from the first until the last encounter for a given problem is the corresponding episode of care. It is entirely at the discretion of the clinician how long the episode lasts. Usually an episode will only be assumed to be "case closed" after the patient did not report back for an extended period of time, or when some knowledge of resolution has somehow come to the clinician.

Each episode of care may comprise one or several encounters. While GNUmed does not yet model this graphically, an analogy based on an example at Dipity, may inform. Encounters would distributed from left to right along the patient's time line. Episodes would each form a horizontal stripe, with the various stripes "stacked" vertically, with each episode positioned at an _arbitrary height, with a left edge determined by the episode start date, and a right edge defined by the episode's end date, except if the episode remains open / active.

An episode may be associated with a health issue.

The Health Issue

At times the clinician will recognize a cluster or subset of distinct episodes of care as looking suspiciously related. In such cases it may make sense to group them under one health issue. Thus, health issues are fundamental issues with a patient's health. They may be active or inactive. Post-MI state is likely to be clinically relevant for the rest of the patient's life. It may not be an active problem at a given time, however. On the other hand, a traumatically amputated finger will always be both clinically relevant and active, if it confers ongoing disability. Health issues will more often be expressed as diagnoses, than will "problems". In GNUmed, past medical history items will mostly be stored as health issues.

Setting aside simple "past history" items, each health issue will aggregate one or several episodes of care.

The Problem List

The problem list (the list of active problems) consists of items being worked on, or kept in mind, while trying to improve the health of the patient. This list includes:

Putting Things Together

The structure of a patient's EMR can be seen as a tree:

* health issues aggregate clinically-related episodes of care

* a further treatment of how this works, but which you may rather skip for the moment, is initiated at EncounterEpisodeIssue

Next: Starting Gnumed


Literature

(sorted by lastnames of authors)