Skip to content

[bot] Fast-forward for 26.3.14#711

Merged
github-actions[bot] merged 2 commits into
release26.3from
26.3_ff_bot_26.3.14
Jun 21, 2026
Merged

[bot] Fast-forward for 26.3.14#711
github-actions[bot] merged 2 commits into
release26.3from
26.3_ff_bot_26.3.14

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Generated automatically.
Approve all matching PRs simultaneously.
Approval will trigger automatic merge.
View all PRs: https://internal.labkey.com/Scrumtime/Backlog/harvest-gitOpenPullRequests.view?branch=26.3_ff_bot_26.3.14

…/Score editor (#706)

## Rationale

Adds Selenium coverage for the new category-dependent Observation/Score
editor in the clinical observations bulk edit dialog, introduced in the
related ehrModules PR.

## Related Pull Requests

- LabKey/ehrModules#1145

## Changes

- New `testObservationBulkEdit` in `NIRC_EHRTest` that bulk-edits
observation rows and verifies the Observation/Score editor is rebuilt
per the selected Category (lookup combo for Appetite, free text for
Mass), stays enabled across category changes, clears stale values, and
applies the submitted values to every selected row.
#### Rationale

When a clinical observation is entered from the observation schedule and
multiple orders match on category and scheduled date/time, an entry is
created in clinical_observations for each matching order. Previously the
duplicate entries reused the originating order's existing schedule task
id, so the entered observations were tied back to the schedule order
tasks instead of a task representing the recording session. This change
groups the entries by their originating order's taskid and assigns one
task per group.

#### Related Pull Requests

* N/A

#### Changes

* NIRC_EHRTriggerHelper.handleScheduledObservations now groups scheduled
observation entries by their originating order's taskid: the first order
group reuses the form's own task and each additional distinct order
group gets a freshly created task cloned from the form task, so no
order's existing schedule task id is reused and the form task is never
left empty.
* Added resolveGroupTaskId and createTaskFromForm helpers plus a
per-batch grouping map that is cleared from the clinical_observations
onInit trigger.
* clinical_observations.js sets the triggering row's taskid to the
resolved group task.
* Added the caseId/problemCategory column to the clinical_observations
default view.
@github-actions github-actions Bot merged commit d98c54d into release26.3 Jun 21, 2026
15 checks passed
@github-actions github-actions Bot deleted the 26.3_ff_bot_26.3.14 branch June 21, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants