Data for: Representing Oncology in Datasets: Standard or Custom Biomedical Terminology?

Published: 7 May 2019 | Version 1 | DOI: 10.17632/xzbzz6czr7.1

Description of this data

We collected 250 cancer-related records that had already been coded using a custom terminology at Roche Inc (ROCHE). The purpose was to annotate substances of pharmacological interest, taking both anatomy (Roche.Anatomie) and histology (Roche.Histology) into account. 150 records were given to either of two medical students (CoderA and CoderB).

Coders were asked to identify representational units that expressed the same meaning in four target terminologies (SNOMED CT, NCIt, ICD-10 + ICD-O, and MedDRA) with as few codes as possible. Fifty of the cases were overlapping (double-coded), in order to enable the computation of inter-rater agreement.

For evaluation, we used the following definitions: Hit=At least one code was provided for that terminology. Agreement=Both coders provided exactly the same codes. Therefore, an absence of codes by both counted as an agreement, and a same primary code but different secondary code counted as a disagreement.

Experiment data files

This data is associated with the following publication:

Representing oncology in datasets: Standard or custom biomedical terminology?

Published in: Informatics in Medicine Unlocked

Latest version

  • Version 1


    Published: 2019-05-07

    DOI: 10.17632/xzbzz6czr7.1

    Cite this dataset

    López-García, Pablo; Daumke, Philipp; Schulz, Stefan; Romacker, Martin (2019), “Data for: Representing Oncology in Datasets: Standard or Custom Biomedical Terminology?”, Mendeley Data, v1


Views: 170
Downloads: 10


Cancer, Medical Informatics, Annotation, Ontology, Medical Terminology


CC BY 4.0 Learn more

The files associated with this dataset are licensed under a Creative Commons Attribution 4.0 International licence.

What does this mean?
You can share, copy and modify this dataset so long as you give appropriate credit, provide a link to the CC BY license, and indicate if changes were made, but you may not do so in a way that suggests the rights holder has endorsed you or your use of the dataset. Note that further permission may be required for any content within the dataset that is identified as belonging to a third party.