| | 1 | Conversation regarding file structure of mapping table: |
| | 2 | (11:18:29) jeff.lusted@briccs.org.uk: The main structure would have to include something like: path, code and onyx variable |
| | 3 | (11:19:52) jeff.lusted@briccs.org.uk: I could build a lot up just from a list of data like that |
| | 4 | (11:21:14) jeff.lusted@briccs.org.uk: So each code had a path (snomed or local) and a corresponding onyx variable |
| | 5 | (11:22:26) jeff.lusted@briccs.org.uk: We may need to work on the name to depict an onyx variable. It will probably need to be structured in some way so I can navigate the onyx questionnaires to find it within an export |
| | 6 | (11:23:54) jeff.lusted@briccs.org.uk: I think the latter is probably suck it and see. If I have sufficient, I can find it given the xml we already have for metadata from onyx |
| | 7 | (11:24:13) jeff.lusted@briccs.org.uk: or report an ambiguity |
| | 8 | (11:24:44) Nick: OK, that makes sense. Should we aim for one file for each questionnaire stage? And are we talking about an excel file or something else? |
| | 9 | (11:25:41) jeff.lusted@briccs.org.uk: I've never read from an excel file (yet), but a comma separated file would be OK. I think you can emit them from excel? |
| | 10 | (11:26:34) Nick: Yeah, easily enough. But would something else be better? csv / excel is easy to work on manually because of the imposed cell-structure. But if you prefer xml or something we can look at that... |
| | 11 | (11:27:36) jeff.lusted@briccs.org.uk: A csv file with one line per code should be OK |
| | 12 | (11:28:32) jeff.lusted@briccs.org.uk: Perhaps one file for each questionnaire stage would make naming the onyx variable easier |
| | 13 | (11:28:40) jeff.lusted@briccs.org.uk: But I'm easy. |
| | 14 | (11:29:48) jeff.lusted@briccs.org.uk: If it makes more logical sense to have them all in one file, logically grouped (not necessarilly by qu' stage), I'm sure that would be OK |
| | 15 | |
| | 16 | |
