Convention for patients "still in hospital"
@clairblacketer ya está trabajando en esto.
Desde el 2/5/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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)
- Lenguaje dominante
- HTML
- Estrellas
- 1.1k
- Forks
- 513
- Merge medio
- 8 d 3 h
- PR fusionados (30 d)
- 4
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OHDSI/CommonDataModel
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
OHDSI/CommonDataModel#802 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
OHDSI/CommonDataModel#799 ·
-
fix: mark cohort_definition_id as primary key in cohort_definition table for v5.3 and v5.4Posiblemente ocupada @rtmalikian la tomó hace 137 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
OHDSI/CommonDataModel#787 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
OHDSI/CommonDataModel#784 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
OHDSI/CommonDataModel#823 ·