You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the data element IDs start with IMMZ.D1.DE. and some start with IMMZ.D.DE. Is this intentional? I had tried to just use IMMZ.D for everything to keep them all in the same codesystem for the L3, but then there were conflicts with the last number so I kept them as they are in the DAK. This is fine, but I wanted to confirm this was as intended because changing them now will require a bit of work and even more the later.
Hey @lukeaduncan ! It seems that this happened because initially the IDs using the notation with the activity number included (e.g. IMMZ.D1.DE.) were already used in the L3. To avoid braking the L3, we have decided to keep those IDs as is. If this is not the case anymore we can plan for a data dictionary update so that all the data elements have the same notation, meaning "IMMZ.D.DE.". Could you please confirm that using the notation "IMMZ.D.DE." for all the data elements from tab D would work in L3, so that we can plan the update? Thanks!
It would be fine to change them and if being done, then the sooner the better as I'm currently working on them. One issue was that the last number isn't unique across D and D1 so if you can track which ones change, then that would make it easier for me to update what I've already done.
Some of the data element IDs start with IMMZ.D1.DE. and some start with IMMZ.D.DE. Is this intentional? I had tried to just use IMMZ.D for everything to keep them all in the same codesystem for the L3, but then there were conflicts with the last number so I kept them as they are in the DAK. This is fine, but I wanted to confirm this was as intended because changing them now will require a bit of work and even more the later.
@litlfred @c-corman @catsieseo
The text was updated successfully, but these errors were encountered: