LifeLines Catalog meeting 2012/01/23

Back to Catalog main page

Basic features:

• On front page summary of LifeLines + how many individuals in total
• Per measurement: label, description, dataType, unit, categories, verification status, derivation info (all in English)
• Per protocol: PDFs/links/SOPs
• Separate catalogs for panels: children (<18), adults, elderly(>65). (Of course largely overlapping.)

Big todo: create mock-up of new catalog user interface.

New major features required:

Protocols

We want capability to add more details to protocols: hyperlinks to attached files (SOPs, publications)

Implementation:

• Use MolgenisFile with an xref to Protocol
• Show in the user interface as download link

Derivates

Derivate is a value that is derived from one or more other values using some protocol. For example

• BMI: derived from length and weight using calculation
• blood pressure: derived from 10x blood pressure taking average of last 10

For each derivate we should define the 'protocol' and optionally a 'formula'.

Ideas for implementation:

• we should look into ComputeProtocol? to encode the derivation protocol
• then this is unambiguous using protocolApplication

Verification

Verification is the procedure used to correct erroneous data entries.

• For each Measurement we want to know if it is 'verified' = 'NO, NA, YES'.
• Each Measurement can have multiple verificationRule explaining how verification is done (describing how the rule works).

Ideas for implementation:

• create a Measurement 'isVerified' and then report each verification via Value(target=MeasurementX, feature=isVerified, value=NO)
• create new Feature called 'VerificationRule?' with an xref to Measurement

Validation

Not in the foreseeable future

Protocol details

Verification | checked | how

Can be multiple verifications.

When will the protocol be applied

We need an additional field to record at what times the protocol will be applied.

For example: 'baseline', '5 years', 'yearly'.

Implementation:

• ??? I can imagine we use 'workflow' for this? Each workflow is then the complete set of protocols...

Download of selected measurement

Instead of 'order' people just should be able to download

• as PDF or Excel
• we log all downloads (using existing 'order' tables)
• for the admin we can then make a plot showing how many times a measurement was selected

Search functionality

Two options:

• Search everything
• Search only item descriptions

Ideas for future versions

• counts per data item
• versions of the catalogue
• some barchart on how many data items are ordered per request (so what items are popular).
• What kind of tools is used to measure bp, how old, where can you order materials, (sample tracking?)
• measurements may not be orderable because discontinued