Skip to content

[FIX] Transferred patient has placement task stuck as scheduled#118

Merged
DaeronAlagos merged 1 commit intoremove-custom-frequencyfrom
16865
Nov 20, 2020
Merged

[FIX] Transferred patient has placement task stuck as scheduled#118
DaeronAlagos merged 1 commit intoremove-custom-frequencyfrom
16865

Conversation

@DaeronAlagos
Copy link
Copy Markdown
Contributor

When a A02 HL7 message is sent (to transfer a patient between wards), the existing placement task is cancelled (from state of scheduled) and a new one is created with a state of scheduled.

When a A03 HL7 message is sent (to discharge a patient), the scheduled placement task remains in a state of scheduled and causes an error if the same patient is admitted again.

As bed assignment is no longer used, the placement task should be processed as completed as soon as it is created and the placement task use the ward as the location.

Fixes #16865

When a A02 HL7 message is sent (to transfer a patient between wards), the existing placement task is cancelled (from state of scheduled) and a new one is created with a state of scheduled.

When a A03 HL7 message is sent (to discharge a patient), the scheduled placement task remains in a state of scheduled and causes an error if the same patient is admitted again.

As bed assignment is no longer used, the placement task should be processed as completed as soon as it is created and the placement task use the ward as the location.

Fixes #16865
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.

2 participants