---
title: Requirement Designation
slug: electronic-prior-auth/guide/requirement-designation
docTags: 
createdAt: 2026-06-18T17:59:02.536Z
---

This table defines the requirement designation for each message element and explains how each element is expected to be used within the specification:

| **Code**                                    | **Description**                                                                                                                  |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| <font color="#0C121D">mandatory </font>     | The element must be used per the specification (e.g., XML schema validation).                                                    |
|                                             | The element is to be used per the conditions specified.                                                                          |
| <font color="#0C121D">business rule </font> | If sent, the element must be used per the Surescripts business rule.<br />**Note**: Not all business rules reside in this table. |
| recommended                                 | Surescripts recommends sending the element as a best practice.                                                                   |
| optional                                    | Some fields do not have specific conditions. Data should be sent if available.                                                   |
| not used                                    | Not used by Surescripts.                                                                                                         |