InputKit · Patient-experience integration
Ask every patient how it went, without anyone remembering to.
InputKit runs patient-experience surveys and review requests. Connected to Clinicmaster it fires off real clinical events — an assessment finished, a follow-up completed, a cancellation, a no-show — with the patient, practitioner, location and language already attached, so feedback collection runs itself.
The InputKit integration
InputKit is a patient-experience platform that collects satisfaction feedback and prompts happy patients for public reviews. Clinicmaster triggers its sequences from real events in the schedule rather than a manual list: which events send, for which disciplines and locations, in which language and at what time of day, is all configured — and the treating practitioner travels with the request, so results are attributable.
What the InputKit integration does.
Feedback that depends on someone remembering to ask does not get collected. This runs off events that happen anyway.
Triggered by four real events
Sequences fire on a completed assessment, a completed follow-up, a cancellation or a no-show — so you learn from the visits that went well and the ones that never happened.
Attributed to the practitioner
The treating clinician and department go out with the request, so feedback can be read per practitioner instead of as one undifferentiated clinic score.
Sent in the patient’s language
The patient’s locale is passed with the sequence, so a francophone patient is surveyed in French without anyone selecting anything.
Configured per discipline and location
Which disciplines participate and which location a request belongs to are set up explicitly, so a multi-site, multi-disciplinary group is not forced into one blanket rule.
Email, SMS or both
Sending mode and the time of day the request goes out are configurable, which is the difference between a survey that gets opened and one that gets ignored.
Reviews from satisfied patients
InputKit routes happy respondents toward leaving a public review, turning the feedback you were collecting anyway into visible reputation.
From completed visit to collected feedback.
Decide what sends, and for whom.
We license the module and configure which events trigger a sequence, which disciplines and locations take part, the sending mode and the send time.
The event happens in the normal course of work.
A treatment is completed, or an appointment is cancelled or no-showed. No one has to remember to add the patient to a list.
InputKit takes it from there.
Clinicmaster passes the patient’s contact details, language, location, department and practitioner to InputKit, which runs the sequence and collects the response.
What this integration does not do
Survey content, scoring and the review-request flow live in InputKit — Clinicmaster supplies the trigger and the context, and does not write survey responses into the clinical chart. Public review placement depends on your InputKit configuration and the review platforms you use. Licensed per clinic and configured by our team.
The context Clinicmaster hands to InputKit.
A survey is only actionable if you know whose visit it was about. These are the fields that travel with each sequence, which is what makes the results segmentable.
Back to all integrations- Patient name and honorific
- Email and phone
- Location
- Department
- Treating practitioner
- Language / locale
- Sending mode
- Time to send
- Date of the patient experience
InputKit integration questions.
Scale your Organization with Clinicmaster.
30-minute working session with a solutions engineer. Bring your current numbers — we'll show you the gap.