Start here
Care CMS terms and conditions
The conditions for licensing, hosting, maintaining and using Care CMS for a live practice website, including privacy responsibilities.
On this page
Provider and agreement
ZoraWebDesign offers Care CMS to practices and healthcare providers acting in a business or professional capacity. An enquiry is non-binding. The accepted offer and agreed contract terms define the software, setup and support included.
Licence and installations
The practice offer covers one production website with its own installation and accounts. The offer defines the licence term, permitted staging installations and handover. Redistribution of the private software is limited to the agreed scope. Rights granted by earlier MIT releases remain in place.
Fees, term and cancellation
The offer sets out setup costs and recurring fees, the billing interval, any minimum term, renewal and notice period. It also states whether and how the installed version may continue to be used once maintenance ends.
Hosting and handover
You can run Care CMS on compatible hosting of your choice. Managed hosting support is optional and agreed separately. Handover records who is responsible for server operation, domain and DNS, TLS certificates, email, backups and recovery. On your own hosting, you retain your provider accounts.
Updates, maintenance and support
The maintenance plan defines which security updates, feature updates and support are included and who installs them. The offer covers response times, maintenance windows, recovery and work arising from third-party changes. Support access is agreed in advance and limited to what is needed.
Content, users and access
The practice decides what to publish and who may edit it. It is responsible for having the rights to use text, images, certifications and other material, and for checking their accuracy. Give team members individual accounts with appropriate roles, revoke access when it is no longer needed and report security incidents through the agreed support channel.
Privacy and data processing
Data protection roles depend on the actual processing. The practice determines the purposes, necessary data, access permissions and retention periods for its website. Where ZoraWebDesign processes personal data on the practice’s behalf, an Article 28 GDPR agreement is put in place before that processing begins. The privacy notice and cookie settings must reflect the live site and its services.
Healthcare use and appointment booking
Care CMS is for publishing website content. It is not a patient-record, medical intake, diagnostic or emergency system. The public demo uses fictional appointments. Live appointment booking or processing health data requires a separately agreed and reviewed workflow with suitable providers and safeguards.
Third-party services and integrations
Booking providers, email, maps, calendars and other integrations may require separate accounts, fees, data processing agreements and provider terms. The offer identifies which connections are set up and maintained. Store credentials only in the protected configuration intended for them.
Content ownership, export and exit
You retain your rights in your own content and ownership of your domain. Export or handover formats, scope and timing are agreed in advance. For managed hosting, the agreement also covers when access ends and how data and backup copies are returned or deleted. Software rights are governed by the licence.
Warranty and liability
The agreed scope, contract terms and applicable law govern warranty and liability. This summary does not limit statutory rights. Commitments on availability, response times or recovery apply to the extent expressly agreed.
Privacy checks before a live deployment
This checklist is for project planning. The practice and its providers should review the actual data flows and applicable national rules before collecting patient or booking information.
- Map where forms, bookings, contact requests, logs, backups and integrations send data. Ask only for information needed for the stated purpose.
- Identify the controller, processors and any subprocessors. Put appropriate processing agreements and transfer safeguards in place where required.
- Identify a lawful basis for processing and any separate condition required for health data. Review whether a data protection impact assessment is required.
- Explain to visitors who handles their data, why, who receives it, how long it is kept and how they can exercise their rights. Identify the correct contact and supervisory authority where applicable.
- Review cookies, analytics, maps, video and other external services for the actual deployment. Obtain consent before loading optional services where applicable and provide a way to withdraw it.
- Set access permissions, retention and deletion procedures. Test account recovery, backups and how the practice will respond to a security incident before launch.
Operator and questions
Care CMS is a ZoraWebDesign project. For questions about licences, hosting, privacy or an installation, contact ZoraWebDesign. Keep medical information out of general support and sales messages.
Something unclear? Contact me about this guide.