v4.0.0-Solution
[4.0.0] - 2021-11-22
The following changes are published to AWS Solution FHIR Works on AWS.
BREAKING CHANGES
-
The Cognito
IdToken
is now used instead of theAccessToken
to authorize requests.-
Multi-tenancy itself is not a breaking change, you can continue to use FHIR works on single-tenant mode
by setting theenableMultiTenancy
to false. -
However, note that updating an existing (single-tenant) stack to enable multi-tenancy is a breaking change. Multi-tenant
deployments use a different data partitioning strategy that renders the old, single-tenant, data inaccessible.
-
-
FWoA now reads/writes Elasticsearch documents from aliases instead of indexes. This change simplifies performing re-indexing operations without downtime.
Aliases are automatically created when resources are written to Elasticsearch, but read operations may fail for existing deployments if the aliases do not exist already. -
Please send 1 update/create request on each resource type existed already to get the aliases created.
Features
-
Implement multi-tenancy and group export
- Multi-tenancy allows a single
fhir-works-on-aws
stack to serve as multiple FHIR servers for different tenants.
Check out our multi-tenancy documentation for more details.
- Multi-tenancy allows a single
-
Use alias for all ES operations
-
interface: add logging framework
-
routing: Support POST based search
-
search: Support number and quantity search syntax
-
search: Allow repeated search parameters a.k.a AND search parameters
-
search: Allow sorting by date type parameters
-
search: Support searching on Period type fields with date type params
-
Add DLQ for ddbToEs sync failures
-
Search now supports
|
as part of token parameters. e.g.GET [base]/Patient?identifier=http://acme.org/patient|2345
-
Search now supports using range prefixes for date parameters. e.g.
GET [base]/Patient?birthdate=ge2013-03-14
-
The capability statement returned by
/metadata
now includes the detail of all search parameters supported -
Add support for the standard FHIR search parameters. Each FHIR resource type defines its own set of search parameters. i.e the search parameters for Patient can be found here
-
Search requests using invalid search parameters now return an error instead of an empty result set
-
/metadata
route in API GW so requests for that route doesn't need to be Authenticated/Authorized -
Support for
fhir-works-on-aws-interface
version4.0.0
-
Change
config
to support new interface.auth.strategy.oauth
changed toauth.strategy.oauthPolicy
authorizationUrl
changed toauthorizationEndpoint
tokenUrl
changed totokenEndpoint
-
Support for
fhir-works-on-aws-authz-rbac
version4.0.0
-
Support for
fhir-works-on-aws-routing
version3.0.0
-
Change non-inclusive terminology in serverless.yaml description
-
Support "System Level" export of DB data
Bug Fixes
- change output file type
- dependency vulnerability
- pin IG download
- Allow running sls offline with Hapi Validator
- typo for passing in custom log level
- persistence:
meta
field was missing from update response even though it was persisted properly - persistence: Improve error logging when sync from ddb to ElasticSearch fails
- search: Token search params were matching additional documents
- Suppress deprecation warning when writing to Info_Output.yml during installation
- Fixed a bug where the
meta
field was being overwritten. This allows to properly store meta fields such asmeta.security
,meta.profile
, etc.