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

Requirement Designation

Message Header Elements

PAInitiationRequest Elements

PARequest Elements

PAResponse Elements

PAAppealRequest Elements

PAAppealResponse Elements

PACancelRequest/Response Elements

PANotification Elements

Element Tables

Codified Field Usage for Federal Medication Terminologies (FMT) Codes

Element Details

year

The virtualization or emulation of a computer system is based on computer architectures and provides the functionality of a physical computer. Virtual machines are based on computer architectures and provide the functionality of a physical computer.

Virtual_Machine_VM

ionos_cloud

A collection of cloud resources used for creating an enterprise-grade IT infrastructure. VDC resources include the processors, memory, disk space, and networks from which Virtual Machine (VMs) are built.

Virtual_Data_Center_VDC

Virtual_Machines_VMs

A distributed file system protocol that allows remote file access and sharing over a network. NFS enables a client-server model, where a central server provides access to files and directories to remote clients.

Network_File_System_NFS

product_keysight

Irion

A network configured specifically for Dante products.

Dante_network

product_name_dante_controller

google-link

product_name_01

ivanti_product_name

libraries

Collibra

companynewname

Cool phone cases for high security purposes

Privolo

Magical pharmaceutical that heals anything. Right?

Paracetamol

continiaVar

insitutionAdress

productName1

companyLegalName

programName

Archbee

customerName1

productName

Product_Name

Test

SEFAS

uptempo

customerName

testName

name1

testvar

customername

apilink1-getallmethod

support

variable_one

capitalize

company_name_adobe

jama_2

jama_1

test

domain

email

product

silviu

Bogdan_test

ferwhethgte

target1

google

product_name

specific

var_miha

new_var_2

new_mih_var

mih_var

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

testheight

available

testulet

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example

scenario

exemplu

variabila

text

refresh_token

Glossary lets you define every tricky term, then gives them a sneak peek explanation on hover... Just like I'm doing with this text right here!

Glossary_feature

Google

aaaa

variable_test_video

variable123

YourBank

MyBank

test12

sdfdssdfsdfsdfsdfdsfsdf

edfsad

dsfsdfsdf

DairyComp305 - VAS Dairy Management Software

DC305

The term "Zone" represents different dairy locations. PULSE Zones may be different physical dairy locations (for example, multiple locations across the state or country) or different user-defined locations within a single dairy site (for example, Pens 1-100 are Zone 1, Pens 101-200 are Zone 2, etc.).

Zone

EE.product

MI.product

PrimaryMI.product

EE.app

PrimaryMI.license2

applications that are allowed on a device. A device that has other apps installed is considered out of compliance.

Allowlist apps

applications that are not approved for installation on a device. A device that has any of these apps installed is considered out of compliance.

Blockedlist apps

applications that must be installed on a device. A device that is missing any of these apps is considered out of compliance.

required apps

automated responses to a device that violates rules for managed devices.

compliance actions

a list of mobile apps you have made available for your users. Includes apps that users can download from public app stores and apps you intend to distribute using the device management system (In-house apps).

app catalog

Primary.Company

PrimaryMI.license3

an app distributed by the device management service rather than downloaded from a public app store.

in-house app

PrimaryMI.app

a list of users that you want to treat in the same way.

user group

Root Level PARequest Elements

Attachment Elements

Request Elements

Electronic Prior Authorization Companion Guide

Electronic Prior Authorization Overview

Integration & Production

Message Descriptions

Acknowledgment Messages

Electronic Prior Authorization Message Flow

Detailed Electronic Prior Authorization Message Scenarios

PANotification Message Scenarios

Validating PAInitiationRequest Data

PAIntiationRequests After Real-Time Prescription Benefit (Real-Time Benefits Inquiry)

Directories

Failure Mode/Response Approach

Messages Overview

Drug Description

Handling PARequests When a Health Plan Changes ePA Processing Vendor

Prescriber Order Number

Utilization for Non-PA Coverage Rules

Sending Prior Authorization Initiation Requests

Electronic Appeals

Automatically Initiating ePA for RxChange Messages

PAInitiationResponse Reason Codes for PBM/Payers

Re-Submitting and Re-Initiating PAInitiationRequests

NewRx

Attachments

Timing for Response

NDC Codes

Empty Tags

XML NextQuestionID Clarification for PA Question Type

Controlled Substances

PBM/Payer Prior Authorization Coverage Lists

Prescription Eligibility for PA Processors (PBM/Payers, Health Plans, and Third-Party Processors)

Code	Description
mandatory	The element must be used per the specification (e.g., XML schema validation).
conditional	The element is to be used per the conditions specified.
business rule	If sent, the element must be used per the Surescripts business rule. 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.