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

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

From HL7Wiki
Jump to navigation Jump to search
m (Financial Management)
 
(20 intermediate revisions by 2 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 32: Line 32:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
−
<i>Please enter the date that the committee approved this IGproposal</i>
+
 
 +
5/6/2019
  
 
==Publishing Lead==
 
==Publishing Lead==
  
−
<!--Name and email of the primary contact for the FMG with respect to publishing for this IG?-->
+
Mark Scrimshire, mark@ekivemark.com
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
−
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
+
Attachments, Patient Administration
−
* Work Group Name
 
−
* or link
 
−
* or "None"
 
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
Line 51: Line 49:
 
==Scope of coverage==
 
==Scope of coverage==
  
−
<!-- Define the full scope of coverage for the IG.  **(NOT the project - Do NOT copy from the PSS)**  The scope must be clearly delineated such that it does not overlap with any other existing or expected HL7 Int'l-maintained IG.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%".  Essentially, set the boundaries that would determine whether new content brought to HL7 should fall within the scope of your IG or somewhere else.  This should be 1 paragraph max.
+
This guide will define the exchange methods and interoperability "standards" and specific use of FHIR resources to support Health Plan member-authorized exchange of healthcare directory and pharmacy directory information for members and third-party applications.May also support an unsecured exchange of directory information (depending on final detailed requirements)
−
 
 
−
Scope should consider numerous aspects of breadth of scope, including:
 
−
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
−
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
−
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
−
* Locale: Country, region
 
−
-->
 
  
 
==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-plan-net
−
 
 
  
 
==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-plan-net
  
 
==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 Healthcare Service Network and Pharmacy Network.
  
 +
==Long Description==
  
−
==Long Description==
+
The PDex FHIR IG will support two scenarios:
  
−
<!-- 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. -->
+
1. 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 Healthcare Network Directory.  
 +
2. 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 Pharmacy Network Directory
  
 +
May also support an unsecured exchange of directory information (depending on final detailed requirements)
  
 
==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 94: Line 86:
 
==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==
  
 
<!-- 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.) -->
 
<!-- 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.) -->
 +
 +
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 Healthcare Network Directory.
 +
2. 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 Pharmacy Network Directory.
  
 
==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

OpenHotTopic.GIF

This page documents a Approved FHIR IG Proposal



Da Vinci Payer Data exchange Plan Network (PDex-plan-net) Implementation Guide


Owning work group name

Financial Management

Committee Approval Date:

5/6/2019

Publishing Lead

Mark Scrimshire, mark@ekivemark.com

Contributing or Reviewing Work Groups

Attachments, Patient Administration

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 healthcare directory and pharmacy directory information for members and third-party applications.May also support an unsecured exchange of directory information (depending on final detailed requirements)

Content location

https://github.com/HL7/davinci-pdex-plan-net

Proposed IG realm and code

US/Davinci-PDex-plan-net

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 Healthcare Service Network and Pharmacy Network.

Long Description

The PDex FHIR IG will support two scenarios:

1. 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 Healthcare Network Directory. 2. 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 Pharmacy Network Directory

May also support an unsecured exchange of directory information (depending on final detailed requirements)

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 Healthcare Network Directory. 2. 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 Pharmacy Network Directory.

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=Da_Vinci_PDex-plan-net_FHIR_IG_Proposal&oldid=165836"