MANSOQ Nursing observations · VERSION 96ca7318
Record a distinct replacement and verify retained history
Save a separate fictional replacement observation, retain the corrected source response and inspect both derived values. This exact-source lesson preserves the open correction-propagation limitation rather than presenting the replacement as a completed clinical correction.
Nurse
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
1Observe the distinct replacement and retained original value
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Observations shows separate74 at 05:39 and original 72 at 05:35 with distinct notes and the same Nurse actor. The earlier source response is Entered in Error, but its linked observation remains Final in this 96ca source. The replacement therefore does not by itself remove the earlier value from observations.
Image SHA-256 20e3884a6275768ec2d9c77b0f776ae8ed59b31f6a799935c2067d3c8f76a705
- Recheck Pulse plot: Verify the plot consequence independently instead of assuming the source correction removed a point.
1Finish on the saved two-record observation history
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The fully loaded Pulse Full History shows both74 at 05:39 and 72 at 05:35 with distinct notes. This final saved checkpoint preserves the original fourteen administration records, four requests, seven condition records and all encounters. The linked source-response error does not retract its derived observation in this source version; that remains an explicit product finding.
Image SHA-256 e052e0d2a1839bf7a7a5f3dc95e7008f9235b75c85bb17b25de25424e7e38134
- Observations: Return to the saved selected-encounter observation list after reviewing the retained history.
10 of 10 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.
Before you begin
- Complete the source-response correction review first. The prior synthetic 72 response is Entered in Error, but its linked observation remains Final on exact 96ca7318. Preserve that record and its original effective time; this demonstration does not overwrite it.
1Recorded release 96ca7318 · 2026-10-19T02:38:28.434Z · 1728 × 921 Verify the retained Entered in Error response
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The source response now visibly displays Entered in Error and retains72 and its author/time. Ordinary Nurse/Doctor readbacks confirm response status entered_in_error. The linked observation remains Final with72 in this committed source; the response correction must not be taught as automatically removing its derived observation.
Image SHA-256
d30189dcce286f11986ad76ece4119490e41b73fe2856487ea5093470964300a- Check linked observations: Verify the derived observation separately after marking the source response in error.
1Recorded release 96ca7318 · 2026-10-19T02:38:41.563Z · 1728 × 921 Recognize the retained derived observation after response correction
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Freshly reloaded Observations still displays72 at 05:35 with the Nurse and training note even though its source response is Entered in Error. Ordinary role readbacks establish the linked observation remains Final. This observed limitation means source-response correction alone does not qualify the observation/plot as clinically corrected.
Image SHA-256
2d219039d35668743786e9a0b58f315ff38263e6c8a1a41e03c4fcccbe793774- Return to Overview: Open the normal form entry point for a distinct replacement observation; this does not overwrite the retained derived record.
- Use the existing authorized Nurse, intended ongoing encounter and same configured Heart Rate form. The new 74 is fictional software data with a note identifying the earlier source response. It is not a physical measurement, a recommendation or a facility-approved correction workaround.
1Recorded release 96ca7318 · 2026-10-19T02:39:05.636Z · 1728 × 921 Identify the distinct replacement entry explicitly
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. A newly opened form contains simulated 74 and an optional note identifying the earlier source response correction. This does not edit or erase the first observation. The note explicitly records the current-source retained 72 limitation and fictional software-only context.
Image SHA-256
0e1c6c410c5bc22e615475c5ee3ff73fea9611716d83abe6cb060a856a5d74e9- Replacement context note: Identify why this is a distinct replacement entry and which source response was corrected.
12Recorded release 96ca7318 · 2026-10-19T02:39:05.906Z · 1728 × 921 Submit the distinct replacement observation
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The new form is reviewed with fictional74 and fixed /min unit. Submit creates a separate response/observation UUID at the new server effective time. It does not overwrite, remove or amend the earlier72 observation.
Image SHA-256
d61173a812a5adbb1d288eb814c2d7d81a45b246da82df48cbbe11a9e8010474- Submit distinct replacement: Save the reviewed new fictional entry once, retaining the earlier source record.
- Replacement value 74: This is a synthetic replacement example, not a real measurement.
1. Open a new form and identify the replacement explicitly
Return to Overview, choose Forms and the same Synthetic Training — Heart Rate form. Enter the distinct simulated value 74. Open the optional note control and identify that this is a separate replacement after the earlier source response was marked Entered in Error. Keep the note explicit that the original derived 72 remains in this version and that no real measurement occurred.
12Open Forms on the intended ongoing encounter
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Ordinary existing Nurse on exact committed 96ca. The existing fictional patient and current Inpatient encounter are confirmed. No prior observations exist for this selected encounter; all prior diagnoses, symptoms, administrations and requests remain unchanged. The configured synthetic Heart Rate form will be used through normal UI.
Image SHA-256 68ff09b207f7a9eb41760d9a7c4f7a1eccf3ce9e3241a89a5d3e650ecbf2e5dd
- Forms: Open the encounter form collection after confirming the intended patient and chosen encounter.
- Chosen encounter context: This is the ongoing Inpatient encounter for the fictional software exercise.
1Select the configured synthetic Heart Rate form
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Actual configured encounter form collection. The existing synthetic Heart Rate form uses the installed LOINC 8867-4 code and UCUM /min unit; other listed forms are not submitted in this exercise.
Image SHA-256 74c936309433b427639c57ea4446330a27a143d9c14c4be30a7a2c8f68998f00
- Synthetic Training — Heart Rate: Choose the configured synthetic observation form, rather than a different clinical template.
1Identify the distinct replacement entry explicitly
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. A newly opened form contains simulated 74 and an optional note identifying the earlier source response correction. This does not edit or erase the first observation. The note explicitly records the current-source retained 72 limitation and fictional software-only context.
Image SHA-256 0e1c6c410c5bc22e615475c5ee3ff73fea9611716d83abe6cb060a856a5d74e9
- Replacement context note: Identify why this is a distinct replacement entry and which source response was corrected.
2. Save the distinct replacement once
Close the note with Escape, review the patient, 74 and fixed /min unit, then choose Submit once. This creates a new response and observation with a new server effective time. It does not overwrite, amend or delete the original response or derived observation.
1Identify the distinct replacement entry explicitly
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. A newly opened form contains simulated 74 and an optional note identifying the earlier source response correction. This does not edit or erase the first observation. The note explicitly records the current-source retained 72 limitation and fictional software-only context.
Image SHA-256 0e1c6c410c5bc22e615475c5ee3ff73fea9611716d83abe6cb060a856a5d74e9
- Replacement context note: Identify why this is a distinct replacement entry and which source response was corrected.
12Submit the distinct replacement observation
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The new form is reviewed with fictional74 and fixed /min unit. Submit creates a separate response/observation UUID at the new server effective time. It does not overwrite, remove or amend the earlier72 observation.
Image SHA-256 d61173a812a5adbb1d288eb814c2d7d81a45b246da82df48cbbe11a9e8010474
- Submit distinct replacement: Save the reviewed new fictional entry once, retaining the earlier source record.
- Replacement value 74: This is a synthetic replacement example, not a real measurement.
3. Verify new and corrected response identities
Open Responses. The new 74 response is filed by Nurse at 05:39 AM and has a distinct UUID, while the earlier 05:35 response remains below it labelled Entered in Error. Independent role reads confirm the new response is Completed. The earlier corrected card may be collapsed, but it is retained.
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
4. Check both observations and plot consequences
Choose Observations. Both new 74 at 05:39 and original 72 at 05:35 remain visible with their distinct notes. Choose Plots and inspect the Pulse graph: it still contains both points. In this source both observations are Final, so the replacement does not make the earlier point disappear or establish a clinically corrected trend.
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
1Observe the distinct replacement and retained original value
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Observations shows separate74 at 05:39 and original 72 at 05:35 with distinct notes and the same Nurse actor. The earlier source response is Entered in Error, but its linked observation remains Final in this 96ca source. The replacement therefore does not by itself remove the earlier value from observations.
Image SHA-256 20e3884a6275768ec2d9c77b0f776ae8ed59b31f6a799935c2067d3c8f76a705
- Recheck Pulse plot: Verify the plot consequence independently instead of assuming the source correction removed a point.
1Verify both retained points in the Pulse graph
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. After replacement, the actual Pulse graph still contains both original 72 at 05:35 and new74 at 05:39. This is an observed correction propagation limitation, not two independently valid physical measurements or proof of a clinically corrected trend. No original clinical record was changed in this viewing step.
Image SHA-256 8d84f1747e69af6bbf493767195970c2bbb1d76a8bbd700312f4dea53a523c1a
- Pulse Full History: Inspect both retained observation rows and times, including the original source-error consequence.
5. Finish by reviewing the retained history
On the Pulse card choose Full History. Confirm both rows, their times, values and Nurse entered-by context. The Code column uses the configured Pulse label; full note text is available from the response rather than these clipped table cells. Independent Nurse/Doctor list and analysis reads each return both observations. Existing seven condition records (four diagnoses and three symptoms), fourteen administrations, four requests and current and three prior encounters were unchanged by this bounded exercise.
1Verify both retained points in the Pulse graph
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. After replacement, the actual Pulse graph still contains both original 72 at 05:35 and new74 at 05:39. This is an observed correction propagation limitation, not two independently valid physical measurements or proof of a clinically corrected trend. No original clinical record was changed in this viewing step.
Image SHA-256 8d84f1747e69af6bbf493767195970c2bbb1d76a8bbd700312f4dea53a523c1a
- Pulse Full History: Inspect both retained observation rows and times, including the original source-error consequence.
1Finish on the saved two-record observation history
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The fully loaded Pulse Full History shows both74 at 05:39 and 72 at 05:35 with distinct notes. This final saved checkpoint preserves the original fourteen administration records, four requests, seven condition records and all encounters. The linked source-response error does not retract its derived observation in this source version; that remains an explicit product finding.
Image SHA-256 e052e0d2a1839bf7a7a5f3dc95e7008f9235b75c85bb17b25de25424e7e38134
- Observations: Return to the saved selected-encounter observation list after reviewing the retained history.
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
Two new records do not erase a correction limitation
The original response and replacement have distinct identities, and both linked observations remain in this exact version. The original source-response error did not retract its derived observation. This lesson documents the actual software boundary; it does not claim an automatic replacement relationship, an amended observation or a completed clinical correction. That remains a separately tracked product finding.
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
1Observe the distinct replacement and retained original value
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Observations shows separate74 at 05:39 and original 72 at 05:35 with distinct notes and the same Nurse actor. The earlier source response is Entered in Error, but its linked observation remains Final in this 96ca source. The replacement therefore does not by itself remove the earlier value from observations.
Image SHA-256 20e3884a6275768ec2d9c77b0f776ae8ed59b31f6a799935c2067d3c8f76a705
- Recheck Pulse plot: Verify the plot consequence independently instead of assuming the source correction removed a point.
1Verify both retained points in the Pulse graph
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. After replacement, the actual Pulse graph still contains both original 72 at 05:35 and new74 at 05:39. This is an observed correction propagation limitation, not two independently valid physical measurements or proof of a clinically corrected trend. No original clinical record was changed in this viewing step.
Image SHA-256 8d84f1747e69af6bbf493767195970c2bbb1d76a8bbd700312f4dea53a523c1a
- Pulse Full History: Inspect both retained observation rows and times, including the original source-error consequence.
1Finish on the saved two-record observation history
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The fully loaded Pulse Full History shows both74 at 05:39 and 72 at 05:35 with distinct notes. This final saved checkpoint preserves the original fourteen administration records, four requests, seven condition records and all encounters. The linked source-response error does not retract its derived observation in this source version; that remains an explicit product finding.
Image SHA-256 e052e0d2a1839bf7a7a5f3dc95e7008f9235b75c85bb17b25de25424e7e38134
- Observations: Return to the saved selected-encounter observation list after reviewing the retained history.
Observed scope
Only the two explicitly fictional observations were added through normal Nurse UI, and only the first new source response was marked Entered in Error. No configuration, permission, clock, original diagnosis, symptom, administration, request or prior encounter was changed. No new screenshot or article asserts that a later repair is already present on this committed source.
1Identify the distinct replacement entry explicitly
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. A newly opened form contains simulated 74 and an optional note identifying the earlier source response correction. This does not edit or erase the first observation. The note explicitly records the current-source retained 72 limitation and fictional software-only context.
Image SHA-256 0e1c6c410c5bc22e615475c5ee3ff73fea9611716d83abe6cb060a856a5d74e9
- Replacement context note: Identify why this is a distinct replacement entry and which source response was corrected.
12Submit the distinct replacement observation
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The new form is reviewed with fictional74 and fixed /min unit. Submit creates a separate response/observation UUID at the new server effective time. It does not overwrite, remove or amend the earlier72 observation.
Image SHA-256 d61173a812a5adbb1d288eb814c2d7d81a45b246da82df48cbbe11a9e8010474
- Submit distinct replacement: Save the reviewed new fictional entry once, retaining the earlier source record.
- Replacement value 74: This is a synthetic replacement example, not a real measurement.
1Verify the new response alongside the retained error record
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. Responses now shows the distinct new74 response filed by Nurse at 05:39 AM and the retained earlier response labelled Entered in Error. The new response UUID is c5bbde6f-7a0e-423c-9444-8bebd9174297. The replacement does not overwrite the earlier response or derived observation.
Image SHA-256 f231da87fb19966b0da512043aad335f9f62cc339414f58fd93496e81ac12ce5
- Compare derived observations: Check both saved observation values and times after the distinct replacement entry.
1Finish on the saved two-record observation history
Capture details
Exact committed release 96ca7318 on an isolated nonproduction clone, using an existing Nurse and fictional Polyclinic inpatient case. The synthetic patient name retains an earlier release label. The fully loaded Pulse Full History shows both74 at 05:39 and 72 at 05:35 with distinct notes. This final saved checkpoint preserves the original fourteen administration records, four requests, seven condition records and all encounters. The linked source-response error does not retract its derived observation in this source version; that remains an explicit product finding.
Image SHA-256 e052e0d2a1839bf7a7a5f3dc95e7008f9235b75c85bb17b25de25424e7e38134
- Observations: Return to the saved selected-encounter observation list after reviewing the retained history.
Source evidence
Every citation uses this exact committed version. The private source repository requires access.
- repositories/platform/mansoq-web/src/components/Questionnaire/QuestionnaireForm.tsx:740 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
e6e48112c033602b02815eb3685119882242f22b14975dffc3feba7d96e20923 - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionnaireForm.tsx:857 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
e6e48112c033602b02815eb3685119882242f22b14975dffc3feba7d96e20923 - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/NumberQuestion.tsx:22 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
fd8183d93ed6c65e651dfc6b790c5ebc740fceef5cf6d0d5dc3d107f465b8dab - repositories/platform/mansoq-web/src/components/Questionnaire/QuestionRenderer.tsx:55 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
9d82262b8344fca498cf3303b31faed7e0174773e3d5405da21000df84ba206a - repositories/platform/mansoq-core/mansoq/emr/resources/questionnaire/utils.py:354 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
8425858d2179a66f482f38a3fd7f0fc0dcb70a4bcd85450fe7ce748b3081826c - repositories/platform/mansoq-core/mansoq/emr/resources/questionnaire_response/spec.py:24 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
e1aff7243f7557d61fa33271652df53ce0fe0220505abdf3f5d20cdb5fa1a555 - repositories/platform/mansoq-web/src/pages/Encounters/tabs/observations.tsx:76 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
652b6beefcdf45cd3b2813248c1d020583d7593fd0791819abd3fdc4f431f949 - repositories/platform/mansoq-web/src/pages/Encounters/tabs/observations.tsx:140 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
652b6beefcdf45cd3b2813248c1d020583d7593fd0791819abd3fdc4f431f949 - repositories/platform/mansoq-web/src/components/Common/Charts/ObservationChart.tsx:118 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
dcfb2e78c7a32f179608af2bfbfc447914ec0768636453b97be6e9d04fd272d8 - repositories/platform/mansoq-web/src/components/Common/Charts/ObservationHistoryTable.tsx:70 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
03fc5ded1d44bab0f10b9e2c404913b2b280599a615b09e63b127b8459953745 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/observation.py:45 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
9bf1491928c5879124ddc218e334865fd6be8c0906353b503552933d65c55555 - repositories/platform/mansoq-web/src/components/Facility/ConsultationDetails/QuestionnaireResponsesList.tsx:271 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
c4c607439b9c4bbeec4d54915d50a02aa12c67d43993011dc2365e19ff28c9c7 - repositories/platform/mansoq-web/src/components/Facility/ConsultationDetails/QuestionnaireResponsesList.tsx:555 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
c4c607439b9c4bbeec4d54915d50a02aa12c67d43993011dc2365e19ff28c9c7 - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/questionnaire_response.py:38 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
e91f52d5191853851af09e05b8eb373b9645dce489043cf5821b7b5169a84e42 - repositories/platform/mansoq-core/mansoq/emr/resources/questionnaire_response/spec.py:48 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
e1aff7243f7557d61fa33271652df53ce0fe0220505abdf3f5d20cdb5fa1a555 - repositories/platform/mansoq-core/config/settings/config.py:323 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
80e2bd16a124b5b9e80eefab7a9d5b2f20a874a8fe645b223f26cad04e6cd60a - repositories/platform/mansoq-core/mansoq/emr/api/viewsets/observation.py:45 ·
96ca7318eb2b93f5fa477908a1543075e0d1f056Source file checksum
9bf1491928c5879124ddc218e334865fd6be8c0906353b503552933d65c55555