# The Calendar Cannot Belong to CRM

_Published 2026-09-05._

The clinic did not have four separate problems. It had one operational day that four separate tools were trying to describe.

A booking was created in one place. The patient relationship lived somewhere else. The visit changed the commercial picture, but the ERP did not always see the same event. People became the handoff between screens.

## One appointment, many readers

Middlelink makes the appointment an operational fact. It belongs to a location and practitioner, binds to a patient record, moves through a visit workflow, and produces consequences that CRM and ERP can read.

CRM does not own the calendar. ERP does not invent the visit. They are consumers of a record that belongs to the operational domain.

The [Middlelink case study](/work/middlelink) makes location a first-class node as well. In a multi-clinic operation, “the clinic” cannot be a label attached to a user. It shapes availability, workflow, permissions, and reporting.

Sharing facts does not mean putting every field in one table. Patient identity, commercial accounts, appointments, and locations have different boundaries. The useful shared core is a set of explicit relationships and events, not a giant record that every module edits.

The best integration is sometimes a domain model that gives every reader the same event.