This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Product Director Page"
Jump to navigation
Jump to search
(migrate to Confluence and add links) |
|||
| (9 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | This content has been migrated to Confluence here: https://confluence.hl7.org/display/FHIR/FHIR+Product+Director+Page | ||
| + | |||
| + | |||
The FHIR Product Director is presently Grahame Grieve. This page gathers together the documentation relating to the Product Director role. | The FHIR Product Director is presently Grahame Grieve. This page gathers together the documentation relating to the Product Director role. | ||
| − | == Summary == | + | ==Summary== |
The role of the FHIR Product Director is: | The role of the FHIR Product Director is: | ||
| − | * Liaise with all parts of the FHIR community (including committees, HL7 management, stakeholders, members) to ensure continued development of FHIR product and community | + | *Liaise with all parts of the FHIR community (including committees, HL7 management, stakeholders, members) to ensure continued development of FHIR product and community |
| − | * Work with existing management and governance structures to build FHIR product and community | + | *Work with existing management and governance structures to build FHIR product and community |
| − | * Work with TSC to formalize the role and develop a job description | + | *Work with TSC to formalize the role and develop a job description |
| − | * Run the FHIR balloting and publishing process, and ensure business continuity around these arrangements (including documenting FHIR processes and procedures) | + | *Run the FHIR balloting and publishing process, and ensure business continuity around these arrangements (including documenting FHIR processes and procedures) |
| − | * Work with HL7 and the FHIR community to create the FHIR Foundation (http://fhir.org) | + | *Work with HL7 and the FHIR community to create the FHIR Foundation (http://fhir.org) |
| − | * Produce a monthly report documenting FHIR Product Director activities, issues and concerns | + | *Produce a monthly report documenting FHIR Product Director activities, issues and concerns |
[[FHIR Product Director Position Description]] | [[FHIR Product Director Position Description]] | ||
| − | == Product Manager Documentation == | + | ==Product Manager Documentation== |
| − | * [[Posting the FHIR specification on hl7.org]] | + | *[[Posting the FHIR specification on hl7.org]] |
| − | * [[FHIR IG QA process]] | + | *[[FHIR IG QA process]] |
| + | *[[Process for Publishing a FHIR IG]] | ||
| − | == Conflict of Interest Statement == | + | ==Conflict of Interest Statement== |
While I am FHIR product director, I also consult on a commercial basis with various implementation programs. This is useful because it keeps me intimately aware of implementation and adoption issues, but it also raises conflict of issue questions. | While I am FHIR product director, I also consult on a commercial basis with various implementation programs. This is useful because it keeps me intimately aware of implementation and adoption issues, but it also raises conflict of issue questions. | ||
My policy with regard to conflict of interest and industry engagement is: | My policy with regard to conflict of interest and industry engagement is: | ||
| − | |||
| − | |||
| − | |||
| − | === Current Commercial Engagements === | + | *As FHIR product director, I will meet with any implementation organization that has questions, comments or contributions about the FHIR specification or community |
| + | *I will meet such organizations under an NDA if required, as long as the NDA only concerns details about the other organization. I will not enter into any NDA regarding information sourced from the FHIR community | ||
| + | *If am engaged commercially with an organization, I will declare the nature of the engagement in the list below. The specifics of the engagement may be covered under NDA, but the fact of the engagement, and the summary of intent cannot be under NDA | ||
| + | |||
| + | ===Current Commercial Engagements=== | ||
Main roles: | Main roles: | ||
| − | |||
| − | |||
| − | + | *HL7 FHIR product director - management responsibilities and community communications | |
| − | * | + | *US ONC: general support for publishing FHIR Release 4 and bulk data implementation |
| − | * | + | |
| − | * | + | Minor engagements: |
| − | * | + | |
| − | * | + | *Australian Digital Health Agency: Consulting around interoperability, messaging, and vendor relationships |
| − | * | + | *Johns Hopkins: Provide general advice around directions of FHIR community and specifications |
| + | *Genie: Consulting around interoperability and cloud usage | ||
| + | *Regenstrief: Provide general advice around directions of FHIR community and specifications | ||
| + | *Accenture: Provide general advice around directions of FHIR community and specifications | ||
| + | *Odin Health: Provide general advice around directions of FHIR community and specifications | ||
| + | *Telus: technical support for validator and publisher on 2016May version of FHIR | ||
Latest revision as of 15:42, 8 November 2019
This content has been migrated to Confluence here: https://confluence.hl7.org/display/FHIR/FHIR+Product+Director+Page
The FHIR Product Director is presently Grahame Grieve. This page gathers together the documentation relating to the Product Director role.
Contents
Summary
The role of the FHIR Product Director is:
- Liaise with all parts of the FHIR community (including committees, HL7 management, stakeholders, members) to ensure continued development of FHIR product and community
- Work with existing management and governance structures to build FHIR product and community
- Work with TSC to formalize the role and develop a job description
- Run the FHIR balloting and publishing process, and ensure business continuity around these arrangements (including documenting FHIR processes and procedures)
- Work with HL7 and the FHIR community to create the FHIR Foundation (http://fhir.org)
- Produce a monthly report documenting FHIR Product Director activities, issues and concerns
FHIR Product Director Position Description
Product Manager Documentation
Conflict of Interest Statement
While I am FHIR product director, I also consult on a commercial basis with various implementation programs. This is useful because it keeps me intimately aware of implementation and adoption issues, but it also raises conflict of issue questions.
My policy with regard to conflict of interest and industry engagement is:
- As FHIR product director, I will meet with any implementation organization that has questions, comments or contributions about the FHIR specification or community
- I will meet such organizations under an NDA if required, as long as the NDA only concerns details about the other organization. I will not enter into any NDA regarding information sourced from the FHIR community
- If am engaged commercially with an organization, I will declare the nature of the engagement in the list below. The specifics of the engagement may be covered under NDA, but the fact of the engagement, and the summary of intent cannot be under NDA
Current Commercial Engagements
Main roles:
- HL7 FHIR product director - management responsibilities and community communications
- US ONC: general support for publishing FHIR Release 4 and bulk data implementation
Minor engagements:
- Australian Digital Health Agency: Consulting around interoperability, messaging, and vendor relationships
- Johns Hopkins: Provide general advice around directions of FHIR community and specifications
- Genie: Consulting around interoperability and cloud usage
- Regenstrief: Provide general advice around directions of FHIR community and specifications
- Accenture: Provide general advice around directions of FHIR community and specifications
- Odin Health: Provide general advice around directions of FHIR community and specifications
- Telus: technical support for validator and publisher on 2016May version of FHIR
