Module 1 “Understanding” — Lesson 37 · Reading time approx. 6 min

Anyone who takes a genogram to supervision or a seminar needs a version without names but with all the patterns. This lesson shows what may stay, what must go, and where the line to re-identification lies.

Names Gone, Patterns Stay

In supervision, what counts is how a family functions. What it is called does not matter. The group has to see the triangles, the ruptures and the repetitions across generations. It does not need names for that.

Still, the file usually holds the full version. With names, occupations and notes. Anyone who carries it into the group unchecked passes on more than the purpose requires. The solution is a second version. It shows the same pattern, but no names.

Two genograms of the same made-up family across three generations, side by side. On the left, the people carry first names and birth years, and the mother also carries the diagnosis code F32. On the right, the letters A to G stand in place of the names; birth years and F32 remain. Lines, symbols and arrangement are the same in both versions.
Figure 1: On the left the working version, on the right the version for supervision. The pattern is the same, only the names are missing. The diagnosis stays visible, as in the view in GenoEasy. Made-up family.

What “Pseudonymized” Means

The GDPR knows two terms that are often confused.

Pseudonymization means: The data can no longer be attributed to a person without additional information. That is what Art. 4(5) says, in essence. The additional information must be kept separately. In a genogram, that is your key: Who is “Person A”?

Anonymization goes further. Here the person can no longer be identified, not even with additional knowledge. Recital 26 describes the standard. What has to be taken into account is “all the means reasonably likely to be used, such as singling out” to identify a person. This includes cost and time.

The difference has a practical consequence. Pseudonymized data remains personal data. The duty of confidentiality still applies. Only true anonymization takes the data out of data protection law. And that is hard to achieve with a genogram.

What May Stay and What Must Go

As a rule of thumb: What carries the pattern may stay. What names a person must go.

  • Structure and sequence of generations
  • Symbols for gender
  • Relationship lines, separations and deaths
  • Years of birth or age
  • Diagnoses as patterns

Must go, because it names the person:

  • First and last names
  • Occupations
  • Addresses and places
  • Names of schools, employers and institutions
  • Free-text notes and photos

The file name and the header of the printout also belong to what must go. “Family M. from Köpenick” pseudonymizes nothing.

Why Three Harmless Details Together Give a Family Away

Each detail on its own says little. Together, they can give a family away.

Hypothetical case example: A counselor is preparing a case presentation for their supervision group. They replace all names with letters. They leave in the diagnosis of a very rare metabolic disorder, the child’s exact date of birth and the place of residence, a village of 900 inhabitants. A colleague from the neighboring district is in the group. This colleague knows a support group for exactly this condition. After one glance at the slide, the colleague knows which family it is, although no name appears on it.

That is the idea behind “singling out” in the recital. Anyone who knows the diagnosis, the date of birth and the place does not need the name. The rarer the detail, the stronger its effect. A common diagnosis in a big city reveals hardly anything. A rare one in a small village reveals almost everything.

Three Occasions, Three Levels of Detail

How detailed the information may be depends on the occasion.

  1. Supervision. The group is small and bound by confidentiality. Here the version without names is usually enough. Years of birth and diagnoses may stay, because the group needs them for its hypotheses.
  2. Teaching and case presentation to a larger or outside audience. Here you give coarser values. Instead of the date of birth, you give the age or the decade. Instead of the place, you give the region. A rare diagnosis you group into a category, such as “chronic illness in childhood”.
  3. Publication. Pseudonymizing is not enough here. Either the family consents, or you change the picture so much that no one can recognize them.

A test helps with the decision: Could anyone in the audience know this family? If so, show less.

Checklist Before Passing It On

  • Have all names, occupations, places and institutions been replaced or removed?
  • Do notes and labels still contain clues to people?
  • Is the combination of diagnosis, age and region too distinctive?
  • Is the file named differently from the family?
  • Is the key (“Person A is …”) stored separately and securely?
  • Is the necessary release from confidentiality in place for this occasion?

How It Works in GenoEasy

GenoEasy comes with a pseudonymized view for this. You switch it on with the button in the side toolbar, or via the “Security” menu.

The view replaces names, occupations, notes and labels with placeholders such as “Person A”. Health information, dates of birth and places deliberately remain visible. This also applies to session notes. Read them through before the supervision. That way the pattern stays analyzable.

Three things you should know:

  • It is only a view. What gets saved is always the real data.
  • A notice appears before you switch it on. It names as a prerequisite the client’s release from confidentiality and participants who are themselves bound by confidentiality.
  • The view is not intended for presentations or publications. There, the coarser details from levels 2 and 3 apply, which you set by hand.

The feature is available only in the full version, not in the demo.

Sources