Topics discussed:

• John's answer to "how do we get more people involved" wasn't outreach, it was distribution. There's already an implementation in FHIR core, which means it's reachable from HAPI, and the same could be done for .NET. He's candid that it would never set the world on fire on performance — a naive implementation over HAPI's JPA schema is a baseline, not a contender — but that's the point: it's a gateway drug. Make the functionality work inside what people already run, and the ones who need speed will go looking for an analytics-focused implementation on their own.
• The same argument extended to bulk data. John's read on the last few years is blunt: plenty of people tried to bolt bulk export onto the side of a transactional FHIR server and it didn't work. The question is where those people go next, and whether SQL on FHIR has anything to offer them. Gino Canessa supplied the opening — there's an Argonaut project this year reconciling bulk data, bulk import and bulk publish into one IG, ending in a publication cycle. If the group wants notes about SQL in that spec, that cycle is the window, and it's sooner rather than later.
• John described how he runs connectathon tracks at home, which is more organised than most: a participant capability matrix filled in ahead of time, one row per system, so on the day you can look at the table and know who to talk to for a client. Applied here, the split is between people who want to pick up a runner and run ViewDefinitions on their own platform — self-contained — and people who want to poke at somebody else's server, which only works if the endpoints and auth details have been harvested in advance.
• Craig McClendon offered the week's best analogy for the current moment: semi-technical people are now building hyper-personalised apps and dashboards for themselves, and it reminds him of the era when a cheesy Visual Basic app somebody knocked together quietly became load-bearing for half a company's business process. Steve had a live example from the other direction — an enthusiastic interventional cardiologist turning up with an implementation of profile validation, which is not a small thing to write, and asking whether he could contribute it.