[{"data":1,"prerenderedAt":148},["ShallowReactive",2],{"navigation":3,"\u002Ftechnical-details\u002Fdata-model":44,"\u002Ftechnical-details\u002Fdata-model-surround":145},[4,8,30],{"title":5,"path":6,"stem":7},"TREAT-NMD Core Datasets","\u002F","0.index",{"title":9,"icon":10,"path":11,"stem":12,"children":13,"page":29},"Introduction","i-lucide-book-open","\u002Fintroduction","1.introduction",[14,19,24],{"title":15,"path":16,"stem":17,"icon":18},"About","\u002Fintroduction\u002Fabout","1.introduction\u002F1.about","i-lucide-house",{"title":20,"path":21,"stem":22,"icon":23},"Item","\u002Fintroduction\u002Fitems","1.introduction\u002F2.items","i-lucide-download",{"title":25,"path":26,"stem":27,"icon":28},"Records","\u002Fintroduction\u002Frecords","1.introduction\u002F3.records","i-lucide-sliders",false,{"title":31,"icon":32,"path":33,"stem":34,"children":35,"page":29},"Technical details","i-lucide-cog","\u002Ftechnical-details","2.technical-details",[36,40],{"title":37,"path":38,"stem":39},"Metadata model","\u002Ftechnical-details\u002Fmetadata-model","2.technical-details\u002F1.metadata-model",{"title":41,"path":42,"stem":43},"Data model","\u002Ftechnical-details\u002Fdata-model","2.technical-details\u002F2.data-model",{"id":45,"title":41,"body":46,"description":138,"extension":139,"links":140,"meta":141,"navigation":142,"path":42,"seo":143,"stem":43,"__hash__":144},"docs\u002F2.technical-details\u002F2.data-model.md",{"type":47,"value":48,"toc":133},"minimark",[49,53,70,73,98,107,118,121,124],[50,51,41],"h1",{"id":52},"data-model",[54,55,56,57,64,65,69],"p",{},"To understand the data model, please first consult the ",[58,59,63],"a",{"href":60,"rel":61},"https:\u002F\u002Fdatasets.treat-nmd.org\u002Fintroduction",[62],"nofollow","general introduction on the specification website"," and the ",[58,66,68],{"href":67},"metadata-model","technical description of the metadata model",".",[54,71,72],{},"The main principles are:",[74,75,76,80,83,86,95],"ul",{},[77,78,79],"li",{},"For each patient and each singular (i.e., basic or datestamped) item reference, there may exist zero or one item value.",[77,81,82],{},"For datestamped item references, the datestamp is included in the data model.",[77,84,85],{},"For each patient and each longitudinal item reference, there may exist any number of item values, and the respective datestamp is included in the data model.",[77,87,88,89,94],{},"For each patient and each record, there may exist any number of record instances. Depending on the record type, the record instance contains various dates (datestamp, start\u002Fstop dates etc.; see the ",[58,90,93],{"href":91,"rel":92},"https:\u002F\u002Fdatasets.treat-nmd.org\u002Fintroduction\u002Frecords",[62],"introduction"," for details).",[77,96,97],{},"For each record instance and each record item reference belonging to that record, there may exist zero or one item value.",[54,99,100,101,106],{},"Currently, data is submitted by registries in a tabular format for which an Excel template is provided in the section \"Downloads\" section on the website (see, for instance, the ",[58,102,105],{"href":103,"rel":104},"https:\u002F\u002Fdatasets.treat-nmd.org\u002Fsma\u002Fdownloads",[62],"SMA downloads","). This Excel file contains the following tables:",[74,108,109,112,115],{},[77,110,111],{},"One table for all singular items. It contains exactly one row for each patient. For every basic item reference, there exists one column for the item value. For each datestamped item reference, there exists one column for the value and one for the datestamp.",[77,113,114],{},"One table for all longitudinal items references. It contains one row for each patient and unique datestamp, so that every patient generally has multiple rows. For every longitudinal item reference, there is one column for the value.",[77,116,117],{},"One table for each record. In each record table, there is one row per record instance, and one column for every item reference belonging to that record.",[54,119,120],{},"This format is centered around the multiplicity of the values and ensures that there are no redunancies while each row makes sense by itself.",[54,122,123],{},"The following UML diagram illustrates the conceptual model (although it currently does not convey the multiplicity constraints described above):",[54,125,126],{},[58,127,129],{"href":128},"\u002Fdata.png",[130,131],"img",{"alt":132,"src":128},"UML model",{"title":134,"searchDepth":135,"depth":136,"links":137},"",1,2,[],"To understand the data model, please first consult the general introduction on the specification website and the technical description of the metadata model.","md",null,{},true,{"title":41,"description":138},"gQYFbC_ZxCJuzHy-ZGn1NvXbWdFybpa6A3eL0jKL5bw",[146,140],{"title":37,"path":38,"stem":39,"description":147,"children":-1},"The TREAT-NMD Core Datasets are described on a dedicated web app. The content of this website is completely defined in the JSON file library.json. This structure of this file, which should serve as source for any tools operating on data in the TREAT-NMD data model, is described in the following. Note that this document only contains the technical and imlementation details that are not described in the general introduction to the datasets, so please read that document first.",1782940343647]