Type | Standard / Implementation Specification | Standards Process Maturity | Implementation Maturity | Adoption Level | Federally required | Cost | Test Tool Availability |
---|---|---|---|---|---|---|---|
Standard
|
Final
|
Production
|
![]() |
No
|
$
|
No
|
|
Implementation Specification
|
Final
|
Production
|
![]() |
Yes
|
$
|
Yes
|
|
Implementation Specification
|
Final
|
Production
|
![]() |
Yes
|
$
|
No
|
|
Implementation Specification
|
Final
|
Feedback requested
|
Feedback Requested |
No
|
$
|
No
|
|
Implementation Specification
|
Final
|
Feedback requested
|
Feedback Requested |
No
|
|||
Implementation Specification
|
Final
|
Pilot
|
![]() |
No
|
$
|
No
|
Limitations, Dependencies, and Preconditions for Consideration |
Applicable Security Patterns for Consideration
|
---|---|
|
|
Comment
Submitted by shellyspiro on 2023-10-02
Pharmacy HIT Collaborative (PHIT) comment
PHIT supports NCPDP’s recommendation updating NCPDP SCRIPT Standard, Implementation Guide, Version 2017071 to Federally Required; update NCPDP Formulary and Benefits Standard, Version 3 to Federally Required with an adoption level of 4; sunsetting NCPDP Formulary and Benefit Standard Versions 53, 54, and 55; and adding NCPDP Formulary and Benefit Standard Version 60.
Submitted by pwilson@ncpdp.org on 2022-09-30
NCPDP Comments
- NCPDP recommends to sunset NCPDP SCRIPT Standard Implementation Guide Version 2013101
- NCPDP recommends updating – NCPDP Formulary and Benefit Standard Version 53 to the following:
Submitted by pwilson@ncpdp.org on 2021-09-29
NCPDP Comments
NCPDP supports ONC’s recommendations.
Submitted by pwilson@ncpdp.org on 2020-11-07
NCPDP Comment
- Modify NCPDP SCRIPT Standard, Implementation Guide, Version 2017071 Adoption Level to 4
Submitted by pwilson@ncpdp.org on 2019-09-23
NCPDP Comment
- Update Implementation Maturity to Production (as of 1/1/2020).
Submitted by pwilson@ncpdp.org on 2018-10-01
NCPDP Comment
- Title should say: “Allows a Prescriber to Request, Cancel or Appeal Prior Authorization for Medications”.
- NCPDP SCRIPT 2013101 should have:
- an adoption level of 3.
- Modify testing tool availability to Yes
- Add the following:
Type-Implementation Specification
Standard Implementation/Specification- NCPDP SCRIPT Standard, Implementation Guide, Version 2017071
Standards Process Maturity – Final
Implementation Maturity- Pilot
Adoption Level – 1
Federally Required – No
Cost – $
Test Tool Availability – Yes.
Submitted by shellyspiro on 2018-10-01
Pharmacy HIT Collaborative's Comments on ONC's Proposed 2018 ISA
The Pharmacy HIT Collaborative supports the move to NCPDP SCRIPT Version 2017071 as soon as participants can reasonably be ready to implement such a change. The Collaborative supports theuse of NCPDP SCRIPT Standard, Implementation Guide Version 2013101.
Submitted by pwilson@ncpdp.org on 2017-11-20
NCPDP - Comment on Version 10.6
-
- The adoption level should be modified to a 2.
- Under Limitations, Dependencies, and Preconditions for Consideration add the following:
- The following transactions need to be implemented for interoperability purposes:
- PAInitiationRequest and PAInitiationResponse
- PARequest and PAResponse
- PAAppealRequest and PAAppealResponse
- PACancelRequest and PACancelResponse
- Both the prescriber and the payer/processor/pharmacy benefits manager (PBM) must have their systems configured for the transaction in order to facilitate successful exchange.
- The following transactions need to be implemented for interoperability purposes:
- Under Applicable Security Patterns for Consideration add the following:
- Secure Communication – create a secure channel for client-to- serve and server-to-server communication.
- Secure Message Router – securely route and enforce policy on inbound and outbound messages without interruption of delivery.
- Authentication Enforcer – centralized authentication processes.
- Authorization Enforcer – specifies access control policies.
- Credential Tokenizer – encapsulate credentials as a security token for reuse (e.g., – SAML, Kerberos).
- Assertion Builder – define processing logic for identity, authorization and attribute statements.
- User Role – identifies the role asserted by the individual initiating the transaction.
- Purpose of Use - Identifies the purpose for the transaction.
Submitted by pwilson@ncpdp.org on 2023-10-06
NCPDP Comment
Type- Implementation Specification
Standard Implementation/Specification- NCPDP Formulary and Benefits Standard, Version 60
Standards Process Maturity – Final
Implementation Maturity- Pilot
Adoption Level – 1
Federally Required – No
Cost – $
Test Tool Availability – No