fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 27069–27080

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:05:13 UTC

A.15.1:6.1 - Surgical case (overlap and episodes)

  • Top work occurrence: Appendectomy_Case_2025-08-10T0905_1142.
  • Actual method and containing-system relation: enactsMethod -> Appendectomy@Hospital-2025; SurgicalWorkOccursWithinServiceBoundary@Hospital-8472(Appendectomy_Case_2025-08-10T0905_1142, SurgicalService_A) obtains under the service delimitation declared in SurgicalServiceWorkBoundaryRelations@Hospital-8472.
  • Patient and administered dose: project relation specification MED-ADM-2026, owned by ClinicalAdministrationRelations@Hospital-8472, declares ClinicalWorkAdministersDoseToPatient(dose, patient, clinicalWork, interval). The stipulated administration facts make it obtain for MedicineDose_8472, Patient_8472, Appendectomy_Case_2025-08-10T0905_1142, and the surgery interval. This relation establishes only that administration claim. The case names no admitted predicates for theatre, consumables, or staff-time resource use, so those optional claims return missing-governor[SURGERY-RESOURCE-USE] and do not enter Work identity.
  • methodDescriptionRef: Appendectomy_v5.
  • A.13 Agent basis, performer System, and assignment: SurgicalTeamSystemRole is a declared local agential kind for coordinated operative action; its criterion requires goal-directed, condition-sensitive regulation of the stated surgical action, the fixture classifies OR_Team_A : U.System under it, and cited evidence supports that local criterion and classification for the surgery scope and window; no Grade or autonomy-profile claim is used. SurgicalTeamAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. OR_Team_A_SurgicalTeamAssignment_2025-08-10 is the obtaining occurrence: its holder is OR_Team_A, its assigned kind is SurgicalTeamSystemRole, and its extent covers the surgery. F.6 states that OR_Team_A performed this Work under that occurrence. The team System acts; the kind, species, and occurrence do not.
  • Operational parts: Incision (09:15–09:22), Exploration (overlaps with monitoring), Closure (11:10–11:35).
  • Episode: a brief power dip occurs from 10:02 to 10:07. The named surgery-continuity use applies HospitalWorkContinuityPolicy_2025, a C.2.1 policy episteme interpreted under Hospital-Operating-Scheme-2025; its stated pause-and-resumption criterion keeps both event-bounded fragments under the same parent Work. The power dip alone would not decide that grouping.
  • B.1.4 temporal roll-up: SurgeryORUtilizationAggregation-8472 uses union under ORUtilizationUnionPolicy-2025; SurgeryPatientLeadTimeAggregation-8472 uses hull under PatientLeadTimeHullPolicy-2025. Both consume the named surgery and part intervals; neither supplies a resource-use or acceptance relation.
  • B.1.6 resource roll-up: no positive aggregate is asserted in this fixture because the direct theatre-, consumables-, and staff-time resource-use predicates are absent. Preserve the Work and the administration relation and return missing-governor[SURGERY-RESOURCE-USE]; open B.1.6 only after the project declares those predicates and supplies their actual participants and facts.