Hi, spontaneously, why don’t you enter all “generic” & “more” information in the same Form? This would also save you the “confirmation” step since everything would be made in the Form.
You could use "User Profil Columns (special values) to automatically feed the generic information (see picture below), and text entry components for the “more” information.
1. User profile
→ Tab [User]: columns required for the “generic information” (ex. age, gender, current treatments…), that will be automatically provided in each Booking.
→ Tab [Doctor]: columns to enter the list of Doctors and minimum associated information (ex. address, specialty…) NB: this is in the case where you enter yourself the list of doctors. If doctors are also users who register themselves, they should probably be in the [User] tab and distinguished from patients with a “type of user” column.
→ Tab: [Booking], including columns:
basic text: id booking
date: booking creation
basic text: user email, first and last name
basic text: each column required for “generic patient information” nb: if the Patient data are to be integrated in a future Doctor’s Patients database, you should rather use a Relation between [Booking] and [User] (via “user email”), then Lookups on each patient “generic information”. This would allow the possible changes in the [User] generic information to be updated in the Doctor’s Patients database.
basic text: “more patient info” column(s)
basic text: doctor
date: date and time.
→ Screen “Booking”: linked to [Booking] with a Form component linked to [Booking].
The Form includes at least the components:
special values: unique id, user email, date (for Booking creation)
special values “User Profile Columns” (see screenshot below): first, last name, each generic information