Type | Standard / Implementation Specification | Standards Process Maturity | Implementation Maturity | Adoption Level | Federally required | Cost | Test Tool Availability |
---|
Limitations, Dependencies, and Preconditions for Consideration |
Applicable Security Patterns for Consideration
|
---|---|
|
|
Comment
Submitted by pwilson@ncpdp.org on
NCPDP Comment
- NCPDP recommends that ONC update: NCPDP Telecommunication Standard, Implementation Guide, Version F2, March 2018 and Equivalent Batch Standard Implementation Guide, Version 15 to NCPDP Telecommunication Standard, Implementation Guide Version F6, April 2022 and equivalent Batch Standard Implementation Guide Version 15
- NCPDP recommends that ONC update: NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 3, Release 0 (Version 3.0), July 2007 to NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0
- NCPDP recommends that ONC update: NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 10 to NCPDP Batch Standard Subrogation Implementation Guide Version 10
- NCPDP recommends that ONC remove: HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide. The guide does not support pharmacy claims submission nor is it adopted under HIPAA.
- NCPDP recommends that ONC update the Limitations, Dependencies, and Preconditions for Consideration section to remove: Information about the CMS May 2020 Interoperability and Patient Access final rule and the HL7 FHIR APIs included in that rule may be found on the CMS Interoperability website. This rule includes use of the HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide.
- Rationale: You cannot submit a claim using the HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide. This guide possibly belongs under the section “Allows Pharmacy Benefit Payers to Communicate Formulary and Benefit Information to Prescriber Systems”; however, the purpose of the guide is to allow a consumer to verify formulary and benefit information.
Submitted by shellyspiro on
Pharmacy HIT Collaborative (PHIT) comment
PHIT supports the following NCPDP recommendations: updating NCPDP Telecommunication Standard, Implementation Guide, Version F2, March 2018 and Equivalent Batch Standard Implementation Guide, Version 15 to NCPDP Telecommunication Standard, Implementation Guide, Version F6, April 2022 and Equivalent Batch Standard Implementation Guide, Version 15; updating NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 3, Release 0 (Version 3.0), July 2007 to NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0; and updating NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 10 to NCPDP Batch Standard Subrogation Implementation Guide Version 10.
Submitted by pwilson@ncpdp.org on
NCPDP Comments
- NCPDP recommends updating: NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 10 to the following:
- NCPDP recommends updating: NCPDP Telecommunication Standard, Implementation Guide, Version F2, March 2018 and Equivalent Batch Standard Implementation Guide, Version 15 to the following:
- NCPDP recommends removing the following:
- Standard / Implementation Specification: HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide and
- Limitations, Dependencies, and Preconditions for Consideration: Information about the CMS May 2020 Interoperability and Patient Access final rule and the HL7 FHIR APIs included in that rule may be found on the CMS Interoperability website. This rule includes use of the HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide.
- Rationale: You cannot submit a claim using the HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide. This guide possibly belongs under the section “Allows Pharmacy Benefit Payers to Communicate Formulary and Benefit Information to Prescriber Systems”; however, the purpose of the guide is to allow a consumer to verify formulary and benefit information.
Submitted by pwilson@ncpdp.org on
NCPDP Comments
- Modify NCPDP Telecommunication Standard, Implementation Guide, Version F2, March 2018 and equivalent Batch Standard Implementation Guide, Version 15 to reflect Version F6.
- NCPDP Telecommunication Standard, Implementation Guide, Version F6, April 2020 is published, adoption level of N/A and not Federally Required yet.
- NCPDP has requested this version be named under HIPAA.
Submitted by pwilson@ncpdp.org on
NCPDP Comment
- Add the following:
Type-Implementation Specification
Standard Implementation/Specification- NCPDP Telecommunication Standard, Implementation Guide, Version F2, March 2018 and Equivalent Batch Standard Implementation Guide, Version 15
Standards Process Maturity – Final
Implementation Maturity- Pilot
Adoption Level – 1
Federally Required – No
Cost – $
Test Tool Availability – No.
Limitations, Dependencies, and Preconditions for Consideration |
|
|
|
Submitted by pwilson@ncpdp.org on
NCPDP - Comment
-
- The Standard Listed – NCPDP Version D.0 is incorrect. The Standard and Implementation Guide are not separated. There is no separate standard and the Standard section material should be deleted.
- Standard Implementation/Specification: incorrectly lists the wrong version of the Telecommunication Standard Implementation Guide. It should be Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2010.
Submitted by pwilson@ncpdp.org on
NCPDP Comment
Rationale: You cannot submit a claim using the HL7® FHIR® DaVinci Provider Data Exchange (PDex: Formulary) Implementation Guide. This guide possibly belongs under the section “Allows Pharmacy Benefit Payers to Communicate Formulary and Benefit Information to Prescriber Systems”; however, the purpose of the guide is to allow a consumer to verify formulary and benefit information.