This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Template:FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 35: Line 35:
  
  
=PutProposedIGNameHere=
+
==Proposed IG Name==
<noinclude><small><i>
+
FHIR DME (Durable Medical Equipment) Orders
<span style="color:#0000FF">IG names should meet the following characteristics:</span>
 
* <span style="color:#0000FF">Title Case</span>
 
* <span style="color:#0000FF">U.S. English</span>
 
* <span style="color:#0000FF">Domain-friendly</span>
 
* <span style="color:#0000FF">Short</span>
 
* <span style="color:#0000FF">Clear</span>
 
* <span style="color:#0000FF">Unique</span>
 
* <span style="color:#0000FF">Avoid non-universal abbreviations (e.g. URL would be ok)</span>
 
* <span style="color:#0000FF">Be consistent with other similar IGs</span>
 
</i></small><br/></noinclude>
 
<!-- Resource names should meet the following characteristics:
 
* 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==
<noinclude><small><span style="color:#0000FF"><i>
+
Orders & Observations
The name of the work group that is proposed to have responsibility for developing and maintaining the IG.
 
</i></span></small><br/></noinclude>
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. -->
 
[[YourWorkGroupName]]
 
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
Line 69: Line 45:
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
<noinclude><small><span style="color:#0000FF"><i>
+
None
Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional)
 
</i></span></small><br/></noinclude>
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
 
* Work Group Name
 
* or link
 
* or "None"
 
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
<noinclude><small><span style="color:#0000FF"><i>
+
1496
Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (If submitted but not yet approved, just write “pending”.)  The link to the PSS template can be found [[http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc|here]]
 
</i></span></small><br/></noinclude>
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
  
 
==Scope of coverage==
 
==Scope of coverage==
<noinclude><small><i>
+
This project will define exchange methods, use of other interoperability "standards" (e.g. CDS Hooks and SMART on FHIR) and specific use of FHIR resources to effectively exchange orders for DME and associated supplies and medications, supporting clinical information (to qualify the order or establish medical necessity), provenance of the order and supporting clinical information, between the ordering provider and the intended supplier. Support will be provided for the communication of substantiating review (e.g. prior authorization, appropriate use, medical review services) information (e.g. tracking and authorization numbers)
<span style="color:#0000FF">Define the full scope of coverage for the IG.  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%".</span>
 
  
<span style="color:#0000FF">Scope should consider numerous aspects of breadth of scope, including:</span>
+
This project will utilize, where possible, existing profiles for each of the relevant FHIR releases (e.g. Argonaut for DSTU2, US Core for STU3, and US Core for R4). Creation of resources, extensions and profiles will be limited to situations here the current artifacts do not meet the requirements for DME ordering.
* <span style="color:#0000FF">Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)</span>
 
* <span style="color:#0000FF">Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research</span>
 
* <span style="color:#0000FF">Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)</span>
 
* <span style="color:#0000FF">Locale: Country, region</span>
 
  
</i></small><br/></noinclude>
+
The project team plans to work with existing FHIR artifacts where possible. If changes are necessary, the project team will work with the responsible Work Group to review and implement (via tracker items or new PSS) any necessary enhancements to base FHIR resources, extensions, and/or profiles.
<!-- Define the full scope of coverage for the IG.  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%"
 
  
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
 
-->
 
  
 
==IG Purpose==
 
==IG Purpose==
<noinclude><small><i>
+
Payers, Providers, Suppliers and Patients need the ability to order Durable Medical Equipment (DME) electronically to eliminate paper / FAX / verbal orders, ensure accurate ordering, minimize denials, reduce time required to supply patients with needed DME and related supplies. There is currently no well adopted standard for ordering DME equipment and supplies. An informal survey of the DME industry leaders conducted by a CMS contractor noted that over 90% of all orders are conducted by FAX or verbal exchanges and the fewer than 5% utilize any published standards (excluding NCPDP for items that can be ordered via the pharmacy networks). This implementation guide will provide a standard for adoption by providers and suppliers for the exchange of DME orders using FHIR based standards.
<span style="color:#0000FF">Why is this IG necessary?</span>
 
</i></small><br/></noinclude>
 
<!-- Why is this IG necessary? -->
 
  
 
==Content location==
 
==Content location==
<noinclude><small><i>
+
https://github.com/HL7/DMEOrders
<span style="color:#0000FF">What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name?</span>
 
</i></small><br/></noinclude>
 
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
 
  
  
 
==Proposed IG realm and code==
 
==Proposed IG realm and code==
 +
US
 
<noinclude><small><i>
 
<noinclude><small><i>
 
<span style="color:#0000FF">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</span>
 
<span style="color:#0000FF">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</span>

Revision as of 01:27, 18 February 2019

To use this Template:

  1. Search (or Go to) for a page with name like xxxxx_FHIR_IG_Proposal
  2. Click on the RED link to the (previously) undefined page in order to edit it.
  3. Type {{subst::Template:FHIR IG Proposal}} as the only content for the new page.
  4. Preview (if desired) to verify the reference was typed correctly
  5. "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.
  6. Re-edit the page to include the appropriate content in each of the sections
  7. Save again
The displayed contents below this line is the outline for a resource proposal


For additional guidance on considerations for IG creation, refer to FHIR IG Considerations


Proposed IG Name

FHIR DME (Durable Medical Equipment) Orders

Owning work group name

Orders & Observations

Committee Approval Date:

Please enter the date that the committee approved this IGproposal

Contributing or Reviewing Work Groups

None

FHIR Development Project Insight ID

1496

Scope of coverage

This project will define exchange methods, use of other interoperability "standards" (e.g. CDS Hooks and SMART on FHIR) and specific use of FHIR resources to effectively exchange orders for DME and associated supplies and medications, supporting clinical information (to qualify the order or establish medical necessity), provenance of the order and supporting clinical information, between the ordering provider and the intended supplier. Support will be provided for the communication of substantiating review (e.g. prior authorization, appropriate use, medical review services) information (e.g. tracking and authorization numbers)

This project will utilize, where possible, existing profiles for each of the relevant FHIR releases (e.g. Argonaut for DSTU2, US Core for STU3, and US Core for R4). Creation of resources, extensions and profiles will be limited to situations here the current artifacts do not meet the requirements for DME ordering.

The project team plans to work with existing FHIR artifacts where possible. If changes are necessary, the project team will work with the responsible Work Group to review and implement (via tracker items or new PSS) any necessary enhancements to base FHIR resources, extensions, and/or profiles.


IG Purpose

Payers, Providers, Suppliers and Patients need the ability to order Durable Medical Equipment (DME) electronically to eliminate paper / FAX / verbal orders, ensure accurate ordering, minimize denials, reduce time required to supply patients with needed DME and related supplies. There is currently no well adopted standard for ordering DME equipment and supplies. An informal survey of the DME industry leaders conducted by a CMS contractor noted that over 90% of all orders are conducted by FAX or verbal exchanges and the fewer than 5% utilize any published standards (excluding NCPDP for items that can be ordered via the pharmacy networks). This implementation guide will provide a standard for adoption by providers and suppliers for the exchange of DME orders using FHIR based standards.

Content location

https://github.com/HL7/DMEOrders


Proposed IG realm and code

US 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

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

Short Description

1-2 sentences describing the purpose/scope of the IG for inclusion in the registry


Long Description

1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history


Involved parties

1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history


Expected implementations

Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations

Content sources

List all of the specifications (beyond those in the standard list of source specifications) that you’re planning to consult

Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider?

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.)

IG Relationships

Are there any IGs this resource depends on or that depend on this IG?

Timelines

Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting

When IG Proposal Is Complete

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

FMG Notes