ExplanationOfBenefit has different mapping depending on the target profile that are now displayed separately in its documentation page.
Also, resource documentation pages now include an index to their sections at the beginning (they can be quite long so that helps navigating them).
(C/0c2fd5bb)
Observation.valueQuantity
with large values fixAttempts to POST Observations with a valueQuantity.value
greater than 999,999,999 used to fail, now it is accepted.
(H/e82fa8d8)
The insured name, address, contact information etc. are now rendered in a contained Patient resource that is referenced by Coverage.subscriber
. Previously they were rendered as custom extension, using a contained Patient is more standard. The custom extensions are preserved for backward compatibility.
When POSTing Coverage resource the system now also looks for a referenced contained Patient to get the insured details.
(H/1298a182)
Always populate supportingInformation.sequence
Don't output old Carin BB system URI in supportingInformation.code
when it is not necessary for backward compatibility
Add data absent reason extension to total.amount
when there is no value
(H/713e2590)
. . . for Coverage, Patient, Practitioner and Organization
(H/75d558c2)
This fixes potential out of memory errors when exporting lots of big DiagnosticReports or DocumentReferences
(H/4f73ef24)
The ExplanationOfBenefit mapping is now profile-specific, i.e. the underlying claim data is mapped to/from ExplanationOfBenefit differently depending on which of the Carin BB profile it corresponds to (inpatient, oral, outpatient, pharmacy, professional)
Update the care team codes in valueset http://hl7.org/fhir/us/carin-bb/STU2/ValueSet-C4BBClaimInstitutionalCareTeamRole.html
. Add new rendering
which replaces performing
. Left rendering
for backward compatibility.
Add service-start-date
search parameter
supportingInfo
updates:
http://hl7.org/fhir/us/carin-bb/STU2/CodeSystem-C4BBSupportingInfoType.html
. Keeping in the old codes for backward compatibility.adjudication
updates:
http://hl7.org/fhir/us/carin-bb/STU2/ValueSet-C4BBAdjudication.html
and http://hl7.org/fhir/us/carin-bb/STU2/ValueSet-C4BBAdjudicationCategoryDiscriminator.html
. Keeping in the old codes for backward compatibility.benefitpaymentstatus
slice output to adjudication, keeping in total
to maintain backward compatibility.benefitpaymentstatus
and renderingnetworkstatus
based on profile requirements.hsapaid
to paidbypatienthealthaccount
and denialreason
to adjustmentreason
. Keeping the old slices for backward compatibility.Documentation Updates:
In the Practitioner and (contained) Organization resources the npi
identifier type system uri is now http://terminology.hl7.org/CodeSystem/v2-0203
. Keeping also the old type system uri for backward compatibilty.
(H/97f43c0a)
Output files are created directly compressed instead of being first created uncompressed and then compressed.
(H/3edca3e2)
When the binding is extensible (for example R4 Encounter.class) if the underlying data cannot be mapped to the bound value set the Coding is now set to the available data as-is - previously it was not set. This mimics the existing behavior for CodeableConcepts bound to an extensible value set.
(H/a46f6900)
Breaking change
POSTed JSON data is processed with a new JSON parser that is around 8 times faster than the old.
The new parser is more restrictive (and more secure...) than the old one:
JSON using single quote as property and string delimiter is no longer accepted
Special characters (e.g. new lines) in JSON strings must always be properly escaped - previously they were also accepted as-is
Commas after the last element of an object or array now cause an error
(H/07512f0a)
Previously such resources where (wrongly) considered non-complaint and so not tagged with their US Core profile URL (and removed if the endpoint is in 'strict compliance' mode)
(H/49bf5546)
performer
standard search parameter to the Observation resource(H/68198b5b)
Support the :iterate
modifier for the _include
parameter - see the specifications.
(H/412a9f29)
_lastUpdated
standard search parameter to the DocumentReference resource(H/18c63cd4, H/daf037e6)
The profile URLs placed in the meta.profile
elements now include the version number - e.g. http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance|3.1.1
instead of http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance
.
(H/e83bdc13)
reference
search parameter to reference-concept
Breaking change
ValueSet reference
is defined in the base specs to search by the code system, whereas what we search for is the entire system + code
(H/42087ee2)