-
Notifications
You must be signed in to change notification settings - Fork 1
Add detailed query for discharged but incomplete IP encounters at SSMM #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 2 commits
cf54b03
529d7cb
4b61520
c2d7eba
f8efe04
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| ````markdown | ||
| # Discharged but Incomplete IP Encounters - SSMM | ||
|
|
||
| > IP encounters that were marked as discharged more than a day ago but are still not marked as completed | ||
| ## Purpose | ||
|
|
||
| Identifies in-patient (`encounter_class = 'imp'`) encounters at SSMM whose status history shows a `discharged` event more than 1 day ago, yet the encounter's current `status` is **not** `completed`. | ||
|
|
||
| ## Parameters | ||
|
|
||
| *This query has no parameters.* | ||
|
|
||
| --- | ||
|
|
||
| ## Query | ||
|
|
||
| ```sql | ||
| WITH first_discharged AS ( | ||
| SELECT DISTINCT ON (e.id) | ||
| e.id AS encounter_id, | ||
| e.status AS current_status, | ||
| (discharged_status->>'moved_at')::timestamp + INTERVAL '5 hours 30 minutes' AS discharged_datetime | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. use at timezone |
||
| FROM emr_encounter e | ||
| CROSS JOIN LATERAL jsonb_array_elements(e.status_history->'history') AS discharged_status | ||
| WHERE e.encounter_class = 'imp' | ||
| AND e.deleted = FALSE | ||
|
sonzsara marked this conversation as resolved.
Outdated
|
||
| AND discharged_status->>'status' = 'discharged' | ||
| AND e.status != 'completed' | ||
| ORDER BY e.id, (discharged_status->>'moved_at')::timestamp DESC | ||
| ), | ||
|
|
||
| latest_bed AS ( | ||
| SELECT DISTINCT ON (fle.encounter_id) | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So here you are looking at all historical encounters, which is unnecessary given you are only interested in a small subset. go for a left lateral join and join this query to first_discharged's id (encounter id). |
||
| fle.encounter_id, | ||
| fl.name AS bed_name, | ||
| fle.created_date AS bed_assigned_date | ||
| FROM emr_facilitylocationencounter fle | ||
| JOIN emr_facilitylocation fl ON fle.location_id = fl.id | ||
| WHERE fl.form = 'bd' | ||
| AND fl.root_location_id != 300 | ||
| ORDER BY fle.encounter_id, fle.created_date DESC | ||
| ) | ||
|
|
||
| SELECT | ||
| p.name AS patient_name, | ||
| pi.value AS ssmm_id, | ||
| fd.discharged_datetime, | ||
| fd.current_status, | ||
| lb.bed_name AS latest_bed, | ||
| lb.bed_assigned_date | ||
| FROM first_discharged fd | ||
| JOIN emr_encounter e ON fd.encounter_id = e.id | ||
| JOIN emr_patient p ON e.patient_id = p.id | ||
| LEFT JOIN emr_patientidentifier pi ON p.id = pi.patient_id AND pi.config_id = 21 | ||
| JOIN latest_bed lb ON e.id = lb.encounter_id | ||
| WHERE fd.discharged_datetime < CURRENT_TIMESTAMP - INTERVAL '1 day' | ||
| ORDER BY p.id, fd.discharged_datetime DESC, p.name; | ||
| ``` | ||
|
|
||
|
|
||
| ## Notes | ||
|
|
||
| - **Hardcoded values:** | ||
| - `pi.config_id = 21` — SSMM patient identifier configuration. | ||
| - `fl.root_location_id != 300` — excludes fake beds. | ||
| - `fl.form = 'bd'` — only bed-type facility locations. | ||
| - This query has no Metabase parameters; the date threshold is fixed at "more than 1 day ago". | ||
|
|
||
| *Last updated: 2026-05-04* | ||
|
|
||
| ```` | ||
Uh oh!
There was an error while loading. Please reload this page.