← This release collection

Clinical care · VERSION 3dfb7c9f

Open a fictional Consent form and recover date validation

Confirm the synthetic encounter, cancel an untouched form and practise the three date controls with the actual validation messages in the captured 3dfb interface.

Doctor

Doctor synthetic encounter context on the explicitly fictional Consent metadata example1234
Recorded release 3dfb7c9f · 2026-10-19T23:23:58.372Z · 1728 × 921

Doctor synthetic encounter context

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 deecf6cdd228d8bdb8b6b06d1fa10f19dfba388456dfd0982db2268935d14558

  1. Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
  2. Confirm the fictional patient: Use the named SYNTHETIC training patient.
  3. Read In Progress: The chosen Inpatient encounter is active.
  4. Choose Consents: Open the encounter Consents tab.

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

Before you begin

  • Use an authorised ordinary Doctor account with write access to the assigned active synthetic encounter. Actual screenshots show the Doctor role only.
    Doctor synthetic encounter context on the explicitly fictional Consent metadata example1234
    Recorded release 3dfb7c9f · 2026-10-19T23:23:58.372Z · 1728 × 921

    Doctor synthetic encounter context

    Capture details

    Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

    Image SHA-256 deecf6cdd228d8bdb8b6b06d1fa10f19dfba388456dfd0982db2268935d14558

    1. Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
    2. Confirm the fictional patient: Use the named SYNTHETIC training patient.
    3. Read In Progress: The chosen Inpatient encounter is active.
    4. Choose Consents: Open the encounter Consents tab.
  • Use only an approved fictional software-training case. No person gives or refuses consent, no signature is collected, and no legal, treatment, research or disclosure authority is represented.
    Final fictional draft full note before save on the explicitly fictional Consent metadata example1
    Recorded release 3dfb7c9f · 2026-10-19T23:28:59.875Z · 1728 × 921

    Final fictional draft full note before save

    Capture details

    Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

    Image SHA-256 e189d4247390b7fecda8bda2de7f8919f85bec69b4c8844dd83ae505b1730570

    1. Enter and read the full training note: The entire final fictional create note is visible after blur.

1. Confirm the Doctor and the fictional encounter

Check MANSOQ E2E Doctor / qa-doctor and SYNTHETIC Release39b727 Nursing MAR Training. The selected Inpatient encounter is In Progress. These guides demonstrate software metadata only: no person gives or refuses consent, and no signature, legal authority or patient-care decision is represented.

Doctor synthetic encounter context on the explicitly fictional Consent metadata example1234
Recorded release 3dfb7c9f · 2026-10-19T23:23:58.372Z · 1728 × 921

Doctor synthetic encounter context

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 deecf6cdd228d8bdb8b6b06d1fa10f19dfba388456dfd0982db2268935d14558

  1. Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
  2. Confirm the fictional patient: Use the named SYNTHETIC training patient.
  3. Read In Progress: The chosen Inpatient encounter is active.
  4. Choose Consents: Open the encounter Consents tab.

2. Open Consents and Add Consent

Choose Consents in the encounter tabs, then Add Consent. The starting list in this exercise says No Consents found. This describes the visible encounter list at that point; it is not a clinical statement about a person.

Doctor synthetic encounter context on the explicitly fictional Consent metadata example1234
Recorded release 3dfb7c9f · 2026-10-19T23:23:58.372Z · 1728 × 921

Doctor synthetic encounter context

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 deecf6cdd228d8bdb8b6b06d1fa10f19dfba388456dfd0982db2268935d14558

  1. Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
  2. Confirm the fictional patient: Use the named SYNTHETIC training patient.
  3. Read In Progress: The chosen Inpatient encounter is active.
  4. Choose Consents: Open the encounter Consents tab.
Empty consents add entry on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:24:05.962Z · 1728 × 921

Empty consents add entry

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6ea8c255cab334496edbce6be1ea55c24c4782d32d9d2566f4ae1bb1644a2e83

  1. Choose Add Consent: Open the fictional metadata form.
  2. Read the starting empty list: This is the visible list before the single create.

3. Inspect the untouched defaults and choose Cancel

Consent Given On has a required marker. Given On and Valid From initially contain the current local date and time, while Valid Until is empty. Permit, Treatment and Active are the initial selections; Note is empty. Choose Cancel without editing. The sheet closes with no warning and the empty list returns. Open Add Consent again for the following unsaved exercises.

Untouched default form three date controls on the explicitly fictional Consent metadata example12345
Recorded release 3dfb7c9f · 2026-10-19T23:24:15.642Z · 1728 × 921

Untouched default form three date controls

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 846386690ceebe5758cde0df429e01a1179a5535400b12013b6203c8cbd6deb1

  1. Read required Given On: The required marker belongs to Consent Given On.
  2. Read initial Valid From: The initial local date and time are populated.
  3. Read initially empty Valid Until: This period endpoint has no required marker.
  4. Read default Permit: The initial decision is Permit.
  5. Choose Cancel untouched: Close this first form without editing or saving.
Untouched cancel returns empty list on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:24:23.166Z · 1728 × 921

Untouched cancel returns empty list

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6ea8c255cab334496edbce6be1ea55c24c4782d32d9d2566f4ae1bb1644a2e83

  1. Verify the empty list after Cancel: The untouched form closed without a saved record.
  2. Open Add Consent again: Begin the later unsaved field exercises.

4. Observe the required date’s incomplete-value refusal

In Consent Given On, select the day segment and clear it with Backspace. The screenshot shows dd while the other date and time segments remain present. Choose Save once. The browser asks for a valid value because the field is incomplete or invalid. This is client validation; it is not a captured server refusal.

Required date cleared before client save on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:24:39.921Z · 1728 × 921

Required date cleared before client save

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 b13875930012bad0eaf5a4bc73b1ef8dca9bdd4fed7a1bb6c6bad924a7a64ded

  1. Read the cleared day segment: Only the day is missing; other segments are still present.
  2. Use Save once for this client check: The incomplete Given On field blocks the attempt.
Required date incomplete client refusal on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:24:49.428Z · 1728 × 921

Required date incomplete client refusal

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 5b24c5742dd1d383b21c4ddcf8ec7aa90b3ff9464ef0dd89b4723afe9c336fe2

  1. Read the browser validation message: The native bubble reports an incomplete or invalid field.
  2. Read the incomplete required date: The day segment remains empty.

5. Enter complete fictional dates with the keyboard

Select each date/time segment, enter its value, and move between segments with the keyboard. Set Given On to 20/10/2026 12:00 AM, Valid From to 20/10/2026 12:30 AM and Valid Until to 20/10/2026 01:00 AM. Move focus out of the field and re-read all three controls. These are fixed software-demo examples shown in the Asia/Riyadh local time zone, not a consent-validity recommendation.

Three explicit fictional date times on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:25:36.013Z · 1728 × 921

Three explicit fictional date times

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 b082d4e959cc7db6dd72c88c26d4f7319e0cd3f915dadf1a6ac4d546cc99fdb3

  1. Enter and read Given On: The fictional example is 20 October 12:00 AM.
  2. Enter and read Valid From: The example starts at 12:30 AM.
  3. Enter and read Valid Until: The example ends at 01:00 AM.

6. Clear both optional period controls and read the actual limitation

Clear every date and time segment in Valid From and Valid Until so both controls are visibly empty. Choose Save once. In this captured 3dfb sequence, both fields show Invalid input even though they lack a required marker. Do not treat this as a successful blank-period save or repeatedly click Save; restore the approved complete period for this exercise.

Optional period cleared native inputs on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:25:44.375Z · 1728 × 921

Optional period cleared native inputs

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6661b0c4a8e5469eca847365d0d082ac35b49da13a988909edd6bf144a8c0623

  1. Read fully cleared Valid From: All date and time segments are empty.
  2. Read fully cleared Valid Until: Both optional period controls are blank in this attempt.
  3. Choose Save once: Observe the actual cleared-period validation result.
Cleared optional period invalid input feedback on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:25:51.577Z · 1728 × 921

Cleared optional period invalid input feedback

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 9d6dd228afae3519f4f5b235edc4e363ad52e643d49d8be3a7e5962f8bb67c9a

  1. Read the first Invalid input: The cleared Valid From value is refused in this captured sequence.
  2. Read the second Invalid input: The cleared Valid Until value is also refused.

7. Read the reversed-period check

With Given On at 12:00 AM, this unsaved test sets Valid From to 01:30 AM and Valid Until to 01:00 AM, then uses Save once. The pictured result says Valid From must be before Valid Untill. Read the two values and the message before correcting them. The spelling shown is the installed interface’s wording.

Valid from after until client refusal on the explicitly fictional Consent metadata example1234
Recorded release 3dfb7c9f · 2026-10-19T23:26:14.868Z · 1728 × 921

Valid from after until client refusal

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 f7e2341b62b2c87205f457d27e68daa617669dcb5408d4517e7ad25eea4850b7

  1. Read the later start time: Valid From is 01:30 AM.
  2. Read the earlier end time: Valid Until is 01:00 AM.
  3. Read the reversed-period error: The pictured message follows the one invalid Save attempt.
  4. Locate the Save control used for this check: This is the form Save control, not a second action instruction.

8. Read the before-Given-On check

The next unsaved test uses Valid From 19/10/2026 11:30 PM, before Given On 20/10/2026 12:00 AM, and uses Save once. The form says Valid from date cannot be before the given date of the consent. This is another client-side refusal; no record was created by these date exercises.

Valid from before consent date client refusal on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:26:26.693Z · 1728 × 921

Valid from before consent date client refusal

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 65ed6d30de427085017d3a3a60c9985e688416e34ab565b33c65a5bcf5a605d3

  1. Read the previous-day start: Valid From is 19 October 11:30 PM.
  2. Read the before-Given-On error: This start precedes the required consent date.
  3. Locate the form Save control: One invalid attempt produced the pictured message.

9. Restore and re-read the complete period

Restore Given On 20 October 12:00 AM, Valid From 12:30 AM and Valid Until 01:00 AM. Move focus away and read the settled values. Leave the form unsaved for the choice and note exercises that follow.

Restored valid fictional period after refusals on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:26:36.815Z · 1728 × 921

Restored valid fictional period after refusals

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6ad0b1cc93f02e18f8346423c968c9da744e9b52fe54e53ba3cca542fda81589

  1. Verify restored Given On: The final fictional date is 20 October 12:00 AM.
  2. Verify restored start: Valid From is back to 12:30 AM.
  3. Verify restored end: Valid Until is back to 01:00 AM.

Keep the optional-clear result version-specific

These screenshots and messages belong to the captured 3dfb interface. The observed optional-period clearing path returned Invalid input; the guide does not say that every initially blank optional field fails or that a later product version behaves the same way. Keyboard segment entry is demonstrated here; a calendar-popup selection was not established.

Optional period cleared native inputs on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:25:44.375Z · 1728 × 921

Optional period cleared native inputs

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6661b0c4a8e5469eca847365d0d082ac35b49da13a988909edd6bf144a8c0623

  1. Read fully cleared Valid From: All date and time segments are empty.
  2. Read fully cleared Valid Until: Both optional period controls are blank in this attempt.
  3. Choose Save once: Observe the actual cleared-period validation result.
Cleared optional period invalid input feedback on the explicitly fictional Consent metadata example12
Recorded release 3dfb7c9f · 2026-10-19T23:25:51.577Z · 1728 × 921

Cleared optional period invalid input feedback

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 9d6dd228afae3519f4f5b235edc4e363ad52e643d49d8be3a7e5962f8bb67c9a

  1. Read the first Invalid input: The cleared Valid From value is refused in this captured sequence.
  2. Read the second Invalid input: The cleared Valid Until value is also refused.
Restored valid fictional period after refusals on the explicitly fictional Consent metadata example123
Recorded release 3dfb7c9f · 2026-10-19T23:26:36.815Z · 1728 × 921

Restored valid fictional period after refusals

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 6ad0b1cc93f02e18f8346423c968c9da744e9b52fe54e53ba3cca542fda81589

  1. Verify restored Given On: The final fictional date is 20 October 12:00 AM.
  2. Verify restored start: Valid From is back to 12:30 AM.
  3. Verify restored end: Valid Until is back to 01:00 AM.

Keep supporting files separate

Select Files is visible under Supporting Documents, but no file was selected or uploaded in this metadata exercise. Attachment handling, signatures, verification, printing and a legal-consent process are separate from the controls demonstrated here.

Untouched default form three date controls on the explicitly fictional Consent metadata example12345
Recorded release 3dfb7c9f · 2026-10-19T23:24:15.642Z · 1728 × 921

Untouched default form three date controls

Capture details

Actual committed3dfb software. Temporary choices are unsaved; one fictional metadata Draft was created and the same record corrected to Entered in Error. Native required-date and optional-clear validation limitations retained. No actual legal consent, refusal, signature or patient-care decision.

Image SHA-256 846386690ceebe5758cde0df429e01a1179a5535400b12013b6203c8cbd6deb1

  1. Read required Given On: The required marker belongs to Consent Given On.
  2. Read initial Valid From: The initial local date and time are populated.
  3. Read initially empty Valid Until: This period endpoint has no required marker.
  4. Read default Permit: The initial decision is Permit.
  5. Choose Cancel untouched: Close this first form without editing or saving.

Source evidence

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