Connecting your practice systems: where to start
Connecting two systems can save staff from entering the same information twice. It can also create confusion if nobody agrees what should pass across, which…
The Kay & Co. resource library
Connecting your systems
Help information reach the right team, avoid repeated typing and plan a careful move between systems.
Find an answer
Search a question, a task or a few words.
Search results
Matching resources
A useful starting point
Start here
Moving systems without losing useful information
Moving information between systems is often called a data migration. For your practice, success means staff can find the right records, open the right…
Get website form answers into the right fields
A website enquiry reaches the CRM but its service choice appears in a free-text note instead of the field used for assignment. Connecting a form to your…
The complete list
All connecting your systems resources
Showing 1–24 of 50 resources, ordered by title.
Agree report definitions before combining systems
A dashboard combines two systems that use different meanings for a completed enquiry. Two systems may both say complete while referring to different events.…
Agree what an HL7 connection should achieve for staff
HL7 refers to standards used to exchange healthcare information between systems. A supplier proposes an HL7 connection but the receiving team has not agreed…
Agree what shared information fields mean
Teams use the same field name for different concepts, creating confusion in integrations and reports. A shared glossary of important fields prevents teams…
Attach transferred documents to the correct record
A file transfers successfully but is attached to the wrong administrative record in the receiving system. A transferred document is useful only when…
Cancel related reminders and resources when bookings change
An appointment is cancelled in the diary but related reminders and room allocations remain active. Cancelling in the diary may need to release a room and…
Carry communication preferences into messaging tools
A messaging tool receives contact details but not the preferences used by the organisation's main system. Contact details alone do not tell a messaging tool…
Carry the full appointment details between systems
An integration transfers the appointment time but loses the selected location or appointment type. The date and time are only part of a booking. Location,…
Check access has ended across connected systems
A central account is disabled but an integrated application still permits access through an existing session or separate login. Disabling one login does not…
Check an API can perform the business task you need
A supplier confirms it has an API but has not shown whether it supports the clinic's required update. An API is a supported way for software to exchange…
Check the complete booking journey after payment changes
A supplier changes checkout settings and the payment still works, but the booking handover breaks. A working payment screen does not prove the whole booking…
Check the meaning of information exchanged through HL7
HL7 refers to standards used to exchange healthcare information between systems. An interface transfers a value that has a different local meaning in the…
Check two FHIR suppliers support the same intended task
Two vendors both mention FHIR but have not confirmed that their implementations support the same exchange. Two suppliers naming the same standard still need…
Check website enquiries actually reach your team
The contact page reports success after saving a form locally, but the CRM connection fails before creating the task. The website can receive an enquiry even…
Check who can see documents after transfer
A shared transfer location gives more teams access than the original sending process intended. A file's destination can have wider access than the place it…
Confirm permission to use a specific FHIR service
A team assumes that public FHIR documentation means it can immediately access an NHS or vendor interface. A public standard explains how information can be…
Confirm supplier approvals and costs before connecting tools
A software quote assumes API access is included, but the receiving vendor requires separate approval or charges. A connection can depend on another…
Connect each payment to its invoice or booking
A payment provider reports a successful transaction but staff cannot identify which invoice or booking it belongs to. Staff need to connect a payment with…
Connecting your practice systems: where to start
Connecting two systems can save staff from entering the same information twice. It can also create confusion if nobody agrees what should pass across, which…
Correct information where it is maintained
Staff fix an incorrect value in a report but the error returns after the next source refresh. Fixing an error in a report can hide it temporarily while…
Decide which system holds the current contact details
A contact detail changes in the CRM but an older website submission overwrites it during synchronisation. When two tools can change the same detail, the…
Explain payment results that are still pending
A payment result arrives later than the website expects and the visitor is shown an uncertain outcome. A delayed payment result can leave the visitor unsure…
Explain the practical purpose of a FHIR connection
A project brief asks for a FHIR integration without explaining what information needs to move or why. FHIR is a standard for exchanging healthcare…
Find records missing between connected systems
Both systems appear healthy but several records never arrived at their intended destination. Both systems can be available while individual records are…
Fix information problems that stop useful work
A team spends time cleaning cosmetic differences while missing fields continue blocking important work. Cleaning every formatting difference equally can…