Difference between revisions of "Da Vinci PDex-formulary FHIR IG Proposal"
| Line 91: | Line 91: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| − | + | 1. An Authenticated Member at a Health Plan will be able to use an OAuth2.0 authorization to permit a Third-Party Application to access the Health Plan's FHIR API to read the Plan's Prescription Drug Formulary. | |
==IG Relationships== | ==IG Relationships== | ||
Revision as of 13:59, 1 May 2019
This page documents a Pending FHIR IG Proposal
Contents
- 1 Da Vinci Payer Data exchange formulary FHIR IG Proposal
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Publishing Lead
- 1.4 Contributing or Reviewing Work Groups
- 1.5 FHIR Development Project Insight ID
- 1.6 Scope of coverage
- 1.7 Content location
- 1.8 Proposed IG realm and code
- 1.9 Maintenance Plan
- 1.10 Short Description
- 1.11 Long Description
- 1.12 Involved parties
- 1.13 Expected implementations
- 1.14 Content sources
- 1.15 Example Scenarios
- 1.16 IG Relationships
- 1.17 Timelines
- 1.18 When IG Proposal Is Complete
- 1.19 FMG Notes
Da Vinci Payer Data exchange formulary FHIR IG Proposal
Owning work group name
Attachments
Committee Approval Date:
Please enter the date that the committee approved this IGproposal
Publishing Lead
Contributing or Reviewing Work Groups
Pharmacy
FHIR Development Project Insight ID
Scope of coverage
This guide will define the exchange methods and interoperability "standards" and specific use of FHIR resources to support Health Plan member-authorized exchange of Health Plan drug formulary information for members and third-party applications.
Content location
Proposed IG realm and code
Maintenance Plan
Short Description
Long Description
Involved parties
Expected implementations
Content sources
Example Scenarios
1. An Authenticated Member at a Health Plan will be able to use an OAuth2.0 authorization to permit a Third-Party Application to access the Health Plan's FHIR API to read the Plan's Prescription Drug Formulary.
IG Relationships
This guide will reference, where possible the "standards" defined by the Da Vinci Health Record exchange (HRex) Framework Implementation Guide which in turn will utilize prior work from Argonaut, US Core, and QI Core efforts for FHIR DSTU2, STU3, and R4.
This Guide will also be referenced by the Da Vinci Payer Data Exchange (PDex) Implementation Guide and will in turn reference the Validated Healthcare Directory Implementation Guide.
Timelines
Submit for STU Ballot (Second Ballot Cycle) 2019 Sep Early Ballot
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
