In some cases it was output as a timingDateTime
, that is non-compliant - now fixed to always use either timingPeriod
or timingDate
.
(H/d6d40bc7)
When mapping to FHIR populate Immunization.manufacturer.display
with the underlying display value and Immunization.manufacturer.identifier.value
with the underlying code
Keep the mapping to a contained Organization resource for backward compatibility, populating also Organization.identifier.value
with the underlying code
When mapping from FHIR use first Immunization.manufacturer.display
and Immunization.manufacturer.identifier.code
, look at the referenced contained organization only if Immunization.manufacturer.display
is empty
When mapping from FHIR create the manufacturer term in the default term namespace - not to 'pollute' the CareEvolution namespace
(H/175d5a31)
Consider only our own custom http://careevolution.com/fhirextensions#coding
extension and not other extensions with a coding value
Use the extension userSelected
value (if present) also when there is no main code
(H/db40ab63)
. . . for patients that did not have an associated user that last modified it.
(H/33472c4a)
Meta.source
and the corresponding DSTU2/STU3 extensionThis allow endpoints to revert to the old behavior where Meta.source
or the corresponding extension (for DSTU2/STU3) was not populated.
(H/b4af7db0)
It caused weird errors when updating certain resources (notably Patient)
(H/56f0f079)
If-None-Exist
on create, update, or in a transactionOur server does not support conditional create (yet), so it is better to fail instead of just ignoring that header / element.
(H/42871b25)
Previously Basic resources (representing referrals) did not have a corresponding Provenance.
(H/8e5a839e)
Added explicit documentation to some search parameters that either lacked it or whose standard documentation did not really apply to our case (eg MedicationDispense.context being 'Returns dispenses with a specific context (episode or episode of care)' whereas in our implementation it is always and only encounters)
(H/c3250e75)
Bulk export crashed due to a problem introduced by the 'Populate meta.source' change.
(H/68cafbe9)
Consumers 29.20.3, HIEBus 29.19.1
Consumers 29.20.2, HIEBus 29.19.1
Consumers 29.20.1, HIEBus 29.19.1
Consumers 29.20.0, HIEBus 29.19.0
The Put, Post, Delete and Operation tabs of the FHIR test page ([WebClient base]/fhir/search
) have a new 'Source' drop-down allowing the select one of the available sources and pass it in the request URL.
(C/0c865bcf)
Processing transaction with many resources of the same type (e.g. a lot of Observations) is now considerably faster.
(H/29f0b6c4)
meta.source
meta.source
in R4 resources and its corresponding http://hl7.org/fhir/4.0/StructureDefinition/extension-meta.source
extension in STU3/R4 resources is now populated with the resource source URI.
(H/988dc74c)
Reduced the number of database queries generated when processing transactions
(H/76b2f583)
Provenance.occurredDateTime
and Provenance.recorded
for patientsThey always used only the patient creation date, without considering subsequent updates, now fixed.
(H/1ff79946)
Clients specify the source when POSTing / PUTing / DELETEing data with (in order of priority):
specifying the source URI using the _source
parameter in the request URL
sending the source URI in the custom x-ce-source
HTTP header;
setting the POSTed / PUTed resource meta.source
element to the source URI;
when POSTin / PUTing a Patient or Practitioner using the source URI as the system of one of its identifiers
When POSTing a transaction or batch Bundle method (3) above looks first in Bundle.meta
, if no source is specified there it then looks at the meta element of all resources. If different resources specify different sources an error is returned.
Similarly, when POSTing a transaction Bundle method (4) looks at all the Patient and Practitioner resources contained in the bundle, and returns an error if there are conflicting sources.
meta.source
is available only from FHIR R4, for FHIR DSTU2 and STU3 clients can use the corresponding meta
extension http://hl7.org/fhir/4.0/StructureDefinition/extension-meta.source
.
The server has an internal configuration listing the possible sources for each connecting user. There is a new operation $list-sources
that returns the list these sources. Attempts to specify a source that is not in this list results in an error.
The common standard search parameter _source
now works for all resources supporting a source.
Searching by _source
and provenance-agent
now works also for the Practitioner resource, previously provenance-agent
was not implemented.
(H/7d204f87)
Consumers 29.19.2, HIEBus 29.18.0
Consumers 29.19.1, HIEBus 29.18.0
Consumers 29.19.0, HIEBus 29.18.0
Previously only custom search parameter had a description, now also all the standard search parameter have one (matching the description in the FHIR specifications)
(H/02a90276)
Provenance.occurred
and Provenance.recorded
for some resourcesThe Provenance.occurred
and Provenance.recorded
element values could be not correct because they did not consider all the possible changes for CareTeam, CarePlan, ProcedureRequest and ServiceRequest resources - now fixed.
(H/d3d0cbf4)
prefer
header on searchesSee 'Unknown and unsupported parameters' in the specifications.
(H/72e64f8f)
Make sure that ExplanationOfBenefit.item.sequence
and Claim.item.sequence
are always populated (with an increasing counter if there is no corresponding data in the CareEvolution model)
Update the R4 ExplanationOfBenefit.supportingInfo
mapping so that we output the Carin BB slices correctly when there are multiple medications on a claim. The DaysSupplied, RefillNum, and DawCode (DispenseAsWritten) values should all be the same if there are multiple medications. We will not output these slices if they do not match. We output once per slice if values match.
(H/729f599e)
It resulted in an error 500 returned to the client and a logged InvalidCastException
.
(H/72356df2)
:missing
modifier on applicable search parametersPreviously the :missing
modifier worked only on reference search parameters, now it works also for strings, tokens and dates.
(H/a50cef9f)
meta.profile
is now populated also for Argonaut-complaint DSTU2 resources
Observation.meta.profile
discriminate between labs, vital signs and smoking status
fixed the profile URI for STU3 CarePlan and STU3 Immunization
(H/60e23cd5)
E.G. a search like [base]/Person?_id=48a1efae-51b1-ec11-8112-f8f21e213b20&_include=:missingPerson:relatedpatient
caused a crash (error 500), now retrurns a 400 with an explanation of the wrong _include
.
(H/26b64cbe)
_since
(H/8e27e5d9, H/8d2dc3a5)
The (custom) bulk export parameter provenance-agent-identifier
now supports multiple comma-separated values.
There is a new (again, custom) bulk export parameter _recordAuthorityCodes
, it accepts a comma-separated list of record authority codes used
to filter the output (it complements the existing _recordAuthorityCode
parameter that accepts only a single value).
(H/a1400c8a, H/1b3d41b3)
(H/9f8182e1, H/e4f8e4ee, H/fac3e7af)
Consumers 29.18.2, HIEBus 29.17.0
Consumers 29.18.1, HIEBus 29.17.0
Consumers 29.18.0, HIEBus 29.17.0
(C/79eb9457)
The software version returned in the CapabilityStatement / Conformance and displayed in the /fhir auto-generated documentation page now matches the versions listed in the release notes.
(C/16dbf1de)
entry.fullUrl
in the Bundle returned by the $everything operationPreviously it was absent, that is non-conformant with the specifications.
(H/e6f207a0)
_summary
parameter in read interactionsPreviously attempts to use the _summary
parameter for reads (as opposed to searches) resulted in an error, now when set to true
returns only the summary and required elements of the resource as per the FHIR specifications.
(H/baa606fa)
_has
search conditionsSearch conditions using the _has modifier did not work correctly for the Immunization and Condition resources, they could returned extra resources that were not really matching the condition; now fixed.
(H/4aad202b)
_since
(H/8e27e5d9, H/8d2dc3a5)
The (custom) bulk export parameter provenance-agent-identifier
now supports multiple comma-separated values.
There is a new (again, custom) bulk export parameter _recordAuthorityCodes
, it accepts a comma-separated list of record authority codes used
to filter the output (it complements the existing _recordAuthorityCode
parameter that accepts only a single value).
(H/a1400c8a, H/1b3d41b3)
Consumers 29.17.3, HIEBus 29.16.0
Consumers 29.17.2, HIEBus 29.16.0
Consumers 29.17.1, HIEBus 29.16.0
Consumers 29.17.0, HIEBus 29.16.0
(H/1dca69e2)
Consumers 29.16.7, HIEBus 29.15.1
Consumers 29.16.6, HIEBus 29.15.1
Consumers 29.16.4, HIEBus 29.15.1
Consumers 29.16.3, HIEBus 29.15.1
(H/990e8572)
Consumers 29.16.2, HIEBus 29.15.0
Consumers 29.16.1, HIEBus 29.15.0
Consumers 29.16.0, HIEBus 29.15.0
(C/bfd63379, C/062ae7d7)
The previous link was to the default (currently 2.0) specifications, fixed to point to the 1.0 specifications.
(C/de7d2c22)
(H/9f8182e1, H/e4f8e4ee, H/fac3e7af)
(H/1a95a314)
hasMember
element referencing a non-contained resource(H/6d7a507b)
Consumers 29.15.0, HIEBus 29.14.0
(H/bab31b81)
(H/67ff740e)
(H/9097e573)
(H/576b018a)
Consumers 29.14.0, HIEBus 29.13.0
Expands the list of FHIR endpoints for sites that use multiple brands (e.g. Anthem that is going to have about 30 of these and that might change over time).
Also makes that list of endpoints available as Json.
Removed the links to client registration and get token pages.
(C/da4a9b88)
Consumers 29.13.0, HIEBus 29.13.0
(C/c29af26a)
(H/a5a7f6c0)
(H/9dc41b3b)
(H/9d65d0b0)
(H/b79e120d)
(H/a8cbd4cd)
Consumers 29.12.0, HIEBus 29.8.0
text
element from existing codings.Breaking change
The text
element is populated only when there is an actual separate text in the source data, to better align with the FHIR specifications.
See the documentation on how to use text
and display
elements.
(H/e56568a6, H/1ad2da96)
Potentially breaking change: R4 Coverage.status may be null - making the resource invalid - if the insurance status is not mapped to FHIR a status*
(H/c0157426)
http://careevolution.com/fhirextensions#coverage-priority
(for DSTU2) from the newly added CareEvolution Insurance.Priority property(H/c0157426)
_since
parameter now includes also all the data for patient that have been added to the group since the specified date(H/b0b051b3)
Consumers 29.11.9, HIEBus 29.4.0
Expands the list of FHIR endpoints for sites that use multiple brands (e.g. Anthem that is going to have about 30 of these and that might change over time).
Also makes that list of endpoints available as Json.
Removed the links to client registration and get token pages.
(C/da4a9b88)
Consumers 29.11.8, HIEBus 29.4.0
Consumers 29.11.7, HIEBus 29.4.0
Consumers 29.11.6, HIEBus 29.4.0
Consumers 29.11.5, HIEBus 29.4.0
Consumers 29.11.3, HIEBus 29.4.0
Consumers 29.11.1, HIEBus 29.4.0
Consumers 29.11.0, HIEBus 29.4.0
active
. This undo the change done back in version 28.23 to compute the status based on dates, because it resulted in many Coverage without any status, that is invalid(H/2cebb5cf)
provenance-agent-identifier
parameter to bulk export to restrict the output to only resources with the specified provenance (identified via Provenance.agent.identifier). (#3643)(H/bc790f9d)
(H/bc790f9d)
Consumers 29.10.0, HIEBus 29.3.0
(H/0d666485)
(H/21d9092e)
Consumers 29.9.10, HIEBus 29.2.1
Consumers 29.9.9, HIEBus 29.2.1
Consumers 29.9.8, HIEBus 29.2.1
Consumers 29.9.7, HIEBus 29.2.1
Consumers 29.9.6, HIEBus 29.2.1
active
. This undo the change done back in version 28.23 to compute the status based on dates, because it resulted in many Coverage without any status, that is invalid(H/2cebb5cf)
Consumers 29.9.5, HIEBus 29.2.0
Consumers 29.9.4, HIEBus 29.2.0
Consumers 29.9.3, HIEBus 29.2.0
Consumers 29.9.2, HIEBus 29.2.0
Consumers 29.9.1, HIEBus 29.2.0
Consumers 29.9.0, HIEBus 29.2.0
Consumers 29.8.0, HIEBus 29.2.0
If a user
then attempts to access this second patient data failed with a 404 error. This has been fixed.
(H/b88747c4)
http://careevolution.com/fhirextensions#explanationOfBenefit-referralReference
extension to ExplanationOfBenefit (R4 only), it contains a reference to a Basic resource representing the associated referral. It maps CareEvolution Claim.ReferralID(H/8104b907)
Consumers 29.6.0, HIEBus 29.1.0
Consumers 29.5.0, HIEBus 29.1.0
Consumers 29.4.0, HIEBus 29.1.0
Consumers 29.3.0, HIEBus 29.1.0
Consumers 29.2.0, HIEBus 29.1.0
Consumers 29.1.0, HIEBus 29.1.0
(H/0aeabb17)
http://careevolution.com/fhirextensions#explanationOfBenefit-claimRevision
extension to ExplanationOfBenefit, mapping CareEvolution Claim.Revision(H/725df5b0)
http://careevolution.com/fhirextensions#explanationOfBenefit-claimRevision
and http://careevolution.com/fhirextensions#claim-revision
respectively) containing the claim revision number(H/725df5b0, H/84ae7565)
(H/a9b3b7af, H/a4d6e9e9)
:exact
for all string search parameters(H/96259029)
ScheduledTime is required in CareEvolutiondata model, and it is what we really use as the immunization date-time.
MedicationAdministration.DoseStartTime is still mapped from FHIR and to FHIR for compatibility.
(H/205fd905)
(H/fc5ad4c6)