metamodeling forms
a study period report
Denise Warzel, NCICBIIT
Jim Davies, Charles Crichton, Andrew Tsui, James Welch,
Steve Harris* Department of Computer Science, Oxford
Daniel Abler, CERN
agenda
•
•
•
•
•
•
why might we need one
what instances already exist
what are their common features
what one might look like
what would be its scope
where do we go next
motivation
• specification
– I want this data to be collected
• interoperability
– we should be collecting this data
– we have collected this kind of data before
• documentation
– this is how this data was collected
– no, this is what this data means
motivation …
• discovery and reuse
– of data
• was any data like this collected?
– of form designs
• can I save some time here?
• is there some way of collecting this kind of data that is validated?
• model driven software engineering
– I need to guarantee that my system collects the data I have
described
– I need bespoke functionality, not bespoke software
– I want my software to be more general
examples – in paper
• euro QoL
• TCGA follow-up form (NCI, partial specification)
• business process templates
examples - electronic
•
•
•
•
•
•
open clinica/redcap
slot extensions in EAP software
caDSR
CDISC ODM
HL7 CDA
DDI 3.x
presentatio Exception
Field static
field runtime
control logic
n
handling
re-use
User management
other
Selection of
can value
Field
items from
Form roles*
preincluding
pairs be
definitions
value
arbitrary
data
elements
/ fine
attributing configurabl
population
execution graphics*/
for
specified by
(Questions, domain
field
constraints/
skip logic
are
grained users to set e form level audit record signature
of data
order
multimedia validation look-up,
Value
(one,
annotation validation
versionable user access of user
metadata
fields
**
e.g. webdomain) multiple,
control**
service?
number)
none has
(clearly
none of the
defined)
none of the
models
form roles
models
all form
all have some some way of
provides
or fine
allows to
elements
expressing multiplicity of
discrepancy
grained
specify
are
fields//tables, most have
all have grouping
manageme
user access
accessibility
referencabl
multilanguage support, 'mandatory'
nt that is
control, ,
options like
e, at least
flag for fields.
configurabl
not possible
voice or
internally
e through
to attribute
braille
model
users to
different
sets
y*/n**/?**
?
?*
*
?*/?**
y
y*"/y**
?*/n**
y
some
y
?*/n**
n
n
y
y
Documenta CDISC-ODM y
?*/?**/?**
tion
DDI
y
?
?*
*
?*/?**
y
?*/n**
?*/y**
n
n
y
?*/n**
?
n
?
?
eDCI
y
n
OpenClinica y
RedCap
?
y
?
n
?
CancerGrid y
n
n
caBig Formsy
n
n
Generation
y*/n**/n**
*
n*/n**
n
y*/n**
y*/n**
n
n
n
n*/n**
n
n
n
n
y*/?**/n**
*
y*/n**
?
?
y
?
y*"/n**
?
n*/n**
?*/?**
y
?
n
n
?
n*/n**
?
n
?
n
?
n
?
n
?
y
n*^/n**
n*/n**
n
n
n
n*/n**
n
n
n
n
n
n*^/n**
n*/n**
n
n
y
n*/n**
n
n
n
n
n*/n**/n**
*
n*/n**
n*/n**/n**
*
n*/n**
* = provide
some
annotation
capabilitiy,
e.g. concept * = for
* = fixed
reference, single field value
external
code list;
but not
arbitrary
** =
** =
computed computed
across fields from fields
* = form
elements
within
forms
** = forms
within
study
metamodel elements
•
•
•
•
identification
static structure and mapping
validation
control logic/flow
metamodel elements - structure
• questions
– typing
– instruction text
– their relationship to data elements
• sections
– their relationships to other sections on other
forms
• the container
– essential annotation of scope
metamodel elements - validation
• field-level data checking logic
– narrows typing information from ISO11179
– account for dependencies (scope?)
• default values
metamodel elements - flow
• ordering
• paging
• skip logic
• to what extent is style in scope?
administered
item
terminology
value domains
data elements
models
17
scope
• not a data model or a workflow model
– although clearly related
• not an implementation
– although it has to encompass XForms, webforms, JSF,
ASP.NET forms …
• maybe has elements of a meta-standard
– may specify constraints on DSLs for validation/flow
control/skip logic/workflow
scope …
• will describe how to specialise ISO/IEC11179 data
elements into questions
• will specialise ISO/IEC19763 – is it simply another
component standard of the family
• will reuse administration modeling from this
workgroup
next steps
• approval to begin turning the research into a
standard
• advice on how the standard is structured and
presented
– abstract or concrete metamodel?
– multipart?
– specification + guidance notes?
PTCRi
Particle Therapy Cancer Research Institute
Webpage: ht t p:/ / www.pt cri.ox.ac.uk/
PARTNER
Particle Training Network for European Radiotherapy
Part icle T herapy Marie Curie Early Init ial Training Network Fellowship
of t he European Community’s Sevent h Framework Programme under
cont ract number (PIT N-GA-2008-215840-PART NER).
Webpage: ht t p:/ / www.pt cri.ox.ac.uk/
ULICE
Union of Light Ion Centres in Europe (ULICE)
Co-funded by t he E. C. wit hin t he Framework Programme 7 Capacit ies
Specific Programme. (Grant Agreement 228436).
Webpage: ht t p:/ / ulice.web.cern.ch