← This release collection

Clinical care · VERSION 3dfb7c9f

Return the Emergency encounter to In Progress and verify its history

Save the return on the same dedicated encounter, verify it after reload, read its three status-history entries and confirm its return to the Emergency board.

Doctor

On hold filtered retained own encounter in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:23:42.069Z · 1728 × 921

On hold filtered retained own encounter

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 e49eadd5b895df41380662a7ceb41fc20062a8001a540155ab9a0872b5af949c

  1. Verify Status is On Hold chip: The selected read filter is now applied.
  2. Verify Today date filter: Both filters define the visible list.
  3. Verify retained On Hold card: Filtering did not mutate the encounter.
  4. Choose View Encounter: Open only the matched dedicated encounter.

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

Before you begin

  • Use an authorised ordinary Doctor account in the assigned synthetic facility and patient scope. Actual native screenshots demonstrate Doctor only; Nurse and Staff checks are read-only authority observations.
    Emergency board unconfigured existing rows in the fictional Emergency encounter demonstration12345678910
    Recorded release 3dfb7c9f · 2026-10-20T00:07:53.010Z · 1728 × 921

    Emergency board unconfigured existing rows

    Capture details

    Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

    Image SHA-256 772ce2e5bcd1b03a608e96e88bc15717c2ceb0e826833e46149477b4b8b0c367

    1. Open Emergency board: Use the facility sidebar Patients section.
    2. Check the ordinary Doctor account: The actual account is MANSOQ E2E Doctor / qa-doctor.
    3. Read the unconfigured triage warning: Priority and arrival ordering does not infer a triage level.
    4. Read Not configured: This cell contains no triage level.
    5. Read encounter priority: This Emergency label is a priority, not a calculated triage result.
    6. Read waiting and arrival: The cell includes elapsed minutes and the displayed time zone.
    7. Read location: An existing demonstration row displays ER Bed 01; no location was assigned in this exercise.
    8. Read practitioners: The row shows its recorded practitioner role.
    9. Read Handover Notes: The link count is associated with that particular row.
    10. Locate Refresh: Manual Refresh requests the current board data.
  • Use only an approved fictional software-training case with validated creation/update prerequisites. No triage, treatment, clinical urgency, handover, admission or discharge decision is represented.
    Existing synthetic patient profile and home link in the fictional Emergency encounter demonstration12
    Recorded release 3dfb7c9f · 2026-10-20T00:08:26.168Z · 1728 × 921

    Existing synthetic patient profile and home link

    Capture details

    Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

    Image SHA-256 71f570730dbc162c980a84f3073daaac96cbcb24d66a846bb56db4693a767252

    1. Confirm the fictional patient: Use the assigned SYNTHETIC training identity.
    2. Choose Patient Home: Open the existing patient home without editing the profile.

1. Open the matched encounter and review only In Progress

From the retained On Hold card, choose View Encounter, then Update Encounter. Open Encounter Status and choose In Progress. The screenshot shows that final selection with Routine and the other form values unchanged. Use the same dedicated encounter; do not create another record.

On hold filtered retained own encounter in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:23:42.069Z · 1728 × 921

On hold filtered retained own encounter

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 e49eadd5b895df41380662a7ceb41fc20062a8001a540155ab9a0872b5af949c

  1. Verify Status is On Hold chip: The selected read filter is now applied.
  2. Verify Today date filter: Both filters define the visible list.
  3. Verify retained On Hold card: Filtering did not mutate the encounter.
  4. Choose View Encounter: Open only the matched dedicated encounter.
Own on hold saved overview in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:21:10.430Z · 1728 × 921

Own on hold saved overview

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 21ba87fefd5a7aabaab975bc46e8ae538e208fbbbddf91a6d79ff26bcad3fc0c

  1. Verify saved On Hold: The selected encounter displays the saved pause state.
  2. Verify Emergency remains: Status did not change the encounter class.
  3. Verify the same start: The original local minute display remains.
  4. Locate Update Encounter: Reopen this editor only for the later return to In Progress.
Own in progress reviewed before submit in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:23:51.421Z · 1728 × 921

Own in progress reviewed before submit

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 01febe8a3215251672b15578c6db05294d5a97f653d997b93802c0b5a1e23af3

  1. Review In Progress: Only the own encounter status is restored.
  2. Recheck unchanged Routine: No priority or hospitalization field is changed.
  3. Choose Submit once: Save the approved return on the same encounter.

2. Submit the return once and inspect the settled Overview

Choose Submit once. Wait for the Overview to settle, then check In Progress in the selected encounter and Encounter Details. Emergency, Routine, the displayed start and ongoing end remain unchanged. If a brief previous status appears while data refreshes, wait for the result instead of submitting again.

Own in progress reviewed before submit in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:23:51.421Z · 1728 × 921

Own in progress reviewed before submit

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 01febe8a3215251672b15578c6db05294d5a97f653d997b93802c0b5a1e23af3

  1. Review In Progress: Only the own encounter status is restored.
  2. Recheck unchanged Routine: No priority or hospitalization field is changed.
  3. Choose Submit once: Save the approved return on the same encounter.
Own in progress saved overview in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:24:07.331Z · 1728 × 921

Own in progress saved overview

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 9f30ed0b8c8c6231ce33f28e59ecf85c05d666f5ccf4ad3253cb9a709a9b0bc6

  1. Read saved In Progress: The settled Overview confirms the return.
  2. Verify Emergency class: The class remains separate from care state.
  3. Verify original start: The displayed local start is retained.

3. Reload normally and confirm the same saved state

Use the browser’s normal Reload once. After loading, verify the same Emergency encounter In Progress, Routine and start time. The separate older Ambulatory encounter remains visible. This screenshot was captured after that actual reload.

Own in progress after normal reload in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:24:34.879Z · 1728 × 921

Own in progress after normal reload

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 7832dc12bf52cf766c948fb348d8e65f50dc1c2ac1f996c6c12effd157c3b2d4

  1. Verify In Progress after normal reload: This original was captured after the one actual browser reload.
  2. Open Status History: Choose the status badge and its down arrow.
  3. Verify retained Emergency class: No class conversion occurred.

4. Open and read Status History

In Encounter Details, select the In Progress status badge with its down arrow. The popover lists the three saved states in order: In Progress, On Hold and In Progress, each with its recorded local date and time. The history concerns this encounter’s status, not a class conversion. Press Escape to close it.

Own in progress after normal reload in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:24:34.879Z · 1728 × 921

Own in progress after normal reload

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 7832dc12bf52cf766c948fb348d8e65f50dc1c2ac1f996c6c12effd157c3b2d4

  1. Verify In Progress after normal reload: This original was captured after the one actual browser reload.
  2. Open Status History: Choose the status badge and its down arrow.
  3. Verify retained Emergency class: No class conversion occurred.
Own status history created paused resumed in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:25:06.898Z · 1728 × 921

Own status history created paused resumed

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 75e52f2c651b24366c7563f42caabc95d01e0e0d5bce96950c1028846fb33dc9

  1. Read the status-history trigger: The popover is open for this same status badge.
  2. Read initial In Progress entry: The popover records the create status and local timestamp.
  3. Read On Hold entry: The first saved update is retained in the history.
  4. Read returned In Progress entry: The second saved update appears after On Hold.

5. Return to the Emergency board

Expand the sidebar if needed and choose Emergency board. The same synthetic encounter is visible again because its class is Emergency and its status is In Progress. Its Routine priority, Not configured triage, arrival time and Notes (0) belong to the same row.

Resumed overview board navigation in the fictional Emergency encounter demonstration12
Recorded release 3dfb7c9f · 2026-10-20T00:25:12.824Z · 1728 × 921

Resumed overview board navigation

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 42369d3fd0fbd006b65814d49be3ebf3149581ac931846966ebd373923f2331e

  1. Choose Emergency board: This sidebar navigation is visible in the expanded view.
  2. Verify resumed header before leaving: The chosen encounter is In Progress.
In progress returned to emergency board in the fictional Emergency encounter demonstration123456
Recorded release 3dfb7c9f · 2026-10-20T00:25:16.776Z · 1728 × 921

In progress returned to emergency board

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 e109e5689f9e83bae90430383169973b4e43d552d0f826a7bc432af9f45015fc

  1. Locate the returned synthetic row: The same encounter is again included while In Progress.
  2. Read Not configured triage: No triage level was authored.
  3. Read Routine priority: The original priority is retained.
  4. Read arrival and elapsed time: Waiting is a displayed duration, not an assessment.
  5. Locate this row’s Notes (0): Use only the intended synthetic row’s link.
  6. Choose Refresh: Request current board data once.

6. Verify the board row after Refresh

Choose Refresh. The row remains present in the captured result. Notes (0) opens the same encounter’s empty Discussions view if you need to inspect it; choose Overview to return without creating a thread. The separate board-reading guide shows that exact read-only navigation.

In progress returned to emergency board in the fictional Emergency encounter demonstration123456
Recorded release 3dfb7c9f · 2026-10-20T00:25:16.776Z · 1728 × 921

In progress returned to emergency board

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 e109e5689f9e83bae90430383169973b4e43d552d0f826a7bc432af9f45015fc

  1. Locate the returned synthetic row: The same encounter is again included while In Progress.
  2. Read Not configured triage: No triage level was authored.
  3. Read Routine priority: The original priority is retained.
  4. Read arrival and elapsed time: Waiting is a displayed duration, not an assessment.
  5. Locate this row’s Notes (0): Use only the intended synthetic row’s link.
  6. Choose Refresh: Request current board data once.
Board after manual refresh own row retained in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:25:21.509Z · 1728 × 921

Board after manual refresh own row retained

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 8e50eb9f2bcaec14fcb5a9a01660be43088f23d36383f84feac2fe8c662e5fc8

  1. Read Refresh after the actual click: The manual refresh completed without changing the row.
  2. Verify the same retained synthetic row: The read-only result retains the encounter.
  3. Choose own Notes (0): Open the linked Emergency encounter discussion view.
Board own notes link empty encounter discussions in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:25:29.850Z · 1728 × 921

Board own notes link empty encounter discussions

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 380f431f8073fe6953b48b908c20bc4454974bcbcfc5a68f21e2742334f28080

  1. Confirm chosen Emergency encounter: The Notes link opened this encounter, not the older Ambulatory one.
  2. Read No discussions yet: No discussion thread is created here.
  3. Read selected Notes tab: This is the encounter-scoped Discussions view.
  4. Choose Overview: Return without using New or Send.
Final clean own emergency overview in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:25:30.514Z · 1728 × 921

Final clean own emergency overview

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 a26ec1d08a5f31941629fc0aac196b531d9e1d07a9855bcc9ac53ae344b1bcbd

  1. Verify final In Progress: The workflow ends on a clean saved Overview.
  2. Verify dedicated Emergency encounter: The chosen encounter remains distinct.
  3. Verify older Ambulatory entry remains separate: The exercise never changed its care state.

Use the finite demonstrated outcome

The completed example is one new synthetic Emergency encounter, one On Hold save and one return to In Progress. It contains no triage entry, handover message, discharge, terminal-state save or change to the older Ambulatory encounter. The screenshots document the captured 3dfb interface; later releases may expose different controls.

Own status history created paused resumed in the fictional Emergency encounter demonstration1234
Recorded release 3dfb7c9f · 2026-10-20T00:25:06.898Z · 1728 × 921

Own status history created paused resumed

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 75e52f2c651b24366c7563f42caabc95d01e0e0d5bce96950c1028846fb33dc9

  1. Read the status-history trigger: The popover is open for this same status badge.
  2. Read initial In Progress entry: The popover records the create status and local timestamp.
  3. Read On Hold entry: The first saved update is retained in the history.
  4. Read returned In Progress entry: The second saved update appears after On Hold.
Final clean own emergency overview in the fictional Emergency encounter demonstration123
Recorded release 3dfb7c9f · 2026-10-20T00:25:30.514Z · 1728 × 921

Final clean own emergency overview

Capture details

Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.

Image SHA-256 a26ec1d08a5f31941629fc0aac196b531d9e1d07a9855bcc9ac53ae344b1bcbd

  1. Verify final In Progress: The workflow ends on a clean saved Overview.
  2. Verify dedicated Emergency encounter: The chosen encounter remains distinct.
  3. Verify older Ambulatory entry remains separate: The exercise never changed its care state.

Source evidence

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