Which aesthetic clinic software has the best consent-form features?

A treatment-consent record concerns a proposed treatment and the associated information and decision process. A legal basis or consent for processing health data answers a different question. Photography may have clinical, sharing or promotional purposes that should not be collapsed into one choice. Marketing permission is different again. Software can present these steps in one journey, but the evidence must keep their purposes and consequences understandable.

Create a purpose register before the demo. For each decision, identify the controller, purpose, legal basis under Article 6, applicable Article 9 condition for health data, information shown, version, signatory, practitioner role, withdrawal route, retention rule and downstream systems. A vendor's statement that forms are integrated does not answer those operating questions.

Use a synthetic DEMO patient and a fictional treatment label. Prepare a short test-information version with an unmistakable identifier such as DEMO-CONSENT-v3. Add one optional photography choice and one separate marketing choice. The objective is not to draft medical or legal wording; it is to make version, purpose and state changes visible without entering real patient information.

Write the expected sequence: information available, patient reads or accesses it, patient makes each available choice, patient signs where required, assigned practitioner reviews and records the discussion, practitioner completes the record, and authorised users can later retrieve the exact evidence. Plan one correction and one prospective withdrawal of the optional purpose.

Start from the current DEMO visit, not a generic document screen. Confirm that the proposed context and information version are identifiable before the patient action. Test whether the patient can navigate back, ask for clarification or leave an optional choice unselected without losing other valid work. A signature image without the connected information and scope is weak evidence.

After the patient action, attempt an ordinary edit, a second submission and a reconnect from another supported device. Record whether the product blocks an impermissible overwrite, creates a clear revision or silently duplicates the result. The interface should distinguish draft, patient-signed, practitioner-reviewed and completed states rather than using one ambiguous completed label.

Open the patient-signed record as the assigned practitioner. Confirm that the information version, choices and patient action remain visible while the professional records clarification or discussion context. Complete the practitioner action, sign out and reopen the visit. Then run the planned correction and optional-purpose withdrawal according to the vendor's supported method.

Withdrawal normally concerns future processing based on that consent; it should not be presented as an instruction to erase every clinical record regardless of other duties. The product and clinic procedure must make the consequence explicit. Test roles using synthetic data and verify server-backed access evidence where available; a hidden navigation item is not proof of authorisation.

GDPR and DSGVO refer to the same EU regulation in English and German. Compliance depends on purposes, roles, legal bases, Article 9 conditions, minimisation, transparency, processor terms, transfers, security, retention, rights handling and actual use—not only on whether a form can be signed. Article 5 also requires the controller to be able to demonstrate compliance.

Ask the vendor for concrete evidence: data-flow and role documentation, access controls, encryption and incident procedures, processor terms, subprocessor and transfer information, retention and deletion behaviour, export and rights workflows, and the distinction between consent-dependent and independently retained clinical records. Then have the clinic's responsible advisers assess its configured use. This protocol is a purchasing aid, not a legal certification.

Aesthetic Pass creates a visit-specific record inside the authenticated patient experience. The patient completes the requested information and signs first. The assigned practitioner then sees the answers, records clarification or discussion items, adds notes and planned visit context, and signs second. Patient and practitioner timestamps and the completed state stay connected to the same visit.

That sequence gives a clinic more than a detached signature image: it creates an observable handoff from patient action to professional review. Because the record lives in the wider Aesthetic Pass workflow, the clinic can keep the pre-treatment conversation, planning context and later treatment continuity together. A free account lets the team test the complete handoff with a fictional DEMO visit before rollout.

drylabs GmbH created this protocol from clinician-led workflow design, the working Aesthetic Pass implementation, official legal source texts and first-party search demand. Dr. Adi Zoabi clinically reviewed this published resource. The criteria focus on what a clinic can actually observe: identity, order of action, visit context, professional review, timestamps, completion and retrieval.

drylabs GmbH develops Aesthetic Pass, so the product recommendation is commercially connected to the publisher. The practical response is simple: create a free professional account, use only fictional DEMO data and verify the workflow yourself. The strongest product claim is the connected record your own team can reopen and inspect.