opensafely / codelist-development

Repository for discussion of OpenSAFELY codelists
7 stars 4 forks source link

*DISEASE* Venous thromboembolic disease (DVT and PE) #33

Closed hmcd closed 4 years ago

hmcd commented 4 years ago

DEFINITION: Codes for venous thromboembolic disease

Variables: (1) a binary variable denoting the presence of one of the codes at any point in the patient record. (2) the earliest date of such a code.

CODE LISTS:

(1) Read 2 code list from Helen Strongman and Angel Wong combined here: DVT_PE_Strongman_Wong.xlsx

have suggested not to include (1) suspected/possible codes and (2) PEs specified as air embolism or amniotic fluid embolism as would not indicate at ongoing risk of a venous clot.

(2) SNOMED to search (3) map to CTV3 - to do (4) check and refine post mapping

FLEXIBILITY NEEDED BETWEEN STUDIES: This list doesn't include air embolism or amniotic fluid embolism - some studies of PE may wish to include these. The list includes codes for a history of DVT or PE - studies of incident DVT/PE may wish to exclude these.

EFFECTS ON COHORT SELECTION: None

POTENTIAL BIASES: None

hmcd commented 4 years ago

With apologies for the delay! Have searched SNOMED for deep vein thrombosis codes, and have a list here SNOMED_DVT.xlsx

It's got some oddly detailed codes in because some of the high level codes included, for example, haemorrhoids, so for those I had to go to the more detailed levels to keep to DVTs. I've suggested inclusion/exclusion sticking to the same principle as above of not including suspected DVT or referral to clinic. But I wasn't sure about the "enhanced services administration" codes - do they imply DVT?

Will search for PE codes next.

hmcd commented 4 years ago

SNOMED search for PE SNOMED_PE.xlsx Since we're interested in it as an indication of clotting risk, I didn't include air embolisms, fat embolisms, or amniotic fluid embolisms or suspected PE. I did assume unspecified PEs were blood clots.

So combining the lists, and dropping the codes I'd suggest not including, for mapping to CTV3 would propose: SNOMED_DVT_PE_included_only.xlsx and Readv2_DVT_PE_included_only.xlsx

hmcd commented 4 years ago

@alexwalkercebm @StatsFizz @johntaz Apologies - had a hectic fortnight but now back! This has been closed but not sure we have looked through the results of mapping to CTV3 to produce a CTV3 codelist - I can do that today or tomorrow if the Read 2/SNOMED have been mapped to CTV3- or is this now not needed?

johntaz commented 4 years ago

@hmcd The codelist has been mapped now, please could you review? CTV3_Raw_DVT_PE.xlsx

hmcd commented 4 years ago

Have annotated this version. CTV3_Raw_DVT_PE_HMcomments.xlsx

I suggested:

Include==1

Exclude==0

I have some questions for @amirmehrkar... (1) XaaBG on deep vein thrombosis care pathway. @amirmehrkar is this someone being treated for DVT, or could they just be at high risk? (2) 14A8. H/O: [thrombo-embolism] or [embolism] or [thrombosis] - I thought that as this started with 'thromboembolism' it'd be an odd code to choose to use for superficial thrombophlebitis. So I've suggested including it, but do you agree? (3) cerebral venous clots - have marked as 'c' so we have them identified. My inclination would be to see those as a separate condition. The cause may be cerebral inflammation, e.g. meningitis, whereas we're looking for history of VTE as an indication of future risk of clots. @amirmehrkar do you agree or should we be including these as venous thromboembolic disease? (4) portal vein thrombosis and mesenteric venous thrombosis - marked as 'p' (including mesenteric vein - as I think the question is the same even if it's not portal). Again, I'd be inclined to see those as a separate condition, for which the cause may be local/ liver disease e.g. HCC, rather than indicating a systemic state where the patient is at risk of DVT/PE. @amirmehrkar do you agree or should be be including these as venous thromboembolic disease?

@johntaz please note Iist still includes the codes which I'd recommend excluding, for Amir's review. Once Amir's reviewed, we'll need to actually remove the codes we don't want from the list.

amirmehrkar commented 4 years ago

Hi @hmcd @johntaz I think this one is quite tricky because by joining DVT and PE together there is a deliberate constraint put on this codelist ie that there needs to be the ability to cause a PE from the DVT, given that a PE by definition requires an antecedent event.

So, given that in mind, I think, answers to your questions:

(1) - In my mind a pathway starts with suspicion of a condition and exit from the pathway if not proven. I would remove the XaaBG and use in preference actual diagnostic codes. We ought to have a code for a "thombotic/pe" event if the entry to the pathway proved positive.

(2) - Yes I would include, although it would be worthwhile asking TPP / EMIS how often it is used; if very infrequently then probably not an issue and could be removed. Either way, I wouldnt personally have used it for superficial thrombophlebitis.

(3) - There are case reports (albeit rare) from googling that cerebral venous thrombosis has led to PEs; therefore, based on the constraint implied I would include them.

(4) - Again, based on the constraint implied, I would remove these because you cannot get a PE (anatomically) from a portal vein or mesenteric venous thrombosis. (but you can from the hepatic vein). However, given infection is a cause of mesenteric vein thrombosis, and it can be lethal, I could consider including it..... I think one way to manage this is to identify this as a subset and simply justify why/why not included. I think both reasons are valid.

(5) - The other issue I am pondering is whether inclusion of pregnancy is important? Would pregnancy not be a confounder - ie should these codes simply be removed, unless there is a specific study on pregnant women and C19 risks?

My comments - rows with no comments == agree with Helen. CTV3_Raw_DVT_PE_HMcomments AMcomments.xlsx

hmcd commented 4 years ago

Thank you Amir!

Your suggestions on (1) and (2) sound good to me.

For (3) and (4) I don't have a strong view either way, and I would think so long as we're consistent and the definition is also clear to patients, that either approach is reasonable.

There are perhaps two ways of looking at how the DVT codes should relate to PE risk, depending on time frames:

(5) For pregnancy would someone who had a history of a DVT/PE in pregnancy be likely to be at increased risk of PE if they contract COVID? If so, I'd be inclined to keep them in the codelist and simply ask about 'DVT/PE ever' without specifying that it was outside of pregnancy. (As an aside it might not be possible to reliably exclude DVT/PE in pregnancy, if not all episodes of DVT/PE in pregnancy specify pregnancy in the code - though I'd have expected that most would?) I don't think the risk tool will be designed to apply to women who are currently pregnant - it might be something to add to the caveats, @StatsFizz and @johntaz ?

Another consideration is how we will ask about this risk factor for the risk prediction tool. There's a pragmatic argument that asking about 'clots in legs or lungs' might be clearer than trying explain 'clots in veins but not arteries' for cerebral venous thrombosis but not stroke - in which case we might not want to include the cerebral, portal and mesenteric venous thromboses.

hmcd commented 4 years ago

Discussed today with @amirmehrkar @laurietomlinson and @johntaz

Summary of discussion The rationale for including DVT/PE in the risk prediction model, is that among individuals with a COVID-19 infection, an individual with a history of venous thrombosis may be at higher risk than the general population of a venous thromboembolic event (such as PE) which could increase the risk of mortality from COVID-19 infection.

For the risk prediction tool, the variable definition needs to correspond to a question that can be answered by an individual as a self-report. We thought a sensible question for the risk prediction tool would be: "Have you ever had a blood clot in your veins, such as a deep vein thrombosis (DVT) or blood clot in your lung, called a pulmonary embolism (PE)?"

We agreed to include a history of venous clot in any location (including cerebral venous thrombosis, portal thrombosis and mesenteric thrombosis) , as a history of venous thrombosis in any location could indicate that the individual is likely to have an increased risk of a future venous thrombosis during a COVID-19 infection. In addition, all sites of venous thrombosis has an associated mortality: a DVT can lead to a PE; a cerebral venous thrombosis can (rarerly) lead to a PE but also cause local sequelae; similarly mesenteric DVT has a mortality risk.

In addition, the inclusion of PE (as seqaelae of DVT or cerebral venous thrombosis) was included because in theory a PE necessitates a pre-existing thrombosis in the venous system and it is possible that clinicians did not record (or find) the causal thrombosis. Therefore, inclusion of PE codes ensures that individuals at risk are not missed from analyses that help inform risk calculations.

We agreed not to restrict based on the context in which the venous thrombosis or PE occurred: whilst it was acknowledged that past DVTs/PEs which occurred in the context of a temporary risk factor (such as pregnancy or post-operative or long-haul flight) may be less strongly associated with future risk of venous thrombosis than other DVTs/PEs, often a limitation of coding in EHR systems means it is not easy to identify the context of the DVT/PE whilst human review of records. Some of the codes do specify that a DVT/PE occurred during pregnancy. However, we could not be confident that all DVTs/PEs which had occurred in pregnancy would be coded with a code specifying the context of pregnancy, and so we couldn't reliably exclude DVTs/PEs which occurred in pregnancy. In addition, a history of DVT/PE during a pregnancy is likely to indicate a somewhat increased risk of venous thrombosis during a COVID-19 infection compared to the general population, even when no longer pregnant.

DEFINITION: A history of venous thromboembolic disease

Variables: (1) a binary variable denoting the presence of one of the codes at any point in the patient record. (2) the earliest date of such a code.

CODE LISTS:

Process (1) Read 2 code list from Helen Strongman and Angel Wong combined here: We did not include codes for suspected/possible DVT/PE; nor PEs specified as air embolism or amniotic fluid embolism as would not indicate at ongoing risk of a venous thrombosis/clot. (2) SNOMED searched for DVT and PE

FLEXIBILITY NEEDED BETWEEN STUDIES: This list

EFFECTS ON COHORT SELECTION: None

POTENTIAL BIASES: This variable includes a history of any venous thrombosis. Some DVTs/PEs will have occurred in the context of a temporary condition (e.g. pregnancy, meningitis, immobility), and some individuals identified by this codelist will be at higher risk of future DVT/PE than others.

FINAL CLEAN CODELIST CTV3_venous_thromboembolism_final_clean.xlsx

EPIDEMIOLOGY SIGN OFF & DATE: Helen McDonald @hmcd 08/09/2020 20:40

CLINICAL SIGN OFF & DATE: Amir Mehrkar @amirmehrkar 10/09/2020 09:30

SHARED WITH WIDER TEAM:

FINAL SIGN OFF DATE (and apply label)

hmcd commented 4 years ago

@amir @laurie @johntaz hope the above summarises the discussion- please do edit if not! @amirmehrkar if you're happy with the codelist would you be happy to be the clinical sign off?

amirmehrkar commented 4 years ago

Just to be clear - on the xls for the "FINAL CLEAN CODELIST" - we will be including all all 1, P and C in column D.

hmcd commented 4 years ago

Ah, good spot! we need to remove the codes that we don't want to be using from the final clean codelist - sorry, I thought I had done this. Amir, did you change any code decisions, or can I just upload the file I have?

amirmehrkar commented 4 years ago

I didnt change your code decisions in Column D - I just made my comments. Hence 1 + P + C = inclusion list as I understand it.

hmcd commented 4 years ago

Fab, then the codelist is CTV3_venous_thromboembolism_final_clean.xlsx also updated inthe signed off version above.

johntaz commented 4 years ago

Thanks everyone - I agree with your summary and will upload to the codelists website