Safest minimum launch model and opening-readiness gates
Confirm the day-one clinical scope.
Define which procedures can activate and under what gates.
Confirm the referral-to-booking workflow.
Approve the billing architecture or record remaining exceptions.
Approve the role framework in principle and send drafts to HR/legal review.
Confirm the public-information approval queue and next owners.
Decision, defer, or assign a clear next step. Do not leave a provisional item looking final.
Approved and ready to operate on.
A working position, pending doctor sign-off.
Cannot proceed until explicitly cleared.
Out of scope for this launch, by choice.
Working assumptions are useful for planning, but they do not authorise clinical delivery, public claims, booking, or implementation.
Not every candidate procedure is available on day one.
DEC-02 and DEC-10 are recorded as done and should be treated as the current operating rule unless the doctors explicitly reopen them.
Consultations plus selected procedures from day one, subject to individual clinical readiness gates.
Do not present the populated final-decision field as approved while the record remains "In progress."
Reception can acknowledge and coordinate; reception does not interpret clinical urgency or provide clinical advice.
Medicare claim processed after the consultation and payment workflow.
Verify the final policy against current billing, consumer-law and medical-indemnity advice before implementation.
Position descriptions do not replace employment contracts, service/facilities agreements, credentialing, scope-of-practice approvals, or privacy documentation.
Anaphylaxis Response Protocol — AI DRAFT, generated 19 July 2026. Not reviewed, not approved, not for clinical or operational use.
Source: Anaphylaxis Response Protocol
Every deferred item needs either an owner, a trigger, or an explicit reason to revisit.
Decisions belong in Doctor Decisions.
Implementation work belongs in Launch Tracker.
Clinical records and patient-identifiable information belong in Gentu.