About E2B(R3) codelists
Study designers can assign one of the E2B(R3) code lists to form items while designing a study. Site users are required to select one of the code list values when completing form items with the E2B(R3) code lists applied. This ensures that all collected data can easily be sent to Safety.
For more information, see About collecting safety case data when integrating with Safety.
For a list of E2B(R3) data elements, see E2B(R3) dictionary.
The dictionary and code lists are backward compatible, meaning existing data items are not removed or changed; only new items are adopted.
The following E2B(R3) code lists are available:
| Codelist Title | To be used with element... |
|---|---|
| E2B - Patient Age Group | D.2.3 |
| E2B - Term Highlighted by the Reporter | E.i.3.1 |
| E2B - Outcome of Reaction | E.i.7 |
| E2B - Test Result Code | F.r.3.1 |
| E2B - Characterization of Drug Role | G.k.1 |
| E2B - Action Taken with Drug | G.k.8 |
| E2B - Additional Information on Drug | G.k.10.r |
E2B(R3) codelists, like other custom codelists, are only available in English. On your E2B(R3) codelists you can perform the following actions:
- Hide options in an E2B(R3) codelist.
- Add options to an E2B(R3) code list.
- Update the Order, Label, and Code, but not the Value of an E2B(R3) code list option.
- Limitations:
- Do not copy E2B(R3) code lists; doing so can create issues with E2B(R3) mappings during an Oracle Clinical One Platform upgrade.
Parent topic: Add a code list to a question