A healthcare client wants to process patient records with Claude. What should you settle before design work begins?
Why D is the answer
Whether the deployment route and contract terms cover regulated health data
Compliance constraints decide which platforms and data flows are even allowed. Settling them late forces a redesign.
In detail
- Compliance decides which platforms and data flows are allowed.
- Settling it late can force a redesign.
- Bring legal and compliance in during discovery.
Use case
An illustrative scenario, not a real incident.
A hospital group asks for a records assistant. The architect settles the contract terms and deployment route first, and that decides which platform is allowed.
See it in different ways
flowchart LR A["Classify the data"] --> B["Apply regulation"] B --> C["Choose deployment and vendors"] C --> D["Minimize and redact"] D --> E["Log and audit"]
mindmap
root((Compliance))
Health data
Contract terms
EU personal data
Lawful basis
Where it is processed
US federal
FedRAMP
All
Data minimization
Audit trailflowchart LR S0["Identify the data"] --> S1["Confirm terms and route"] --> S2["Choose the platform"] --> S3["Design"]
Key point: Compliance decides what can be built.
Why the other options are wrong
- A. How many tools the first agent should have and which team will own them
- Tool count matters only after the allowed path is known.
- B. Which model produced the highest score on a public reasoning benchmark
- A public benchmark does not decide whether health data may be processed.
- C. Which prompt style the clinicians prefer for summaries of patient notes
- Prompt style is a detail to settle later.