Title of session: Data Capture
Day: Monday, October 24
Participants: Barry Radler, Dan Smith, Wolfgang Zenk-Moltgen, Kelly Chatain, Arofan Gregory (visiting)
Chair: Barry Radler
Note taker: Kelly Chatain
Morning Session
Background information
Not much work since Dagstuhl 2015 by the Data Capture team. In general waiting to hear back on the work already completed and in need of review.
Reviewed the team members, a few were removed due to inactivity and other reasons. Sophia, Ingo, and Brigitte. Jannik has not had the time to help with the modelling and therefore a new modeller for Data Capture should be assigned (issue created in Jira).
Backing-up and Reviewing the model:
The group went back to the model to review changes made by others outside of the team.
Implemented instrument based on conceptual instrument, which organizes infinite number of 'captures' (superclass) that are associated with represented variable. Created Represented Measurement (includes question and non-question) as well as Represented question. Instance question measurement, Instrument component (the base class)...
**All ties into the process model with a DDI Act. But how? Where do we define the questionnaire flow (the sequence), the instrument itself?
10:55 - Arofan brings in Larry's rendering of what's in drupal workflow
Random notes by Kelly (may discard)
- Defining an Act (instructional command= command code, but not applicable for asking a question) Command code is part of instrument component.
- Workflow service - not applicable for specifying questionnaire, i.e. for setting the conditional?
- Workflow has a sequence, acts are ordered by the workflow sequence
- Instance question = act
- Conceptional instrument has workflow sequence (concrete). Workflow sequence is control construct, has properties that say instance Q1 (act1), followed by Instance Q2(act2)
- How to order them? Collection pattern? or the sequential sequence? (Some stuff should be pushed to methodology?)
End of random notes
Dan: Wants to get some response domains defined.
Issue: How to describe what the actual response domain is?
Goal - Basic questionnaire, workflow
**If methodology needs more information about an act, then they should add it to their patterns.
Decisions
Use basic questionnaire to walk through the model. Perhaps using three examples to illustrate 1)prescriptive needs for designing a questionnaire 2) run-time needs for processes, and 3) archival needs for describing after data is received.
Afternoon Session
Participants: Kelly Chatain, Barry Radler, Dan Smith, Wolfgang Zenk-Möltgen
Created two question, one measurement instrument with an introductory statement and interviewer instructions. (see attached)
Decisions
Will create one example to illustrate prescriptive (design), run-time, and archive activities.
Issues:
How to name a question?
Problems with bindings In/Out parameters
DDI Data Capture Use Case #1.
Description: Permission form for blood pressure data capture performed in a clinical setting by a nurse or clinician.
Introduction: Please complete the following fields to provide permission for collecting a blood pressure reading.
Question1: “What is your full name?”
Description: Question with two separate responses; response options are open-ended text.
- First name ___________________
- Last name ____________________
Question2: May we perform a blood pressure reading on you?
Description: Question with one response; response option is closed-ended dichotomous category.
- Yes
- No
Instructions to Interviewer/Clinician: If participant provides permission, attach blood pressure cuff and perform standard 30 second BP measure. Record blood pressure and pulse in fields below.
Measurement1:
- Systolic blood pressure: _ _ _
- Diastolic blood pressure: _ _ _
- Pulse (beats per minute): _ _ _
First graphs:
How DDI 3.2 would do it
DDI 4
DDI 4 with bindings
