Stream: CARIN IG for Blue Button®
Topic: Announcement - CARIN BB STU2 Block-Vote-3
Corey Spears (Mar 29 2022 at 19:48):
As per the discussion on the 2022-03-29 Financial Management Workgroup call we are proposing the following block vote to be voted on 2022-04-05 Block-Vote-3 :
You may withdraw any item from the block vote by responding to this thread with the specific Key for the item you wish to withdraw or do so on the FM WG call prior to the vote.
Jira search string: project = "FHIR Specification Feedback" AND Specification = "US CARIN Blue Button (FHIR) [FHIR-us-carin-bb]" AND created >= 2021-12-01 AND Grouping = Block-Vote-3 ORDER BY updated DESC
| Issue key | Summary | Proposed Resolution | Reporter |
|---|---|---|---|
| FHIR-35030 | Redefined NPI slice issue | Not Persuasive | Ruby Nash |
| FHIR-35031 | Patient Must Support Issues Persuasive with Modification | Ruby Nash | |
| FHIR-35215 | Profiles (except Pharmacy). Service Facility Location should be .facility, not slice on add'l info | Not Persuasive | Mary Kay McDaniel |
| FHIR-35358 | supportingInfo:benefitpaymentstatus breaks the pattern established in other “supportingInfo slices” | Persuasive with Modification | Josh Mandel |
| FHIR-35360 | Document that a server advertises support with CapabilityStatement.instantiates | Persuasive | Josh Mandel |
| FHIR-35411 | Defining URL should be anchored in THO not hl7.org/fhir. Only those with required binding to a 'code' data type should be anchored in hl7.fhir.org.12 | Not Persuasive | Joan Harper |
| FHIR-35430 | Defining URL should be anchored in THO not hl7.org/fhir. Only those with required binding to a 'code' data type should be anchored in hl7.fhir.org.31 | Not Persuasive | Joan Harper |
@MaryKay McDaniel @Josh Mandel @Joan Harper @Ruby Nash @Rick Geimer
Additionally, we are looking to discuss and possibly vote on:
FHIR-35213 - Oral EOB. Remove .prescription reference to VisionPrescription
Not Persuasive with Mod.,
Will add wording to General Guidance section stating that constraints have only been applied to the scope defined by the IG. Data that is not part of this scope has not been constrained out, and as such, may be included by the Health Plan API. If a Health Plan API includes additional information, there SHALL be no expectation that client applications support the data in any way in order to be conformant with this specification.
Last updated: Apr 12 2022 at 19:14 UTC
