globaldothealth / outbreak-data

For users of G.h data: notes, timelines, sources, etc.
MIT License
0 stars 0 forks source link

How best to determine Date_confirmation and Date_death when not provided by source #9

Closed aimeehan1 closed 4 months ago

aimeehan1 commented 4 months ago

Best practice is to use the Date_report for date_confirmation/death when not explicitly reported by source. This is what we have done for mpox and other outbreaks.

Does our best practice fit Case ID17? @abhidg @julianasopko @JacqSauer

Review Case ID17: Date_report June 7 Date_report(ed) to WHO June 5 Date_hospitalized May 11 (reported as 'subsequently passed away')

According to source_I: "On 5 June 2024, an infection with an A(H5N6) virus was reported in a 41-year-old male from Fujian Province who had an onset of illness on 8 May 2024. The patient was hospitalized on 11 May with severe pneumonia and subsequently passed away. The case had exposure to backyard poultry. Samples from the close contacts and the environment tested negative and no further cases in the family of the patient were reported."

JacqSauer commented 4 months ago

@aimeehan1 it looks like the new source linked as source_I states that "Between 7 June to 13 June 2024, one new case of human infection with avian influenza A(H5N6) virus was reported to WHO in the Western Pacific Region. The case is a 41-year-old male from Fujian Province, with an onset of illness on 8 May 2024. The patient was hospitalized with severe pneumonia and the case was confirmed positive for A(H5N6) on 14 May. He subsequently passed away." All the other case information fits what we have for ID17. I would assume we then would update the confirmation date to 2024-05-14. Date of death is still hard to determine from this report

aimeehan1 commented 4 months ago

Curator agreement -- for Date_death, use Date_report.

JacqSauer commented 4 months ago

date_death and date_confirmation for cases where the sources don't explicitly give this information were updated to reflect the date of the corresponding report