The EngineConstitutional Accountability
Here: Constitutional AtlasStage: ObservationPerspective: EmployerDepth: Executive SummaryNext: UnderstandingReturn to the Constitution

Specialty 28

Urology

Where you are

Urology — Atlas

This specialty validates a distinct constitutional property of accountability (Volume II). Its canonical case, obligation architecture, and constitutional relationships are transcribed from the ratified specialty corpus.

Active constitutional concepts

  • Constitutional specialty
  • Canonical case
  • Constitutional property

Next: Review the canonical case and obligation architecture, then compare related specialties.

Back to the Atlas

Constitutional summary

Canonical case

Temporary Ureteral Stent Without Demonstrable Removal, Exchange, or Definitive Closure of the Obligation Created at Placement

Constitutional first cause

The Engine begins when: A temporary ureteral stent is placed and its intended removal, exchange, or reassessment requirement becomes known. The first cause is not later infection, encrustation, obstruction, or kidney damage. Those are possible consequences. The accountability obligation begins at placement.

Obligation architecture

  1. 1Event observed — Ureteral stent placed.
  2. 2Obligation 1 — Device identity recorded — The device, laterality, indication, placement date, and relevant characteristics must be documented. — Evidence: operative note, implant record, procedure report.
  3. 3Obligation 2 — Intended disposition established — The record must specify whether the stent is to be removed, exchanged, reassessed, or retained for a defined therapeutic reason. — Evidence: postoperative plan, removal interval, exchange schedule, documented exception.
  4. 4Obligation 3 — Removal owner identified — A named clinician, service, or program must accept responsibility for ensuring the future disposition occurs. — Evidence: assigned owner, accepted follow-up, stent registry entry.
  5. 5Obligation 4 — Patient informed — The patient must understand that the stent remains present, why it was placed, what symptoms require attention, and what future action is required. — Evidence: discharge instructions, teach-back, written device information, acknowledged plan.
  6. 6Obligation 5 — Future action scheduled — Removal, exchange, imaging, or reassessment must be ordered and scheduled rather than left as a narrative recommendation. — Evidence: procedure order, appointment, recall date.
  7. 7Obligation 6 — Obligation persistence maintained — The future-dated obligation must remain active after the original surgery, hospitalization, or stone episode closes. — Evidence: durable registry entry, active due date, unresolved-device list.
  8. 8Obligation 7 — Pre-due verification — Before the planned date, the system must confirm that the responsible service, patient, and required resources remain available. — Evidence: reminder, confirmation, authorization, transportation or procedural readiness.
  9. 9Obligation 8 — Missed-action escalation — A missed appointment, failed contact, or scheduling barrier must create a new escalation obligation. — Evidence: failed-contact record, rescheduling attempt, clinician escalation, certified communication where appropriate.
  10. 10Obligation 9 — Removal or exchange executed — The required procedure must actually occur. — Evidence: cystoscopy or operative record, exchange note, device removal documentation.
  11. 11Obligation 10 — Closure verified — The system must verify the device’s final disposition and close the obligation only when supported by evidence. — Evidence: removed-device record, imaging where indicated, updated implant status, documented continuing plan.

Constitutional observations

Constitutional lesson

A procedure can be technically complete while the accountability created by the procedure remains open. Temporary interventions require durable responsibility beyond the encounter that placed them.

What The Engine makes visible

Conventional records may each appear correct: the stent placement was successful; discharge instructions mentioned follow-up; a removal order was entered; the patient was told to call urology; the surgical episode was closed; the scheduler attempted contact. But those facts do not demonstrate that the temporary device ever reached its intended disposition. The Engine asks: Did the intervention-created obligation remain durably owned until removal, exchange, or justified continuation was verified? That is the accountability center of the case. The device itself becomes physical evidence that an unresolved obligation remains inside the patient. Constitutional-property mapping This case clearly exercises: CP-001 — Referral Continuity CP-003 — Dynamic Obligation Creation CP-005 — Evidence-Dependent Obligation Gating CP-007 — Distributed Obligation Convergence It also strongly reinforces the principle seen in Pulmonology and other future-dated pathways: Closing the initiating encounter does not close the obligation it created. But CP-003 already explains part of that phenomenon, so no new principle should be inferred automatically. Possible candidate observation: Planned Reversal or Removal The case may reveal a narrower pattern: Some interventions are incomplete by design until a later reversal, removal, exchange, or deactivation obligation is fulfilled. Examples may later appear in: temporary vascular filters; external or internal drains; temporary ostomies; orthopedic hardware intended for removal; central venous access devices; temporary pacing systems; postoperative packing or splints. This is worth tracking, but it should remain only an observed mechanism, not a constitutional candidate yet. The important question is whether it proves distinct from ordinary obligation persistence and dynamic obligation creation.

Constitutional relationships

Validated constitutional properties

Related specialties (shared properties)

Demonstration

No worked demonstration is provisioned for this specialty in this build. Occupational Medicine (Specialty 25) is the first domain and carries the worked demonstration; the constitutional architecture above is shared across specialties.