7. Rhythm, communication and writing SOPs

Draft — fill in days and times.

Meetings

• Lab meeting: weekly; notes are kept in the lab's project workspace.
• Imaging meeting and PIER meeting — the CNT clinical-research meetings; join when covering clinical workflows. Confirm current meeting participation, days and times before adding them here.

Channels

• Slack: day to day. The channel list is pinned in the general channel.
• Data-request queue and CRC trackers — the ticket queues (data science, data pull, new-data requests) and the scheduling trackers live in a PHI-approved tracker; ask the lead CRC for access.
• This wiki — procedures and this manual. Project workspace — projects, meeting notes, people pages (ask the PI).
• GitHub (penn-cnt) — code.

Getting help

• Servers, accounts, software — Submitting CETS & PMACS Helpdesk Tickets.
• Penn Medicine systems (PennChart, F5, Citrix, drives) — UPHS IS ticket; see Operations › Access & Accounts.
• Anything else — Important Contacts & Emergency Numbers.

How to write a new SOP

Use the house template:
1. Purpose — one sentence.
2. Scope — who this applies to.
3. Prerequisites — accounts, access, tools.
4. Procedure — numbered steps; one action per step; commands in code blocks.
5. Troubleshooting — the errors people actually hit.
6. Notes: caveats and known limits. Git records who changed the page and when; do not keep dates by hand.
Put it in the theme whose question it answers. Never include a password or a patient identifier. Link to related pages rather than repeating them. Write new and revised SOPs in American English.