已在最新版本中棄用-->
自O(shè)MOP CDM v6.0起这难,DEATH表已被棄用遭殉,有利于在CONDITION_OCCURRENCE表中存儲死因,任何與死亡相關(guān)的觀察結(jié)果都存儲在OBSERVATION表,以及唯一的死亡日期將被并存儲在PERSON表。
“死亡”域包含有關(guān)人員死亡的方式和時間的臨床事件七扰。人員可以在源系統(tǒng)中包含有關(guān)死亡證據(jù)的信息,例如:
- 索賠中的條件代碼或索賠的詳細(xì)信息
- 入選健康計劃的狀況
- EHR數(shù)據(jù)中的顯式記錄
As of OMOP CDM v6.0, the DEATH table has been deprecated in favor of storing the cause of death in the CONDITION_OCCURRENCE table, any observations relating to death stored in the OBSERVATION table, and a singular death date will be chosen and stored in the PERSON table.
The 'Death' domain contains the clinical events surrounding how and when a Person dies. A Person can have information in the source system containing evidence about the Death, such as:
- Condition Code in the Header or Detail information of claims
- Status of enrollment into a health plan
- Explicit record in EHR data
共識
No. | Convention Description | 共識 |
---|---|---|
1 | Living patients should not have a value in PERSON.DEATH_DATETIME, nor should they have any records relating to death either in the CONDITION_OCCURRENCE or OBSERVATION tables | 活體患者不應(yīng)該在PERSON.DEATH_DATETIME中有價值陪白,也不應(yīng)該在CONDITION_OCCURRENCE或OBSERVATION表中有任何與死亡有關(guān)的記錄 |
2 | Only one death date per individual can be used. If a patient has clinical activity (e.g. prescriptions filled, labs performed, etc) more than 60+ days after death you may want to drop the death record as it may have been falsely reported. If multiple records of death exist on multiple days you may select the death that you deem most reliable (e.g. death at discharge) or select the latest death date (THEMIS issue #6). | 每個人只能使用一個死亡日期颈走。如果患者在死亡超過60天后有臨床活動(例如處方藥,實(shí)驗(yàn)室等)咱士,您可能希望丟失死亡記錄立由,因?yàn)樗赡鼙诲e誤報告。如果多天存在多個死亡記錄司致,您可以選擇您認(rèn)為最可靠的死亡(例如出院時死亡)或選擇最新死亡日期(THEMIS問題#6)拆吆。 |
3 | If multiple death records occur, the date and the person have to be the same, but the cause can be different. Can be reported by different sources as well (THEMIS issue #5). | 如果發(fā)生多個死亡記錄聋迎,則日期和人必須相同脂矫,但原因可能不同。也可以由不同的來源報告(THEMIS問題#5)霉晕。 |
4 | If PERSON.DEATH_DATETIME cannot be precisely determined from the data, the best approximation should be used. | 如果無法從數(shù)據(jù)中精確確定PERSON.DEATH_DATETIME庭再,則應(yīng)使用最佳近似值。 |
5 | Any cause of death should be stored in the CONDITION_OCCURRENCE table, using the CONDITION_TYPE vocabulary with the DEATH_TYPE concept class. | 任何死因都應(yīng)存儲在CONDITION_OCCURRENCE表中牺堰,使用帶有DEATH_TYPE概念類的CONDITION_TYPE詞匯表拄轻。 |
6 | All observations relating to death should be stored in the OBSERVATION table, including the concept 4306655. | 與死亡有關(guān)的所有觀察都應(yīng)存儲在觀察表中,包括概念4306655伟葫。 |
7 | The DEATH_DATETIME in the PERSON table should not be used as the way to find all deathsselect * from PERSON where death_datetime is not null should not be the practiceRather, deaths should be found through the OBSERVATION table and the PERSON table is only used to determine which death date should be used in analysis | 不應(yīng)將PERSON表中的DEATH_DATETIME用作查找所有死亡的方法select * from PERSON where death_datetime is not null 不應(yīng)該是這種做法相反恨搓,應(yīng)通過OBSERVATION表找到死亡,PERSON表僅用于確定分析中應(yīng)使用哪個死亡日期 |
本系列在介紹目前世界上最適用于臨床科研+衛(wèi)生經(jīng)濟(jì)學(xué)的標(biāo)準(zhǔn)醫(yī)療大數(shù)據(jù)格式(未經(jīng)嚴(yán)謹(jǐn)考證筏养,但有相關(guān)研究發(fā)表在專業(yè)期刊上)斧抱,儼然是真實(shí)世界研究方案里面最接進(jìn)成熟的基礎(chǔ)建設(shè)方案。感興趣的介紹請移步B站觀看視頻渐溶。
OHDSI——觀察性健康醫(yī)療數(shù)據(jù)科學(xué)與信息學(xué)辉浦,是一個世界性的公益型非盈利研究聯(lián)盟,主要研究全方位醫(yī)學(xué)大數(shù)據(jù)分析的開源解決方案,旨在通過大規(guī)模數(shù)據(jù)分析和挖掘來提升臨床醫(yī)學(xué)數(shù)據(jù)價值,實(shí)現(xiàn)跨學(xué)科刽肠、跨行業(yè)的多方合作攒射。目前筒主,目前振劳,已有來自美國署驻、加拿大驾霜、澳大利亞丐黄、英國等幾十個國家地區(qū)的上百個組織機(jī)構(gòu)斋配,高校,醫(yī)院和公司企業(yè)參與了OHDSI全球協(xié)作網(wǎng)絡(luò)灌闺,如斯坦福艰争、哈佛、杜克大學(xué)醫(yī)學(xué)院桂对,強(qiáng)生甩卓、諾華、甲骨文蕉斜、IBM公司逾柿,擁有超過6億人口的臨床數(shù)據(jù)規(guī)模,累計協(xié)作研究發(fā)表了上百篇論文宅此。
我們在這里邀請國內(nèi)對相關(guān)工作感興趣机错、愿共同學(xué)習(xí)的好學(xué)人士參與到中文興趣小組,互通有無父腕,一起彌補(bǔ)跨行業(yè)弱匪、跨學(xué)科的知識積累。前期主要以對OHDSI在github上的開源工作進(jìn)行翻譯璧亮、交流萧诫、學(xué)習(xí)為主,并會對醫(yī)療大數(shù)據(jù)枝嘶、醫(yī)學(xué)統(tǒng)計學(xué)帘饶、生物信息學(xué)等學(xué)科知識建立學(xué)習(xí)互助、互督的機(jī)制群扶。有興趣的請看文檔及刻,微信群二維碼在內(nèi):OHDSI中文興趣小組共識&OHDSI介紹
OHDSI秉持開源、開放的宗旨竞阐,加快全球醫(yī)學(xué)數(shù)據(jù)研究的步伐缴饭,本文內(nèi)容原創(chuàng)來自Github(https://github.com/OHDSI/CommonDataModel/wiki),若有利益沖突馁菜,請在本頁面留言茴扁,真-侵刪。