MANSOQ Doctor assessment · VERSION ba551c1d
Copy a reviewed prior diagnosis into the current encounter
Use Diagnosis History to select a fictional prior condition, review the copied draft and save a new current record while preserving the source and existing correction. The ba551c1d sort/disabled-row limit is shown explicitly.
Doctor
12Review selected prior diagnosis and its source context
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Selection is still only a choice in the sheet. Add Selected copies values into an unsaved current draft; it does not alter the prior condition or submit the new current record.
Image SHA-256 5556230559639bceec246aca4012e10305f96ad138b74bc442a4e843e325cb66
- Copy selected values: After reviewing the prior context, choose Add Selected to create a current-form draft. Submit remains a later reviewed action.
- Prior context: The expanded note identifies this source as an isolated synthetic IT prerequisite, not real clinical findings.
12Saved historical copy belongs to the current encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Ordinary Doctor/Nurse reads verified fresh current UUID23973b69… with Doctor creator/updater, distinct from prior sourced1e1706b… and original error99980e57…. Both prior conditions/encounter and original error are unchanged, as are14 administrations/fourrequests. The date-only converter records17 October midnight local on the copy; prior09:00 onset is not rewritten.
Image SHA-256 5e43adbcfd9b50f11cd888a984fbb004e0604e0fa65bbb69668dc99f43477372
- Inspect current copy: Reopen the selected current encounter diagnosis editor to verify the copied condition and retained original correction.
- Past onset date: This is the copied onset calendar date, not the creation time of the new current condition.
10 of 10 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.
Before you begin
- Use your existing authorized Doctor account and confirm the intended current patient and In Progress encounter. Review the earlier record-diagnosis lesson for entry and installed terminology controls. This is an isolated fictional Polyclinic inpatient example, not real clinical findings, diagnosis or advice.
12Recorded release ba551c1d · 2026-10-19T00:04:18.317Z · 1728 × 921 Doctor clinical actions versus installed questionnaires
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Installed questionnaire titles can differ from system actions. Use the intended action and verify the form title and selected patient/encounter.
Image SHA-256
9822a91466622019102542e0da2189eb5445b46da0513a1e7fbee1f63ade5df3- Add Diagnosis: This system action opens the Diagnosis questionnaire for the selected encounter.
- Add Symptom: Symptoms use their own condition category and system questionnaire.
12Recorded release ba551c1d · 2026-10-19T00:21:05.428Z · 1728 × 921 Saved historical copy belongs to the current encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Ordinary Doctor/Nurse reads verified fresh current UUID23973b69… with Doctor creator/updater, distinct from prior sourced1e1706b… and original error99980e57…. Both prior conditions/encounter and original error are unchanged, as are14 administrations/fourrequests. The date-only converter records17 October midnight local on the copy; prior09:00 onset is not rewritten.
Image SHA-256
5e43adbcfd9b50f11cd888a984fbb004e0604e0fa65bbb69668dc99f43477372- Inspect current copy: Reopen the selected current encounter diagnosis editor to verify the copied condition and retained original correction.
- Past onset date: This is the copied onset calendar date, not the creation time of the new current condition.
- The eligible prior source was prepared separately through supported IT APIs: a fictional Ambulatory encounter was created In Progress, its M54.5 diagnosis and symptom prerequisites were added, then that encounter was normally completed. A separate earlier attempt to add a condition after completion correctly returned 403; it was not bypassed or reopened. The source creator is Root; this lesson proves the Doctor’s copying steps, not Doctor authoring of that prerequisite.
12Recorded release ba551c1d · 2026-10-19T00:19:56.815Z · 1728 × 921 Select a diagnosis from the fictional prior encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Separate supported IT prerequisite APIs created prior encounter96fab871… In Progress, added valid installed M54.5 conditiond1e1706b…, then completed it normally. A prior attempted already-completed source correctly refused condition creation403 and was not bypassed. This is not Doctor creation proof for the prior record.
Image SHA-256
697aab5308be347d4279dca8c2b7b5620fc6464bd953221d6bcd616b687b830c- Choose prior record: Review the intended prior coding, Active status, Provisional verification, Mild severity, Root prerequisite creator and 17 October onset before selecting.
- Recorded date versus onset: The 19 October group is creation date; the row’s 17 October onset is separate.
12Recorded release ba551c1d · 2026-10-19T00:20:07.233Z · 1728 × 921 Review selected prior diagnosis and its source context
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Selection is still only a choice in the sheet. Add Selected copies values into an unsaved current draft; it does not alter the prior condition or submit the new current record.
Image SHA-256
5556230559639bceec246aca4012e10305f96ad138b74bc442a4e843e325cb66- Copy selected values: After reviewing the prior context, choose Add Selected to create a current-form draft. Submit remains a later reviewed action.
- Prior context: The expanded note identifies this source as an isolated synthetic IT prerequisite, not real clinical findings.
1. Open the selected encounter Diagnosis editor
Confirm the intended current In Progress encounter. Open Encounter Actions → Add Diagnosis, then Diagnosis History. Wait for the selector request to settle. The earlier current diagnosis is Entered in Error and is not an eligible reusable source. The pictured eligible prior row is LOW BACK PAIN, Active, Mild, Provisional, recorded by the Root prerequisite operator with 17 October onset.
12Doctor clinical actions versus installed questionnaires
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Installed questionnaire titles can differ from system actions. Use the intended action and verify the form title and selected patient/encounter.
Image SHA-256 9822a91466622019102542e0da2189eb5445b46da0513a1e7fbee1f63ade5df3
- Add Diagnosis: This system action opens the Diagnosis questionnaire for the selected encounter.
- Add Symptom: Symptoms use their own condition category and system questionnaire.
12Select a diagnosis from the fictional prior encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Separate supported IT prerequisite APIs created prior encounter96fab871… In Progress, added valid installed M54.5 conditiond1e1706b…, then completed it normally. A prior attempted already-completed source correctly refused condition creation403 and was not bypassed. This is not Doctor creation proof for the prior record.
Image SHA-256 697aab5308be347d4279dca8c2b7b5620fc6464bd953221d6bcd616b687b830c
- Choose prior record: Review the intended prior coding, Active status, Provisional verification, Mild severity, Root prerequisite creator and 17 October onset before selecting.
- Recorded date versus onset: The 19 October group is creation date; the row’s 17 October onset is separate.
2. Review the prior context before selecting
Review the returned row’s coding, status, severity, verification, creator and onset. The group date 19 October is creation date; it differs from 17 October onset. Select only the intended row checkbox and expand its information icon to inspect the explicit synthetic prior note. This selector does not display an encounter column, so do not infer source encounter identity from its title alone. Choose Add Selected after deliberate review; this only creates an unsaved current-form draft.
12Select a diagnosis from the fictional prior encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Separate supported IT prerequisite APIs created prior encounter96fab871… In Progress, added valid installed M54.5 conditiond1e1706b…, then completed it normally. A prior attempted already-completed source correctly refused condition creation403 and was not bypassed. This is not Doctor creation proof for the prior record.
Image SHA-256 697aab5308be347d4279dca8c2b7b5620fc6464bd953221d6bcd616b687b830c
- Choose prior record: Review the intended prior coding, Active status, Provisional verification, Mild severity, Root prerequisite creator and 17 October onset before selecting.
- Recorded date versus onset: The 19 October group is creation date; the row’s 17 October onset is separate.
12Review selected prior diagnosis and its source context
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Selection is still only a choice in the sheet. Add Selected copies values into an unsaved current draft; it does not alter the prior condition or submit the new current record.
Image SHA-256 5556230559639bceec246aca4012e10305f96ad138b74bc442a4e843e325cb66
- Copy selected values: After reviewing the prior context, choose Add Selected to create a current-form draft. Submit remains a later reviewed action.
- Prior context: The expanded note identifies this source as an isolated synthetic IT prerequisite, not real clinical findings.
3. Review the copied values and the captured control limit
The copied draft retains the prior calendar date, Active status, Mild severity, Provisional verification and contextual note. In this captured version a sort/index defect disables the earlier-onset new draft while incorrectly enabling the original 19 October error row. Leave the original correction untouched. If the copied values need changes and the intended row is disabled, cancel rather than edit the wrong row. In this fictional exercise the reviewed copied values are deliberately retained, so Submit once saves that new draft. This does not demonstrate correction of the index defect.
123Review a copied prior diagnosis and the existing-error row limit
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Actual ba551 index-association limitation: sorted draft rows are disabled using the fetched row array index instead of saved identity. Do not change the incorrectly enabled error record. This synthetic copy intentionally retains the prior values; if changes to the copied row were required, cancel rather than alter the wrong row.
Image SHA-256 ef0387ecb473d3e1161e9930724062c1b7352fcdf6a13b4f93220376eb9f5ca7
- Copied draft is disabled: The intended copied row retains 17 October onset and prior values, but these controls are disabled in this version.
- Leave original correction intact: The original current error record is wrongly enabled by array-index association. Do not edit it.
- Submit only reviewed intended values: In this fictional example the copied values are intentionally retained. Submit once saves the new current condition; it should preserve the prior source and original correction.
4. Verify the new current condition and author
After the overview settles, confirm the copied Active/Mild/Provisional condition under the chosen current encounter. Its onset appears as 2 days ago. The saved row information menu identifies Doctor as Reported by; the source row showed Root. Separate ordinary Doctor and Nurse reads verified a fresh current UUID distinct from the prior source and original error. The prior encounter and both prior conditions, the original current correction, all fourteen administrations and all four requests remain unchanged.
12Saved historical copy belongs to the current encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Ordinary Doctor/Nurse reads verified fresh current UUID23973b69… with Doctor creator/updater, distinct from prior sourced1e1706b… and original error99980e57…. Both prior conditions/encounter and original error are unchanged, as are14 administrations/fourrequests. The date-only converter records17 October midnight local on the copy; prior09:00 onset is not rewritten.
Image SHA-256 5e43adbcfd9b50f11cd888a984fbb004e0604e0fa65bbb69668dc99f43477372
- Inspect current copy: Reopen the selected current encounter diagnosis editor to verify the copied condition and retained original correction.
- Past onset date: This is the copied onset calendar date, not the creation time of the new current condition.
12The current copied diagnosis has Doctor creator
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Copying creates a new current condition rather than moving the original. Independent current/source reads verify the distinct UUIDs and unchanged original source.
Image SHA-256 ee9b388d294f8a55483e5608316cc2f6924f72c27334c0fd93d9aed4f7d0a046
- New record author: Immediately left, Reported by identifies Doctor for this new current record; the prior source showed Root.
- Copied context: The prior contextual note is retained on the new current copy. Review copied context deliberately.
5. Inspect both current records without another save
Reopen the current Diagnosis editor. The newly saved 17 October copy and original 19 October Entered in Error record are both retained. In this freshly fetched ordering, the new copy is editable and the original error row is disabled; this does not remove the earlier pre-save sort/index defect. The copy’s saved onset is locked. Cancel after read-only verification, confirming the generic leave warning only after checking that no intended edits need saving. Independent reads confirmed all diagnosis records were unchanged by this inspection.
123Reopened saved copy and original correction
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Both records retain distinct UUIDs and the source prior encounter/condition is unchanged. The pre-save sort/index limitation is separate; this refreshed ordering happens to align the fetched indices. No further update is made here.
Image SHA-256 207a6859a37652eac68a02b987a4c5686d72f59dbfc8b77d442686a3a01a5aa1
- New saved copy: The new current condition is Active/Mild/Provisional and its saved onset date is locked.
- Original correction preserved: The original saved error record remains disabled after this fresh read.
- Leave inspection: Cancel after read-only verification; do not resubmit unchanged records.
Copy versus move and date precision
The Doctor copy is a new condition associated with the selected current encounter. It does not move or overwrite the prior source. The interface converts the onset to a calendar date: this source’s 17 October 09:00 Riyadh onset becomes 17 October 00:00 Riyadh on the current copy, while the original source timestamp is unchanged. The lesson therefore demonstrates calendar-date reuse, not exact timestamp preservation. Review onset under facility policy rather than assuming every historical field is copied at its original precision.
12Select a diagnosis from the fictional prior encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Separate supported IT prerequisite APIs created prior encounter96fab871… In Progress, added valid installed M54.5 conditiond1e1706b…, then completed it normally. A prior attempted already-completed source correctly refused condition creation403 and was not bypassed. This is not Doctor creation proof for the prior record.
Image SHA-256 697aab5308be347d4279dca8c2b7b5620fc6464bd953221d6bcd616b687b830c
- Choose prior record: Review the intended prior coding, Active status, Provisional verification, Mild severity, Root prerequisite creator and 17 October onset before selecting.
- Recorded date versus onset: The 19 October group is creation date; the row’s 17 October onset is separate.
123Review a copied prior diagnosis and the existing-error row limit
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Actual ba551 index-association limitation: sorted draft rows are disabled using the fetched row array index instead of saved identity. Do not change the incorrectly enabled error record. This synthetic copy intentionally retains the prior values; if changes to the copied row were required, cancel rather than alter the wrong row.
Image SHA-256 ef0387ecb473d3e1161e9930724062c1b7352fcdf6a13b4f93220376eb9f5ca7
- Copied draft is disabled: The intended copied row retains 17 October onset and prior values, but these controls are disabled in this version.
- Leave original correction intact: The original current error record is wrongly enabled by array-index association. Do not edit it.
- Submit only reviewed intended values: In this fictional example the copied values are intentionally retained. Submit once saves the new current condition; it should preserve the prior source and original correction.
123Reopened saved copy and original correction
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Both records retain distinct UUIDs and the source prior encounter/condition is unchanged. The pre-save sort/index limitation is separate; this refreshed ordering happens to align the fetched indices. No further update is made here.
Image SHA-256 207a6859a37652eac68a02b987a4c5686d72f59dbfc8b77d442686a3a01a5aa1
- New saved copy: The new current condition is Active/Mild/Provisional and its saved onset date is locked.
- Original correction preserved: The original saved error record remains disabled after this fresh read.
- Leave inspection: Cancel after read-only verification; do not resubmit unchanged records.
Observed scope and remaining work
One existing Doctor copied one eligible fictional prior diagnosis into one Polyclinic inpatient encounter. The private prerequisite and failed closed-encounter write are separate from this UI proof. Other codes, multiple selection, other roles/facilities, chronic conditions, changes to the disabled copied row and complete history audit remain separately unqualified. The saved original Entered in Error condition was preserved.
12Select a diagnosis from the fictional prior encounter
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Separate supported IT prerequisite APIs created prior encounter96fab871… In Progress, added valid installed M54.5 conditiond1e1706b…, then completed it normally. A prior attempted already-completed source correctly refused condition creation403 and was not bypassed. This is not Doctor creation proof for the prior record.
Image SHA-256 697aab5308be347d4279dca8c2b7b5620fc6464bd953221d6bcd616b687b830c
- Choose prior record: Review the intended prior coding, Active status, Provisional verification, Mild severity, Root prerequisite creator and 17 October onset before selecting.
- Recorded date versus onset: The 19 October group is creation date; the row’s 17 October onset is separate.
123Review a copied prior diagnosis and the existing-error row limit
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Actual ba551 index-association limitation: sorted draft rows are disabled using the fetched row array index instead of saved identity. Do not change the incorrectly enabled error record. This synthetic copy intentionally retains the prior values; if changes to the copied row were required, cancel rather than alter the wrong row.
Image SHA-256 ef0387ecb473d3e1161e9930724062c1b7352fcdf6a13b4f93220376eb9f5ca7
- Copied draft is disabled: The intended copied row retains 17 October onset and prior values, but these controls are disabled in this version.
- Leave original correction intact: The original current error record is wrongly enabled by array-index association. Do not edit it.
- Submit only reviewed intended values: In this fictional example the copied values are intentionally retained. Submit once saves the new current condition; it should preserve the prior source and original correction.
123Reopened saved copy and original correction
Capture details
Exact committed ba551c1d isolated synthetic clone, ordinary existing Doctor account, fictional Polyclinic inpatient encounter. The patient retains an earlier release name; actual captured source is ba551c1d. All examples are software training only, not real symptoms, diagnosis, treatment or clinical advice. Both records retain distinct UUIDs and the source prior encounter/condition is unchanged. The pre-save sort/index limitation is separate; this refreshed ordering happens to align the fetched indices. No further update is made here.
Image SHA-256 207a6859a37652eac68a02b987a4c5686d72f59dbfc8b77d442686a3a01a5aa1
- New saved copy: The new current condition is Active/Mild/Provisional and its saved onset date is locked.
- Original correction preserved: The original saved error record remains disabled after this fresh read.
- Leave inspection: Cancel after read-only verification; do not resubmit unchanged records.
Source evidence
Every citation uses this exact committed version. The private source repository requires access.
- repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx:299 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
800733fc03b30528ba90689524d5c3a39b2f777ffdbb9dc8ef5ad5e874c3e504 - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx:508 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
800733fc03b30528ba90689524d5c3a39b2f777ffdbb9dc8ef5ad5e874c3e504 - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx:648 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
800733fc03b30528ba90689524d5c3a39b2f777ffdbb9dc8ef5ad5e874c3e504 - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx:698 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
800733fc03b30528ba90689524d5c3a39b2f777ffdbb9dc8ef5ad5e874c3e504 - repositories/platform/mansoq-web/src/components/Questionnaire/structured/handlers.ts:139 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
796209bfb43e9be152a55372f0118c6cf12c1c332477dc408f0fef012f9e3ad8 - repositories/platform/mansoq-web/src/components/HistoricalRecordSelector/index.tsx:290 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
ed49e6aa587ed90db0bd986cb9adc6596be31539fa1b865cf073c130e75a0ac8 - repositories/platform/mansoq-web/src/components/Patient/diagnosis/DiagnosisTable.tsx:187 ·
ba551c1d67031248136fd2016afe227b5fc994bdSource file checksum
45e40342661a50ac9ad52a4e34cfc2dc4d153ce389dc8829ffdb52c0f44f4c19