Versions Compared

Old Version 25

changes.mady.by.user Christine Connolly

Saved on

compared with

New Version 26

changes.mady.by.user Christine Connolly

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Definition: The Device In-Use (DU) domain represents properties of an ancillary device that are intentionally set when the device is used in the context of a study.
  2. Tobacco products—including ENDS devices—are not considered ancillary devices and would not be represented here. An ancillary device is a device used within a study but which is not the target of the study 
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-521
    (e.g., a smoking machine that performs a smoking regimen). If settings for an ancillary device in a study need to be recorded and the device needs to be identified in the data, Device Identifiers (DI) must be used for that identification.
  3. The DU domain captures characteristics and properties of a device that can vary from subject to subject or usage to usage over the course of a study. For example:
    1. While the full range of field strengths for a given MRI machine might be 0.5 to 3 Tesla, DU would record the specific settings used for a given subject (e.g., the field strength for the MRI scan for subject 123 was 0.5T for visit 1).
    2. The software for a pacemaker may start at Version 1, and be updated to Version 2 during the study. This change can be captured in the DU domain. 
  4. There are 2 primary identifiers in this domain: USUBJID and SPDEVID. Both are Expected. Either 1 or the other or both must be used. For example, a device under study will always have a SPDEVID, but may or may not have a USUBJID. An ancillary device (one not under study) for which in-use data are required may have a USUBJID but may or may not have SPDEVID. In all cases where SPDEVID is used, it must be defined in the DI domain.
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-519
       
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-691
     
  5. This domain is not intended to capture manufacturer-set (i.e., nominal) settings, but rather the customized settings for a given usage.
  6. Because any number of device settings (e.g., coil strength, placement of leads) can be reported in this domain, each setting is represented by a separate row and is defined in the topic variable DUTESTCD. The original result goes into DUORRES.
  7. DUREFID is the identifier for a unique scan or other test result to link a group of settings (e.g., field strength or slice thickness in an MRI scan) to the results obtained from the reading or interpretation of the test (e.g., the MRI image).
  8. The DUSPID variable can be used to link this domain to other domains if necessary, such as Clinical Observations (CL),
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-520
    and/or Exposure.
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-516
  9. The following Qualifiers would not generally be used in DU: --MODIFY, --BODSYS, --POS,--ORNRLO, --ORNRHI, --STNRLO, --STNRHI, --STNRC, --NRIND, --RESCAT, --REASND, --XFN, --NAM, --LOINC, --SPEC, --SPCCND, --LOC, --METHOD, --FAST, --DRVFL, --EVAL, --TOX, --TOXGR, --SEV, --DTHREL, --LLOQ.