Discussions:
Expand | ||
---|---|---|
| ||
Tried to introduce another object variously referred to as ExternalAid or OtherMaterial to refer to external stimulus materials used in data capture instruments (e.g. images, URNs, other stimulus material). But OtherMaterial already exists as an object in Simple | Use Case_Dagstuhl1.1Codebook. Where should OtherMaterial live? Can it live in two models at once? |
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
* Use case 1.1: Simple Survey + ConceptualInstrument |
Expand | ||||
---|---|---|---|---|
| ||||
Jay's Breakthrough:
This morning's diagram:
What is A? A is conceptual/ logical What is B? B is the implemented one But what are the relationships between A, B and Instrument Component?
|
...
Expand | |||||
---|---|---|---|---|---|
| |||||
What to do with Instructions?? Does it relate to Statement or Act? It is an object which related to Act. Question has a property of text. Use cases Survey example - Dagstuhl evaluation questionnaire Note need to make sure our definitions are tight enough to give guidance to users on how to use objects appropriately
Parking lot - Question Grid and Question Block related to Capture |
...
Warning | ||
---|---|---|
| ||
Monday relationship to Conceptual objects, Question block Question Grid and Question Block related to Capture Tuesday Do we have only statement? Or do we need to add in external objects? Wednesday This is a parking lot item. It is two new objects I would like to add at the "content level" to Measurement. Measurement would have 0..1 State and 0..1 Protocol. What is a state? What is this "protocol"? They are elements of an openEHR object called archetype. See https://www.dropbox.com/s/4y074kt3572k1vi/state.jpg?dl=0 Booz Allen in its VA Health and CMS work and Sam here from CDISC have adopted archetypes as the de facto "data element" for measurements now. That is, State and Protocol are used to extend data elements. Think of our micro-array use case for instrument right now. Here is the current state of instrument: http://lion.ddialliance.org/package/newobjectsforsimpleinstrument. Yesterday we were able to talk about the manufacturers of each micro-array in our use case in which there was one "conceptual" instrument and two "implemented" instruments by pulling in a machine agent from the process model and describing some of her properties. Arguably the standard way is with Protocol. One property of Protocol is the Method. Each micro-array manufacturer has her own method. Furthermore, Protocol can grow to handle Formula. Think of a virtual micro-array. Someone like BAH or another group has built it. It is actually a derived variable. It gets it data from a formula. The formula is how we translate the results of the different methods (manufacturers) into a single yardstick – one SNP fits all. See http://en.wikipedia.org/wiki/Single-nucleotide_polymorphism. Leaving this second example aside which is perhaps a use case we might give more thought to in the context of provenance, were we to have a Protocol attached to a Measurement, the first example with two manufacturers is straightforward. |
Other files to share:
Attachments |
---|