Stream: implementers
Topic: R4B
Hans Buitendijk (Nov 29 2021 at 17:36):
What is the current target date for publication?
David Pyke (Nov 29 2021 at 18:42):
2022 sometime
Lloyd McKenzie (Nov 29 2021 at 23:15):
Reconciliation of BR&R content is near complete. FHIR-I still working on technical corrections. Based on current progress, I expect the publication request will go in sometime in January. @Rik Smithies, @Hugh Glover - would you agree?
Rik Smithies (Nov 29 2021 at 23:28):
seems reasonable yes
Lee Surprenant (Dec 06 2021 at 03:47):
Is someone working to restore the "latest" version at https://build.fhir.org/branches/R4B/ ? That used to have the latest changes but has been 404 Not Found for some time now.
Grahame Grieve (Dec 06 2021 at 03:52):
I guess that would be. I didn't know about that
Josh Mandel (Dec 06 2021 at 04:08):
We clear out branch builds that are inactive after 21 days -- https://github.com/FHIR/auto-ig-builder/blob/master/images/ci-build/publish#L35, and R4B is treaded like any other branch.
Looks like no activity on R4B for ~4 weeks, for what It's worth. I expect this will change as we gear up for publication?
Grahame Grieve (Dec 06 2021 at 04:32):
should do
Lee Surprenant (Dec 07 2021 at 12:59):
saw the R4B branch is back up. thanks grahame.
Grahame Grieve (Jan 11 2022 at 16:39):
test.fhir.org now supports R4B at http://test.fhir.org/r4b
Lee Surprenant (Feb 07 2022 at 15:04):
Is there an updated ETA for R4B publication? If not, is there a good list we can use to track to see the remaining work?
Lloyd McKenzie (Feb 07 2022 at 15:38):
In theory, publication request is a couple of weeks away and publication is a couple of weeks after that. So I expect it'll come out after R5 ballot opens. You can search on R4B tickets and the various Medication governance resource tickets.
Lee Surprenant (Feb 18 2022 at 14:14):
I'm a bit nervous that the two issues I opened related to unexpected breaking changes in R4B havn't even been triaged yet: FHIR-35961 and FHIR-35962
Lee Surprenant (Feb 18 2022 at 14:37):
searching by "Grouping in (R4B,MedDef)" shows just 5 unresolved issues.
but searching by "Raised in Version" = "R4B" yields 19 (and only one overlap with the above set).
23 if you count resolved with status=triaged:
- 4 submitted
- 1 waiting for input
- 18 triaged
Lee Surprenant (Feb 18 2022 at 14:38):
and
- 41 "Raised in version R4B" with a status of "Resolved - Change Required"
- 26 others with "Grouping in (R4B,MedDef)" with status "Resolved - Change Required"
Lee Surprenant (Feb 18 2022 at 14:39):
does all of that need to be completed before R4B publication or just some subset?
Rik Smithies (Feb 18 2022 at 14:49):
I can't explain those figures but all of the MedDef changes I am aware of for R4B are actually made (pre-applied), even if the votes have not yet approved them or the items are not updated. Some are "done" but awaiting commenter review, so are not really done. I am not sure who is in charge of the two breaking change ones you have raised though.
Lee Surprenant (Feb 18 2022 at 14:50):
yeah, I think they need to get triaged first before they even show up on any workgroups queue. not sure when that happens but its been a couple weeks so I thought I'd ask
Lloyd McKenzie (Feb 18 2022 at 15:00):
@Melva Peters typically handles triage. I've taken care of these two
Last updated: Apr 12 2022 at 19:14 UTC
