This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Product Director Page"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
=== Current Commercial Engagements === | === Current Commercial Engagements === | ||
− | * Australian Digital Health Agency: | + | * Australian Digital Health Agency: Provide support and tools to help Australia use FHIR effectively |
− | * Intermountain / HSPC: | + | * Intermountain / HSPC: Provide support and tools to help HSPC use FHIR effectively |
− | * DAF project: | + | * ONC via DAF project: Provide tooling support for publication of US artifacts |
− | * Kestral Computing: | + | * Kestral Computing: Support legacy code base & products, and provide strategic advice |
− | * RCPA: | + | * RCPA: General informatics & modelling advice for RCPA business processes |
+ | * Inpriva: Provide general advice around using FHIR effectively |
Revision as of 19:37, 15 January 2017
The FHIR Product Director is presently Grahame Grieve. This page gathers together the documentation relating to the Product Director role.
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
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
- Australian Digital Health Agency: Provide support and tools to help Australia use FHIR effectively
- Intermountain / HSPC: Provide support and tools to help HSPC use FHIR effectively
- ONC via DAF project: Provide tooling support for publication of US artifacts
- Kestral Computing: Support legacy code base & products, and provide strategic advice
- RCPA: General informatics & modelling advice for RCPA business processes
- Inpriva: Provide general advice around using FHIR effectively