# SD1079: wrong order for added variables in SE

**URL:** <https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535>\
**Category:** SDTM\
**Created:** [September 30, 2013, 5:36am UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535 "2013-09-30T05:36:15Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergiy](https://sea1.discourse-cdn.com/certara/user_avatar/forum.certara.com/sergiy/32/2553_2.png) [@Sergiy](https://forum.certara.com/u/Sergiy)\
**Post date:** [October 1, 2013, 7:10pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/1 "2013-10-01T19:10:40Z")

</div>

Hi Cathy,

It’s quite confusing.

CDISC SDTM model defines an order of Timing variables as …TAETORD, EPOCH, --UPDES, …, --STDTC, --ENDTC, …, --STDY, --ENDY, …

However SE is not a General Observation Class Domain.

In SDTM IG the standard timing variables for SE domain are ordered as --STDTC, --ENDTC, TAETORD, EPOCH, --UPDES. There is an inconsistency with SDTM Model General Obs. Class Variables. However there is no formal requirements on order of variables for Special Purpose domain.

Therefore SDTM Model and IG do not provide complete information on this topic.

In current version of OpenCDISC specifications the order of SE Timing variables was set as 1. defined in IG for standard variables 2. then followed as defined in Model for other model permissible variables.

I realize that it is not 100% valid and not sure what is the correct answer.

I think that CDISC team needs to modify SDTM IG to make an order of variable consistent for all domain inclduding Special Purpose ones.

Kind Regards,

Sergiy

P.S. This is an order of variables in OpenCDISC specifications:

|   
- SESTDTC  
 |
| --- |
|   
- SEENDTC  
 |
|   
- TAETORD  
 |
|   
- EPOCH  
 |
|   
- SEUPDES  
 |
|   
- VISITNUM  
 |
|   
- VISIT  
 |
|   
- VISITDY  
 |
|   
- SEDTC  
 |
|   
- SEDY  
 |
|   
- SESTDY  
 |
|   
- SEENDY  
 |
|   
- SEDUR  
 |
|   
- SETPT  
 |
|   
- SETPTNUM  
 |
|   
- SEELTM  
 |
|   
- SETPTREF  
 |
|   
- SERFTDTC  
 |
|   
- SESTRF  
 |
|   
- SEENRF  
 |
|   
- SEEVLINT  
 |
|   
- SESTRTPT  
 |
|   
- SESTTPT  
 |
|   
- SEENRTPT  
 |
|   
- SEENTPT  
 |

---

<div class="post-metadata">

**Author:** ![cbezek](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@cbezek](https://forum.certara.com/u/cbezek)\
**Post date:** [October 1, 2013, 7:37pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/2 "2013-10-01T19:37:37Z")

</div>

Thanks Sergiy! It’s different than what we expected, but now we know how to avoid the error.

---

<div class="post-metadata">

**Author:** ![Sergiy](https://sea1.discourse-cdn.com/certara/user_avatar/forum.certara.com/sergiy/32/2553_2.png) [@Sergiy](https://forum.certara.com/u/Sergiy)\
**Post date:** [October 1, 2013, 8:32pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/3 "2013-10-01T20:32:00Z")

</div>

I would like to say it again. Our order of variables is not correct as well. Unfortunately there is no clear standard specifications on that.

I refer to a temporary OpenCDISC interpretation only.

Regards,

Sergiy

---

<div class="post-metadata">

**Author:** ![Liron.m](https://avatars.discourse-cdn.com/v4/letter/l/6f9a4e/32.png) [@Liron.m](https://forum.certara.com/u/Liron.m)\
**Post date:** [June 21, 2016, 10:25am UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/4 "2016-06-21T10:25:14Z")

</div>

Can you please specify what should be the accurate label for SESTDY and SEENDY?

---

<div class="post-metadata">

**Author:** ![Sergiy](https://sea1.discourse-cdn.com/certara/user_avatar/forum.certara.com/sergiy/32/2553_2.png) [@Sergiy](https://forum.certara.com/u/Sergiy)\
**Post date:** [June 23, 2016, 9:31pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/5 "2016-06-23T21:31:53Z")

</div>

Hi Liron,

If you need to look at Pinnacle 21 specifications, there is an option to use Internet Explorer with a provided stylesheet. It’s similar to reviewing define.xml file in a browser.

Go to _ **…\components\config** _ folder of P21 Community tool. Select any specific validation configuration file and open it with Internet Explorer. It gives you user-friendly view of standard metadata and rules assignment to each domain. Variable Labels are a part of standard metadata used for validation.

Kind Regards,

Sergiy

---

<div class="post-metadata">

**Author:** ![Liron.m](https://avatars.discourse-cdn.com/v4/letter/l/6f9a4e/32.png) [@Liron.m](https://forum.certara.com/u/Liron.m)\
**Post date:** [June 26, 2016, 8:16am UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/6 "2016-06-26T08:16:05Z")

</div>

Thank you. That would be very helpful for few other questions as well 🙂

---

<div class="post-metadata">

**Author:** ![thyresias](https://avatars.discourse-cdn.com/v4/letter/t/a3d4f5/32.png) [@thyresias](https://forum.certara.com/u/thyresias)\
**Post date:** [December 11, 2016, 3:01pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/7 "2016-12-11T15:01:44Z")

</div>

Hi

The order of SE variables has been changes in 2.2 vs. 2.1. In particular, the order is now SEUPDES TAETORD EPOCH SESTDTC SEENDTC, while it was SESTDTC SEENDTC TAETORD EPOCH SEUPDES, which matches the SDTM 1.4 & SDTM-IG 3.2. What is the reason for this change? Should be follow the SDTM(IG) or your order?

Best,

– Thierry

---

<div class="post-metadata">

**Author:** ![thyresias](https://avatars.discourse-cdn.com/v4/letter/t/a3d4f5/32.png) [@thyresias](https://forum.certara.com/u/thyresias)\
**Post date:** [March 9, 2017, 5:23pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/8 "2017-03-09T17:23:32Z")

</div>

Up…

Any news on this?

Best

---

<div class="post-metadata">

**Author:** ![Sergiy](https://sea1.discourse-cdn.com/certara/user_avatar/forum.certara.com/sergiy/32/2553_2.png) [@Sergiy](https://forum.certara.com/u/Sergiy)\
**Post date:** [March 11, 2017, 2:25pm UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/9 "2017-03-11T14:25:43Z")

</div>

Hi Thierry,

A new minor release is expected within a month.

Regards,

Sergiy

---

<div class="post-metadata">

**Author:** ![rmarshall](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rmarshall](https://forum.certara.com/u/rmarshall)\
**Post date:** [November 20, 2018, 11:32am UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/10 "2018-11-20T11:32:22Z")

</div>

The inconsistency between the SDTM 1.4 model document and the SDTM IG 3.2 is addressed on the SDTM 3.2 Errata page on the CDISC Wiki:

[https://wiki.cdisc.org/display/PUB/SDTMIG+v3.2+Errata](https://wiki.cdisc.org/display/PUB/SDTMIG+v3.2+Errata)

The published corrected order for the last six variable in the SE domain in the IG is ELEMENT, TAETORD, EPOCH, SESTDTC, SEENDTC, SEUPDES. The timing variables appear to have been reordered to be consistent with the order of standard timing variables for general observation classes, but SEUPDES remains the final variable in the domain. This implies that the correct order for all eligible SE variables should be:

- Identifiers
- ETCD
- ELEMENT
- Timing variables (in standard timing variable order)
- SEUPDES.

---

<div class="post-metadata">

**Author:** ![cbezek](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@cbezek](https://forum.certara.com/u/cbezek)\
**Post date:** [September 30, 2013, 5:36am UTC](https://forum.certara.com/t/sd1079-wrong-order-for-added-variables-in-se/535/11 "2013-09-30T05:36:15Z")

</div>

Hi,

I added SESTDY and SEENDY to the SE domain. They were added after SEENDTC, so that the order looks like:

..SESTDTC, SEENDTC, **_SESTDY, SEENDY_** , TAETORD, EPOCH, SEUPDES

This order is similar to how SVSTDY and SVENDY are placed after SVENDTC.

Please let me know if there is a problem with the rule derivation, or the correct location for where the two variables should be placed in the dataset.

Thanks,

Cathy
