CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®), published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.1.0-snapshot1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/carin-bb/ and changes regularly. See the Directory of published versions
Change Notes
CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) was developed under the CARIN Alliance.
Changes and Updates for Version 2.1.0 (from version 2.0.0)
The current official published version of CARIN BB for FHIR R4
- Changed base profile of the Patient, Coverage, Practitioner, Organization, and RelatedPerson to US Core 6.1 and added complies with requirements to US Core 3.1.1 where there was a profile in that version (FHIR-46374) *. Note: Most of the changes from US Core 3.1.1 to 6.1 are reductions in Must Support requirements, but there are a small number of breaking changes to note, including:
- The Coverage profile now requires the member identifier, if present, to have a type of
MB
from system http://terminology.hl7.org/CodeSystem/v2-0203
. The previous version of this profile did not have specific requirements for the member ID, though the example had a member ID that matched US Core 6.1 requirements.
- The Coverage profile now has an extensible binding to a ValueSet to Coverage.type, where there was no previous binding.
- The Organization and Practitioner profiles now have ID validation checks for NPI and CLIA numbers
- Added "Basis" profiles for all EOB types that identify all data requirements excluding financial data. This is made available for other IGs (e.g. Da Vinci PDex) that need communicate EOB information to parties other than the patient/member. This does not represent any change of conformance requirements for the existing EOB profiles. (FHIR-40999 and FHIR-40820)
- Corrected the ICD-9 CodeSystem url (changed from http://terminology.hl7.org/CodeSystem/icd9 to http://hl7.org/fhir/sid/icd-9-cm) (FHIR-41791)
- Corrected several invariants that either had the wrong context or an expression that returned false negatives if the element of interest had multiple iterations (FHIR-46276)
- Added a
masked
Data Absent Reason Code to the Diagnosis Codes ValueSet to allow for masking of sensitive diagnosis codes. (FHIR-40441)
- Reduced meta.profile requirements for all profiles. meta.profile still required, but the invariant checking for the profile url of this guide is no longer an error, but a informational warning. (FHIR-41498)
- Fixed the expression for the Service Start Date SearchParameter (FHIR-46376)
- Added the ability for the ExplanationOfBenefit.provider to be an Organization for the Oral EOB Profile (FHIR-44662)
- Removed the inclusion of codes in Benefit Payment Status from the (FHIR-40245)
- Updated guidance for the Service Date Search Parameter to state that the search parameter is to simplify the search in case the client does not know the specific date type to search for based on EOB type. (FHIR-41634)
- Clarified search removing the need for a patient search argument in the Capability Statement. (FHIR-41628)
- Improved the EOB Professional 1 example to include more realistic amounts and a payee. (FHIR-43464)
- Updated the menu structure adding support links. (FHIR-46270)
Changes and Updates for Version 2.0.0 (from version 1.1.0)
The current official published version of CARIN BB for FHIR R4
- Added Oral ExplanationOfBenefit profile and vision type to Professional NonClinician ExplanationOfBenefit profile (FHIR-34009, FHIR-27025, FHIR-37706, FHIR-37562, and FHIR-35146)
- Added orthodontics and prosthesis to Supporting Info Type ValueSet used as a discriminator for the EOB Oral profile supportingInfo slice discriminator (FHIR-34010)
- Added US Surface Codes for Oral ExplanationOfBenefit.item.subSite (FHIR-34089)
- Added Invariants requiring all ExplanationOfBenefit.supportingInfo[additionalBodySite] instances be referred to by at least one ExplanationOfBenefit.item and require a tooth number for line items where a surface code in ExplanationOfBenefit.item.subsite exists in Oral ExplanationOfBenefit profile (FHIR-34091)
- Changed cardinality of ExplanationOfBenefit.item from 0..* to 1..* in Base ExplanationOfBenefit profile requiring ExplanationOfBenefit for all all Resource ExplanationOfBenefit profiles (FHIR-34114) *
- Require item.location[x] to be only CodeableConcept in Professional and Oral ExplanationOfBenefit profiles (FHIR-32067) *
- Changed Professional NonClinician ExplanationOfBenefit item.location[x] from cardinality of 0..1 to 1..1 and added Must Support (FHIR-34148) *
- Changed item.serviced[x] and billablePeriod cardinality (FHIR-31639 and FHIR-36760) *
- Changed the Pharmacy Explanation Of Benefit profile serviced[x] to only be a date (FHIR-38668) *
- Added Must Support to ExplanationOfBenefit.item.serviced[x] leaf elements on the Outpatient Institutional and Professional NonClinician ExplanationOfBenefit profiles (FHIR-38669) *
- Moved ExplanationOfBenefit.total[benefitpaymentstatus] slice to ExplanationOfBenefit.adjudication[benefitpaymentstatus] (therefore not requiring an amount property) for Inpatient Institutional, Outpatient Institutional, Pharmacy, and Oral ExplanationOfBenefit profiles, changed the pattern to match other adjudication repetitions, and update the invariants appropriately(FHIR-33082, FHIR-37726, FHIR-38063, and FHIR-35358) *
- Changed codes term of "performing" provider to "rendering" provider in the Claim Care Team Role and Adjudication Discriminator CodeSystems and in Oral ExplanationOfBenefit and Professional NonClinician ExplanationOfBenefit profiles rendering provider network status (FHIR-37727) *
- Changed rendering network status from ExplanationOfBenefit.supportingInfo slice to ExplanationOfBenefit.adjudication slice in Oral ExplanationOfBenefit and Professional NonClinician ExplanationOfBenefit profiles and changed billing network status ExplanationOfBenefit.supportingInfo slice to ExplanationOfBenefit.adjudication slice in all non-abstract ExplanationOfBenefit profiles (FHIR-37728) *
- Changed provider "contracting network status" to provider "network status" by updating Adjudication Discriminator; changing the C4BBPayerProviderContractingStatus ValueSet to C4BBPayerProviderNetworkStatus ValueSet with `innetwork` and `outofnetwork` codes; removing "contracted" and "notcontracted" codes in Payer Adjudication Status ValueSet, and updating the `innetwork` and `outofnetwork` code definitions for applicability for the provider network status (FHIR-38059) *
- Updated the definition of Must Support to state "Health Plan API actors SHALL be capable of populating all data elements the payer maintains" which are marked as Must Support, and remove the requirement that "Consumer App actors SHOULD be capable of storing the information for other purposes" (FHIR-36675 and FHIR-35730)
- Changed ExplanationOfBenefit.adjudication and ExplanationOfBenefit.item.adjudication slicing from closed to open for all Resource ExplanationOfBenefit profiles (FHIR-34241)
- Add not-applicable code to Professional Procedure Codes ValueSet and Oral Procedure Code ValueSet for Professional NonClinician ExplanationOfBenefit profile (with Invariant allowing only if type = vision) and Oral (ExplanationOfBenefit.item.productOrService) (FHIR-33024)
- Removed Invariant that not allowing not-applicable code for Outpatient Institutional ExplanationOfBenefit profile item.productOrService (FHIR-32850)
- Changed Practitioner and Organization profiles identifier.type in the NPI slice to use the `NPI` from CodeSystem http://terminology.hl7.org/CodeSystem/v2-0203 (FHIR-35712) *
- Updated the Base Explanation Of Benefit profile to require the identifier to contain the unique claim id (FHIR-38660) *
- Added Non-emergency transport information to ExplanationOfBenefit.supportingInfo slices to the Professional NonClinician ExplanationOfBenefit profile along with invariant rules (FHIR-37615)
- Removed meta.profile requirements on Abstract base ExplanationOfBenefit profile (FHIR-34504)
- Added refillsAuthorized slice to ExplanationOfBenefit.supportingInfo of Pharmacy ExplanationOfBenefit profile (FHIR-33487)
- Added to rejectreason code to Adjudication Discriminator and changed ExplanationOfBenefit.item.adjudication denialreason slice to rejectreason with a fixed category code of rejectreason in Pharmacy Explanation Of Benefit profile. (FHIR-38062) *
- Changed payee.party cardinality from 1..1 to 0..1 and added invariant requiring payee.party if payee.type='other' in Base ExplanationOfBenefit profile and added new RelatedPerson profile as a reference option (FHIR-31699 and FHIR-37740)
- Added service-start-date search parameter and billable-period-start search parameter (FHIR-33165 and FHIR-34428)
- Added _id search parameter for all resources and change conformance expectation for Practitioner and Organization resources to SHOULD to allow for them to be supported as contained resources in Capability Statement with associated guidance and related the resources' meta.lastUpdated requirement (FHIR-38108 and FHIR-36676)
- Added guidance on the expectation of _include support and interpretation of _include=ExplanationOfBenefit:* to search Parameters page and Capability Statement including adding ExplanationOfBenefit:payee (FHIR-32982)
- Added a requirement in the General Guidance that servers SHALL include a CapabilityStatement that has a CapabilityStatement.instantiates specifying the CapabilityStatement in this specification (FHIR-35360)
- Updated the CapabilityStatement security section allowing unauthorized requests responses of HTTP 403 "Forbidden" or HTTP 404 "Not Found" in addition to the previously stated HTTP 401 "Unauthorized" (FHIR-35766)
- Moved ExplanationOfBenefit searches documentation from read interaction to search-type interaction in Capability Statement (FHIR-33176)
- Removed invalid invariant from Professional NonClinician ExplanationOfBenefit profile that required ExplanationOfBenefit.careTeam.provider to be an Organization reference when careTeam.role was 'site' ('site' not a code in the role ValueSet) (FHIR-31658)
- Corrected invalid invariant for the CareTeam qualification being from a specific CodeSystem when the type is rendering in the Abstract base ExplanationOfBenefit profile (FHIR-35889)
- Added paidbypatientcash, paidbypatientother, paidbypatienthealthaccount codes to Adjudication ValueSet and Adjudication CodeSystem (FHIR-33996 and FHIR-37831)
- Updated the url for the HCPCS Level II codes in C4BBEOBInstitutionalProcedureCodes (FHIR-37334)
- Removed the fixed meta.profile slice requirement including the full version and replaced with invariant requirements requiring a meta.profile with the major and minor version included in all non-abstract ExplanationOfBenefit profiles (to allow instances from different patch versions to still validate) (FHIR-34223)
- Updated from US Core 3.1.0 to 3.1.1. (FHIR-33177 and FHIR-35708)
- Modified security guidance in Security and Privacy Considerations page (FHIR-31693, FHIR-35729 and FHIR-35722)
- Changed display of code other from default value of "Provider to "Other" in Payee Type ValueSet (FHIR-34020)
- Added guidance for the use of the 11-digit NDC code for Pharmacy ExplanationOfBenefit profile item.productOrService and item.detail.productOrService (FHIR-32660)
- Corrected XPath expression for the service-date SearchParameter (FHIR-32843)
- Corrected invariant for Inpatient Institutional and Outpatient Institutional ExplanationOfBenefit profiles to allow other adjudication slices that do not have a category.code from C4BBAdjudication ValueSet (adjudicationamounttype slice) (FHIR-32978)
- Removed second extra repetition of meta.profile on all examples (FHIR-32428)
- Added clearer guidance on ExplanationOfBenefit.supportingInfo[servicefacility] and ExplanationOfBenefit.item.location[x] to Professional NonClinician ExplanationOfBenefit profile; ExplanationOfBenefit.item.location[x] and ExplanationOfBenefit.supportingInfo[typeofbill] to Inpatient Institutional and Outpatient Institutional ExplanationOfBenefit profiles (FHIR-34087)
- Removed references to PractitionerRole and Location from Background Relation to other IGs section (FHIR-33060)
- Added clearer description of ExplanationOfBenefit.related for Base ExplanationOfBenefit profile (FHIR-31411)
- Removed CodeSystems that were duplicative of those identified in terminology.hl7.org (THO). These removals are non-substantive as they do not change the CodeSystem url used in resource instance communication (FHIR-38285)
- Updated element short descriptions to be more meaningful for all all Resource profiles (FHIR-34091)
- Add guidance to the General Guidance section providing more information on considerations payers and consumer apps should make for understanding improving rendering of the Explanation Of Benefit data. A example explanation of benefit document with mapping to CPCDS data elements and profile paths is provided to assist consumer app developers in understanding the data elements and suggesting how payers might improve their API documentation for connecting system developers (FHIR-31069)
- Updated diagrams and CPCDS resources to match the changes on the latest version of this specification and added comparison of Explanation of Benefit dates (FHIR-35212, FHIR-34513, and FHIR-38661)
- Remove Must Support from Patient.address.district in the Patient profile (FHIR-35710)
- Added a note for implementers to all locally defined CodeSystems that may switch the to central terminology.hl7.org (THO) that the code system is subject to change in a future version (FHIR-37830)
- Added guidance regarding the definition of the payer id identifier to the Identifier Type CodeSystem and the Organization profile identifier payerid slice (FHIR-36771 and FHIR-36770)
- Made navigation and title updates FHIR-38692)
- Removed broken link reference to "API Resource Collection in Health (ARCH)" from the General Guidance page (FHIR-35956)
Changes and Updates for Version 1.1.0
STU Update of STU 1
Note: Items marked with an "*" are non-compatible with earlier versions - Existing data may not be valid against the new specification.