I'll start this month's report with a photo from Dave Bronkhart's keynote at the annual SPM event:
Rallying cry from @ePatientDave: "Don't get stuck being a proud expert on the obsolete model. Enable radically disruptive data spigots. Set yourself on #FHIR!" #PatientExperience #PatientsIncluded #pinksocks pic.twitter.com/oFGbigmOQy— Irma Rastegayeva at #xMed Innovation Catalyst (@IrmaRaste) November 5, 2018
Check the top left slide. Dave will be at DevDays in Amsterdam, so I'll include a full report on what he's saying in the next report.
SNOMED International held a Day of the Dev session in Vancouver, Canada focused on helping application developers use FHIR terminology services to leverage the power of SNOMED CT. The 1-day event was a mix of education and hands on exercises with over 45 attendees. Exercises included using terminology services to help in guiding code selection and in providing decision support.
Foundation Member James Agnew visited Chile for "Tech Connect", organised by CENS, a semi-autonomous-academic organization tasked with promoting a ehealth in Chile, including interoperability. James reports:
The event was a very interesting one. CENS broke the event into 3 tracks: Patient, Medication, and Referral Management. Like a standard FHIR connectathon, they had track cards at each table and track leads running the tracks. However, very different from any other FHIR connectathon event I've been to: They had a series of tasks for each track, ranging from easy to hard. Participants had to go through the tasks for their track, and submit their results to a server they had built (a modified HAPI server) that logged all submissions and gave them an evaluation UI where a judge could evaluate the data sent in by the participant teams.
The tasks included some pretty hard stuff. The final challenge in the referral track required the creation of a custom Search Parameter for example. At the end, they had a few judges who looked at the results in their evaluation tool and scored the participants. The winning team are getting tickets to DevDays Seattle as a prize.
(Now there's a serious prize, generously supported by Foundation support Intersystems)
I visited Argentina for a series of meetings around FHIR, organised by Foundation member Diego Kaminker. I met with Fernando Campos' team at the Italian Hospital, the Department of Health, and CALILAB 2018.
The Argentine community is actively developing several FHIR based solutions:
The Dept of Health meeting included a connectathon using a HAPI derived server acting as a PIX end-point (spanish documentation). The Argentine community is active and well-informed (as you'd expect, given that both Diego and Fernando are very active in HL7 education, and manage the on-line FHIR Fundamentals course). There was a particularly Argentine flavor in the background of the workshop - check the following video taken looking out the window during the connectathon:
The 3rd round of FHIR Normative balloting opened today, for HL7 members. This round of balloting is specifically focused on 5 specific substantive changes made to the normative parts of the FHIR ballot:
Balloting includes anyone who already balloted in rounds #1 and #2, and is closed to that group.
In the mean time, preparation of the final version of R4 is proceeding at http://build.fhir.org, and we'll be doing a call for QA shortly.
Carequality are creating some new workgroups to extend their technical framework to cover FHIR interfaces as well. According to their announcement:
As adoption of HL7’s Fast Healthcare Interoperability Resources (FHIR®) Specification continues to gain momentum throughout the healthcare industry, we at Carequality believe we’re in a great position to help advance this cause. With much of the healthcare industry either starting to implement FHIR at some level, or planning to do so, we believe it’s a good time to start thinking ahead to the type of broad, nationwide deployments that Carequality governance can enable. We are, therefore, adding FHIR-Based Exchange to our existing Query-Based Document Exchange Use Case model, and are seeking volunteers for two new workgroups that will extend Carequality’s governance Framework to the FHIR exchange ecosystem
This was reported in the media as:
The Carequality unit of the Sequoia Project is seeking help in developing a governance structure for the FHIR data exchange standard
Note the subtle change of emphasis here.... expressed this way, some feathers got ruffled. So watch out for this in the media - it's hard for them to convey things without creating erroneous impressions. Anyway, I asked FHIR Foundation member Didi Davis what exactly Carequality was going to be doing with FHIR, and she responded:
I am attaching the Carequality FHIR-based Exchange Use Case Charter document distributed to workgroup members this week. The workgroup is open to all Carequality members or non-members. We would welcome the FHIR community to participate, but I know time is limited for all of us.
Feel free to contact me if you have any questions as I am on both of the workgroups and happy help as needed. This really is a consensus based way of creating an IG that the Carequality Policy Framework can enable for all networks who are implementers. These implementers exchange >11 Million documents per month today in production across the US. Carequality plans to use these workgroups to define the requirements pointing to existing standards and adding policy and other requiements where necessary to open the pipes to allow exchange using FHIR based plumbing as well.
As Didi says... time is indeed limited. I'm glad to see Carequality taking on this problem, but it does overlap with other related FHIR community activities - either inside or outside HL7 (HSPC, the CARIN alliance, Direct Trust, Commonwell, etc. Carequality acknowledge this issue in their workgroup charter however that doesn't solve it - I encourage FHIR foundation members in USA to devote any time they have to keeping informed of these various activities and identifying overlaps and alerting the relevant organizations where they diverge in the overlaps.