Here's what it looks like to your patients:
Differences with in-clinic filling
Form filling on the web is a little different to in-clinic form filling for the time-being:
They're designed for patients to be sent a link to the form, not to be embedded in a website (but let us know if you want this).
Forms do not pre-populate with patient details, yet (we're working on this).
Forms do not flow automatically through to Cliniko, but instead go to the Inbox first in the Finger-Ink portal. From here, you can choose to create a new patient, or update an existing (matching) patient.
Forms update patient information (where changed), and attach a PDF to the patients' files, and create treatment notes, but do not automatically mark the patient as arrived.
All forms are processed and sent to Cliniko through our servers, not on your iPads. See our security section below for ensure security and privacy of patient data.
How do I get started?
Web form filling works with your existing forms, you just need to enable it on a per-form basis.
Once you've enabled web form filling and published the form, copy the public link and put it in your booking confirmation and/or appointment reminder templates as per Cliniko's helpful article on the subject.
With web form filling, patient information is now stored on our servers. Although, it's only stored for as long as necessary — as soon as we've had confirmation from Cliniko that your decision to create or update a patient has succeeded, we remove all patient data for that particular form response.
In addition, all patient data is encrypted twice. Once at the disk level, and again at our application level.
Delivering all this securely required an infrastructural change for us. While we're not yet HIPAA compliant, we made the decision to migrate to a hosting provider that is. That means our database can only be accessed by us, all access to our server and DB is audited, our backups are regular and secure, and we have a team continuously monitoring the infrastructure for suspicious activity.
If you're interested, we've also written a longer, and more detailed article on what data we store.