Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:25:20 UTC
A.15.2:6.1 - Hospital OR day plan (shift rota + cases)
WorkPlan:OR_DayPlan_2025-08-12-E3 : U.WorkPlan is one C.2.1 episteme. Its present EntityOfConcern is exact existing system OR-Service-System-12 : U.System; its effective reference scheme is HospitalORPlanningScheme-E4; its horizon is 2025-08-12T00:00:00+03:00/2025-08-13T00:00:00+03:00. Proposed case performances remain ClaimGraph designators and are not dated Work occurrences.
One PlanItem:Case_1_Appendectomy coordinates proposed performance PlannedAppendectomy-Case1 through the following exact content.
intended performer and system-role-kind conditions
one performer System satisfying SurgeonSystemRole and AppendectomyLeadCapability-v3; one performer System satisfying AnesthetistSystemRole and ORAnesthesiaCapability-v2; these are intended conditions, not system-role assignments
budget and reservations
90 minutes of OR-3, one SterileKit-A17, and consumables budget ORCase1-Consumables-B3
dependency
positive PreOpClearance-Case1-E2 claim must be current before the planned window starts
acceptance target
procedureCompleteBy10:30, compared under C.27.TA against the exact Work extent after Work occurs
baseline
exact C.2.1 episteme OR-DayBaseline-2025-08-05-E1
Later Work: A.13 first recovers the surgeon and anesthetist as the exact actual performers through their respective obtaining assignments, and A.15.1 independently admits AppendectomyWork-2025-08-12-Case1 : U.Work with workContinuityPolicyRef = SingleProcedureFromAnesthesiaStartToHandover-E1, temporal extent 2025-08-12T09:04:00+03:00/2025-08-12T10:21:00+03:00, and enactsMethod to LaparoscopicAppendectomyMethod-E2. Because the named one-case policy expressly consumes both assignment-bound attributions, F.6 afterward establishes performedUnderAssignment for RA-Surgeon-DrK-2025-08-12 and RA-Anesthetist-DrM-2025-08-12 through those same assignments. The named policy tests the exact within-window claim qualified under C.27.TA. The plan created none of those facts, and either failed F.6 relation would leave the Work intact while preventing this attribution-dependent fulfilment conclusion.
Named one-case policy:ORCase1FulfilmentPolicy-E2 is one exact C.2.1 episteme about exact plan episteme OR_DayPlan_2025-08-12-E3, interpreted under HospitalORPlanningScheme-E4. Its ClaimGraph is limited to item Case_1_Appendectomy and states positive polarity only when the identified Work enacts the target Method, both required performedUnderAssignment relations obtain, and its extent lies inside the planned window. It uses only those four facts for this local conclusion, does not travel to another plan episteme, and admits no fulfilment relation kind.
Visible result: C.2.1 assertion episteme OR-DayPlan-Case1-Fulfilment-Assertion-E1 has OR_DayPlan_2025-08-12-E3 as its exact EntityOfConcern; its ClaimGraph names AppendectomyWork-2025-08-12-Case1, item Case_1_Appendectomy, policy ORCase1FulfilmentPolicy-E2, the four supporting facts, and positive polarity. The result says that this Work satisfies this plan item under that policy. It does not rewrite the plan and does not assert a universal relation.
Nearest false shortcut: a theatre log row carrying key Case_1_Appendectomy and start time 09:04 establishes neither performedUnderAssignment nor enactsMethod. Without those independently obtaining facts the local conclusion returns missing-information; matching labels and times produce neither negative polarity nor fulfilment.
Edition boundary:OR_DayPlan_2025-08-12-E3 is the first plan episteme used for this day, so this case has no EpistemeEditionRelation and needs no change note. If planners later change its ClaimGraph but establish no edition predicate, C.2.1 identifies a new, non-continuing plan episteme. Reusing the day-plan label or adding a Rev-4 note cannot turn that replacement into a continuation; a later policy must name whichever exact plan it judges.