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

Difference between revisions of "Da Vinci Payer Coverage Decision FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(14 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 15: Line 15:
 
=PutProposedIGNameHere=
 
=PutProposedIGNameHere=
  
<!-- Resource names should meet the following characteristics:
+
Payer Coverage Decision Exchange
* Title Case
 
* U.S. English
 
* Domain-friendly
 
* Short
 
* Clear
 
* Unique
 
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
* Be consistent with other similar IGs
 
-->
 
  
 
==Owning work group name==
 
==Owning work group name==
Line 44: Line 35:
 
==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 IG will provide a FHIR standard for exchanging, at member request, current treatments/support,conditions, guidelines (commercial), and supporting documentation for a payer member with a new
 
+
payer when the member moves from one covered payer to another. This is to support the "treatment portability" described in the CMS Interoperability NPRM from March 3, 2019. The plan is to use the
Scope should consider numerous aspects of breadth of scope, including:
+
CarePlan resource as the basis for associating the information with regard to current therapy.
* 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-pcovex
 
 
  
 
==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-PCD
  
 
==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? -->
+
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. -->
+
Payer coverage decision exchange will promote continuity of treatment when a member moves from one covered payer to another without increasing provider burden or cost to the member. This IG enables member-authorized
 
+
sharing of treatment, conditions, authorizations, relevant guidelines and supporting documentation from an original payer to a new payer when a patient changes coverage plans.
  
 
==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 Payer Coverage Decision (PCD) Exchange FHIR IG will support the secure Member-authorized exchange of information between a current and prior payer regarding ongoing problems/treatments 1)
 
+
The exchange will use OAuth2.0 and FHIR APIs for information sharing 2) Information to exchange will include the "careplan" for any current conditions/treatments 3) Relevant conditions 4) Relevant
 +
guidelines (reference to commercially available guidelines) 5) Any relevant prior-authorizations, with any remaining scope/duration (e.g. number of authorized session left) 6) relevant past or current medical history used to support coverage of the current treatment 7) other information as appropriate
  
 
==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==
  
<!--Provide named implementations if possible - ideally provide multiple independent implementations. -->
+
Da Vinci payer members in response to the details in the CMS final rule
  
 
==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 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. General: An Authenticated Member at their old Health Plan will be able to use an OAuth2.0 authorization to permit their New Health Plan to access the old Health Plan's FHIR API to access the
 +
member's payer coverage decisions using a superset of profiles defined in this guide, US Core and Da Vinci Health Record Exchange (HRex) Profiles. 2. Specific: A member that is currently receiving home oxygen therapy will be able to exchange supporting documentation form the prior payer to the new payer to avoid, where possible, discontinuation of the current treatment, payment out of pocket, and/or need for a provider to submit documentation that is currently available to the previous plan.
  
<!-- 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. Specific: A member that is currently receiving step therapy for diabetes will be able to exchange supporting decisions, prior treatment, guidelines and documentation form the prior payer to the new payer to avoid, where possible, a need to restart treatment that has deemed ineffective and/or need for a provider to submit documentation that is currently available to the previous plan.
  
 
==IG Relationships==
 
==IG Relationships==
  
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
+
This project will reference, where possible the "standards" defined by the Health Record exchange (HRex) Framework Implementation Guide which in turn will utilize prior work from US Core and R4.
 +
In addition, this guide will refer to the Payer Data Exchange (PDex) Implementation Guide since it uses the same member directed exchange methods and clinical content standards for the Payer to Payer
 +
exchange described in PDex.
  
 
==Timelines==
 
==Timelines==
  
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
+
Submit for STU Ballot for 2019 Sep Ballot cycle
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==

Latest revision as of 19:58, 15 July 2019



PutProposedIGNameHere

Payer Coverage Decision Exchange

Owning work group name

Financial Management

Committee Approval Date:

Approved by FM on 7/2/2019

Publishing Lead

Paul Knapp pknapp@pknapp.com

Contributing or Reviewing Work Groups

Attachments

FHIR Development Project Insight ID

1515

Scope of coverage

This IG will provide a FHIR standard for exchanging, at member request, current treatments/support,conditions, guidelines (commercial), and supporting documentation for a payer member with a new payer when the member moves from one covered payer to another. This is to support the "treatment portability" described in the CMS Interoperability NPRM from March 3, 2019. The plan is to use the CarePlan resource as the basis for associating the information with regard to current therapy.

Content location

https://github.com/HL7/davinci-pcovex

Proposed IG realm and code

US/DaVinci-PCD

Maintenance Plan

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

Short Description

Payer coverage decision exchange will promote continuity of treatment when a member moves from one covered payer to another without increasing provider burden or cost to the member. This IG enables member-authorized sharing of treatment, conditions, authorizations, relevant guidelines and supporting documentation from an original payer to a new payer when a patient changes coverage plans.

Long Description

The Payer Coverage Decision (PCD) Exchange FHIR IG will support the secure Member-authorized exchange of information between a current and prior payer regarding ongoing problems/treatments 1) The exchange will use OAuth2.0 and FHIR APIs for information sharing 2) Information to exchange will include the "careplan" for any current conditions/treatments 3) Relevant conditions 4) Relevant guidelines (reference to commercially available guidelines) 5) Any relevant prior-authorizations, with any remaining scope/duration (e.g. number of authorized session left) 6) relevant past or current medical history used to support coverage of the current treatment 7) other information as appropriate

Involved parties

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

Expected implementations

Da Vinci payer members in response to the details in the CMS final rule

Content sources

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

Example Scenarios

1. General: An Authenticated Member at their old Health Plan will be able to use an OAuth2.0 authorization to permit their New Health Plan to access the old Health Plan's FHIR API to access the member's payer coverage decisions using a superset of profiles defined in this guide, US Core and Da Vinci Health Record Exchange (HRex) Profiles. 2. Specific: A member that is currently receiving home oxygen therapy will be able to exchange supporting documentation form the prior payer to the new payer to avoid, where possible, discontinuation of the current treatment, payment out of pocket, and/or need for a provider to submit documentation that is currently available to the previous plan.

2. Specific: A member that is currently receiving step therapy for diabetes will be able to exchange supporting decisions, prior treatment, guidelines and documentation form the prior payer to the new payer to avoid, where possible, a need to restart treatment that has deemed ineffective and/or need for a provider to submit documentation that is currently available to the previous plan.

IG Relationships

This project will reference, where possible the "standards" defined by the Health Record exchange (HRex) Framework Implementation Guide which in turn will utilize prior work from US Core and R4. In addition, this guide will refer to the Payer Data Exchange (PDex) Implementation Guide since it uses the same member directed exchange methods and clinical content standards for the Payer to Payer exchange described in PDex.

Timelines

Submit for STU Ballot for 2019 Sep Ballot cycle

When IG Proposal Is Complete

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

FMG Notes