Clinical care · VERSION 3dfb7c9f
Cancel an update, then put the Emergency encounter On Hold
Read the actual update controls and leave warning, save one status change, then find the retained On Hold encounter through the Emergency encounter list and its status filter.
Doctor
Created emergency overview new identity
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 e3f4523f6cc18fb07eed82d5b442c5197f0499fda8fd85260c03257e98656bec
- Read the chosen Emergency encounter: This is the separate new encounter.
- Read In Progress: The newly saved status is visible.
- Verify Emergency class: The older Ambulatory encounter was not converted.
- Verify Routine: The saved priority matches the review.
- Verify the local start: The saved display is 20 Oct 2026 02:00 AM.
- Read ongoing end: The create did not complete or discharge the encounter.
- Keep the older Ambulatory encounter separate: The previous encounter remains under Other Encounters.
- Choose Update Encounter: Open only the dedicated Emergency encounter editor.
15 of 15 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.
Before you begin
- Use an authorised ordinary Doctor account in the assigned synthetic facility and patient scope. Actual native screenshots demonstrate Doctor only; Nurse and Staff checks are read-only authority observations.
Recorded release 3dfb7c9f · 2026-10-20T00:07:53.010Z · 1728 × 921 Emergency board unconfigured existing rows
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256
772ce2e5bcd1b03a608e96e88bc15717c2ceb0e826833e46149477b4b8b0c367- Open Emergency board: Use the facility sidebar Patients section.
- Check the ordinary Doctor account: The actual account is MANSOQ E2E Doctor / qa-doctor.
- Read the unconfigured triage warning: Priority and arrival ordering does not infer a triage level.
- Read Not configured: This cell contains no triage level.
- Read encounter priority: This Emergency label is a priority, not a calculated triage result.
- Read waiting and arrival: The cell includes elapsed minutes and the displayed time zone.
- Read location: An existing demonstration row displays ER Bed 01; no location was assigned in this exercise.
- Read practitioners: The row shows its recorded practitioner role.
- Read Handover Notes: The link count is associated with that particular row.
- Locate Refresh: Manual Refresh requests the current board data.
- Use only an approved fictional software-training case with validated creation/update prerequisites. No triage, treatment, clinical urgency, handover, admission or discharge decision is represented.
Recorded release 3dfb7c9f · 2026-10-20T00:08:26.168Z · 1728 × 921 Existing synthetic patient profile and home link
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256
71f570730dbc162c980a84f3073daaac96cbcb24d66a846bb56db4693a767252- Confirm the fictional patient: Use the assigned SYNTHETIC training identity.
- Choose Patient Home: Open the existing patient home without editing the profile.
1. Confirm the dedicated Emergency encounter and open Update Encounter
On Overview, verify the chosen Emergency encounter and the separate older Ambulatory entry. Choose Update Encounter in Encounter Details. Keep the same fictional patient and dedicated Emergency encounter throughout this guide.
Created emergency overview new identity
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 e3f4523f6cc18fb07eed82d5b442c5197f0499fda8fd85260c03257e98656bec
- Read the chosen Emergency encounter: This is the separate new encounter.
- Read In Progress: The newly saved status is visible.
- Verify Emergency class: The older Ambulatory encounter was not converted.
- Verify Routine: The saved priority matches the review.
- Verify the local start: The saved display is 20 Oct 2026 02:00 AM.
- Read ongoing end: The create did not complete or discharge the encounter.
- Keep the older Ambulatory encounter separate: The previous encounter remains under Other Encounters.
- Choose Update Encounter: Open only the dedicated Emergency encounter editor.
Own update untouched before cancel
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 0fe9676c8c6eb3e1a511411ca779012e42a7fbc7354a897f1cb3fdd1f977f8e5
- Read In Progress: The untouched editor loads the current status.
- Read Routine: Leave this field unchanged.
- Leave Hospital Identifier empty: No identifier is authored by this exercise.
- Leave Mark for discharge unused: Discharge is a separate workflow.
- Leave Re-admission off: No hospitalization switch change is made.
- Leave Admit Source unselected: No source is chosen here.
- Leave Diet Preference unselected: This form value stays empty.
- Leave Add Forms untouched: No additional form is part of the status update.
- Choose Cancel untouched: The actual leave confirmation follows.
2. Inspect the untouched update controls
The update form contains Encounter Status, Priority, Hospital Identifier, Mark for discharge and hospitalization fields. In this release it has no class selector or start-date editor. Leave Hospital Identifier empty, Re-admission off, Admit Source and Diet Preference unselected, and Add Forms untouched.
Own update untouched before cancel
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 0fe9676c8c6eb3e1a511411ca779012e42a7fbc7354a897f1cb3fdd1f977f8e5
- Read In Progress: The untouched editor loads the current status.
- Read Routine: Leave this field unchanged.
- Leave Hospital Identifier empty: No identifier is authored by this exercise.
- Leave Mark for discharge unused: Discharge is a separate workflow.
- Leave Re-admission off: No hospitalization switch change is made.
- Leave Admit Source unselected: No source is chosen here.
- Leave Diet Preference unselected: This form value stays empty.
- Leave Add Forms untouched: No additional form is part of the status update.
- Choose Cancel untouched: The actual leave confirmation follows.
3. Choose Cancel and read the actual leave confirmation
Choose Cancel without editing. In this observed run, a browser-native confirmation appeared even though no user field edit had been made. It says You have unsaved changes. Are you sure you want to leave? Choose OK to leave this untouched form; the dialog’s Cancel would keep the form open. The screenshot is the genuine compact macOS confirmation, not a web page or print dialog.
Own update untouched before cancel
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 0fe9676c8c6eb3e1a511411ca779012e42a7fbc7354a897f1cb3fdd1f977f8e5
- Read In Progress: The untouched editor loads the current status.
- Read Routine: Leave this field unchanged.
- Leave Hospital Identifier empty: No identifier is authored by this exercise.
- Leave Mark for discharge unused: Discharge is a separate workflow.
- Leave Re-admission off: No hospitalization switch change is made.
- Leave Admit Source unselected: No source is chosen here.
- Leave Diet Preference unselected: This form value stays empty.
- Leave Add Forms untouched: No additional form is part of the status update.
- Choose Cancel untouched: The actual leave confirmation follows.
Native unsaved-changes confirmation after untouched update Cancel
Native macOS confirmation dialog, shown in its original proportions.
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 b3421f8ef6e6f1186996558ac3a1ca77dd1a2a36d01ab6d06fe55433b8366181
- Read the unsaved-changes confirmation: This actual warning appeared after an untouched Update Cancel.
- Read Cancel alternative: Cancel would stay in the form; it was not chosen in this dialog.
- Choose OK to leave: The observed OK dismisses the untouched form without submitting.
4. Verify the encounter after leaving
The form closes and the Overview still shows In Progress, Emergency, Routine and the same start time. The older Ambulatory encounter remains separate. Cancel did not save a status update.
Own unchanged update cancel return
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 4554b61d47184263a9043a261d65b116fbf5b3734347eb99054c769320a89cf5
- Verify In Progress after leaving: The native confirmation returned to the same saved status.
- Reopen Update Encounter: The next step reads actual update options.
5. Reopen Update Encounter and read the six status options
Choose Update Encounter again and open Encounter Status. The actual menu offers Planned, In Progress, On Hold, Cancelled, Discontinued and Entered in error. Completed is not an option in this update menu, and the form does not convert the encounter class. Only On Hold is selected next in this exercise.
Own unchanged update cancel return
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 4554b61d47184263a9043a261d65b116fbf5b3734347eb99054c769320a89cf5
- Verify In Progress after leaving: The native confirmation returned to the same saved status.
- Reopen Update Encounter: The next step reads actual update options.
Own update six status options
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 cbcab24c919bdff729f0517f487a2934a1e19cbeaf48a0036133a8d177ba6cf4
- Read Planned: One of the six update options.
- Read current In Progress: The checkmark identifies the loaded status.
- Choose On Hold: Only this alternative is saved next.
- Read Cancelled: No terminal status is saved in this exercise.
- Read Discontinued: This alternative remains unused.
- Read Entered in error: This is an option in the update menu; no such update is made.
6. Select On Hold and review the unchanged fields
Choose On Hold. Recheck Routine, the empty Hospital Identifier, Re-admission off, unselected Admit Source and Diet Preference. Leave Mark for discharge and Add Forms untouched. Only this status change is intended.
Own update six status options
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 cbcab24c919bdff729f0517f487a2934a1e19cbeaf48a0036133a8d177ba6cf4
- Read Planned: One of the six update options.
- Read current In Progress: The checkmark identifies the loaded status.
- Choose On Hold: Only this alternative is saved next.
- Read Cancelled: No terminal status is saved in this exercise.
- Read Discontinued: This alternative remains unused.
- Read Entered in error: This is an option in the update menu; no such update is made.
Own on hold reviewed before submit
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 b08c173875cd2ed32d8552b8f2e2a827c4cafd5ff189a9e9f0e1d868ab83a97f
- Review On Hold before Submit: Only the status has been changed.
- Recheck unchanged Routine: The priority is retained.
- Choose Submit once: Save the reviewed On Hold update only.
7. Submit the On Hold update once
Choose Submit once and wait for the settled Overview. Verify On Hold in the chosen encounter and Encounter Details, with Emergency, Routine, the same displayed start and ongoing end retained. The screenshot shows the completed status change, not an unsaved form selection.
Own on hold reviewed before submit
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 b08c173875cd2ed32d8552b8f2e2a827c4cafd5ff189a9e9f0e1d868ab83a97f
- Review On Hold before Submit: Only the status has been changed.
- Recheck unchanged Routine: The priority is retained.
- Choose Submit once: Save the reviewed On Hold update only.
Own on hold saved overview
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 21ba87fefd5a7aabaab975bc46e8ae538e208fbbbddf91a6d79ff26bcad3fc0c
- Verify saved On Hold: The selected encounter displays the saved pause state.
- Verify Emergency remains: Status did not change the encounter class.
- Verify the same start: The original local minute display remains.
- Locate Update Encounter: Reopen this editor only for the later return to In Progress.
8. Read the board’s changed scope
Use the sidebar Emergency board link. The dedicated On Hold encounter is absent from this In Progress board, while existing synthetic rows remain. This is a status-based view change; it is not evidence of deletion, discharge or completion.
On hold overview emergency navigation
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 09e97f8fc294f17c7dff732b838eb550a00003e5a6c4e1880d1694434ab9761f
- Choose Emergency board: The sidebar link opens the narrower In Progress view.
- Read the chosen On Hold state: Only visible header/navigation are taught from this expanded-sidebar frame.
On hold absent from emergency board
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 b3ba9b11a2b827bc37cf7cc8d06efa7c748290159be3d876ebeade04d7972b57
- Read the unchanged configuration warning: No triage setup was changed.
- Compare the three remaining synthetic rows: The dedicated On Hold row is absent from this board.
- Choose Emergency Encounters: Open the broader encounter list to find the retained record.
9. Find the retained record in Emergency Encounters
Choose Emergency Encounters in the sidebar. The list’s Date Is on Today filter is visible, and the same synthetic encounter appears On Hold with Emergency, Routine and 20 October 02:00 AM. The list therefore serves a different purpose from the board.
On hold absent from emergency board
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 b3ba9b11a2b827bc37cf7cc8d06efa7c748290159be3d876ebeade04d7972b57
- Read the unchanged configuration warning: No triage setup was changed.
- Compare the three remaining synthetic rows: The dedicated On Hold row is absent from this board.
- Choose Emergency Encounters: Open the broader encounter list to find the retained record.
On hold retained emergency encounters today
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 12c57def033e6bad62bd70b698c79d18dd28de70915724f81e2a004ba1908b18
- Read the patient-name search control: This search was not used in the finite example.
- Read Today date filter: The currently visible date scope is Today.
- Read retained On Hold: The dedicated encounter remains saved in the list.
- Choose Filter: Open the available filter categories.
- Locate View Encounter: Use the matched card to return to its saved detail.
10. Open the list Filter menu and choose Status
Choose Filter, then Status. The menu also provides Priority, Department, Care Team, Tags and Date filter categories. Those other categories were read but not configured in this exercise. Read-only list filtering does not update the encounter’s status.
Encounter list filter menu
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 e88bb2a649ad64825e030982ec1c8332ac79883a180ac511bb9a4bdaa5eb2ab1
- Choose Status filter: This filters the list without changing the encounter.
- Read Priority category: Other filter categories were not configured here.
- Read Department category: This is a read filter, not a department assignment.
- Read Care Team category: The list can expose this filter category.
- Read Tags category: No tag filter is configured here.
- Read Date category: Today is the existing date scope.
Read-only status filter with On Hold checkbox before selection
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 9036945d20dabd1ee0a94202be8bbfe7d8eacf235edfc8676962b2d24823e25b
- Select On Hold filter checkbox: The pictured checkbox is the actual On Hold filter control before selection.
- Read Discharged read-filter option: A list filter is separate from update status choices.
- Read Completed read-filter option: This label does not make Completed an update-editor option.
11. Filter for On Hold and open the matched encounter
Select the On Hold checkbox in the status filter, then dismiss the popover with Escape. Verify the Status is On Hold chip, Today date filter and the retained matching card. Choose that card’s View Encounter to continue. Discharged or Completed appearing in this read filter does not make them choices in the update editor.
Read-only status filter with On Hold checkbox before selection
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 9036945d20dabd1ee0a94202be8bbfe7d8eacf235edfc8676962b2d24823e25b
- Select On Hold filter checkbox: The pictured checkbox is the actual On Hold filter control before selection.
- Read Discharged read-filter option: A list filter is separate from update status choices.
- Read Completed read-filter option: This label does not make Completed an update-editor option.
On hold filtered retained own encounter
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 e49eadd5b895df41380662a7ceb41fc20062a8001a540155ab9a0872b5af949c
- Verify Status is On Hold chip: The selected read filter is now applied.
- Verify Today date filter: Both filters define the visible list.
- Verify retained On Hold card: Filtering did not mutate the encounter.
- Choose View Encounter: Open only the matched dedicated encounter.
Do not confuse care state, class and discharge
On Hold paused this encounter’s displayed care state. It left the class Emergency and the end ongoing. This exercise did not use Mark for discharge, any terminal status, a location assignment or an Emergency-to-Inpatient conversion.
Own on hold saved overview
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 21ba87fefd5a7aabaab975bc46e8ae538e208fbbbddf91a6d79ff26bcad3fc0c
- Verify saved On Hold: The selected encounter displays the saved pause state.
- Verify Emergency remains: Status did not change the encounter class.
- Verify the same start: The original local minute display remains.
- Locate Update Encounter: Reopen this editor only for the later return to In Progress.
On hold filtered retained own encounter
Capture details
Captured committed 3dfb interface. One separate Emergency create, one On Hold update and one return to In Progress; no triage, discharge or change to the older Ambulatory encounter. Browser and native originals retain their actual dimensions.
Image SHA-256 e49eadd5b895df41380662a7ceb41fc20062a8001a540155ab9a0872b5af949c
- Verify Status is On Hold chip: The selected read filter is now applied.
- Verify Today date filter: Both filters define the visible list.
- Verify retained On Hold card: Filtering did not mutate the encounter.
- Choose View Encounter: Open only the matched dedicated encounter.
Source evidence
Every citation uses this exact committed version. The private source repository requires access.
- repositories/platform/mansoq-web/src/pages/Facility/emergency/EmergencyBoard.tsx:44 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
f71db4dd0fdea13df8ed5f587dfabd03648516256e75badde7077dd604cb5b6c - repositories/platform/mansoq-web/src/pages/Facility/emergency/emergencyBoardApi.ts:27 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
33e8286f0f259e49267bd02152c02769cdaad32c5764bac9c4fe4d3e031fd513 - repositories/platform/mansoq-web/src/components/ui/sidebar/facility/facility-nav.tsx:89 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
26a257157ad5c4272295c13ac63f349cc4f2ba61ede92af64e671a0eb9be5d95 - repositories/platform/mansoq-web/src/Routers/routes/FacilityRoutes.tsx:54 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
e42381cbb2ce6c5ba8cdf2203ad05e90582e6bf59c27be491a071ea5417cc534 - repositories/platform/mansoq-web/src/pages/Encounters/EncounterList.tsx:187 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
2dbe49fe5456b9161dbd171510f1614cd81a9c915ae766dd48346643d2ba61b1 - repositories/platform/mansoq-web/src/components/ui/multi-filter/filterConfigs.tsx:80 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
ff846a8365ca3b3351883b7b41bd5ecd3577d8d3c2bd422029c3d2bf0d9046a5 - repositories/platform/mansoq-web/src/components/Encounter/CreateEncounterForm.tsx:89 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
849ee40ade505c03c37ead86ac160b0c611bedf5f35da2e7dec1700288d4daca - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/EncounterQuestion.tsx:69 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
3a18093287f1975b8f3387b83216b981d9ec6e75975ccecde4544e4d4c91cb2c - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionnaireForm.tsx:834 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
ee6c2195f13e48f0896a2d3da566c2f2a67910adad08894df6b77862f9cfdeec - repositories/platform/mansoq-web/src/components/Questionnaire/structured/handlers.ts:179 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
459ade48f77316279ab2978dc7b4466cb96acb8223c61b9a1f87ca9973be7c7f - repositories/platform/mansoq-web/src/pages/Encounters/EncounterProperties.tsx:23 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
f8077c29c8df9f307e2687894d4997526efb015feb628832378c3aefd1521091 - repositories/platform/mansoq-web/src/components/Encounter/EncounterCommandDialog.tsx:248 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
361a31246fc38a50a86c8960dadb3254afcfcb7fb8eb53d7bf59c1699512683c - repositories/platform/mansoq-web/src/pages/Encounters/utils/EncounterProvider.tsx:162 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
d2609fc0452c91c20104237bf02be40ecb3bf48225011aba1f4bca2d50620d75 - repositories/platform/mansoq-web/src/pages/Encounters/utils/useEncounterProgressController.ts:19 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
d627cc15e3bad6b3bfd3fd61271787f274bfc325dc0d815e846e5d580554a265 - repositories/platform/mansoq-web/src/types/emr/encounter/encounter.ts:117 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
178ad4319d92bef379a78ed07c74d87d4c185774b3cdf989affc0f7e06ac08db - repositories/platform/mansoq-web/src/types/emr/encounter/encounterApi.ts:17 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
dc3397b24f1343b3d39f1b8ee3b01da8b3b9c16011d53427d118e6f48a674eaf - repositories/platform/mansoq-core/mansoq/emr/resources/encounter/emergency_board.py:35 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
de05aec7b2b1c2a956bde172243c221aadc9dcc4c671e0775d929664d5273cff - repositories/platform/mansoq-core/mansoq/emr/resources/facility/triage.py:15 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
a77ef80e937c9592c90051ad870c6efbf087e68dbbafc3f648b77509650f0ab4 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/encounter.py:172 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
95deb76fba78fa3426ea5eae2fa175db4a31bd3ea8a6bc70da5f80632a05d2f8 - repositories/platform/mansoq-core/mansoq/emr/resources/encounter/spec.py:44 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
c500756ac656d65d419fd08381905d7201414d63cb7910205a6eb7fd52099545 - repositories/platform/mansoq-core/mansoq/emr/resources/encounter/constants.py:4 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
4cb075b4aee3c09c6275cab553865929e2ea1bced4c5e66eb571855bcbb9f52a - repositories/platform/mansoq-core/mansoq/security/authorization/encounter.py:28 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
0e7ff8afcfb57b2371201e16ee6fac26125d6e686af66ed7edd95e49bc07de78 - repositories/platform/mansoq-core/mansoq/security/permissions/encounter.py:24 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
06b74efb763810e425de8529660f748ebd56509c729ebc532c8d115102b29218 - repositories/platform/mansoq-core/mansoq/emr/models/encounter.py:43 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
9a506456aba3ae2e3be5cfd25f32e552d3406ddd7290c0d0edef5e136782b46e - repositories/platform/mansoq-core/mansoq/emr/models/patient.py:116 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
35fa574cbdb97bd985a5561827116945e5acb81a38a93c678774ec422721e8aa - repositories/platform/mansoq-core/mansoq/emr/signals/patient/base.py:68 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
c6b7fc7fdd8af00756411343db2a4e2503c2f0166a4df0cb0e8e6bb7536b2d32 - repositories/platform/mansoq-core/mansoq/emr/signals/patient/facility_name_identifier.py:27 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
dd72b45263ce4c61a552f3d461eba4b4cd49ac295e2b31c9e2e5a84c11e26c34 - repositories/platform/mansoq-core/mansoq/emr/signals/patient/name_identifier.py:26 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
bd6bf5abfe31beeafd5bc07b9ad78b00c36506fe57dd68e929bd0e4060129821 - repositories/platform/mansoq-core/mansoq/emr/signals/patient/phone_number_identifier.py:26 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
843f7eeef76c4ee36117303644590f357f0b7d6ad2415e869dd26abe49c81f15 - repositories/platform/mansoq-core/mansoq/emr/resources/patient_identifier/default_expression_evaluator.py:48 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
0c5d676a96d65c6ca897ac6c9ae968e4497810260d1e7b4d7ce84f48621e8a31 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/location.py:558 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
646ce12d299831d9c6dba43121d80fba8a10afb85a69a26c73cae8d4a7e10a31 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/device.py:517 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
2940ecc132dd70b97cbbdadffcca205260dd65df63f16572c22b981b7bf207d7 - repositories/platform/mansoq-core/mansoq/emr/rcm/services/service_date.py:15 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
f98d08481591f0c3526a9c81dc0744267f3ba93f5abcc885379a7911d5e2aa77 - repositories/platform/mansoq-web/src/components/Questionnaire/data/StructuredFormData.tsx:3 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
434386c27b8e583e1dbd0a6f506250e7a0fb3640963c572445123bae62880f0f - repositories/platform/mansoq-core/config/settings/config.py:13 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
80e2bd16a124b5b9e80eefab7a9d5b2f20a874a8fe645b223f26cad04e6cd60a - repositories/platform/mansoq-core/config/settings/base.py:23 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
34f8931a2bae5a35f45bf6247695ee6bac09ccada3be766773861b4245817d6f - repositories/platform/mansoq-core/mansoq/emr/models/organization.py:102 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
1658c05cd0022370c55fe9d9a39d87278228141543fa3542b395119c32ee85f0 - repositories/platform/mansoq-core/mansoq/emr/models/location.py:12 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
3cafb18e62f616c20adc01ba2d5f9f11c4dd2f79451fa02e9b0ee1f2b9587a83 - repositories/platform/mansoq-core/mansoq/emr/models/device.py:7 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
9f9e3b431230d969391ac50d204d36b45eeca895fcd9423cb256974f5f7540f0 - repositories/platform/mansoq-core/mansoq/emr/resources/permissions.py:30 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
6822429d64e1f5a5c4cf7bdf37cb401e2f270d89d3b105d075ac42c6bce70f3e - repositories/platform/mansoq-core/mansoq/emr/resources/facility/spec.py:28 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
33c04d305762ea2f0f89dd6499544701aef27241e46874085f6b9c0973acbc9d - repositories/platform/mansoq-core/mansoq/emr/resources/base.py:82 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
bc406c723888997dd99fc408cb3c5dec51fb0b54d10272ca31bfd8c98c893229 - repositories/platform/mansoq-core/mansoq/facility/models/facility.py:155 ·
3dfb7c9f519fb5b4cd4452439f3c12346bf58319Source file checksum
64d598b63209caefad63c76e14d5010ba6838b9fd2cb5deca345d065a7e25ca3














