BHW Medical

Staff Guide — Where Everything Is

BHW Medical Group · BHWcrewOS
Updated September 30, 2026
Patient Requests + Role-routed Clinical Alerts + Team Notes + Staff Chat + Website Content + Document Builder + BHW Capture
Type what you're trying to do. Sections that don't match will hide.
Everything starts herecrewhq.bhwmedical.org/crewosSign in with your name + PIN
Your live workPatient Requests + 🔔 alertsOne Google-backed queue
Main line — Dialpad(443) 762-5343Approved calls and patient texts
Fax — iFax(833) 258-3941Referrals, records, orders

01Signing in & your home page

How to get in

  1. Go to crewhq.bhwmedical.org/crewos on any phone, tablet, or computer.
  2. Pick your name from the list, enter your PIN, tap Sign in.
  3. You land on your home page — the front desk role lands on Front Desk, the care coordinator on Chronic Care, primary care providers on Primary Care, and so on.
Everything else is one tap away. The list down the left side (or across the top on a phone) is the rail — every page you're allowed to see lives there. You always land on your own page; you're never locked out of the others.
Never share your PIN. Every action you take is stamped with your name. If you think someone else knows it, tell the practice owner and it gets changed.

02The rail — what each page is for

Your pages

PageWhat it's forWho uses it most
Your division page
(Primary Care, Chronic Care, Mind & Mood, CharmEd, Porter House, Flow)
Warm handoff inbox, referral queue, upcoming schedule, resources, and the tools built for that divisionEveryone, on their own division
Admin MasterEvery division at once — open referrals, aging, full schedule, minutes rollupOwner, operations lead
My SpaceYour role & responsibilities, the office calendar, your availabilityEveryone
Patient RequestsThe authoritative staff work queue for patient calls, texts, portal messages, voicemails, referrals, prior authorizations, medication requests, billing requests, and general follow-upEveryone, filtered by role and service line
🔔 CrewOS clinical alertsOptional, minimum-necessary alerts for clinical work routed to your role. Front Desk receives patient-access and referral work; MA/BHA receives medication, authorization, and clinical-review work; Care Coordination receives referrals and care-review work; RCM receives billing and authorization work. Providers receive provider-attention items only. Managers receive urgent, safety, and escalated items instead of every open request. Raw fax alerts stay in Front Desk OS. Open the bell and use Notifications on/off for that device.Every signed-in staff member chooses
Front Desk OSPatient lookup, referral finder/generator, fax tools, and front-desk operational snapshots. Work communication requests in Patient Requests so they are not duplicated.Front desk role
Panel & DischargesUtilization, HEDIS scorecard, hospital discharge trackingOwner, care coordination role
Positive ANA?Analyze an ANA result, immune patterns, 100 conditions, management protocolsProviders
Hormone AnalysisLab-based hormone interpretation with ratios and patternsProviders
Billing ToolkitCare management documentation, audit tool, and every preventive code with its ICD-10Billing role, providers
Care Program SOPSearchable intake, enrollment, consent, care-plan, documentation, billing-readiness, risk-scoring, and fee-schedule guidance for APCM, CCM, PCM, BHI/CoCM, CHI, PIN, RPM/RTM, and TCMCare coordination, providers, billing, operations
BHW CrewCareProvider doorway to the Google Patient Requests queue, Health 360 Care Plans, and the protected Patient RegistryProviders
Website ContentDraft, preview, review, schedule, publish, and archive Care Connect announcements, public resources, and practice detailsShade, designated staff, operations manager
Patient page previewsWhat patients see for each programAnyone, for reference

02bWebsite Content — public updates

Use this page for general Care Connect information that patients may read. It is not a patient chart, message inbox, clinical documentation tool, or place to store private files.

Safe publishing procedure Shade + designated staff

  1. Open CrewHQ → Website Content and choose Announcement, Resource link, or Practice detail.
  2. Write the exact public wording. The approved staff ChatGPT may help with wording, but never paste patient information, private links, passwords, API keys, or other credentials into it.
  3. Review the on-screen preview, dates, links, display order, and optional start/stop time.
  4. Check the no-patient-information confirmation, save the draft, and verify the page says Saved to BHW Cloud.
  5. Select Submit for review. An operations manager or executive reviews the exact wording and selects Publish.
  6. Open Care Connect after publication and verify the public result. If something is wrong or no longer current, archive it instead of silently overwriting history.
What can go here: office-hour changes, closures, general program announcements, non-personal educational resources, forms, and public contact details.
What cannot go here: any patient's name, birth date, telephone number, email, diagnosis, medication, appointment, request, image, document, or individualized medical advice. Route those through the protected clinical workflow.

03The daily rhythm

Front desk day Front desk role

  1. At sign-in — open the 🔔 alert bell. Review urgent, escalated, overdue, and unassigned work routed to Front Desk.
  2. Open Patient Requests. Assign each unclaimed front-desk request, then tap Start when work begins.
  3. Work by urgency. Urgent/escalated first, then overdue, then routine requests in received-time order.
  4. Check the shared inbox once at 9:00 and again around 3:00 as a backup for anything that did not enter CrewOS automatically. Do not create a second request if it is already present.
  5. Before you leave: every urgent or escalated item is resolved, handed to the correct role, or has a documented next step.
Patient Requests is the one queue. Patient texts, missed calls, voicemails, portal requests, and supported intake channels write into the Google-backed workflow. The shared-inbox sweep is a safety check—not a second worklist.

What the colors mean

ColorMeansDo it by
🔴 BREACHUrgent item with no response yet, over 2 hours oldRight now — stop and handle it
🟠 At riskHigh-priority item approaching 48 hoursToday
🟡 AgingRoutine item approaching a weekThis week
🟢 On trackWithin its windowNormal flow
The clock stops when you tap Start — not when you finish. If you've reached out and are waiting on the patient or a specialist, Start it so it stops screaming red while you wait.

03bPatient Requests training — the one work queue

Use this module for new-hire orientation, role changes, and annual refresher training. It teaches the live CrewOS workflow without using real patient data.

Purpose, scope, and pass standard Trainer + trainee

Purpose: teach staff to safely receive, claim, advance, communicate about, and close patient work in the Google-backed Patient Requests page.

By the end, the trainee can…Pass standard
Explain which system is authoritativePatient Requests in CrewOS is the one work queue. Google Chat is a no-PHI alert/action mirror, not a second queue.
Work only appropriate requestsUse the request's routed service line and the staff member's authorized role. Escalate instead of working beyond role or license.
Record the real milestoneAssign, Start, and select the exact outcome that actually occurred—never skip from submitted/sent to approved/scheduled.
Coordinate with coworkersUse request-linked Team Notes and optional @mentions. The note stays in protected CrewOS and is never sent to the patient or copied to Google Chat.
Handle patient communication safelyUse only approved no-PHI wording, confirm delivery status, and never describe suppressed, queued, failed, or gated messages as delivered.
System boundaries: Google Cloud/Firestore stores the patient roster and workflow record; CrewOS is where staff work it; RCM receives billing work as a downstream specialist system; WelcomeToBHW remains HR/onboarding only; retired Notion patient records are read-only migration history.

15-minute trainer-led walkthrough

TimeTrainer demonstratesTrainee does
0–3 minOpen the alert bell, explain role routing, then open the exact request.States why opening an alert does not resolve the request.
3–7 minReview the request-type totals and filter, request history, routed team, current owner, and communications.Finds one unclaimed synthetic request and identifies the correct category and service line.
7–11 minUse Assign to me, Start, an exact milestone, and Escalate.Completes the same sequence on a different synthetic request.
11–15 minAdd a Team Note, @mention the synthetic teammate, then show Notify patient and communications/delivery.Explains internal versus patient communication, unread markers, no-PHI SMS, suppression, quiet-hours, duplicate-send, and automation-gate rules.
Process flow: Alert or intake → open the record → confirm route and urgency → assign → start → do the work → record the exact milestone → notify only if eligible → verify delivery → resolve or escalate.
Current release: the CrewOS queue, request-linked Team Notes, optional alert bell, and Google Chat mirror are available. Non-provider staff can receive alerts across request types; providers receive triage/provider-question, assigned-provider, urgent, safety, waiting-on-clinician, escalated, and explicit @mention alerts. Automated patient SMS is gated off. A patient message counts only when Notify patient is available, the send is accepted, and the communications record shows the resulting delivery state.
Training data only: use synthetic/de-identified records labeled BHW0000. Never create, display, text, or test with a real patient's name, phone number, date of birth, diagnosis, medication, payer, or appointment.

What the 🔔 alert bell means Everyone

Read is not resolved. A bell count disappearing only means you opened the alert panel. The request stays open until the correct workflow action is recorded.

How to work a request Assigned role

Visibility and alerts are separate: every signed-in staff member, including providers, can view the shared Patient Requests queue. The bell shows only role-relevant clinical work, direct assignments, and explicit mentions. Providers receive alerts and work controls only for clinical triage/provider questions, items assigned to them, waiting-on-clinician work, clinical safety concerns, and escalations. Other requests remain visible as view-only for provider oversight. Billing urgency and raw fax intake do not become provider alerts; those remain in their appropriate workspaces.
  1. Check the category mix or use the request-type filter, then select the request in the left work queue. The right side shows status history, route, owner, communications, and delivery results.
  2. If it is unclaimed, tap Assign to me. Tap Start when you begin the work.
  3. Choose the exact milestone that happened—do not skip ahead. Use Escalate when the request needs a higher role or cannot safely continue.
  4. Use Notify patient only when it is available. Select or write a no-PHI message, confirm the no-PHI box, and send through the approved BHW line.
  5. Check Communications and delivery. “Sent” means the channel accepted it. “Suppressed,” “queued,” or “failed” does not mean the patient received it.
RequestMilestones that must stay distinctPrimary owner
MedicationWaiting on clinician ≠ waiting on pharmacy; Complete and Needs visit are different outcomesMedication/clinical team
ReferralReferral sent ≠ ready to schedule ≠ scheduledReferral/care-coordination team
Prior authorizationPA submitted means awaiting a decision; it is never the same as Approved or DeniedAuthorization/clinical team
BillingWith RCM ≠ waiting on payer ≠ resolvedRCM/billing team
GeneralReceived → in progress → waiting or completedRouted service line
If the category is wrong: do not work it under a misleading referral, authorization, billing, or medication status. An operations administrator can use Correct category while the request is Received or In progress. The correction resets ownership, reroutes the Chat mirror, writes an audit event, and does not send a patient text. A waiting or completed request must first be moved back to an active state so its nuanced milestone is not silently rewritten.

Team Notes — internal staff coordination Signed-in staff

  1. Open the request and use Team Notes below its status and patient-communication sections.
  2. Write the coordination update and select one or more teammates under Mention teammates when their attention is needed.
  3. Choose Add team note and wait for Saved to BHW Cloud. The author and timestamp are recorded automatically.
  4. A New team note marker appears for unread discussion inside the request. The bell alerts staff only when the request is relevant to their role or they were explicitly mentioned. An explicit Mentioned in team note alert does not widen routine role routing.
  5. Choose Mark notes read after reviewing. Use Load older notes for earlier history. A reply does not automatically mark other notes read.
  6. If a save is not confirmed, use Retry save without retyping it. The same send key prevents a duplicate. Drafts remain only in the open page; save before leaving.
Separate channels: Team Notes never send an SMS, update a Google Chat card, or appear in Communications and delivery. Use Notify patient for approved patient outreach.
Team Notes are not the legal medical record. Keep content limited to what coworkers need for this request. Document diagnoses, treatment decisions, orders, and other required clinical content in CharmHealth.

Staff Chat — across signed-in staff pages CrewOS staff identity

  1. Choose the floating Staff Chat button on a signed-in staff page. On your first visit to each staff site, or after switching staff accounts, sign in with your existing CrewOS account in the separate window. Later pages on that site reuse the chat sign-in.
  2. Use BHW Team for general staff coordination or Message a teammate for a direct conversation. A teammate appears after opening Staff Chat once.
  3. Confirm the message contains no patient or confidential personnel information, choose Send, and wait for Saved to BHW Cloud. This confirms storage, not that a teammate has read it.
  4. Messages and your selected conversation follow you between staff pages. Unsaved drafts do not; send them before navigating. Reopen the button when switching sites.
  5. The unread badge is optional and off initially. Enable Show unread badge across staff pages if you want it. The preference follows your account. No sounds, pop-up alerts, or browser push notifications are requested.
  6. Choose Mark read after reviewing. The open panel checks for updates about every 12 seconds; closed panels check less often. This is not an emergency or urgent-clinical channel.
Separate purposes: patient-specific coordination belongs in Patient Requests → Team Notes; confidential personnel matters stay in HR. Staff Chat does not send SMS, post to Google Chat, or change a request's status. Each app keeps its existing access restrictions. New staff still need an approved CrewOS account.

Who owns what

StepResponsibleAccountableConsult / inform
Review and claimStaff member in the routed teamService-line leadFront desk if intake details are missing
Clinical decision or medication outcomeLicensed clinicianAssigned providerMedication/authorization staff
Referral scheduling statusReferral/care coordinatorCare-coordination leadProvider and patient as appropriate
Billing requestRCM/billing specialistOperations leadFront desk; provider when clinical documentation is needed
Patient notificationPerson recording the milestoneService-line leadPatient through the approved channel

Exceptions and edge cases

What you seeWhat to do
The same request appears in Chat and CrewOSThat is one request shown in two places. Work it once; confirm the status in CrewOS.
“This action was already applied”Do not repeat it. Refresh Patient Requests and use the current status.
SMS suppressed / consent unavailable / phone match ambiguousDo not claim the patient was notified. Use the approved fallback workflow or ask the service-line lead.
Queued for quiet hoursLeave it queued. The system rechecks consent and suppression before release.
“automation-not-enabled”No SMS was sent. Tell the operations lead; do not retry repeatedly.
The request category is wrongStop before recording a category-specific milestone. Ask an operations administrator to use Correct category; never treat Referral sent, PA submitted, With RCM, or another nuanced state as interchangeable.
Urgent/emergency symptoms or safety concernFollow the emergency rule in section 10 first. The queue never replaces 988/911 or immediate provider notification.

Synthetic practice lab Trainee drives

The trainer prepares five de-identified BHW0000 requests. The trainee narrates each decision before selecting an action.

Practice requestRequired demonstrationDo not misstate
RefillAssign → Start → Waiting on clinician or Waiting on pharmacy → exact final outcomeWaiting is not completed; a refill request is not proof a prescription was sent.
ReferralRecord Referral sent, Ready to schedule, Scheduled, or Closed without scheduling only when trueReferral sent does not mean the appointment is scheduled.
Prior authorizationRecord PA submitted, then later Approved or Denied when the payer decision is knownPA submitted does not mean approved.
Billing / RCMRoute downstream to RCM and distinguish With RCM, Waiting on payer, and ResolvedSending to RCM does not resolve the patient's question.
General requestUse Received → In progress → Waiting or Completed, escalating if ownership or safety is unclearDo not use a generic completion when follow-up is still pending.

Competency check and sign-off

Pass only when every safety item is correct. If the trainee misses role boundaries, status distinctions, PHI rules, delivery meaning, or emergency escalation, review that section and repeat the synthetic scenario before access is considered complete.
TraineeTrainerDateResult / follow-up
________________________________________________Pass / repeat: ____________________

04Front Desk OS — lookup, referrals & support tools

1 · Open Patient Requests Front desk

Use Patient Requests for the live communication workflow. Front Desk OS may show operational snapshots, but staff actions belong in the Google-backed request record:

Do not work a second copy. If an old Front Desk card and Patient Requests refer to the same patient contact, use Patient Requests as the source of truth and report the duplicate.

2 · Patient lookup Everyone

Type a phone number or name → their profile appears before you answer the call.

The clinical snapshot is for context and routing only. Use it to decide "she's on a blood thinner — flag this refill as high." Never read a medication list back to a patient as final, and never make a clinical decision from it. CharmHealth is the chart. Check the "as of" date at the bottom — if it's old, verify in Charm.

3 · Referral finder Front desk, providers

  1. Choose the specialty and the patient's insurance.
  2. Tap Find in-network — preferred partners (⭐) come first.
  3. Copy fax grabs their fax number, or → Use in referral loads them straight into the referral form.

4 · Generate a referral Front desk, providers

  1. Look the patient up first, then tap use last lookup — name, DOB, phone, member #, and insurance fill in.
  2. Pick the specialist from the dropdown (or use the finder's button) — their whole block fills, including the fax.
  3. Provider fills in reason, brief history, what's being requested, place of service, number of visits.
  4. Tap Generate referral PDF — it downloads and opens ready to print.
  5. Then tap 📠 Fax to specialist to send it straight to the consultant's fax from the practice line — no printing or fax machine needed.
Always verify the member # against the card before it goes out. A wrong member number is the #1 reason referrals bounce back.

04bEach role's home base

Primary Care providers NP role

Care coordination Coordinator role

Behavioral health Psych / therapy roles

Billing & operations Ops role

05Patient pages — setting a patient up

Using the existing patient page Providers, care coordination

  1. Find and select the patient’s existing Google-backed Patient Master record. Do not create a second patient because a link is missing.
  2. Open the patient-facing page from the approved CrewOS/patient workflow link. Medication and status routing already belongs to that patient page.
  3. Keep detailed status, instructions, medication information, appointment details, and payer information behind the authenticated patient page.
  4. Use SMS only as a no-PHI nudge telling the patient that a secure update is available.
  5. If the patient page or link is missing, report the missing link to the operations lead. Do not build a replacement page or a new patient record.
Do not create new Notion patient pages. The protected Google Cloud Patient Registry is the only operational patient roster.
If access fails: verify the patient’s approved contact information in the authoritative record, then escalate the access problem. Never send detailed medical information by ordinary SMS as a workaround.

06BHW CrewCare — the provider side

Building or updating a care plan Providers

  1. Open BHW CrewCare → Health 360.
  2. Pick the verified Patient Registry patient and open Health 360, or start the program care-plan form.
  3. Save the draft to BHW Cloud. A licensed clinician reviews it before marking the patient copy “It’s Ready.”
One record: integrated labs, the five physiologic domains, program actions, medication/supplement tolerance and benefit, and follow-up all live in the same Health Blueprint.

Lab results and between-visit work

  1. Add interpreted lab results in Health 360 Care Plans; do not post them to an older patient page.
  2. Use Patient Requests for between-visit follow-up so Front Desk and CrewOS see the same work item.
  3. Send only the approved no-PHI “It’s Ready” notice after the Blueprint passes clinical review.
Do not create a second patient page or patient list. Patient identity comes from the Google Cloud Patient Registry, and patient-care drafts save to that patient's protected Health 360 record.

06aCare Program Intake & Enrollment SOP

Use the current program rules before enrolling or billing Care coordination, providers, billing

Open the Care Program SOP from the CrewOS rail or BHW HQ. It contains the common intake assessment, program-specific qualification questions, consent and initiating-visit requirements, Whole Person Care Plan standard, monthly readiness checks, combination safeguards, operational risk score, outreach tiers, and 2026 Baltimore Medicare fee reference.

  1. Start with the existing Patient Registry patient; never create a second patient identity for program work.
  2. Record potential eligibility separately from practitioner-approved enrollment and monthly billability.
  3. Use the program branch and readiness checklist, then create or update the protected Health 360 care plan.
  4. Use Care Management Log for monthly activity, time, device/data evidence, interaction, follow-up, and missing-requirement review.
  5. Send green rows to the billing practitioner and RCM for final attestation. Green is never automatic claim approval.
Closed work stays reviewable. Keep prior enrollments, declines, pauses, care-plan versions, communications, readiness evidence, risk scores, overrides, billing outcomes, and coverage changes attached to the same patient history.
Verify current rules. The SOP is an internal education and workflow reference. Current CMS and payer policy, practitioner judgment, and RCM review remain controlling.

06bStaff tools — paperwork, documents & fax

BHW HQ — the staff launchpad Everyone

BHW HQ is the tile page that links the big destinations (crewOS, the RCM platform, the onboarding portal) plus the Staff Tools row. Each tool opens on its own page and reuses your crewOS sign-in to pull patients.

ToolWhat it does
Patient RequestsThe authoritative command center for routed patient work. Assign, start, record exact milestones/outcomes, escalate, review communications/delivery, and—when enabled—send approved no-PHI notifications through Dialpad.
Paperwork StudioChart pulls, prior auth, disability, FMLA & MTA. Paste a note and AI read note pre-fills it, fills the real agency/payer PDF, and can 📠 Fax it out.
Care Plan StudioBranded, patient-ready annual care plans per program — pull the existing patient, tailor it, print/Save-PDF, and save the draft to the same BHW Cloud Health Blueprint.
Document BuilderPatient handouts, after-visit summaries, care plans, letters, and medication lists — branded, print/Save-PDF. Includes ✨ Draft with AI (below).
Send a FaxFax any PDF out through the practice line — pick a file, enter the number, send.
Patient MonitorLive roster of who's checking in and active today.

Draft with AI — describe it, it writes the first draft Providers, staff

  1. Open the Document Builder and pick the document type at the top (handout, after-visit summary, care plan, or letter).
  2. Tap ✨ Draft with AI.
  3. Optional: search a patient in the box — it pulls their name, DOB, allergies, and medications so the draft is tailored to them.
  4. Type what you need in plain English, e.g. "a nutrition plan for a patient with high homocysteine and stage 3 CKD — foods to favor, foods to limit, and simple daily targets."
  5. Tap Draft it. The document fills in — headings, bullets, key-point callouts — right in the builder.
  6. Read it, fix anything that needs it, then Print / Save PDF.
An AI draft is a starting point, never the final word. It can be wrong or miss a contraindication. A licensed clinician reads and edits every draft before it reaches a patient. It does not replace the chart or your judgment.
Works for handouts, after-visit summaries, care plans, and letters. The structured medication list is still built by hand.

06cDocument Builder — guide, templates & role practice

Use this module for new-hire orientation, role changes, and annual competency review. The live Document Builder now includes a role-filtered template library and the same role-based practice assignments below.

Purpose and scope Everyone who prepares patient materials

Create branded HTML or PDF patient education, after-visit summaries, care plans, letters, medication lists, check-ins, and trackers without creating a second chart or work queue. A builder draft is a local working document until reviewed and intentionally shared.

Process flow: Choose document type or template → replace every placeholder → complete role and clinical review → Download HTML or Print / Save PDF → select the verified Patient 360 record in Patient Materials & Feedback → upload the reviewed file → generate the expiring assignment → intentionally Record as sent.
No automatic save or send: opening a template, using AI, downloading HTML, or saving a PDF does not place the document in the chart, save it to BHW Cloud, assign it to a patient, or prove delivery. The protected share record begins only in Patient Materials & Feedback.

Detailed steps Trainee drives, trainer observes

  1. Start: open CrewHQ → Patient Education & Documents. Choose Templates for a structured starting point or choose the correct document type manually.
  2. Build: replace every bracketed placeholder. Use Build sections for structured editing or Paste text for headings, bullets, tables, and callouts. Use larger text or icons when the patient needs them.
  3. Review: verify the patient, date, provider, plain-language accuracy, warnings, links, accessibility, and every role boundary. A licensed clinician approves all patient-specific diagnoses, medication directions, thresholds, treatment advice, orders, and return precautions.
  4. Export: use Download HTML or Print / Save PDF. Open the exported file and read it once more; export success is not clinical approval or patient delivery.
  5. Share only when authorized: open Patient Materials & Feedback, select the verified Patient 360 record, upload the reviewed file, set the assignment and expiry, send the exact private link through an approved channel, attest, and Record as sent. Generated means not yet recorded as sent; recorded sent is a staff attestation, not carrier delivery.
Stop and escalate for an identity mismatch, unclear medication or threshold, unsupported clinical statement, missing clinician approval, crisis/emergency concern, expired or wrong-patient link, or any placeholder remaining in a final document.

Who owns each step RACI

StepResponsibleAccountableConsulted / informed
Choose template and prepare draftAuthorized staff member working within roleService-line leadAssigned clinician when content is patient-specific or clinical
Verify clinical content and release readinessLicensed clinicianAssigned providerMA, behavioral-health clinician, care coordinator, or other content owner as appropriate
Verify patient and upload reviewed fileAuthorized sending staff memberService-line leadPatient Registry owner if identity is missing, duplicated, or uncertain
Send exact private link and record as sentThe person who actually sends itService-line leadAssigned care team; patient as appropriate
Review patient response or problem reportRouted care-team roleAssigned clinician for clinical decisionsFront desk, care coordination, billing, or pharmacy staff as needed

Template library Filter by role in the builder

TemplateBest starting rolesRequired safety check
Weekly Check-In + Medication RequestMA / clinical support, care coordination, front desk, providerCreate the expiring link for the verified patient in Medication Request Links; a request is not a prescription.
Mental Health Conversation Check-InBehavioral health, provider, supervised clinical supportIt is non-scored and not diagnostic; 988/911 safety action is immediate.
After Visit Summary — Safe StarterProvider; MA transcriptionClinician verifies every diagnosis, medication, order, threshold, follow-up, and warning sign.
Home Vitals TrackerMA, care coordination, providerNever invent call thresholds; use the patient-specific clinician-approved plan.
Questions for My Care TeamAll patient-facing rolesOrganizes questions; it does not answer them or create a clinical request.
Symptom & Trigger TrackerClinical support, care coordination, behavioral health, providerNot continuously monitored and never a substitute for urgent evaluation.
Care Coordination Follow-UpCare coordination, MA, providerUse exact statuses and keep the authoritative queue current.
Appointment & Insurance PreparationFront desk, billing/operations, care coordinationDo not guarantee coverage or write clinical justification for the clinician.

Role-specialized synthetic practice BHW0000 only

Use synthetic patient BHW0000. Do not enter a real name, birth date, diagnosis, medication, phone number, email, private patient link, payer detail, or appointment. Do not complete a live share.

RolePractice assignmentPass evidence
Front deskUse Appointment & Insurance Preparation; add one synthetic accessibility need and scheduling barrier; export HTML; describe the protected share steps without sending.Content stays non-clinical; states downloaded is not sent; identifies verified patient, upload, expiring link, and Record as sent.
MA / clinical supportUse Weekly Check-In + Medication Request; leave the link TEST ONLY; add one provider-approved monitoring question; export PDF and identify every clinician-review item.No real link; no promise of a prescription; medication/threshold changes are escalated.
Care coordinationUse Care Coordination Follow-Up; add a synthetic transportation barrier, exact referral status, owner, and due date; export HTML.Referral sent ≠ ready to schedule ≠ scheduled; authoritative queue remains the source of truth.
Behavioral healthUse Mental Health Conversation Check-In; add one neutral function question; read the crisis language aloud; export PDF.Calls it non-scored; preserves 988/911 language; states that crisis action is immediate.
ProviderUse After Visit Summary — Safe Starter; replace every placeholder with synthetic content; add a return precaution; complete the release read-back.No placeholders; identity, plan, medication wording, follow-up, and warning signs are internally consistent and approved.
Billing / operationsUse Appointment & Insurance Preparation; add a synthetic coverage question and requested document; export HTML.No coverage guarantee; no independent clinical justification; states the file is not a claim, authorization, chart entry, or proof of delivery.
Trainer sign-off: record learner, role, trainer, date, browser/device, template used, export type, identity check, role-boundary check, clinical-review result, save/send teach-back, and any remediation.
Pass only when every safety item is correct. If the learner misses identity, role boundaries, clinical review, crisis handling, private-link handling, placeholder removal, or the draft/export/share distinction, review that section and repeat the synthetic scenario before independent access.

07Care coordination requests

Asking care coordination for help Any division

On the Chronic Care page, the "Request care coordination" card has a button for each reason:

Each button opens a referral already addressed to Chronic Care with the type filled in. Add the Needed by timeframe so the coordinator knows the urgency.

08Clinical tools

What each one does Providers

ToolUse it when
Positive ANA?An ANA comes back positive. Enter the titer, pattern, antibody results, medications, and symptoms — it ranks the differential, flags organ-threatening features, builds an order set, and links to the management protocol for each condition.
Hormone AnalysisStart from symptoms to see which axes to work up and the first-line panel, then interpret the results against the pattern library. Includes a systems reference and endocrine red flags.
Hormone ReferenceStaff resource — the feedback-systems explainer to use while thinking through a case.
Hormones ExplainedPatient-facing — open it with a patient to explain how their hormones work.
Panel & DischargesUtilization and HEDIS review, hospital discharge follow-up tracking.
Billing ToolkitDocumenting care management months, auditing before you bill, and finding the right preventive code with its ICD-10 pair for the superbill.
Every clinical tool is decision support, not a diagnosis. They organize thinking and surface what to check next. The chart, the exam, and your judgment decide.

08aBHW Capture — visit recording & recovery

Start from the authoritative patient identity Patient-facing staff

  1. Open BHW Capture and choose Capture for patient audio.
  2. Select the patient only from the protected Google Cloud Patient Registry. Match the displayed name and canonical BHW ID to the scheduled patient before recording.
  3. If the patient is missing, duplicated, or does not match, stop and route the identity issue to the Registry owner. Do not use the historical Patient Index Guide, create a substitute record, or record under another patient.
  4. Verify the current signed recording/AI-transcription consent and confirm that the patient and everyone who may be heard agrees to recording today.
The Patient Registry is the identity authority. The historical Patient Index and its guide are retired migration references and must not be used to select or create the patient for Capture.

Long visits and five-minute protected segments

  1. Keep the Capture tab open and visible for the entire visit. Confirm the screen-awake indicator is active; if it is not, keep the device awake manually.
  2. The recorder automatically closes, secures, and transcribes each five-minute segment while the next segment continues. Do not end a longer visit merely because a segment is processing.
  3. At the end of the encounter, select Finish once and wait until every segment reports transcribed before closing the tab.
  4. Review the assembled transcript for missing transitions, repeated text, speaker errors, and the segment immediately before and after any interruption.

If recording is interrupted

  1. Pause for an intentional interruption or when anyone withdraws agreement. Resume only after agreement is reconfirmed.
  2. If the session expires or a segment fails, leave this tab open. Use the new-tab CrewHQ sign-in, return to the same Capture tab, and choose Retry retained audio.
  3. Do not refresh, close the tab, switch patients, or press Clear audio and draft while a segment is retained. Those actions can remove audio still held only in page memory.
  4. If the browser, device, or tab closes, document the interruption and notify the provider. Never claim the transcript is complete; reconstruct missing clinical content through provider review and the legal-record workflow.
Safe completion: all segment audio shows successfully transcribed, the assembled draft is reviewed, and any gap or interruption is identified before the transcript is copied into the documentation workflow.

Competency check and sign-off Training owner

Before independent real-patient use, the learner must complete all four checks with synthetic patient BHW0000. Attendance or reading the guide is not sufficient.

Observed checkPassing evidence
Registry identitySelects BHW0000 from the protected Patient Registry, verifies name + canonical BHW ID, and states that a missing or mismatched patient must be escalated rather than recreated.
Segmented longer visitRecords across a segment boundary, explains that recording continues while five-minute protected segments transcribe in order, finishes once, and waits for all segments.
Planned interruptionPauses, reconfirms agreement, resumes, and checks the transcript on both sides of the interruption.
Failure recoveryResponds to a simulated expired session or failed segment by preserving the open tab, reauthenticating in a new tab, retrying retained audio, and escalating any unrecoverable gap.
Training owner sign-off: record learner, trainer, date, device/browser, four pass results, remediation if needed, and authorization status. Any failed check means supervised use only until successfully repeated.

08bMy Space — your role & the office calendar

What's on your Space page Everyone

New here? Your Space page is the first thing to read — it tells you your responsibilities and where they hand off to the next role.

09Where everything lives

The systems and what belongs in each

SystemWhat lives there
CharmHealthThe medical record. Always the source of truth for anything clinical.
Google Cloud / FirestoreThe operational source of truth for Patient Requests, request-linked Team Notes and read markers, task state, communications, notification rules, suppression, and audit events.
BHWcrewOSThe primary staff interface—Patient Requests, alerts, referrals, handoffs, tools, dashboards, and deep links into the appropriate specialist system.
Google ChatA no-PHI staff alert and quick-action mirror. It is not a second queue; verify the final state in CrewOS.
DialpadThe approved patient call/SMS channel on (443) 762-5343. Consent, STOP suppression, quiet hours, safety holds, and delivery status are checked and recorded by the Google workflow.
BHW RCMThe downstream specialist system for billing and revenue-cycle work. Billing requests begin in Patient Requests and route to RCM.
iFaxThe approved fax channel, (833) 258-3941. Verified fax intake creates one Google Cloud Patient Request; work that request once and do not create a duplicate.
info@bhwmedical.orgA backup intake/checkpoint for fax and other notices. If the corresponding Patient Request already exists, do not create another one.
NotionRead-only historical migration and non-patient reference content only. Do not create Patient Requests, patient pages, medication workflows, or patient operational records there.
WelcomeToBHWHR/onboarding only. It is not part of patient care, Patient Requests, or RCM.

10Rules that never bend

Safety and privacy

When you're not sure

SituationGo to
Clinical question about a patientThe patient's assigned provider (primary care NP, or psych NP for behavioral health)
Billing, insurance, or a claimThe billing & operations lead
Care coordination, SDOH, chronic care programsThe care coordinator
Something in crewOS is broken or blankThe practice owner / medical director — report the page, time, and safe request ID/error text without copying patient details into ordinary chat or email
You're not sure how urgent something isTreat it as urgent and ask. Nobody gets in trouble for over-escalating.