Competing Code Provision Contextual Balancing — Safety vs. Confidentiality
P · Principle
Individual
http://proethica.org/ontology/case/136#Competing_Code_Provision_Contextual_Balancing_—_Safety_vs._Confidentiality
Properties
Instance of
CompetingCodeProvisionContextualBalancingObligation
http://proethica.org/ontology/intermediate#CompetingCodeProvisionContextualBalancingObligation
Applied to
Engineer A's competing obligations to maintain attorney-directed confidentiality and to warn tenants of imminent structural danger
Balancing with
Confidentiality Principle
Public Welfare Paramount
Concrete expression
The Board explicitly recognizes that the public safety obligation and the client confidentiality obligation may conflict, characterizes this as a 'natural tension within the Code,' and engages in contextual balancing to determine which obligation prevails under the specific facts — concluding that imminent structural danger to tenants triggers the safety obligation over the confidentiality obligation.
Confidence
0.95
Importance
high
Interpretation
When two code provisions appear to conflict, the engineer must engage in contextual balancing rather than mechanically applying either provision; the Board's analysis of BER 82-2 versus the current case illustrates how the same tension resolves differently depending on whether a conflict of interest exists and whether public safety is immediately endangered.
Invoked by
Board of Ethical Review
Tension resolution
The Board resolves the tension in favor of public safety disclosure when the danger is imminent and the confidentiality rationale (protecting client from adversarial disadvantage) is absent — but acknowledges that the same tension resolves in favor of confidentiality when no public safety concern is present (BER 82-2).
Source Evidence
Source text
Given these two cases, it is clear that there may be facts and circumstances in which the ethical obligation of engineers in protecting the public health and safety conflict with the ethical obligation of engineers to maintain the right of confidentiality in data and other information obtained on behalf of a client.
Text references
Given these two cases, it is clear that there may be facts and circumstances in which the ethical obligation of engineers in protecting the public health and safety conflict with the ethical obligation of engineers to maintain the right of confidentiality in data and other information obtained on behalf of a client.
While we recognize that this conflict is a natural tension which exists within the Code, we think that under the facts of this case, there were reasonable alternatives available to Engineer A which could assist him in averting an ethical conflict.
TTL
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://proethica.org/ontology/case/136#Competing_Code_Provision_Contextual_Balancing_—_Safety_vs._Confidentiality> a proeth:CompetingCodeProvisionContextualBalancingObligation,
owl:NamedIndividual ;
rdfs:label "Competing Code Provision Contextual Balancing — Safety vs. Confidentiality" ;
proeth:appliedto "Engineer A's competing obligations to maintain attorney-directed confidentiality and to warn tenants of imminent structural danger" ;
proeth:balancingwith "Confidentiality Principle",
"Public Welfare Paramount" ;
proeth:conceptCategory "Principle" ;
proeth:concreteexpression "The Board explicitly recognizes that the public safety obligation and the client confidentiality obligation may conflict, characterizes this as a 'natural tension within the Code,' and engages in contextual balancing to determine which obligation prevails under the specific facts — concluding that imminent structural danger to tenants triggers the safety obligation over the confidentiality obligation." ;
proeth:confidence "0.95" ;
proeth:discoveredincase "136" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-03-01T13:03:31.215609+00:00" ;
proeth:firstdiscoveredincase "136" ;
proeth:generatedattime "2026-03-01T13:03:31.215609+00:00" ;
proeth:importance "high" ;
proeth:interpretation "When two code provisions appear to conflict, the engineer must engage in contextual balancing rather than mechanically applying either provision; the Board's analysis of BER 82-2 versus the current case illustrates how the same tension resolves differently depending on whether a conflict of interest exists and whether public safety is immediately endangered." ;
proeth:invokedby "Board of Ethical Review" ;
proeth:principleclass "Competing Code Provision Contextual Balancing Obligation" ;
proeth:sourcetext "Given these two cases, it is clear that there may be facts and circumstances in which the ethical obligation of engineers in protecting the public health and safety conflict with the ethical obligation of engineers to maintain the right of confidentiality in data and other information obtained on behalf of a client." ;
proeth:tensionresolution "The Board resolves the tension in favor of public safety disclosure when the danger is imminent and the confidentiality rationale (protecting client from adversarial disadvantage) is absent — but acknowledges that the same tension resolves in favor of confidentiality when no public safety concern is present (BER 82-2)." ;
proeth:textreferences "Given these two cases, it is clear that there may be facts and circumstances in which the ethical obligation of engineers in protecting the public health and safety conflict with the ethical obligation of engineers to maintain the right of confidentiality in data and other information obtained on behalf of a client.",
"While we recognize that this conflict is a natural tension which exists within the Code, we think that under the facts of this case, there were reasonable alternatives available to Engineer A which could assist him in averting an ethical conflict." ;
proeth:wasattributedto "Case 136 Extraction" ;
prov:generatedAtTime "2026-03-01T13:14:37.525945"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 136 Extraction" .
Metadata
Extraction details
Discovered in case
136
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-03-01T13:03:31.215609+00:00
First case
136
Generated
2026-03-01T13:03:31.215609+00:00
Attributed to
Case 136 Extraction
Generated
2026-03-01T13:14:37.525945
Generated by
ProEthica Case 136 Extraction