BAA data-scope schedule v2
Documentexecuted Quarrington Care Network · contract · executed · 2026-07-30
Executed 30 Jul 2026 schedule listing which CRM, call, helpdesk and accounting fields the brain may load for Quarrington Care Network. Intake ticket free text and call transcripts are excluded. It does not change price, term or service levels.
What it says
What this says
Current to 11 Oct 26Executed 30 Jul 2026 schedule listing which CRM, call, helpdesk and accounting fields the brain may load for Quarrington Care Network. Intake ticket free text and call transcripts are excluded. It does not change price, term or service levels.
What it is: an executed schedule under the business associate agreement and the Growth order form. It "replaces the first version of the schedule in full" and sets a closed allow-list of fields on a minimum necessary basis.
Commits: connectors select only allow-listed fields, field selection changes are logged, and BB-Demo stops a load, notifies the Privacy and Security Officer and removes records if excluded data is found. Changes need a written amendment signed by both parties.
Unusual: free text from intake tickets, call recordings and transcripts, and all other free text fields are excluded in full. A new field added by the customer is not loaded until the table is amended.
Not settled: it repeats a Growth term of 40 licensed users, £50k annual contracted value and a term end of 29 Apr 2027, but says it does not change price, term or service levels. The order form governs those.
As found in this document
Current to 9 Oct 26- Date end29 Apr 2027Source: object_read:doc_079_010
- Date signed30 Jul 2026Source: object_read:doc_079_010
- Price£50,000Source: object_read:doc_079_010
- Field loadingOnly the fields listed in section 4 are in scope, and everything else is out of scope unless the parties agree a further amendment in writing.Only the fields listed in section 4 are in scope, and everything else is out of scope unless the parties agree a further amendment in writing. · Source: object_read:doc_079_010
- Field filtering at loadConnectors are configured to select only the allow-listed fields. Excluded fields are not read into the brain.Connectors are configured to select only the allow-listed fields. Excluded fields are not read into the brain. · Source: object_read:doc_079_010
- Audit trailChanges to connector field selection are logged with the person making the change and the time, and the log is available to the customer for review.Changes to connector field selection are logged with the person making the change and the time, and the log is available to the customer for review. · Source: object_read:doc_079_010
- Unexpected datastop the relevant connector load as soon as the finding is made; tell the customer's Privacy and Security Officer without delaystop the relevant connector load as soon as the finding is made; tell the customer's Privacy and Security Officer without delay · Source: object_read:doc_079_010
- Changes to scheduleonly by a written amendment signed by both partiesonly by a written amendment signed by both parties · Source: object_read:doc_079_010
- Licensed users40Source: object_read:doc_079_010
- Annual contracted value£50,000Source: object_read:doc_079_010
The document
Body
BAA data-scope schedule v2
Status: Executed on 30 Jul 2026
Parties: Quarrington Care Network (the customer) and BB-Demo (the supplier)
Relates to: the business associate agreement and the Growth order form between the parties, customer since 30 Apr 2026
1. Purpose
This schedule sets out exactly which data the company brain may load, index and answer from for Quarrington Care Network. It replaces the first version of the schedule in full. Where this schedule and any earlier scope description differ, this schedule applies.
The principle throughout is minimum necessary: only the fields listed in section 4 are in scope, and everything else is out of scope unless the parties agree a further amendment in writing.
2. Background
Quarrington Care Network is a home-health and hospice operator. Its referral-relations and patient-services teams use the brain to see each referring hospital's calls, tickets and contracts together. The brain is built and run inside the customer's own Snowflake account, so loaded data stays under the customer's control.
Read the whole document (5,477 characters)
The subscription is Growth, with 40 licensed users and an annual contracted value of £50k. The current term ends on 29 Apr 2027.
3. Definitions
- Allow-list: the closed list of fields in section 4. A field not on the list is not loaded.
- Free text: any field in which a person types an open narrative rather than choosing a value from a set list.
- Intake ticket: a helpdesk ticket created when a request, referral query or patient-services matter is first received.
- Protected health information: information about an individual's health or care that is covered by the business associate agreement.
4. Allow-listed fields
Only the fields below may be loaded from each connected system.
| Source | Fields in scope | Purpose |
|---|---|---|
| CRM | Referring organisation name, account owner, relationship stage, contract start and end dates, contract reference | Show each referring hospital's commercial relationship |
| Call recorder | Call date and time, duration, participants by role, referring organisation, call outcome category | Show contact history with each referrer |
| Helpdesk | Ticket identifier, category, priority, status, created and resolved timestamps, referring organisation, assigned team | Show service history and response patterns |
| Accounting system | Invoice date, invoice status, amount, referring organisation | Show commercial standing |
Fields are loaded by name. A new field added to a source system by the customer is not loaded until it has been added to this table by written amendment.
5. Excluded data
The following are expressly out of scope and must not be loaded, indexed or used to answer questions:
- Free text from intake tickets. The description, notes, comments and any attached files on an intake ticket are excluded in full, because these are the places where clinical or personal detail is most likely to be typed.
- Call recordings and call transcripts in their entirety. Only the call metadata in section 4 is in scope.
- Patient names, dates of birth, addresses, identifiers and any clinical or care detail.
- Any other free text field in any connected system, whether or not it appears similar to a field on the allow-list.
6. Controls
- Field filtering at load. Connectors are configured to select only the allow-listed fields. Excluded fields are not read into the brain.
- Documented configuration. BB-Demo keeps a record of each connector's field selection and shares it with the customer's Privacy and Security Officer on request.
- Audit trail. Changes to connector field selection are logged with the person making the change and the time, and the log is available to the customer for review.
- Review. The customer's Privacy and Security Officer may ask for the field selection to be demonstrated at any time, and BB-Demo will do so promptly.
7. Handling unexpected data
If protected health information or other excluded data is found in a loaded field, BB-Demo will:
- stop the relevant connector load as soon as the finding is made;
- tell the customer's Privacy and Security Officer without delay;
- remove the affected records from the brain and confirm in writing that removal is complete;
- agree with the customer what change is needed to prevent a repeat before the load is resumed.
The customer will tell BB-Demo promptly if it changes a source system in a way that may affect the allow-listed fields.
8. Changes to this schedule
This schedule may be changed only by a written amendment signed by both parties. Adding a field, a source or a new category of data requires the customer's Privacy and Security Officer to approve the change before any load takes place. Account contacts for day-to-day questions are Jordan Pike at BB-Demo and Hollie Grieve as customer success manager.
9. Relationship to other documents
This schedule sits under the business associate agreement and the Growth order form. It does not change price, term or service levels. The business associate agreement continues to govern the obligations of each party with respect to protected health information.
10. Signatures
Executed on 30 Jul 2026.
| For Quarrington Care Network | For BB-Demo | |
|---|---|---|
| Name | Marisol Vega | Jordan Pike |
| Title | Privacy and Security Officer | Account Executive, US |
| Date | 30 Jul 2026 | 30 Jul 2026 |
Unusual terms
Current to 9 Oct 26- Intake ticket free text excluded in full
- Call recordings and transcripts excluded
- Closed allow-list of fields by name
- Privacy and Security Officer approval for new fields