Seraya Psikologi — Documentation

Booking and payment MVP · Implementation baseline · 96 ADR

6. Minimize Client Data in Booking MVP

Status

Accepted for the MVP working model; retention, field-level access, and consent wording still need domain/legal review.

Context

The product is a booking-and-payment platform, not a clinical record system. Asking for detailed reasons, symptoms, or intake narratives before a first booking increases sensitivity and creates an accidental clinical-data boundary before the practice has designed a clinical system.

The website still needs enough information to identify the contact, complete payment, communicate the appointment, and record required consent.

Decision

Booking MVP collects only:

The MVP must not require or store diagnosis, detailed symptom narratives, assessment results, clinical notes, treatment details, or session records. If a user enters clinical content into an optional message, the system should not treat it as a clinical record; handling, redaction, or support escalation remains an operational policy decision.

Consequences

Positive:

Costs and constraints:

Open follow-up

Define the exact allowed fields, maximum optional-message length, retention periods, access matrix, deletion/export behavior, and the escalation path when a client discloses crisis content through a non-clinical channel.