Chapter 43 — Industry or public-service practice | Engineering Privacy and data protection

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 43 — Industry or public-service practice

Lesson map

Lesson 43 published. Map, example, EX127.

flowchart TD
  N0["Learning outcomes"]
  N1["43.1 Working in governance"]
  N2["43.2 Conflicting demands"]
  N3["43.3 Professional conduct"]
  N4["43.4 Reflection"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX127"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["43.1 Working in governance"]
  N2["43.2 Conflicting demands"]
  N3["43.3 Professional conduct"]
  N4["43.4 Reflection"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX127"]

[Learning outcomes]
    |
    v
[43.1 Working in governance]
    |
    v
[43.2 Conflicting demands]
    |
    v
[43.3 Professional conduct]
    |
    v
[43.4 Reflection]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX127]

Learning outcomes

You will (1) work within an organisation's privacy governance; (2) handle conflicting stakeholder demands; (3) reflect on professional practice.

43.1 Working in governance

Zara spends a term inside Pellmore's privacy team as a junior engineer. She attends the privacy steering group where the data protection officer, engineering, clinical and commercial leaders meet. She learns that decisions balance legal duties, patient trust, clinical needs and business goals. Her role is to explain technical options and their consequences clearly. She sees that engineers who present options with evidence and trade-offs are listened to more than those who only say what cannot be done, and she adjusts her own style accordingly.

43.2 Conflicting demands

The commercial team proposes sharing aggregated usage data with an insurer partner. The data protection officer worries about re-identification and purpose compatibility. Zara analyses the request: the insurer wants clinic-level usage by condition. She shows that small conditions in small clinics could identify patients, and proposes publishing only differentially private aggregates at regional level under the existing release budget. The insurer accepts the regional data. The steering group records the decision. She learns that technical alternatives can often resolve apparent conflicts. The insurer had wanted record-level data.

43.3 Professional conduct

During the term Zara is asked by a manager to quickly pull a patient's full history to answer a complaint. She checks the purpose and confirms that the complaints process allows access to the relevant records only. She retrieves only what is needed and records the access. The manager is initially impatient but accepts the process. She reflects that professional conduct in privacy often consists of small acts of discipline under time pressure, which together build an organisation's culture more than policies do.

43.4 Reflection

At the end of the term Zara writes a reflective report. She notes that she underestimated how much of privacy work is communication and negotiation, and overestimated how often purely technical problems arise. She also notes that the data protection officer's independence, protected by Article 38 of the GDPR, gave the steering group a voice that commercial pressure could not easily override. Prof. Holm encourages her to keep reflecting in her career, because practice changes faster than any course can predict. She keeps a reflective log.

Worked example

Zara works in Pellmore's privacy governance, resolves an insurer data request with regional differentially private aggregates, retrieves only necessary records for a complaint and reflects on communication and the DPO's independence.

Synthetic case. The steering group and requests are synthetic; GDPR Article 38 is real.

Errors and limits

One placement shows one organisation's culture; others differ.

Exercises

EX127 — Insurer request. How was the insurer request resolved? Rubric: 3 = regional differentially private aggregates within the release budget;; 2 = mentions aggregates;; 1 = full sharing;; 0 = none.
EX128 — Complaint access. How did Zara handle the request for a full patient history? Rubric: 3 = checked purpose, retrieved only relevant records and logged access;; 2 = mentions purpose;; 1 = gave all;; 0 = none.
EX129 — DPO independence. Why did the DPO's independence matter in the steering group? Rubric: 3 = it gave a voice commercial pressure could not easily override;; 2 = mentions independence;; 1 = irrelevant;; 0 = none.

Synthesis

Chapter 43 places Zara in practice. Chapter 44 starts the capstone.

Continue studying — chapter 43 of 50

← Chapter 42 (draft) · Course chapter index · Chapter 44 (draft) →