B-Brain
Quarrington Care Network logo

Approval for additional users and intake coordinator access

Email thread

Quarrington Care Network logo Quarrington Care Network · exec

Marisol Vega approved the additional thirty users on condition that intake coordinators see referrer-level data only, with no patient fields. Hollie Grieve accepted the conditions and promised a written role description.

What was said

What this says

Current to 13 Oct 26

Marisol Vega approved the additional thirty users on condition that intake coordinators see referrer-level data only, with no patient fields. Hollie Grieve accepted the conditions and promised a written role description.

Customer view: Marisol approved the users but wants the restriction applied by role, documented as a control, and wants to be told before anyone is added. She stated that a hidden field is not a control.

BB-Demo response: Hollie agreed a separate role, admin-only changes with an audit trail, and no user added until Marisol says yes.

Next: Hollie sends the written configuration, and the new users stay on hold until Marisol confirms it.

AI · claude-sonnet-5-5 · 13 Oct 2026

The thread

Updated 9 Oct 26
Typeexec
Messages2
First message2026-09-08
Last message2026-09-09

Messages

  1. Marisol Vega
    Marisol Vega 8 Sep 2026 08:49
    to Hollie Grieve
    Hollie, Thank you for the walkthrough of the proposed additional users, and for the written description of what each group would be able to see. I have reviewed it against our business associate agreement and our internal access policy. I am content to approve the additional thirty users, on one condition that I would like documented as a control. The intake coordinators must see referrer-level data only. That means information about the referring hospital or physician group, such as the relationship, calls, tickets and contracts. No patient fields of any kind may be visible to that group, whether in pages, chat answers, search results or dashboards. To be clear about my reasoning: is any PHI in scope for the intake coordinators' work in the brain? My understanding is that it is not, and that the minimum necessary standard is therefore met only if the patient fields are excluded at the access level, not merely left out of the views they are likely to open. A hidden field is not a control. I would like to see the restriction applied by role, with the configuration described in writing. Please confirm the following: how the role is defined, who can change it, and whether a change would be visible in an audit trail. I would also ask that you tell me before any user is added to that role, not after. Danielle is copied so that the referral relations team understands the boundary and does not ask for it to be widened informally. Marisol Vega Privacy and Security Officer, Quarrington Care Network
  2. Hollie Grieve
    Hollie Grieve 9 Sep 2026 14:24
    to Marisol Vega, Danielle Okonkwo
    Marisol, Danielle, Thank you both. Marisol, thanks for being so precise. It makes this easy to act on. On your conditions: - The intake coordinators will be set up as their own role, which sees referrer-level data only. Patient fields are excluded at the access level, so they do not appear in pages, chat answers, search or dashboards for that role. - Changes to the role can only be made by your admins, and any change is recorded in the audit trail, which you can review. - I will tell you before any user is placed in that role, and I will not add anyone until you have said yes. To answer your question directly: no PHI is in scope for the intake coordinators. If that ever changed, it would need a new request from you and I would not treat it as a small tweak. I will send you a short written description of the role configuration by the end of next week so you can file it as the documented control. If anything in it does not match what you expect, tell me and I will correct it before the new users go live. Danielle, I'll hold the new user set-up until Marisol has confirmed the description. Jordan has the commercial side with you, so I will leave that with him. Kind regards, Hollie Hollie Grieve Customer Success Manager, BB-Demo

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only