FHIR Chat · R4B publication plan

Stream: fmg

Topic: R4B publication plan

Josh Mandel (Feb 03 2022 at 17:40):

Is there a freeze date established for R4B ballot-related fixes? (My understanding is that 3/6 is the R5 May cycle content freeze, unrelated to R4B, right?)

Lloyd McKenzie (Feb 03 2022 at 17:53):

R5 freeze is driven by ballot timelines, which are fixed. R4B is driven by "when are the changes done" which is variable.

Josh Mandel (Feb 03 2022 at 17:54):

So... we're not picking a deadline? This creates a deadlock, where authors hold off on changes indefinitely, as long as there's something more pressing to tackle.

Lloyd McKenzie (Feb 03 2022 at 18:17):

We've declared a target of end of January to be ready to publish - which is now past. BR&R is 'close' to done and so is FHIR-I. We could declare a deadline, but if the BR&R changes or FHIR-I technical corrections aren't applied, there wouldn't be much point in shipping it on that deadline.

Josh Mandel (Feb 03 2022 at 19:58):

BR&R is 'close' to done

Do you know if that's the same "close" as 1 or 2 months ago? Or is it "closer"?

John Moehrke (Feb 03 2022 at 19:59):

kind of like "Tomorrow, always a day away."

Elliot Silver (Feb 03 2022 at 20:00):

I really wasn't expecting an Annie quote from you here.

John Moehrke (Feb 03 2022 at 20:01):

What is the process that Security WG can do to get the new security informative html pages migrated to R4B? There is nothing specific to R5, and there have been many improvements due to comments, and impact from Alissa.

Lloyd McKenzie (Feb 03 2022 at 20:55):

In general, R4B is only for technical corrections. The FMG might make an exception for urgent security guidance - you can raise it with the FMG.

"close" is definitely "closer". FHIR-I has applied a number of R4B issues (more than new ones it's identified ;) ) BR&R has made considerable progress on applying changes and getting tickets resolved.