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…
The Kay & Co. resource library
Integrations & data resources · page 2
Connect your booking, enquiry and reporting tools so staff spend less time copying information. Understand your options and the questions to ask suppliers.
Find an answer
Search a question, a task or a few words.
Search results
Matching resources
The complete list
Integrations & data resources
Showing 25–48 of 61 resources, ordered by title.
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…
Explain tracking-name changes before reporting a decline
Activity continues under a new event name while the dashboard still reads the old one. An event name is a dependency shared by configuration, reports and…
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…
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…
Give problems between suppliers a clear coordinator
Two vendors each say their system is working and the clinic is left coordinating an unresolved failure. A failure involving two suppliers can leave the…
Give software connections a renewal and recovery owner
A connection stops when a credential expires because nobody owns its renewal or knows which workflow uses it. Connections rely on access details that can…
Handle appointment slots that change during booking
A website displays a slot that the reception team has already allocated through another channel. Available appointments can change while somebody is…
Keep clinic records up to date after a refund
A refund is completed through the payment provider but the clinic's administrative record still shows the previous state. If a refund happens in the…
Keep incomplete file uploads out of everyday use
A network interruption leaves a partial file that appears available to staff. An interrupted upload should not look like a finished document ready for use.…
Keep internal notes out of external messages
A connector copies an internal note into a message field intended for an external recipient. An internal note may be useful to colleagues but inappropriate…
Keep useful context about where enquiries came from
A clinic knows an enquiry came through its website but loses the service page that prompted it. Knowing an enquiry came from the website may not explain…
Keep website rehearsals distinguishable from genuine enquiries
Routine rehearsals appear alongside genuine activity because nobody agreed how test events would be distinguished.
Keep work accounted for when an HL7 connection changes
HL7 refers to standards used to exchange healthcare information between systems. An interface is replaced while both old and new connections may process the…
Link reporting records without guessing identity
A report cannot connect enquiries to later administrative outcomes because each system uses a different reference. To understand what happened after an…
Make every page send measurement to the practice's account
A copied analytics identifier routes a section's activity into a different account, leaving gaps in the practice report.
Make message delivery problems clear to staff
One system marks a message sent while another records it as rejected, and staff do not know which status to trust. Different systems may use sent to…
Match new staff accounts to approved access
A staff record is created and an integration grants a broad default role in every connected system. Creating an employee record should not automatically…
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…
Plan how incomplete healthcare exchanges will be handled
A demonstration sends a complete example successfully but does not test how the interface handles incomplete or unsupported information. A perfect sample…
Prepare for changes made by connected software suppliers
A vendor changes its interface and the clinic learns about it only after a workflow stops. A supplier update can change the connection even when your own…
Preserve the document version a team has accepted
An integration sends a revised file and silently replaces the version another team already reviewed. Replacing a document can erase the context of an…
Record useful link destinations without unnecessary address details
A link event captures complete external addresses containing values added to the page address the practice never uses in reporting.