Difference between revisions of "Template:FHIR IG Proposal"
Line 60: | Line 60: | ||
==Content location== | ==Content location== | ||
− | https://github.com/HL7/davinci- | + | https://github.com/HL7/davinci-pcd |
==Proposed IG realm and code== | ==Proposed IG realm and code== |
Revision as of 18:17, 2 July 2019
To use this Template:
- Search (or Go to) for a page with name like xxxxx_FHIR_IG_Proposal
- Click on the RED link to the (previously) undefined page in order to edit it.
- Type {{subst::Template:FHIR IG Proposal}} as the only content for the new page.
- Preview (if desired) to verify the reference was typed correctly
- "Save" the page.
- At this point, the contents of this template (with the following exceptions) will replace the substitution link. The exceptions are:
- These instructions will not appear.
- The small blue-font annotations about each entry will be replaced with an <!-- XML Comment --> saying the same thing. These comments are visible while editing, but they do not appear when the Wiki page is previewed or saved.
- At this point, the contents of this template (with the following exceptions) will replace the substitution link. The exceptions are:
- Re-edit the page to include the appropriate content in each of the sections
- Save again
IMPORTANT: DO NOT COPY & PASTE FROM YOUR PSS: The purpose of the elements in the IG Proposal is different. The IG Proposal should not talk about the "project" at all.
For additional guidance on considerations for IG creation, refer to FHIR IG Considerations
Payer Coverage Decision Exchange
Contents
- 1 Owning work group name
- 2 Committee Approval Date:
- 3 Publishing Lead
- 4 Contributing or Reviewing Work Groups
- 5 FHIR Development Project Insight ID
- 6 Scope of coverage
- 7 Content location
- 8 Proposed IG realm and code
- 9 Maintenance Plan
- 10 Short Description
- 11 Long Description
- 12 Involved parties
- 13 Expected implementations
- 14 Content sources
- 15 Example Scenarios
- 16 IG Relationships
- 17 Timelines
- 18 When IG Proposal Is Complete
- 19 FMG Notes
Owning work group name
Financial Management
Committee Approval Date:
Please enter the date that the committee approved this IGproposal
Publishing Lead
Paul Knapp
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-pcd
Proposed IG realm and code
US
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. Member-authorized sharing of treatment, conditions, authorizations, relevant guidelines and supporting documentation.
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.
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