Clinical history connected to the client
Electronic records for aesthetic clinics
Bia's electronic client record brings each care note, product used, consented clinical photo, accepted term and allergy alert from the intake form into one timeline for that client.
It begins where a commercial profile ends. The team opens the right client, selects the related appointment and records what happened without scattering sensitive context across files, a phone gallery and loose notes. Each record keeps its origin and date so the next appointment finds a history rather than an isolated paragraph.
- One timeline for notes, photos and consent terms
- Care updates and products used linked to an appointment
- Before-and-after photos only after explicit consent
- Allergy alert brought forward from intake-form answers
The timeline brings each care update together
Photos, session notes and terms are sorted by creation date in the same timeline. Each note retains the service and appointment date it belongs to, helping the team distinguish a recent update from an older record for the same client.
Past appointments also populate the choices used when a new update is added. The record does not replace scheduling: it uses the appointment as context for organizing clinical history after the work takes place.
- Separate record types in one chronological view
- Service and date shown with each care note
- History remains attached to the correct client
A care note records the procedure and products used
To save a note, the team selects an appointment and writes the care update. Products used can be listed as part of that same session instead of becoming an untraceable comment.
The note and product list are protected at rest. On read, the server verifies the client and the user's scope before returning the record, then writes the sensitive access to the audit trail.
Before-and-after photos require consent
A clinical photo can be marked as before or after and optionally linked to an appointment. Upload remains disabled until explicit image consent is recorded, and that consent date stays with the item shown in the timeline.
The interface resizes the image into a controlled format before upload. The server validates type, content and size again, protects the data and returns the photo through an authenticated endpoint rather than a permanent public URL.
Accepted terms keep text, signer and evidence together
The team enters the title, presented text and signer's name. A term can only be saved after acceptance, and the system records the consent time with a hash calculated from that document's evidence.
Title, text, signer, date and hash stay together in the timeline. The signer's name is protected at rest, and creating a term is also written to the audit trail.
Allergies appear as an alert, not a diagnosis
When a linked intake form contains an allergy answer, the record surfaces that value as an alert. The same information can support the check in scheduling, shortening the distance between a submitted form and the appointment being prepared.
The alert repeats recorded information; it does not interpret symptoms, decide whether a procedure is safe or replace professional assessment. A failed read is shown as unavailable instead of being turned into a false no-allergy result.
What the record stores — and the limits that remain
The history supports continuity, but it still depends on accurate entries, consent and professional assessment.
- The team must choose the correct client and appointment; the system does not invent clinical observations.
- Photos require consent and do not prove treatment outcome, effectiveness or safety on their own.
- The allergy alert reflects an intake-form answer and does not replace diagnosis or an in-person check.
- A term hash preserves technical evidence, while the clinic remains responsible for its wording and applicable legal requirements.
Frequently asked questions
How electronic records work in practice
Are an intake form and an electronic record the same thing?
No. The intake form collects answers and consent. The record organizes care notes, products used, photos, terms and the client's allergy alert over time.
Can a photo be linked to an appointment?
Yes. A photo can be labeled before or after and linked to an appointment. Image consent is required before upload.
Does a term record who accepted it?
Yes. It stores the supplied name, consent time and an evidence hash. The signer's name is protected at rest.
Is access to the record audited?
Sensitive reads pass through the user's scope and create an audit event. The event records the number of photos, notes and terms accessed.
Can a care note list products used?
Yes. A session note accepts a product list and displays it with the service and date of that appointment.
Evaluate the history with a real clinic workflow
Create an account, add a test client and walk through scheduling, intake and records before using real data.
Create my account