We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

SAS import problems (newbie I think)

Having several issues and confusions. Am using SAS 9.2 and PROC CDISC.
Have been able to open a 1.3 version export file with longnames on or off
and then run datasets, or contents. However, when I try clinicaldata to
write out to a library, the software indicates that ODM 1.3 is not supported
by CDISC.
When I run contents on a table of electrolytes (for which I set no decimal
formats, and the XML file has 32 as length with six significant digits) I am
getting an error on each of the items:
ERROR: ItemDef "itemoid goes here" has invalid combination of Length +
SignificantDigits values.
.....
Finally, it appears that clinicaldata is intended to read in one table at a
time - surely there must be a way to import the whole CDISC file without
listing table by table?
Thanks.
-- J. Michael Dean, M.D., M.B.A. H.A. and Edna Benning Presidential Professor of Pediatrics Professor of Biomedical Informatics Vice-Chairman of Pediatrics Chief, Division of Pediatric Critical Care Medicine University of Utah School of Medicine Salt Lake City, Utah

Comments

  • rwattsrwatts Posts: 102
    It was these and other issues (such a bugs, undocumented features and a
    statement from SAS that PROC CDISC is being deprecated) that led us to
    abandon our focus on CDISC for our exports. We now rely on tab separated
    values or SPSS output (for simple studies where our investigators export
    the data themselves) or our own XML export utility.
    Rick.
    -----Original Message-----
    [mailto:[email protected]] On Behalf Of Mike Dean
    Sent: July 31, 2009 10:10 AM
    To: [email protected]
    Subject: [Users] SAS import problems (newbie I think)
    Having several issues and confusions. Am using SAS 9.2 and PROC CDISC.
    Have been able to open a 1.3 version export file with longnames on or
    off
    and then run datasets, or contents. However, when I try clinicaldata to
    write out to a library, the software indicates that ODM 1.3 is not
    supported
    by CDISC.
    When I run contents on a table of electrolytes (for which I set no
    decimal
    formats, and the XML file has 32 as length with six significant digits)
    I am
    getting an error on each of the items:
    ERROR: ItemDef "itemoid goes here" has invalid combination of Length +
    SignificantDigits values.
    .....
    Finally, it appears that clinicaldata is intended to read in one table
    at a
    time - surely there must be a way to import the whole CDISC file without
    listing table by table?
    Thanks.
    -- J. Michael Dean, M.D., M.B.A. H.A. and Edna Benning Presidential Professor of Pediatrics Professor of Biomedical Informatics Vice-Chairman of Pediatrics Chief, Division of Pediatric Critical Care Medicine University of Utah School of Medicine Salt Lake City, Utah
  • JozefJozef Posts: 71
    Just as a remark ...
    Proc CDISC is not really supporting ODM 1.3 - also SAS seems to have discontinued support for Proc CDISC
    (your mail seems to say that CDISC itself does not support ODM 1.3 - which of course is not true).
    So, please blame SAS, not OC.
    Some companies do develop software to transform ODM files into SAS Transport datasets, the way the customer wants it,
    so you may contact me in case you are interested in such a software.
    Needs however some written requirements from your side.
    Best,
    Jozef
    Jozef Aerts
    XML4Pharma
This discussion has been closed.