Convention for patients "still in hospital"
@clairblacketer is already working on this.
Since May 2, 2024.
Assessment
This issue has not been assessed yet.
Description
Convention for patients "still in hospital"
CDM or THEMIS convention?
THEMIS
Table or Field level?
Field
Is this a general convention?
No
Summary of issues
- If patients are still in the hospital at the time of the ETL build, set the visit_end_date to the date of the data extract and set the discharge_to_concept_id to 32220.
Summary of answer
Author 1:
- We updated the
visit_occurrence.end_date, visit_occurrence.end_datetime, visit_detail.visit_detail_end_date, and visit_detail.visit_detail_end_datetimeUser Guide sections to direct users to set the visit_end_datetime to the date of the data extract when an inpatient visit is ongoing and the *.discharged_to_concept_id = 0. - We updated the
visit_occurrence.discharged_to_concept_idandvisit_detail.discharged_to_concept_idETL Conventions sections to notify users it is assumed a Person returns home after a Visit, therefore, there is not a standard concept_id to represent 'home' and set the discharged_to_concept_id = 0
Author 2
We should update this user guidance, as some things have changed.
Concept 32220 - Still Patient is non-standard, and the advice in the user guide for visit_end_date is to add this as the visit_type_concept_id, not discharge_concept_id.
For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 “Still patient” to identify the visit as incomplete.
This is now conflicting with our conventions for type concepts to be standard and of class 'Type Concept'.
Author 3:
- THEMIS issue and still needs consensus on how patients till in the hospital should be handled.
Related links
Other comments/notes
- Please use this section to add any other relevant notes or comments. (i.e. if links are not working, something is out of date or deprecated)
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 513
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OHDSI/CommonDataModel
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
OHDSI/CommonDataModel#802 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OHDSI/CommonDataModel#799 ·
-
fix: mark cohort_definition_id as primary key in cohort_definition table for v5.3 and v5.4Possibly taken @rtmalikian claimed this 137 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OHDSI/CommonDataModel#787 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OHDSI/CommonDataModel#784 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
OHDSI/CommonDataModel#823 ·