Skip to main content

Multi-clinic

Many clinics.One source of truth.

Early-access multi-site administration with site-by-site roles and staff-controlled billing. Cross-site health-record access, SSO/SCIM and autonomous group workflows are disabled pending controller approval and production evidence.

Built in Ireland for private practiceEvery clinical word is authored by a clinicianFounding practices onboarding now

Multi-site operations

Built for groups, not just for clinics.

Cross-site patient records

Cross-site record access is not launch-authorised until the group approves purpose, lawful basis, role mapping, recipient/site boundaries, DPIA and access tests.

Group-wide reporting

Staff-reviewed operational and revenue views by authorised scope. Clinical-outcome reporting and scheduled exports require clinic acceptance evidence.

SSO, SAML & SCIM — disabled

No enterprise identity/provisioning route is launch-authorised. Provider terms, least privilege, offboarding and production authentication evidence are required.

Role-based access

Role controls are implemented, but each site must validate least privilege, privileged access, offboarding and defined-event logging before launch.

Unified billing

Stripe and invoice ownership are configured per signed commercial/clinic structure. Automated PCRS submission is not launch-authorised.

Brigid for groups

Approved templates and staff-controlled scheduling by authorised site. Cross-site rebooking and group care campaigns require separate approval.

Enterprise onboarding

Phased evidence, site-by-site approval.

  1. Phase 1

    Scope & accountability

    The group identifies controllers, sites, purposes, roles, systems and prohibited cross-site flows. Delivery responsibilities are recorded in the signed plan.

  2. Phase 2

    Phased site migration

    Migrate in an agreed sequence with representative imports, role tests, continuity and rollback. No site cuts over until it accepts the evidence; no zero-loss or zero-downtime promise is made without a tested plan.

  3. Phase 3

    Group-wide reporting + go-live

    Validate group reporting and authorised cross-site workflows. Support cadence is stated in the signed order form rather than assumed here.

Questions group operators ask

Things that come up on every architecture call.

Can we keep our existing IT?
No compatibility or replacement claim is made without an interface inventory and validated integration plan. SSO/SCIM and named imaging/lab connections are disabled unless their provider, security and production evidence is approved.
What does data isolation look like across sites?
Tenant and role boundaries are validated per site. Cross-site health-record sharing is disabled for launch unless the controller approves the purpose, lawful basis, Article 9 condition, DPIA, access, revocation and logging tests.
Do you support SCIM provisioning?
SCIM 2.0 automated provisioning for Microsoft Entra ID, Okta and Google Workspace is on our enterprise roadmap. Today, clinicians and admins are provisioned through Brigid’s own role management. Talk to us about timelines for your rollout.
How do we report across sites?
Approved operational and revenue fields can be reported within authorised group scope. Clinical-outcome reporting and scheduled exports require separate validation and recipient controls.
What if a site needs to leave the group?
Exit scope, format, encryption, assistance, timing, deletion and any fees are stated in the signed agreement and tested exit plan. The group verifies a representative export before go-live.

Built for groups

Site-by-site approval before cross-site operation.

Disabled
Cross-site health-record sharing
Required
Controller and role mapping
Per site
Acceptance and rollback evidence
Signed
Support and delivery ownership

Talk it through with us.

Discuss the proposed scope. Any delivery, support, integration or timeline commitment must be recorded in the signed order and implementation plan.

Talk to sales