MANSOQ Knowledge
← This release collection

Doctor assessment · VERSION ba551c1d

Correct a saved diagnosis with Entered in Error

Mark the intended saved condition as Entered in Error, verify the same retained record, and handle the observed history-selector cache boundary on exact ba551c1d.

Doctor

Review Entered in Error before saving. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:23.039Z · 1728 × 921

Review Entered in Error before saving

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. The optional note gives synthetic correction context. Only Submit persists this verification change; no permanent deletion is performed.

Image SHA-256 3616e1c8d945b3416ee01946e4b8c259c9395b0f63e90d887956c7d542d3d00f

  1. Correction verification: Verify Entered in Error on the intended saved row. It differs from Resolved clinical status.
  2. Submit correction: Save the reviewed correction once. The record UUID, code and original onset remain.
Persisted Entered in Error diagnosis remains visible and locked. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:36.977Z · 1728 × 921

Persisted Entered in Error diagnosis remains visible and locked

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 readbacks confirmed same UUID, code/onset, Resolved clinical status, Entered in Error verification and Doctor updater. No diagnosis deletion, new administration or request update occurred.

Image SHA-256 9f5fc4f7fda695b53a187eb1781743c3066cf63b5cd653304ca8f2aef30e817f

  1. Persisted correction: The saved row is retained and disabled, rather than removed from storage.
  2. History selector exclusion: The normal selector query excludes entered-in-error records. A separate captured cache limitation shows why its same-session display must be refreshed before reuse.

9 of 9 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 patient, selected encounter, facility and ongoing status. This observed account is qa-doctor; no permission or membership is added.
    Existing Doctor identity in the selected synthetic encounter. Actual MANSOQ desktop with a fictional training case.1
    Recorded release ba551c1d · 2026-10-19T00:03:34.348Z · 1728 × 921

    Existing Doctor identity in the selected synthetic 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 existing qa-doctor account. Medication and Nutrition events/requests are preserved; this branch concerns assessment documentation only.

    Image SHA-256 f58ee93eda7e76a2bb930fb2508da3a97513acdfd479391e115bc991dd188f80

    1. Doctor identity: Immediately right of the account avatar, the menu identifies MANSOQ E2E Doctor and qa-doctor. Confirm the authorized operator before documenting.
    Resolved diagnosis remains in the selected encounter editor. Actual MANSOQ desktop with a fictional training case.12
    Recorded release ba551c1d · 2026-10-19T00:07:42.785Z · 1728 × 921

    Resolved diagnosis remains in the selected encounter editor

    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. Normal reads verified the same saved UUID and original code/onset. This editor is encounter-specific and retrieves all current conditions, including non-active states.

    Image SHA-256 97ad4b024174c63156d2324415e8e0f716fe2313a39008400241a1e5654e2a3f

    1. Retained resolved record: The condition still exists with its saved clinical lifecycle value.
    2. Diagnosis History selector: This selector uses a different query from the separate Past Diagnoses timeline. Review only settled current results; a same-session cached-row limitation is illustrated separately.
  • All records here are fictional software training. LOW BACK PAIN is an actually returned installed ICD-10-AM terminology choice, M54.5. The example does not establish clinical findings, coding suitability, treatment or a medical decision.
    Select an installed diagnosis terminology result. Actual MANSOQ desktop with a fictional training case.1
    Recorded release ba551c1d · 2026-10-19T00:04:35.783Z · 1728 × 921

    Select an installed diagnosis terminology result

    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. Read-only normal terminology POST confirmed code M54.5, system http://hl7.org/fhir/sid/icd-10-am. No fabricated official code or new terminology installation is used. This fictional example is not a clinical diagnosis recommendation.

    Image SHA-256 5902e4339fa9643c10a4250fe034f89431799a75d7018cbb8facd827c53e58ca

    1. Installed result: Select the actually returned LOW BACK PAIN result. Search text alone does not save a coded diagnosis.
    Review Entered in Error before saving. Actual MANSOQ desktop with a fictional training case.12
    Recorded release ba551c1d · 2026-10-19T00:08:23.039Z · 1728 × 921

    Review Entered in Error before saving

    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. The optional note gives synthetic correction context. Only Submit persists this verification change; no permanent deletion is performed.

    Image SHA-256 3616e1c8d945b3416ee01946e4b8c259c9395b0f63e90d887956c7d542d3d00f

    1. Correction verification: Verify Entered in Error on the intended saved row. It differs from Resolved clinical status.
    2. Submit correction: Save the reviewed correction once. The record UUID, code and original onset remain.

1. Identify the existing record before correction

Reopen the selected encounter Diagnosis editor and confirm the intended saved row. This example begins with the original Resolved/Mild/Confirmed condition and locked onset. Open its ellipsis menu. Remove Diagnosis on an existing record prepares Entered in Error verification; it does not permanently delete the stored condition. This differs from removing an unsaved new draft.

Resolved diagnosis remains in the selected encounter editor. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:07:42.785Z · 1728 × 921

Resolved diagnosis remains in the selected encounter editor

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. Normal reads verified the same saved UUID and original code/onset. This editor is encounter-specific and retrieves all current conditions, including non-active states.

Image SHA-256 97ad4b024174c63156d2324415e8e0f716fe2313a39008400241a1e5654e2a3f

  1. Retained resolved record: The condition still exists with its saved clinical lifecycle value.
  2. Diagnosis History selector: This selector uses a different query from the separate Past Diagnoses timeline. Review only settled current results; a same-session cached-row limitation is illustrated separately.
Remove on an existing diagnosis prepares a correction. Actual MANSOQ desktop with a fictional training case.1
Recorded release ba551c1d · 2026-10-19T00:08:17.546Z · 1728 × 921

Remove on an existing diagnosis prepares a 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. Source changes an existing row verification to Entered in Error and marks it dirty; it does not issue a DELETE. Submit is still required. This is different from discarding an unsaved new row.

Image SHA-256 5e053f56d32192a7fda352ec392e52c85f2667c55628e9af04f86b1c71fb119b

  1. Prepare correction: Use only when correction is intended under facility policy. Review the resulting Entered in Error state before submission.

2. Review the correction and optional context

Choose Remove Diagnosis only when correction is intended and authorized under facility policy. The same row remains with Verification Entered in Error, original code and onset, and unchanged Resolved clinical status and Mild severity. Notes is optional software input; record appropriate correction context under facility policy. The pictured note identifies a fictional training correction. Choose Submit once to persist the reviewed change.

Remove on an existing diagnosis prepares a correction. Actual MANSOQ desktop with a fictional training case.1
Recorded release ba551c1d · 2026-10-19T00:08:17.546Z · 1728 × 921

Remove on an existing diagnosis prepares a 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. Source changes an existing row verification to Entered in Error and marks it dirty; it does not issue a DELETE. Submit is still required. This is different from discarding an unsaved new row.

Image SHA-256 5e053f56d32192a7fda352ec392e52c85f2667c55628e9af04f86b1c71fb119b

  1. Prepare correction: Use only when correction is intended under facility policy. Review the resulting Entered in Error state before submission.
Review Entered in Error before saving. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:23.039Z · 1728 × 921

Review Entered in Error before saving

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. The optional note gives synthetic correction context. Only Submit persists this verification change; no permanent deletion is performed.

Image SHA-256 3616e1c8d945b3416ee01946e4b8c259c9395b0f63e90d887956c7d542d3d00f

  1. Correction verification: Verify Entered in Error on the intended saved row. It differs from Resolved clinical status.
  2. Submit correction: Save the reviewed correction once. The record UUID, code and original onset remain.

3. Verify the retained corrected record

Reopen Encounter Actions → Add Diagnosis after submission. The saved Entered in Error row remains visible but its controls are disabled. Ordinary Doctor and Nurse reads confirmed the same UUID, code and onset, Resolved clinical status, Entered in Error verification and Doctor updater. All fourteen administration entries and all four complete requests were unchanged. No diagnosis DELETE occurred.

Persisted Entered in Error diagnosis remains visible and locked. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:36.977Z · 1728 × 921

Persisted Entered in Error diagnosis remains visible and locked

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 readbacks confirmed same UUID, code/onset, Resolved clinical status, Entered in Error verification and Doctor updater. No diagnosis deletion, new administration or request update occurred.

Image SHA-256 9f5fc4f7fda695b53a187eb1781743c3066cf63b5cd653304ca8f2aef30e817f

  1. Persisted correction: The saved row is retained and disabled, rather than removed from storage.
  2. History selector exclusion: The normal selector query excludes entered-in-error records. A separate captured cache limitation shows why its same-session display must be refreshed before reuse.

4. Recognize a stale same-session selection row

In the captured version, reopening Diagnosis History in the same session can initially retain the earlier cached Resolved/Confirmed row. After the fresh request finishes, expanding its date can still show that stale choice, while the editor behind is already Entered in Error. Do not select or add it. The actual normal selector query excludes error records; this is a presentation cache limitation. Close the sheet and refresh the clean page before using history again.

History selector can retain a stale pre-correction row. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:57.176Z · 1728 × 921

History selector can retain a stale pre-correction row

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. Observed ba551 presentation boundary: shared HistoricalRecordSelector merges cached date groups and does not clear the removed row on a fresh empty response. Do not re-add this stale choice. Close and reload the clean page before reuse; independent current reads verify Entered in Error.

Image SHA-256 52392b51bd57df9af84e6f1ddd2ba74104cea0742f2073f24e975eea2a018eaf

  1. Do not select stale row: This visible Confirmed row is the earlier cached version, not the independently verified current Entered in Error state.
  2. Close stale selector: Close this read-only sheet, leave without submitting changes, and refresh the clean editor before choosing history again.

5. Verify fresh exclusion without resubmitting

After a normal clean reload, reopen Diagnosis History. The settled selector shows No Records Found and disabled Add Selected. The exact ordinary Doctor selector query independently returned no eligible records, while unrestricted Doctor and Nurse reads retain the corrected UUID. This is expected filter exclusion after refresh, not deletion. Close the selector and Cancel out of the read-only editor; if the generic unsaved-changes warning appears despite no edits, confirm leaving only after checking that no intended draft needs saving.

Fresh history selector excludes the corrected condition. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:09:22.678Z · 1728 × 921

Fresh history selector excludes the corrected condition

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. The exact ordinary Doctor selector query independently returned200/count 0 while unrestricted Doctor/Nurse reads retain the same Entered in Error UUID. This confirms filter exclusion after refresh, not deletion.

Image SHA-256 3a054b751496f4b9992082f80bf2d906f95ac7b92d5dd17bbd29bbea89a2e2dc

  1. No reusable selection: Add Selected is disabled because the fresh selector has no eligible non-error record.
  2. Close: Close the read-only selector. No condition was copied or resubmitted during this verification.
Persisted Entered in Error diagnosis remains visible and locked. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:36.977Z · 1728 × 921

Persisted Entered in Error diagnosis remains visible and locked

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 readbacks confirmed same UUID, code/onset, Resolved clinical status, Entered in Error verification and Doctor updater. No diagnosis deletion, new administration or request update occurred.

Image SHA-256 9f5fc4f7fda695b53a187eb1781743c3066cf63b5cd653304ca8f2aef30e817f

  1. Persisted correction: The saved row is retained and disabled, rather than removed from storage.
  2. History selector exclusion: The normal selector query excludes entered-in-error records. A separate captured cache limitation shows why its same-session display must be refreshed before reuse.

Correction scope

The example corrects verification on one saved fictional condition. It does not demonstrate recovery from Entered in Error, permanent deletion, a replacement condition, all correction permissions or a complete change-history audit. A new legitimate diagnosis or reused historical record must be deliberately reviewed and separately submitted, never inferred from a stale selector.

Review Entered in Error before saving. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:23.039Z · 1728 × 921

Review Entered in Error before saving

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. The optional note gives synthetic correction context. Only Submit persists this verification change; no permanent deletion is performed.

Image SHA-256 3616e1c8d945b3416ee01946e4b8c259c9395b0f63e90d887956c7d542d3d00f

  1. Correction verification: Verify Entered in Error on the intended saved row. It differs from Resolved clinical status.
  2. Submit correction: Save the reviewed correction once. The record UUID, code and original onset remain.
Persisted Entered in Error diagnosis remains visible and locked. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:08:36.977Z · 1728 × 921

Persisted Entered in Error diagnosis remains visible and locked

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 readbacks confirmed same UUID, code/onset, Resolved clinical status, Entered in Error verification and Doctor updater. No diagnosis deletion, new administration or request update occurred.

Image SHA-256 9f5fc4f7fda695b53a187eb1781743c3066cf63b5cd653304ca8f2aef30e817f

  1. Persisted correction: The saved row is retained and disabled, rather than removed from storage.
  2. History selector exclusion: The normal selector query excludes entered-in-error records. A separate captured cache limitation shows why its same-session display must be refreshed before reuse.
Fresh history selector excludes the corrected condition. Actual MANSOQ desktop with a fictional training case.12
Recorded release ba551c1d · 2026-10-19T00:09:22.678Z · 1728 × 921

Fresh history selector excludes the corrected condition

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. The exact ordinary Doctor selector query independently returned200/count 0 while unrestricted Doctor/Nurse reads retain the same Entered in Error UUID. This confirms filter exclusion after refresh, not deletion.

Image SHA-256 3a054b751496f4b9992082f80bf2d906f95ac7b92d5dd17bbd29bbea89a2e2dc

  1. No reusable selection: Add Selected is disabled because the fresh selector has no eligible non-error record.
  2. Close: Close the read-only selector. No condition was copied or resubmitted during this verification.

Source evidence

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