INTEGRATION GUIDANCE
Begin with the data boundary.
Patient, booking and staff integrations need an agreed practice scope and authenticated access. Start by reviewing the workflow, permissions and data you need to exchange.
Identity and permissions
Agree the named practice and staff roles an integration will serve. Application permissions and patient access boundaries still apply.
Booking contracts
Booking uses actual patient, location, service and provider records. Availability returns explicit time instants and the location’s time zone; creation rechecks resource ownership and conflicts.
Patient records
Patient workflows require permission to view or update records. Confirm field validation, encrypted storage, pagination and audit requirements for any proposed data exchange.
External services
Agree which system is authoritative, what data is shared, authentication, processor terms and failure handling. Do not treat an unconfigured integration as connected.