# What is safe to prototype in a medical booking site?

Canonical: https://uvilno.com/answers/can-ai-build-a-medical-booking-portal
Updated: 2026-10-27

Prototype service information and an appointment-interest journey before handling medical records. Uvilno's managed collections do not establish healthcare compliance or suitability. Do not collect patient histories, diagnoses or sensitive documents without a separately reviewed system; an interest form must not claim a confirmed clinical booking.

Use fictional data and approved public clinic details during design. A visitor can explore services and request a reply without entering symptoms or a medical history. State whether the form records an inquiry or connects to an actual reviewed appointment system.

Sensitive patient accounts introduce legal, privacy, security and operational requirements beyond a generic app template. Get specialist review for the relevant jurisdiction and systems before production. A premium-looking dashboard, account page or encryption claim is not evidence of a compliant patient-record workflow.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Public content | Approved services and real contact destinations are suitable for a prototype. | Check every business claim and destination. |
| Interest form | A saved inquiry is not an approved appointment. | Review confirmation copy and the real reply process. |
| Sensitive data | Generic app capabilities do not certify healthcare compliance. | Obtain separate specialist review before collection. |

## Steps

1. Use fictional, non-sensitive test records.
2. Remove clinical and identity documents from the prototype.
3. State the actual next step after an interest submission.

## Editable starting brief

Plan a public dental-clinic website with approved services, team information, opening details I supply and an appointment-interest form collecting only minimal reply information. State that submission is not a confirmed booking. Do not request symptoms, patient histories, diagnoses, insurance records or sensitive documents, and do not invent clinical compliance claims.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)