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
Line 76: Line 76:
 
==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. EHR and Payer organizations as part of the Da Vinci project.
 
 
  
 
==Expected implementations==
 
==Expected implementations==

Revision as of 14:01, 1 May 2019



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

This implementation guide has been developed by U.S. EHR and 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.

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

FMG Notes