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
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
- Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
- Confirm the fictional patient: Use the named SYNTHETIC training patient.
- Read In Progress: The chosen Inpatient encounter is active.
- 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.
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- Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
- Confirm the fictional patient: Use the named SYNTHETIC training patient.
- Read In Progress: The chosen Inpatient encounter is active.
- 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.
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- 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
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
- Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
- Confirm the fictional patient: Use the named SYNTHETIC training patient.
- Read In Progress: The chosen Inpatient encounter is active.
- 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
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
- Confirm the Doctor account: Read MANSOQ E2E Doctor and qa-doctor.
- Confirm the fictional patient: Use the named SYNTHETIC training patient.
- Read In Progress: The chosen Inpatient encounter is active.
- Choose Consents: Open the encounter Consents tab.
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
- Choose Add Consent: Open the fictional metadata form.
- 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
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
- Read required Given On: The required marker belongs to Consent Given On.
- Read initial Valid From: The initial local date and time are populated.
- Read initially empty Valid Until: This period endpoint has no required marker.
- Read default Permit: The initial decision is Permit.
- Choose Cancel untouched: Close this first form without editing or saving.
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
- Verify the empty list after Cancel: The untouched form closed without a saved record.
- 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
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
- Read the cleared day segment: Only the day is missing; other segments are still present.
- Use Save once for this client check: The incomplete Given On field blocks the attempt.
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
- Read the browser validation message: The native bubble reports an incomplete or invalid field.
- 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
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
- Enter and read Given On: The fictional example is 20 October 12:00 AM.
- Enter and read Valid From: The example starts at 12:30 AM.
- 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
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
- Read fully cleared Valid From: All date and time segments are empty.
- Read fully cleared Valid Until: Both optional period controls are blank in this attempt.
- Choose Save once: Observe the actual cleared-period validation result.
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
- Read the first Invalid input: The cleared Valid From value is refused in this captured sequence.
- 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
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
- Read the later start time: Valid From is 01:30 AM.
- Read the earlier end time: Valid Until is 01:00 AM.
- Read the reversed-period error: The pictured message follows the one invalid Save attempt.
- 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
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
- Read the previous-day start: Valid From is 19 October 11:30 PM.
- Read the before-Given-On error: This start precedes the required consent date.
- 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
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
- Verify restored Given On: The final fictional date is 20 October 12:00 AM.
- Verify restored start: Valid From is back to 12:30 AM.
- 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
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
- Read fully cleared Valid From: All date and time segments are empty.
- Read fully cleared Valid Until: Both optional period controls are blank in this attempt.
- Choose Save once: Observe the actual cleared-period validation result.
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
- Read the first Invalid input: The cleared Valid From value is refused in this captured sequence.
- Read the second Invalid input: The cleared Valid Until value is also refused.
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
- Verify restored Given On: The final fictional date is 20 October 12:00 AM.
- Verify restored start: Valid From is back to 12:30 AM.
- 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
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
- Read required Given On: The required marker belongs to Consent Given On.
- Read initial Valid From: The initial local date and time are populated.
- Read initially empty Valid Until: This period endpoint has no required marker.
- Read default Permit: The initial decision is Permit.
- 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.
- repositories/platform/mansoq-web/src/components/Consent/ConsentFormSheet.tsx:68 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
b89ccb97b14997364d4c4281498f9e8cbebbcd2d4a8d5b8f6f11544465dbac09 - repositories/platform/mansoq-web/src/pages/Encounters/tabs/consents.tsx:26 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
2f3ee4fe34e9761b7c272dd9e51afbc5bfda09b16edbaf8e2fe6132e47486ddd - repositories/platform/mansoq-web/src/pages/Encounters/ConsentDetail.tsx:56 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
1c91231813f0908fdba7b12023998bad88b4148d378281ca727adf42211d422a - repositories/platform/mansoq-web/src/types/consent/consent.ts:4 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
90674a2497e6024bd015c711593046ac06e348e329d1be3b2c48dfcb448a5581 - repositories/platform/mansoq-web/src/types/consent/consentApi.ts:11 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
43986d090fb6eed6c4ead66df25668dcec638ccf6f8b59479a48d2b003427fbc - repositories/platform/mansoq-web/src/components/Common/DateTimeInput.tsx:6 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
72a885cd20cc0f506da42218669bb8997eefb653d17ef4bb30895ba57cfd4d7f - repositories/platform/mansoq-web/src/lib/validators.ts:3 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
de6a8b925bc793e8145419ed501d3aee37b6d4caf4078e5b78e14661ddbdcc46 - repositories/platform/mansoq-web/src/pages/Encounters/utils/EncounterProvider.tsx:162 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
d2609fc0452c91c20104237bf02be40ecb3bf48225011aba1f4bca2d50620d75 - repositories/platform/mansoq-web/src/pages/Encounters/EncounterShow.tsx:186 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
dba481a8490fa06802648aae1791dc0d91668e6e231e223d6dc4a69369b344d8 - repositories/platform/mansoq-web/src/Routers/routes/PatientRoutes.tsx:9 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
8e3b39ed6e265dc91a238af6ac080ffc7006a7b60e2337908641f1bdf6ec4f31 - repositories/platform/mansoq-web/src/components/ui/RadioInput.tsx:6 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
17b849d60a4f860fdb9f2384625fe43b2bc99fc1179019728c57511fce74813d - repositories/platform/mansoq-web/public/locale/en.json:1480 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
96498c8b964dce856d43c09e4241708efdd175d935e7ebbd14fa2f8d62efa507 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/consent.py:26 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
39b1ef318198a4cbce7b5ee6bf7111b7e050914cf68e4603c4ea978daa69f7d4 - repositories/platform/mansoq-core/mansoq/emr/resources/consent/spec.py:21 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
a8f9c1b4b3d2b219bc887859a259d54a5a12304782515d78be08280436a54ff5 - repositories/platform/mansoq-core/mansoq/emr/models/consent.py:6 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
e6d3853b435445982b8f9cc4d937342be7a82d13b2ac02ac15487aa0c3b1c0e8 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/base.py:94 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
6a287dd315b8a4957b29c58e4bbc1bef7b8d9d257f9149f93045ff0adbdcae6c - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/encounter_authz_base.py:15 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
852c308f990e192a1003e286be7dd57ddcc78840d218da1b90c1fab2eebec4f7 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/condition.py:25 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
f5d22181887766355e1aa847ff777b6f72a492eccce7820f716e4dcb28ad6172 - repositories/platform/mansoq-core/mansoq/security/authorization/encounter.py:97 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
0e7ff8afcfb57b2371201e16ee6fac26125d6e686af66ed7edd95e49bc07de78 - repositories/platform/mansoq-core/mansoq/security/permissions/encounter.py:51 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
06b74efb763810e425de8529660f748ebd56509c729ebc532c8d115102b29218 - repositories/platform/mansoq-core/mansoq/emr/resources/base.py:82 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
bc406c723888997dd99fc408cb3c5dec51fb0b54d10272ca31bfd8c98c893229 - repositories/platform/mansoq-core/mansoq/emr/models/base.py:8 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
61f50a19078c8a6435398e6b3e9174326038e9047129382c0d882f1e8f367b4c - repositories/platform/mansoq-core/mansoq/utils/models/base.py:15 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
1a5270f50188d1e0b044210773ca86a483b904f3a9724bb7b321d4ea463acfaf - repositories/platform/mansoq-core/mansoq/emr/models/file_upload.py:13 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
ebf811b496a25595a7d6ccb9db5181dff79aa6e6a3195819b4fff7292ba79692












