130 likes | 320 Views
The Norwegian Mother and Child Cohort Study. IT-Systems by Ole-Martin Kvinge Arild Sunde. Stuck preparing for a Data Inspectorate audit. Dataflow. MoBaStudy. Scanning. MoBa Data. Load data. MoBa data files. Data from other sources. Coding. Quality control II. Main Systems.
E N D
The Norwegian Mother and Child Cohort Study IT-Systems by Ole-Martin Kvinge Arild Sunde Stuck preparing for a Data Inspectorate audit
Dataflow MoBaStudy Scanning MoBa Data Load data MoBa data files Data from other sources Coding Quality control II
Main Systems • MorBarnData • Questionnaire data and images • Data from other sources (MBR, ABC, ADHD) • Sample analysis results • MoBaStudy • Participant management • Questionnaire management • Sample management
MorBarnData • Questionnaire data management • Client application • Developed in VisualStudio 2005 C# • Database Oracle 10 • Tables automatically created based on Eyes & Hands description files • Track questionnaire versions and linking between versions
Meta data in English and Norwegian • Quality control • Define and modify quality control rules • View questionnaire images and compare to data • Tracks all data changes • Data extraction (shopping list) • Creates SAS and SPSS data files with metadata (variables and values labels)
MoBaStudy • Generic logistics and LIMS system • Client application • Developed in VisualStudio 2005 C# • Database MSSQLServer 2005 • Dual language support • Used by 3 independent studies • Easy setup for new studies
Participant administration • Sample management • Sample retrieval • Communicates with laboratory robots • All user interface labels, menus and messages are defined in the database • User rights to all interface components defined in the database • Change/audit log for all database fields • Load new participants from text file
Logging changes in the database (Data auditing) • Log all updates and deletes on specific tables and their fields in a special table (AuditLog). • A lookup table (LU_LogDef) defines which fields are to be logged. • When LU_LogDef is manipulated (new rows/ changes to the fields Active or LogNullToNotnull), After update and After delete triggers for affected TableNames, are dynamically regenerated through “trigger constructing triggers” on LU_LogDef. • Logging for a single table can be deactivated by disabling triggers or, for all tables, by setting a certain parameter in LU_GlobalParam table to “Off”.
Customizing the application from the database • Form titles, menus, labels, values for dropdown lists are all defined in the LU_FormDef table. • Dual language support (Label and LabelAlt). • Hide or make certain application components invisible or readonly for everyone or for predefined user groups (using the columns Visible, ReadOnly, HiddenToUG, HiddenToUG) • Text for error messages, warnings, and other dialog with user is defined (also with duel lanuage support) in LU_Messages.