This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Da Vinci PDex-formulary FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 29: Line 29:
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. -->
Attachments
+
Financial Management
 
 
 
==Committee Approval Date:==
 
==Committee Approval Date:==
 
<i>Please enter the date that the committee approved this IGproposal</i>
 
<i>Please enter the date that the committee approved this IGproposal</i>
Line 41: Line 40:
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
Pharmacy
+
Pharmacy, Atttachments
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
Line 73: Line 72:
  
 
Secure Member-authorized Exchange of information between Payers and Third-Party Applications using OAuth2.0 and FHIR APIs for information sharing via API of a Health Plan's Prescription Drug Formulary.
 
Secure Member-authorized Exchange of information between Payers and Third-Party Applications using OAuth2.0 and FHIR APIs for information sharing via API of a Health Plan's Prescription Drug Formulary.
 +
 +
May support the unsecured exchange of some formulary data as determined by detailed requirements analysis
  
 
==Involved parties==
 
==Involved parties==
  
This implementation guide has been developed by U.S. EHR and Payer organizations as part of the Da Vinci project.
+
This implementation guide has been developed by U.S. Payer organizations as part of the Da Vinci project.
  
 
==Expected implementations==
 
==Expected implementations==
Line 89: Line 90:
  
 
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.
 
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.
 +
 +
2. An unauthenticated third party may have access to the formulary (based on final requirements)
  
 
==IG Relationships==
 
==IG Relationships==
Line 98: Line 101:
 
==Timelines==
 
==Timelines==
  
Submit for STU Ballot (Second Ballot Cycle)
+
Submit for STU Ballot 2019 Sep Early Ballot
2019 Sep Early Ballot
 
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==

Revision as of 19:54, 1 May 2019



Da Vinci Payer Data exchange formulary FHIR IG Proposal

Owning work group name

Financial Management

Committee Approval Date:

Please enter the date that the committee approved this IGproposal

Publishing Lead

Contributing or Reviewing Work Groups

Pharmacy, Atttachments

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

https://github.com/HL7/davinci-pdex-formulary

Proposed IG realm and code

US/Davinci-PDex-formulary

Maintenance Plan

The Da Vinci project intends to provide ongoing support of this implementation guide.

Short Description

API-based data exchange to Third-Party Applications via Member-authorized sharing of Health Plan's Prescription Drug Formulary.

Long Description

The PDex-formulary FHIR IG will support the following scenario:

Secure Member-authorized Exchange of information between Payers and Third-Party Applications using OAuth2.0 and FHIR APIs for information sharing via API of a Health Plan's Prescription Drug Formulary.

May support the unsecured exchange of some formulary data as determined by detailed requirements analysis

Involved parties

This implementation guide has been developed by U.S. Payer organizations as part of the Da Vinci project.

Expected implementations

Content sources

Requirements are drawn from payer and provider organizations as part of the Da Vinci initiative.

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.

2. An unauthenticated third party may have access to the formulary (based on final requirements)

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 2019 Sep Early Ballot

When IG Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes