This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

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

From HL7Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
+
This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR IG Proposal]]
 
[[Category:FHIR IG Proposal]]
[[Category:Pending FHIR IG Proposal]]
+
[[Category:Approved FHIR IG Proposal]]
  
  
Line 13: Line 13:
  
  
=Da Vinci Payer Data exchange formulary FHIR IG Proposal=
+
=Da Vinci Payer Data exchange drug formulary FHIR IG Proposal=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
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
+
Pharmacy
 
 
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i>Please enter the date that the committee approved this IGproposal</i>
+
2019-05-06
  
 
==Publishing Lead==
 
==Publishing Lead==
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
+
Financial Management, Attachments
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
Line 53: Line 52:
 
==Content location==
 
==Content location==
  
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
+
https://github.com/HL7/davinci-pdex-formulary
 
 
  
 
==Proposed IG realm and code==
 
==Proposed IG realm and code==
  
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
+
US/Davinci-PDex-drug-formulary
  
 
==Maintenance Plan==
 
==Maintenance Plan==
  
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources.  I.e. Who will be maintaining this IG content 5 years after it's published? -->
+
The Da Vinci project intends to provide ongoing support of this implementation guide.
  
 
==Short Description==
 
==Short Description==
  
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry- this is the sentence that will be used here: http://www.fhir.org/guides/registry.  This must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
 
  
 +
API-based data exchange to Third-Party Applications via Member-authorized sharing of Health Plan's Prescription Drug Formulary.
  
 
==Long Description==
 
==Long Description==
  
<!-- 1-2 paragraphs describing the purpose/scope of the IG in more detail for inclusion in the version history - this is content that will be used in your IG's equivalent of this: http://www.hl7.org/fhir/us/core/history.cfml.  Again, this must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
+
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==
 
==Involved parties==
  
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG **for inclusion in the version history**. Don't copy from the PSS - think about the specific language you want to appear in the registry. -->
+
This implementation guide has been developed by U.S. Payer organizations as part of the Da Vinci project.
 
 
  
 
==Expected implementations==
 
==Expected implementations==
Line 85: Line 85:
 
==Content sources==
 
==Content sources==
  
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
+
Requirements are drawn from payer and provider organizations as part of the Da Vinci initiative.
  
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
+
==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.
  
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
+
2. An unauthenticated third party may have access to the formulary (based on final requirements)
  
 
==IG Relationships==
 
==IG Relationships==
  
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
+
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==
 
==Timelines==
  
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
+
Submit for STU Ballot 2019 Sep Early Ballot
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==

Latest revision as of 20:15, 14 May 2019



Da Vinci Payer Data exchange drug formulary FHIR IG Proposal

Owning work group name

Pharmacy

Committee Approval Date:

2019-05-06

Publishing Lead

Contributing or Reviewing Work Groups

Financial Management, Attachments

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-drug-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