| Expand | ||
|---|---|---|
| ||
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 SessionBackground 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. **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 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 SessionParticipants: 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: All issues logged as of Wednesday, Oct. 26th 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.
Question2: May we perform a blood pressure reading on you? Description: Question with one response; response option is closed-ended dichotomous category.
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:
First graphs: How DDI 3.2 represents this data capture use case.
How DDI 4 will capture this use case, using represented and instance questions/measures.
DDI 4 with bindings
|
| Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Attending: Kelly Chatain, Wolfgang Zenk-Möltgen, Barry Radler, Dan Smith Discussion of other classes:
Issues: (All issues logged as of Wednesday, Oct.26th)
The Work: Discussion about the bindings between the output parameters required for making the elements reusable. Parameter collection is what you refer to when you create the binding. Parameters defined in WorkflowStep. Will comment out the issues in the example and link them to actual JIRA Issues, when they are logged. Afternoon SessionAttending: Kelly Chatain, Wolfgang Zenk-Möltgen, Barry Radler, Dan Smith Beginning with the description, which goes into Abstract Question: Where to record language as a property of the fielded questionnaire, but not of the specification design. Perhaps in implementedInstrument as opposed to conceptualInstrument. Question: Layout - can capture pdf or screenshot, but cannot prescribe the layout automatically. Feedback: Issues:
Changed: In Capture - measurementName switched to Name Changed: In Capture - changed to 0..n from 0..1 in source cardinality ResponseDomain
|
| Expand | ||
|---|---|---|
| ||
Notes: Request to look at other types of captures at the high level. Are there candidates to go into the element registry? Besides representedQuestion and representedMeasure - are there other items that could could go in? Taina mentioned something about controlled vocabulary for types of captures. Wendy wants us to think about describing pulling admin data as capture vs. and analysis (Wolfgang). Should we model so that a computer can act or just describe how it was done? What does it need for automatic for real-time data collection...Fitbit example - has software by device and brand. Collecting the data from the API. How to deploy to Blaise or other? When I see the measurement type I will use this piece of code I"ve written. Can't code for every system or device. What is needed in reusable measurement vs instantiated. For instance, series number of blood pressure device could be in instanceMeasurement. Barry - Need link to white paper 4-5 years ago? representedMeasure and use of controlled vocabulary for the type of measure, the responsibility of the user to create and use those vocabularies. In 3.2, ProcessingEvent was vague enough to capture instructions for preparing to take a blood pressure measurement, for instance. Do we pull in a transformation as a Data Capture or push out to the variables. A selection of those tweets to save for future research. Which is external to DDI. Measure defined as a data processing step, then that helps with the selection/analysis. New class - administrative data gathering item - i.e. DataSource class? Big use cases that deserve their own measurement class. Ingo's use case involving educational testing. George Question: Pointing to ontologies with a measurement? Loinc as https://loinc.org/ How do we link the concept? What is the question intent? Questions: Content for instanceVariable? Is there link to the capture for this? Question or measure? or link to a different instanceVariable as a source variable. Linkages to the representedVariable and conceptualVariable on the Data Description side. This photo was updated on Day Four.
|
| Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Morning SessionAttending Joint Discussion: Data Description: Achim Wackerow, Knut Wenzig, Dan Gillman, Larry Hoyle, Arofan Gregory Data Capture: Kelly Chatain, Barry Radler, Wolfgang Zenk-Möltgen, Dan Smith Joint Discussion Notes: Both DD and DC have instanceVariables, so how do the question and definition match up? RepresentedVariable should be in Data Capture because it is created by the ResponseDomain as the intended data type for that question. Can create new instances of ResponseDomain to specify new set of values for different back end systems (Dan S.) Do sentinel value codes lead to different physical instance data sets? If you have different sentinel values, then you have different RepresentedVariables (Dan S.) Some systems select the sentinel codes, some can't. One conceptual variable and several representations (Dan S.) One represented variable and several instances (Dan G.) Concept to terms, not terms to concepts. Data Description - 0,1,1,0 and 0110 are they two separate instance variables or one? Copy to a new file is exactly the same. (Kelly loses track of the conversation) Still trying to define the instance variable Start with the file--the byte points to a value mapping, the value mapping is associated with instance variable, that instance variable points to the instance question, instance question to the represented question, which leads to represented variable. Dan Smith - Data description needs to somehow need to point to the specific response domain of the represented question Where the instance question to the response domain The Dans agree - Instance variable links to instance question links to represented question which has response domains. Represented question links to represented variable which encodes the response domain. Data Description to file three issues - create relationships between IV and IQ also IV to RD1, RD2, RD3. Dan Smith question: How to create derived instance variables? What relationship do we create on an instance variable to point to source variables for derivations? For Data Description to log as an issue. THE DECISION?!
IV=instanceVariable IQ=instanceQuestion RQ=representedQuestion RV=representedVariable RD=responseDomain Second Morning & Afternoon SessionKelly Chatain, Barry (half-time), Wolfgang, Dan Smith, and Kerrin! Looking at Response domains. Pulling from DDI 3.2. recommended data type Response options to define (all extend ResponseDomain): TextResponseDomain (New Class) 3.2 TextDomainType NumericReponseDomain (New Class) 3.2 NumericDomainType CodeResponseDomain (New Class) 3.2 CodeDomainType Will include a conditional text domain to include "Other" entries with a code list. Wolfgang - We need a touch point between data capture and analysis (exists as a GenerationInstruction in DDI 3.2) to capture derived and other transformations.
Question: Why are the properties Name and DisplayLabel on each item and not inherited?
Question: intendedRepresentation - should that be in the ResponseDomain and then inherited by the others Domain types? We put it in the base ResponseDomain.
Question: Do we need classificationLevel as a property in the NumericResponseDomain?
Issue -
Action Items: What to do about multiple selection on code list response domain?
Should we add intendedRepresentation to ResponseDomain
What to do about conditional text with code list response domain? Outline a plan for moving forward: Review summary of Dagstuhl Sprint - Kelly Set up a Data Capture phone call - Barry Continue to work on JIRA issues (before or during EDDI?) Virtual sprint
|
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Kelly, Wolfgang, Dan, Kerrin Storing multiple values - five pieces of data as checked or unchecked or 5 variables with coded representation. In Lion you can't have a choice in the model, you use it using this kind of represented variable. Issues:
Adding a conditional relationship to the CodeListResponseDomain called SpecifyOtherResponseDomain. Attaching display label to response domain. The codelist response domain allows for a (conditional relationship) and creation of a specifyotherresponse domain. The code list response domain can be called a number of times for the example of choosing multiple responses from one code list. Adding category to the boolean (two valued, binary variable) response domain, for checked/unchecked responses. Only allowed to add one category. Added ScaleResponseDomain - operates like CodeListResponseDomain, calling out the different scales - still needs to be modeled. Removed hasIntendedRepresentation from Capture because all response domains have it. Added numericResponseDomains but did not put in the represented variables. |