Stream: CARIN IG for Blue Button®
Topic: 1/1/2021 Implementation
Charlie Filkins (Jul 16 2020 at 15:04):
Given that our company must implement a Patient Access API by 1/1/2021, I am wondering when the CARIN BB IG will be finalized for implementation? I see important changes coming in the CI build, but releasing code to production based on a CI build isn't something I'd recommend. Any guidance here is appreciated.
Thanks ... Charlie
Christopher Marchand (Jul 16 2020 at 15:29):
Charlie Filkins said:
Given that our company must implement a Patient Access API by 1/1/2021, I am wondering when the CARIN BB IG will be finalized for implementation? I see important changes coming in the CI build, but releasing code to production based on a CI build isn't something I'd recommend. Any guidance here is appreciated.
Thanks ... Charlie
I have the same question I posted in a separate thread earlier. ^
Ryan Howells (Jul 18 2020 at 21:50):
@Charlie Filkins @Christopher Marchand We are working through 237 ballot comments where we need to develop a response, disposition, convey that information to the HL7 community to gather feedback and ensure we have consensus, vote in the FM workgroup, and then publish them in a CI build. After Tuesday, we believe we'll be down to two buckets of open ticket items:
1) 49 tickets that relate to terminology which HTA and FM are working on resolving
2) 46 open tickets the CARIN IG for Blue Button® team to resolve with the HL7 community
FYI, we recently published an updated build here: https://build.fhir.org/ig/HL7/carin-bb/branches/master/index.html and anticipate another CI build by the end of July. You can view the latest status for each of our issues in HL7's JIRA. Anyone in the HL7 community can join our ballot reconciliation calls for the latest updates. You can find the call-in information here: https://confluence.hl7.org/display/CAR/CARIN+BB+IG+Ballot+Reconciliation. If you have specific question, please feel free to ask them here. Hope that helps!
Charlie Filkins (Aug 14 2020 at 16:03):
@Ryan Howells Do you expect that this next release will be the one of 1/1/2021 or should we stick to the latest published release (v0.1.0)?
Thanks ... Charlie
Ryan Howells (Aug 14 2020 at 17:54):
The continuous build (https://build.fhir.org/ig/HL7/carin-bb/toc.html) should be referenced as the most recent version because it incorporates the 180+ JIRA ticket items that have been approved by the HL7 community since the beginning of the year. Currently, that's v.0.3.1 but there will be at least couple of more CB versions published over the next few weeks as the HL7 JIRA tickets get discussed and approved. The published release from January is significantly out of date.
Ryan Harrison (Sep 09 2020 at 15:59):
The practical outcome is to, at a minimum, state your version of C4BB compatibility (in C4BB CapabilityStatement).
This will still confuse app developers, who will in all likelihood be expecting the latest release. Moreover, app clients are not required to assert their compatibility to the server. It's very possible to have an app client implicitly assume latest, while the server is using a prior version (as correctly indicated in the server CapabilityStatement).
For future reference, in interim release v0.1.3 (8 September 2020), the version convention is changed to: Release.Ballot.Version
This means that what Howells refered to as v.0.3.1 precedes v0.1.2 (because v0.1.2 uses the updated versioning convention).
Ryan Howells (Sep 15 2020 at 00:37):
Actually, v0.3.1 comes after v0.1.2. The reason why is because we recently needed to update the versioning to conform with HL7's standard. The HL7 version naming convention is: v.b.r
v = published version number. We are trying to get to "1", but are currently pre-publication of 1.0, so we are v = 0
b = ballot number for this version. CARIN IG for BB has been balloted once, so b = 1
r = revision number. The IG team can use this as they wish. This is the third publication of the CI build, so we have used 3.
So, the latest CI build is version to 0.1.3.
You can always find the most updated information about the open JIRA ticket items we have left associated with the IG here: https://confluence.hl7.org/pages/viewpage.action?pageId=91986623 or you can join our weekly public calls which are also located on the same page. We don't have much left. Here are the major items.
Finishing the definitions of Value Sets and Code Systems
Reviewing a few cardinality discrepancies between the IG and the Worksheet
Adding the vision and dental profiles to the worksheet
Final QA and some updates to the background section of the content
Jason Teeple (Sep 15 2020 at 10:59):
Hey @Ryan Howells was iterate search functionality intentionally taken out of the IG or is it missing? I don't remember where we landed.
Edit - including @Amol Vyas and @Pat Taylor
Ryan Harrison (Sep 16 2020 at 00:24):
@Ryan Howells
Actually, v0.3.1 comes after v0.1.2.
For after the HL7 versioning convention change, you're absolutely correct.
Your original post was on 14 Aug, before the versioning convention change.
As of 14 Aug, you'd be referring to
f339995 (tag: v0.3.1)
Sun Jul 26 16:45:32 2020 -0400
Which was the most recent release at that time.
This tag still exists, and will be confusing once the HL7 versioning convention catches up.
Also flagged in another thread: https://chat.fhir.org/#narrow/stream/204607-CARIN-IG.20for.20Blue.20Button.C2.AE/topic/build.20site
Ryan Howells (Sep 16 2020 at 12:04):
@Saul Kravitz Can you please make this change?
Saul Kravitz (Sep 16 2020 at 12:17):
(deleted)
Saul Kravitz (Sep 16 2020 at 13:25):
I've retagged as follows:
- 0.2.0 --> 0.1.1
- 0.3.0 --> deleted this one completely, since the only difference between 0.3.0 and 0.3.1 were very minor
- 0.3.1 --> 0.1.2
- 0.1.3 this is the current CI build
- 0.1.4 this will be the CI build
You can see all of the branches at:
https://build.fhir.org/ig/HL7/carin-bb/branches/
I need to figure out how to get rid of the builds of the older branches from the build site...
Ryan Harrison (Sep 17 2020 at 20:53):
@Saul Kravitz Thank you so much for re-tagging!
Last updated: Apr 12 2022 at 19:14 UTC
