Hello all,
Firstly thanks for everyone's attendance and participation on the call last Wednesday. Below are the notes and action items from the meeting as compiled by Yaron, Kenneth, Gavin and myself. If you have any additions or corrections please just respond to this thread.
GOALS
No objections raised to the stated goals - Results focussed topics with meaningful artefacts. No interest in participating long running theoretical exercises.
Direct questions & knowledge towards FHIR Chat, WGs
- should focus this group on Canadian experience
- good knowledge sharing could be useful to demonstrate how FHIR has been used in Canada
- Grass-roots group should be tied to actual implementation projects.
- practical projects, makes sense to be brought to the group
- conceptual pan-canadian specs, not so interested
STANDARD OPERATING PROCEDURES
No need for formal TOR
- Attila willing to share governance lessons learned for standards working groups
Meeting frequency
- 4th Wednesday of the month. Next meeting 25 January 2016
FHIR Working Group Forums will be continue to be used for discussion and individual threads will be used for Topics of Interest
Documentation Repository
- Continue to use Infocentral and leverage existing repositories for iGuides, specifications and resources
- mapping files
- presentations
- work plans
TOPICS OF INTEREST
Tooling - what exists, what needs to be developed, "cook books" for tooling installation and use (i.e. iGuides)
Existing tools list on InfoScribe site
infoscribe.infoway-inforoute.ca/display/IH/InfoScribe
PR/CR Specifications - V3 to FHIR mappings, resource specifications, Canadian extensions, OIDs etc ...
FHIR Business case
- For the executive audience, can leverage standards selection work on InfoScribe
- share examples where vendors have come up with solutions
- brain-dump proof-of-concept across the jurisdictions, particularly where they touch vendors
Solution Architecture - Develop conceptual and logical models for FHIR services. Implementation lessons learned, integration architecture etc
- defining what parts of the HIAL should be exposed, services that are required
- Have subgroup working on this
- Would like to see deliverable - lessons learned, encryption, authentication, OIDs/URIs management, how this impacts solution design
eReferral specification development
In-Flight projects
- when hitting Canadian-type problems, those are extensions that we would like to see in this FHIR group
- should be shared on central server for profiles/extensions; can be reposted.
OTHER
FHIR Management process not bound to ballot cycles
- can be brought through this group with concrete examples for concrete work
- Collective canadian voice might not carry that much weight
1) If need is identified, no point in delaying the request
2) If not implementing, could use this forum for those discussions
Action Items
- Post notes/minutes : Rod
- Solicit vendor participation : All members (update - two eReferral solution vendors are interested in participating and will join the forum and the WG calls)
- Schedule meetings: Yaron