Difference between revisions of "FHIR Escalation Process"
(Created page with "As part of FHIR development, we expect that individuals and organizations will occasionally have issues with decisions made by the groups developing FHIR content. This page atte...") |
|||
Line 15: | Line 15: | ||
## Mutually satisfactory resolution cannot be achieved within the work group | ## Mutually satisfactory resolution cannot be achieved within the work group | ||
# The concern may be escalated to the [[FHIR Governance Board]] (FGB) if: | # The concern may be escalated to the [[FHIR Governance Board]] (FGB) if: | ||
− | ## There is a concern about the | + | ## There is a concern about the precepts used to reach or justify the decision made by the Work Group and/or FMG |
+ | ## There is a concern about the prioritization and/or resource availability to the issue | ||
+ | # The concern can be escalated to MnM if: | ||
+ | ## The concern is with process (see process escalation below) | ||
# The concern may be escalated to the [[Technical Steering Committee]] (TSC) if: | # The concern may be escalated to the [[Technical Steering Committee]] (TSC) if: | ||
− | ## There is a concern about the process the FGB used when reaching their decision | + | ## There is a concern about the process the FMG or FGB used when reaching their decision |
=Process Issues= | =Process Issues= |
Revision as of 18:26, 3 December 2012
As part of FHIR development, we expect that individuals and organizations will occasionally have issues with decisions made by the groups developing FHIR content. This page attempts to define the process for resolving those issues. The process will be refined as the FHIR governance process continues to be developed.
Issues fall into one of two categories: Content Issues and Process Issues
Escalation occurs by emailing the list server of the appropriate group or by emailing one of their members (who will forward it to the appropriate list)
Content issues
A content issue is one where there's concern about the content in a particular resource or profile definition or some other aspect of the FHIR specification. In some cases, the response to a content issue may be that the content is defined as it is due to FHIR guidelines and processes. In some cases this may result in the identification of a Process Issue
Escalation process:
- Raise the issue with the Work Group responsible for the content (via ballot or list server)
- The concern may be escalated to the FHIR Management Group (FMG) if:
- No Work Group has ownership of the content
- The concern spans content from multiple work groups
- Mutually satisfactory resolution cannot be achieved within the work group
- The concern may be escalated to the FHIR Governance Board (FGB) if:
- There is a concern about the precepts used to reach or justify the decision made by the Work Group and/or FMG
- There is a concern about the prioritization and/or resource availability to the issue
- The concern can be escalated to MnM if:
- The concern is with process (see process escalation below)
- The concern may be escalated to the Technical Steering Committee (TSC) if:
- There is a concern about the process the FMG or FGB used when reaching their decision
Process Issues
Process issues cover concerns about the FHIR methodology itself including precepts, guidelines, QA processes, submission rules, etc. The concern might reflect methodology that exists or methodology that is proposed.
- Raise the issue with the FHIR Management Group (FMG)
- The FMG may consult or delegate the issue to the Methodology Group
- The concern may be escalated to the FHIR Governance Board (FGB) if:
- There is a concern about the process used by the FMG when reaching their decision
- The concern may be escalated to the Technical Steering Committee (TSC) if:
- There is a concern about the process the FGB used when reaching their decision