PVCs in first dataset (CPSC) missing?

[martin.ba...@protonmail.com]

Dear Challenge-Organizers,

when examining the mapping of scored labels, we found that in the first dataset (CPSC) no records are labelled as PVC ("premature ventricular contractions"). This is confusing as during the unofficial phase, this dataset included exactly 700 records with this label.

We found in the mapping of unscored labels, that for this dataset 700 records are now labelled as "ventricular ectopics", which is reasonable as both diagnoses describe the same abnormality. However, models recognising them are not benefitting from correct classification of this pathology anymore as this class is in the unscored list although being almost identical to the scored diagnosis PVC.

If this change from PVC to ventricular ectopics is intended, it might be helpful to add ventricular ectopics to the scored mapping and map it to the PVC and VPB classes.

Kind regards,

Martin

[PhysioNet Challenge]

Dear Martin,

Thank you for your question, you raised a good point. Please see the announcement on June 18th (https://groups.google.com/g/physionet-challenges/c/eNc26q2luM4/m/gLUu0vRlBgAJ), but basically:

Each database is labelled using a different ontology, or subset of terms in an ontology (or sometimes no ontology - just free text). We therefore had to make a call about how to map these. For example, we have the following four labels for ventricular ectopic beats:

 

Description, SNOMED Code, Abbreviation

premature ventricular complexes,164884008,PVC

premature ventricular contractions,427172004,PVC

ventricular ectopic beats,17338001,VEB

ventricular premature beat, 17338001, VPB

You'll note that while we have chosen to retain the distinction between these in terms of SNOMED codes,  (although we have merged PVCs, because we could really see no reason they had two separate codes), in the scoring matrix they carry the same weight, and mixing them up doesn't cost you any points. You may then ask, 'why not merge them all in the labelling'? Well that's a question you have to answer for yourself. You are certainly welcome to do that - but you may not want to. You may note that only VPB indicates the temporal location of the beat relative to the preceding normal beat. This may, or may not, affect your algorithm, depending on how you write your code. You may or may not want it to affect your algorithm - the relative timing of beats certainly given you information! We have therefore tried to provide you with as much useful information as possible, without overwhelming you with a complete data dump.

Let me know if you have any questions,

Best,

Erick

(On behalf of the Challenge team.)

https://physionetchallenges.github.io/

Please post questions and comments in the forum. However, if your question reveals information about your entry, then please email chal...@physionet.org. We may post parts of our reply publicly if we feel that all Challengers should benefit from it. We will not answer emails about the Challenge to any other address. This email is maintained by a group. Please do not email us individually. 

---

https://physionetchallenges.github.io/2020/

www.PhysioNet.org

--
You received this message because you are subscribed to the Google Groups "physionet-challenges" group.
To unsubscribe from this group and stop receiving emails from it, send an email to physionet-challe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/physionet-challenges/f27d48cc-7f80-4c45-8e10-489182bd4b3fo%40googlegroups.com.