Design entity/field?

[roll]

Background As a part of the #2 issue we have to discuss with @danfowler and the team some parts of the ideal data model. It's a subtask named "Analyze the data we have, in comparison to the ideal model".

Topic

Design - trial methodology

Our ideal data model doesn't have a Design entity or field but the Cochrane database has. This entity/field stands for describing trial methodolody like RCT (randomized controlled trial) or CCT (case-control trial).

Proposed solutions

• we can have an entity Design with o2m relation with Trial (as in the Cochrane database)
• we can have a field Trial.design implemented as enum

See also - https://github.com/okfn/opentrials-cochrane-schizophrenia-data/wiki

[pwalsh]

So, it seems that Design is choice from some code list, more or less (RCT, CCT)? Does the database have the identifier and the description?

[roll]

@pwalsh, Cochrane has only 2 options RCT, CCT without description (see wiki link to read about terms). But med trials in general I think have other options.

May be Design and Method are something similar so we can have it as tags for Trial. For example Trial with tags standing for methodology (as array or m2m): RCT, Random number generation + admission order

Related to #6

[danfowler]

@roll Design and Method are indeed similar and I support the idea of having them as tags on Trial.methodology.

More info on Cochrane's idea of RCT/CCT: http://handbook.cochrane.org/chapter_6/box_6_3_a_cochrane_definitions_and_criteria_for_randomized.htm

[roll]

So we can continue on #6