Convention for patients "still in hospital"

未关闭
#698 5 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@clairblacketer 已经在做这个了。

开始于 2024年5月2日。

评估

这个 Issue 还没有评估数据。

描述

Proposal

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_datetime User 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_id and visit_detail.discharged_to_concept_id ETL 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)
主要语言
HTML
星标
1.1k
派生
513
平均合并
8 天 3 小时
30 天内合并 PR
4

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OHDSI/CommonDataModel 的其他 Issue

查看 OHDSI/CommonDataModel 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。