← This release collection

Appointments and registration handoff · VERSION 3dfb7c9f

Create an Ambulatory encounter from a checked-in appointment

Review the existing appointment, set the intended encounter fields, create the fictional encounter once and verify its saved department and Doctor attribution.

Doctor

Review the saved checked-in appointment before opening its encounter form. Genuine synthetic Doctor workflow.12
Recorded release 3dfb7c9f · 2026-10-19T13:09:59.155Z · 1728 × 977

Review the saved checked-in appointment before opening its encounter form

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 123c035755901dab3d9f0b864dece24e9361a0e34a462df5aa5882fe51706ce6

  1. Start Consultation: Open the normal Doctor encounter form for this saved fictional appointment.
  2. Checked-In: The saved appointment is checked in before the encounter is created.
Review the department and the once-only Create control. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:13:01.403Z · 1728 × 977

Review the department and the once-only Create control

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 77f5ad6bd4690f051fb6fde56039155c653de0e72fa26030e601cd8444b54d49

  1. Administration: Confirm the existing Administration department; no favorite or membership changes are made.
  2. Create Encounter: After reviewing the fields, create the fictional encounter once.
  3. Cancel: Cancel remains available before submission.
Review the saved Ambulatory encounter. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:16:53.984Z · 1728 × 977

Review the saved Ambulatory encounter

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 86ba5e78a59fe38cbe003c316889f34479d0d5326c237a40a02dfd17d8c2bcb3

  1. Ambulatory encounter: The saved encounter is Ambulatory and In Progress.
  2. Saved start time: The saved encounter displays the reviewed 4:09 PM start time.
  3. View appointment: Open the associated appointment to verify its saved state separately.

10 of 10 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.

Before you begin

  • Use an already authenticated authorized Doctor session in the assigned fictional Polyclinic and the intended existing Checked-In appointment. This example uses synthetic DOB patient ending 3301 on 19 October 2026. Its original appointment is 2:00 PM–2:30 PM; the independently reviewed encounter start is 4:09 PM in Asia/Riyadh UTC+03. Confirm the configured browser/scheduling date context; the screens do not print a timezone. Sign-in is separate and is not illustrated here.
    Review the saved checked-in appointment before opening its encounter form. Genuine synthetic Doctor workflow.12
    Recorded release 3dfb7c9f · 2026-10-19T13:09:59.155Z · 1728 × 977

    Review the saved checked-in appointment before opening its encounter form

    Capture details

    Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

    Image SHA-256 123c035755901dab3d9f0b864dece24e9361a0e34a462df5aa5882fe51706ce6

    1. Start Consultation: Open the normal Doctor encounter form for this saved fictional appointment.
    2. Checked-In: The saved appointment is checked in before the encounter is created.
    Review the intended encounter start separately from the appointment time. Genuine synthetic Doctor workflow.1234
    Recorded release 3dfb7c9f · 2026-10-19T13:12:42.491Z · 1728 × 977

    Review the intended encounter start separately from the appointment time

    Capture details

    Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

    Image SHA-256 2302d4c320b466993b9a479127988f87417b9d55f37296fd5f63066594fb2dd2

    1. Encounter time: The normal keyboard edit remains at 4:09 PM after leaving the field; this is the intended encounter start.
    2. Encounter date: Review 19 October 2026 before the once-only create.
    3. In Progress: Keep the existing In Progress status for this software demonstration.
    4. Routine: Keep the existing Routine priority.

1. Review the checked-in appointment

Confirm the intended synthetic patient, practitioner, original date and time, Checked-In badge and retained note. Choose the visible Start Consultation control to open its new encounter form.

Review the saved checked-in appointment before opening its encounter form. Genuine synthetic Doctor workflow.12
Recorded release 3dfb7c9f · 2026-10-19T13:09:59.155Z · 1728 × 977

Review the saved checked-in appointment before opening its encounter form

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 123c035755901dab3d9f0b864dece24e9361a0e34a462df5aa5882fe51706ce6

  1. Start Consultation: Open the normal Doctor encounter form for this saved fictional appointment.
  2. Checked-In: The saved appointment is checked in before the encounter is created.

2. Select Ambulatory

Choose Ambulatory and verify its selected border. The other encounter types are visible choices; this lesson saves only Ambulatory.

Choose Ambulatory for the fictional encounter. Genuine synthetic Doctor workflow.1
Recorded release 3dfb7c9f · 2026-10-19T13:11:50.911Z · 1728 × 977

Choose Ambulatory for the fictional encounter

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 1793afbc52fe3cc74b6324fc6f1d9b49dfd0f6ede494ca294ca9cc3be29519f6

  1. Ambulatory: Choose the Ambulatory software encounter class before creating the fictional encounter.

3. Set and retain the intended encounter date and time

Review 19 October 2026 and enter the intended encounter start using the time field. Move focus away, then verify the value remains 04:09 PM after another field is selected. The encounter start is reviewed separately from the original 2:00 PM–2:30 PM appointment.

Review the intended encounter start separately from the appointment time. Genuine synthetic Doctor workflow.1234
Recorded release 3dfb7c9f · 2026-10-19T13:12:42.491Z · 1728 × 977

Review the intended encounter start separately from the appointment time

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 2302d4c320b466993b9a479127988f87417b9d55f37296fd5f63066594fb2dd2

  1. Encounter time: The normal keyboard edit remains at 4:09 PM after leaving the field; this is the intended encounter start.
  2. Encounter date: Review 19 October 2026 before the once-only create.
  3. In Progress: Keep the existing In Progress status for this software demonstration.
  4. Routine: Keep the existing Routine priority.

4. Review status, priority and department

Keep In Progress and Routine for this fictional example. Scroll the form to confirm the existing Administration department has loaded and is retained before submission.

Review the intended encounter start separately from the appointment time. Genuine synthetic Doctor workflow.1234
Recorded release 3dfb7c9f · 2026-10-19T13:12:42.491Z · 1728 × 977

Review the intended encounter start separately from the appointment time

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 2302d4c320b466993b9a479127988f87417b9d55f37296fd5f63066594fb2dd2

  1. Encounter time: The normal keyboard edit remains at 4:09 PM after leaving the field; this is the intended encounter start.
  2. Encounter date: Review 19 October 2026 before the once-only create.
  3. In Progress: Keep the existing In Progress status for this software demonstration.
  4. Routine: Keep the existing Routine priority.
Review the department and the once-only Create control. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:13:01.403Z · 1728 × 977

Review the department and the once-only Create control

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 77f5ad6bd4690f051fb6fde56039155c653de0e72fa26030e601cd8444b54d49

  1. Administration: Confirm the existing Administration department; no favorite or membership changes are made.
  2. Create Encounter: After reviewing the fields, create the fictional encounter once.
  3. Cancel: Cancel remains available before submission.

5. Create once and inspect the saved result

After the field review, choose Create Encounter once. Wait for the saved encounter Overview. If the outcome is uncertain, read the appointment and encounter before attempting any further action; do not repeat Create to guess the result.

Review the department and the once-only Create control. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:13:01.403Z · 1728 × 977

Review the department and the once-only Create control

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 77f5ad6bd4690f051fb6fde56039155c653de0e72fa26030e601cd8444b54d49

  1. Administration: Confirm the existing Administration department; no favorite or membership changes are made.
  2. Create Encounter: After reviewing the fields, create the fictional encounter once.
  3. Cancel: Cancel remains available before submission.
Review the saved Ambulatory encounter. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:16:53.984Z · 1728 × 977

Review the saved Ambulatory encounter

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 86ba5e78a59fe38cbe003c316889f34479d0d5326c237a40a02dfd17d8c2bcb3

  1. Ambulatory encounter: The saved encounter is Ambulatory and In Progress.
  2. Saved start time: The saved encounter displays the reviewed 4:09 PM start time.
  3. View appointment: Open the associated appointment to verify its saved state separately.

6. Verify the saved department and Doctor attribution

In the saved Details panel, review Administration and the Created By and Last Modified By entries for MANSOQ E2E Doctor at 4:14 PM on 19 October 2026. No account found is the observed account state.

Saved department and Doctor attribution. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:19:25.264Z · 1728 × 977

Saved department and Doctor attribution

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 88d4da5d3e40b0d9b620f8bbf71202197b82a74bcfe3d933b71ca6634b941cff

  1. Saved department: Administration is retained in Departments and Teams.
  2. Created by Doctor: The saved encounter identifies MANSOQ E2E Doctor as creator.
  3. No account: The saved encounter currently shows No account found.

Check the saved encounter fields

The saved Overview shows Ambulatory, In Progress, Routine and a 19 October 2026 start of 04:09 PM. No responses found is the observed initial state; this software demonstration does not record a real assessment or treatment.

Review the saved Ambulatory encounter. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:16:53.984Z · 1728 × 977

Review the saved Ambulatory encounter

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 86ba5e78a59fe38cbe003c316889f34479d0d5326c237a40a02dfd17d8c2bcb3

  1. Ambulatory encounter: The saved encounter is Ambulatory and In Progress.
  2. Saved start time: The saved encounter displays the reviewed 4:09 PM start time.
  3. View appointment: Open the associated appointment to verify its saved state separately.

Keep the appointment time distinct from the encounter start

The appointment remains 2:00 PM–2:30 PM, while the encounter starts at 4:09 PM. Verify both saved values for their separate purposes rather than treating the form time as a reschedule.

Reloaded appointment retains its booked time and note. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:20:13.255Z · 1728 × 977

Reloaded appointment retains its booked time and note

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 5497e2acf6d9d47a782bb19d8a6ae4976616c1c8db72d2f341e57a1afa7a1f4f

  1. Original booked slot: The original appointment remains scheduled for 2:00 PM–2:30 PM.
  2. Original synthetic note: The original synthetic handoff note is retained.
  3. View Encounter: Use View Encounter to return to the saved linked encounter.
Reloaded encounter and its appointment link. Genuine synthetic Doctor workflow.123
Recorded release 3dfb7c9f · 2026-10-19T13:19:38.881Z · 1728 × 977

Reloaded encounter and its appointment link

Capture details

Exact committed 3dfb source after USB migration. Existing non-superuser Doctor. One explicitly synthetic encounter was created and its appointment linked; later reload and View actions are read-only. No real attendance, diagnosis, treatment or clinical-service claim.

Image SHA-256 67e769e861223a17a14df05251cb1b3536764e08168531dbc605f2e284f004fd

  1. Saved start time: After reload, the encounter retains 19 October 2026 at 04:09 PM.
  2. View appointment: Use View to open the appointment linked to this saved encounter.
  3. Ambulatory encounter: The reloaded chosen encounter remains Ambulatory and In Progress.

Source evidence

Every citation uses this exact committed version. The private source repository requires access.