Imprimer
Courriel
FHIR North
- Attila Farkas
-
- Hors Ligne
- Messages : 128
il y a 8 ans 1 mois #1668
par Attila Farkas
Réponse de Attila Farkas sur le sujet FHIR North
Hey everyone - quick update on the progress since our last community call.
The new FHIR working group has been created on InfoCentral. I noticed that some of you have already started to join in so I think it is necessary to start talking about it even though not everything is in place just yet. As Yaron mentioned in the meeting minutes, we need to focus on the following aspects right away: Tools, Rules of Engagement, Governance and Operations. To this end we propose to:
1. Use the dedicated, new FHIR WG for everything FHIR - using the built in collaboration functions to schedule the meetings, leave notes, documents, webinars, videos, etc., and having dedicated forum threads for all the items we need to resolve for,
2. Enable all participants access to an SVN repository that will be fronting the Implementation Guide building tool that Lloyd has developed (basically collecting the source of truth through the spreadsheet or whatever new means the improved IG development tool uses – Lloyd, Andrew is going to need help in figuring this out).
3. Create overnight/on-demand builds on one of the Infoway servers rendering the content for public consumption through one of the websites (likely InfoScribe as a draft Standards development page).
4. Constantly educate, engage and lead the community with best practices of FHIR based development, including individual development environment, check-in rules, governance.
5. Create a Selection Guide that will track the bigger picture on how the work relates to the domains it touches (e.g. what use cases will be addressed by this work, what existing specs will be extended by this, what jurisdictions, who’s participating, etc.)
6. Start working on a roadmap of where this could be going and what the “official” promotion of complete work might look like. Now and in the future.
I propose moving the discussion over to the WG and create a sticky Forum thread for each of the following (defining details there):
Rules, roles and responsibilities:
Governance and operations (considerations):
I suggest that those interested in FHIR join the new group and sign up for notifications. An article will be posted in the October release of the Dispatch newsletter making a broader announcement to this effect.
I also suggest that we have a webinar in the near future to socialize some of the built in convenience features of the platform to optimize the work (e.g. you may not be aware that you can schedule impromptu videoconferences for free with any WG members without even knowing their personal details so we don't need a webex account to hold a meeting).
See you on the other side.
Attila
The new FHIR working group has been created on InfoCentral. I noticed that some of you have already started to join in so I think it is necessary to start talking about it even though not everything is in place just yet. As Yaron mentioned in the meeting minutes, we need to focus on the following aspects right away: Tools, Rules of Engagement, Governance and Operations. To this end we propose to:
1. Use the dedicated, new FHIR WG for everything FHIR - using the built in collaboration functions to schedule the meetings, leave notes, documents, webinars, videos, etc., and having dedicated forum threads for all the items we need to resolve for,
2. Enable all participants access to an SVN repository that will be fronting the Implementation Guide building tool that Lloyd has developed (basically collecting the source of truth through the spreadsheet or whatever new means the improved IG development tool uses – Lloyd, Andrew is going to need help in figuring this out).
3. Create overnight/on-demand builds on one of the Infoway servers rendering the content for public consumption through one of the websites (likely InfoScribe as a draft Standards development page).
4. Constantly educate, engage and lead the community with best practices of FHIR based development, including individual development environment, check-in rules, governance.
5. Create a Selection Guide that will track the bigger picture on how the work relates to the domains it touches (e.g. what use cases will be addressed by this work, what existing specs will be extended by this, what jurisdictions, who’s participating, etc.)
6. Start working on a roadmap of where this could be going and what the “official” promotion of complete work might look like. Now and in the future.
I propose moving the discussion over to the WG and create a sticky Forum thread for each of the following (defining details there):
Rules, roles and responsibilities:
- Infoway: SVN, build, publishing, collaboration platform support, orientation
- WG members: local build environment for all wanting to check in, contributors and owners of all development work
- FHIR Community experts: provide SME expertise and advice, continuous support with training, build and future direction
- Everyone: contribute to building the future roadmap of the Canadian FHIR eco-system, keeping as close alignment with International as possible
- WG forum and collaboration – Attila to set up on InfoCentral
- FHIR IG publication tool – used for developing and building of the publication package – Lloyd to recommend and work with Andrew to build and run
- SVN for version controlling the input “source of all truth” that drives the publication tool – Andrew, to come up with the on boarding process to allow all WG members disciplined access
- Integration build machine - Andrew to set it up
- A publishing webserver to host the nightly builds available through InfoScribe – Andrew and Attila
- Solution description – Standards Selection Framework – InfoScribe - Attila to create a few draft selection guides that will track the actual problem that's being solved for and provide overview for those wanting to reuse the work
Governance and operations (considerations):
- Mission statement – want to create an all-inclusive, transparent, easy to access and consume FHIR repository of Canadian content
- Access rights and obligations
- Rules of engagement
- Consensus process
- Definition of an IG maturity model
- Training and information sharing tracks – best practices – community experts
I suggest that those interested in FHIR join the new group and sign up for notifications. An article will be posted in the October release of the Dispatch newsletter making a broader announcement to this effect.
I also suggest that we have a webinar in the near future to socialize some of the built in convenience features of the platform to optimize the work (e.g. you may not be aware that you can schedule impromptu videoconferences for free with any WG members without even knowing their personal details so we don't need a webex account to hold a meeting).
See you on the other side.
Attila
Connexion ou Créer un compte pour participer à la conversation.
- Yaron Derman
-
- Hors Ligne
- Messages : 41
il y a 8 ans 1 mois #1653
par Yaron Derman
Réponse de Yaron Derman sur le sujet FHIR North
thank you to everyone for joining today's tcon - I look forward to working with everyone in the future to add to FHIR North
below are my draft notes - apologies if attendee names are (partially) missing, misspelled and for the lack of formatting in the notes below. Feel free to provide updates/modifications/additions to the notes.
Gavin and I will send out the next tcon date/time/call info using this space:
FHIR PR and CR tcon
Thursday, October 06, 2016
Attendees:
• BC MOH : Tony Stehle, Shamil Nizamov
• Jason Roberts (Intelliware)
• Igor Sirkovich (Ontario MOHLTC)
• Sierra Systems: Kris Lewis, Allen Leung, Peter
• Mihir Patel (Alberta Health)
• Finnie Flores (CIHI)
• Gevity Consulting: Lloyd MacKenzie, Gavin Tong, Matthew, Irena Roy
• Attila Farkas (Infoway)
• eHealth Ontario: Peter Bascom, Sue Schneider, Natalya Pogrebetsky, Yaron Derman, Janice Spence, Fariba Behzabi, Eric Labadie, Anil Patel , Fang Cao, Borna Jafarpour, Ken Sinn, Cindy Jiang, Rita Pyle, Duncan Johnstone
• James Agnew (University Health Network)
Agenda
BC
pharm, lab, CR, all based on v2 or v3
o Based on canadian data types
o No longer available in normative editions, on own for those interactions
o Slightly deviated from even from pan-Canadian data types
o Pharmanet is somewhat HL7 v2 compatible
See a strategic path with FHIR
o What resource to use and 90% of elements are optional so we will end up having different
o Need a profile for , ideally pan-Canadian, for both data contribution and consumption
o Patient resource is not enough to cover WHIC PRS
o One health authority implemented its own solution using its own flavour of the resources
Sierra Systems - WHIC Provider Registry System
o Started prototyping with HAPI
o Looking at the compatibility between object models between FHIR and PRS (PRS object model is a collaboration between several jurisdictions)
o Come up with a reference implementation that is feature comparable to the v3 interface
o Plan to continue supporting v3 and add FHIR (and have internal format)
o Support both contribution and consumption; gaps in the v3 contribution because colleges are submitting (80% alignment) and they don't support v3
eHealth Ontario
o Currently support pan-Canadian v3 for both client registry (update and search) and provider registry (search) and there is work on a v3 based consent override
o Also support HL7 v2 pix/pdq for client registry; provider registry also supports an HL7 v2 data-out file format
o Focus on consumption with FHIR before contribution
o Work underway to provide a FHIR dialect of PCR using the IHE PIXm/PDQm and PPR starting with the Argonaut Provider Directory profile argonautwiki.hl7.org/index.php?title=Implementation_Guide
Opportunities for collaboration
• 2 benefits of working together - much of the work will be the same atleast with the paths (not value sets); #2 - there will be extension territory for FHIR because it isn't part of the 80% - Canadian realm extensions
• Tooling, forums - Avoid duplication of work (mapping of terminology, data types) - consistent pan-Canadian equivalent for the datatypes and terminology; sharing of the mapping to
• Multiple Use Cases for Canadian collaboration:
1. Identifying mapping from v3 to FHIR, seeing where everything lives.
2. Look for a SMART-type profile from Canadian perspective
3. Create Canadian Version of DAF, w/ alignment w/ US-DAF
o Keep an eye on the US to stay as aligned as possible
o Infoway forum and tools to support collaboration
• Infoway has an environment that is based on subversion to share code
• ACTION: Attila will investigate if it can be made available outside of like this but it's not ready for a broader usage; subversion based but linked into Active Directory
• ACTION: Attila will set up a FHIR subgroup and/or project collab space, as well as a standards selection guide project with authors from each jurisdiction
New build tool allows for faster build process for publications (Lloyd - can you please share the URL?)
Next meeting:
o Agenda:
• Discuss governance - rules of the road of working together (e.g. when/what type of terms of reference, how to decide when/how to align/diverge, what to collaborate on first, etc)
• Gavin and Yaron volunteered to chair the working group in the near term
• ACTION: ALL - feel free to send other topics for discussion
below are my draft notes - apologies if attendee names are (partially) missing, misspelled and for the lack of formatting in the notes below. Feel free to provide updates/modifications/additions to the notes.
Gavin and I will send out the next tcon date/time/call info using this space:
FHIR PR and CR tcon
Thursday, October 06, 2016
Attendees:
• BC MOH : Tony Stehle, Shamil Nizamov
• Jason Roberts (Intelliware)
• Igor Sirkovich (Ontario MOHLTC)
• Sierra Systems: Kris Lewis, Allen Leung, Peter
• Mihir Patel (Alberta Health)
• Finnie Flores (CIHI)
• Gevity Consulting: Lloyd MacKenzie, Gavin Tong, Matthew, Irena Roy
• Attila Farkas (Infoway)
• eHealth Ontario: Peter Bascom, Sue Schneider, Natalya Pogrebetsky, Yaron Derman, Janice Spence, Fariba Behzabi, Eric Labadie, Anil Patel , Fang Cao, Borna Jafarpour, Ken Sinn, Cindy Jiang, Rita Pyle, Duncan Johnstone
• James Agnew (University Health Network)
Agenda
BC
pharm, lab, CR, all based on v2 or v3
o Based on canadian data types
o No longer available in normative editions, on own for those interactions
o Slightly deviated from even from pan-Canadian data types
o Pharmanet is somewhat HL7 v2 compatible
See a strategic path with FHIR
o What resource to use and 90% of elements are optional so we will end up having different
o Need a profile for , ideally pan-Canadian, for both data contribution and consumption
o Patient resource is not enough to cover WHIC PRS
o One health authority implemented its own solution using its own flavour of the resources
Sierra Systems - WHIC Provider Registry System
o Started prototyping with HAPI
o Looking at the compatibility between object models between FHIR and PRS (PRS object model is a collaboration between several jurisdictions)
o Come up with a reference implementation that is feature comparable to the v3 interface
o Plan to continue supporting v3 and add FHIR (and have internal format)
o Support both contribution and consumption; gaps in the v3 contribution because colleges are submitting (80% alignment) and they don't support v3
eHealth Ontario
o Currently support pan-Canadian v3 for both client registry (update and search) and provider registry (search) and there is work on a v3 based consent override
o Also support HL7 v2 pix/pdq for client registry; provider registry also supports an HL7 v2 data-out file format
o Focus on consumption with FHIR before contribution
o Work underway to provide a FHIR dialect of PCR using the IHE PIXm/PDQm and PPR starting with the Argonaut Provider Directory profile argonautwiki.hl7.org/index.php?title=Implementation_Guide
Opportunities for collaboration
• 2 benefits of working together - much of the work will be the same atleast with the paths (not value sets); #2 - there will be extension territory for FHIR because it isn't part of the 80% - Canadian realm extensions
• Tooling, forums - Avoid duplication of work (mapping of terminology, data types) - consistent pan-Canadian equivalent for the datatypes and terminology; sharing of the mapping to
• Multiple Use Cases for Canadian collaboration:
1. Identifying mapping from v3 to FHIR, seeing where everything lives.
2. Look for a SMART-type profile from Canadian perspective
3. Create Canadian Version of DAF, w/ alignment w/ US-DAF
o Keep an eye on the US to stay as aligned as possible
o Infoway forum and tools to support collaboration
• Infoway has an environment that is based on subversion to share code
• ACTION: Attila will investigate if it can be made available outside of like this but it's not ready for a broader usage; subversion based but linked into Active Directory
• ACTION: Attila will set up a FHIR subgroup and/or project collab space, as well as a standards selection guide project with authors from each jurisdiction
New build tool allows for faster build process for publications (Lloyd - can you please share the URL?)
Next meeting:
o Agenda:
• Discuss governance - rules of the road of working together (e.g. when/what type of terms of reference, how to decide when/how to align/diverge, what to collaborate on first, etc)
• Gavin and Yaron volunteered to chair the working group in the near term
• ACTION: ALL - feel free to send other topics for discussion
Connexion ou Créer un compte pour participer à la conversation.
- James Agnew
-
- Hors Ligne
- Messages : 7
il y a 8 ans 1 mois #1651
par James Agnew
Réponse de James Agnew sur le sujet FHIR North
Thanks Igor. I made it on, it turned out to be a Skype issue on my end. 
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
-
- Hors Ligne
- Messages : 181
il y a 8 ans 1 mois #1650
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet FHIR North
James, we have lots of people on the call. Try the number below:
Local dial-in number: 416-212-8011
Conference ID: 6417915
Local dial-in number: 416-212-8011
Conference ID: 6417915
Connexion ou Créer un compte pour participer à la conversation.
- James Agnew
-
- Hors Ligne
- Messages : 7
il y a 8 ans 1 mois #1649
par James Agnew
Réponse de James Agnew sur le sujet FHIR North
Is anyone else unable to get on this bridge?
Connexion ou Créer un compte pour participer à la conversation.
- Finnie Flores
-
- Hors Ligne
- Messages : 299
il y a 8 ans 1 mois #1634
par Finnie Flores
Réponse de Finnie Flores sur le sujet FHIR North
Thanks Yaron for organizing. I will listen as well.
Connexion ou Créer un compte pour participer à la conversation.
Twitter