All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
3.0.0 (2021-06-15)
- 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 run the addAlias script created in this PR BEFORE upgrading to 3.0.0 to create aliases for all existing indices
- Allow running sls offline with Hapi Validator (#343) (8b98da9)
- typo for passing in custom log level (#345) (83489a6)
2.8.0 (2021-05-26)
- routing: add $docref implementation, see documentation here for more detail. (#86) (105790f), closes #78 #83 #85
- interface: add logging framework (#65) (aa99182)
2.7.0 (2021-04-30)
- routing: Support POST based search (#70) (0c29a2d)
- search: Support number and quantity search syntax (#58) (ac5ca42). e.g.
GET [base]/Observation?value-quantity=le5.4|http://unitsofmeasure.org|mg
- search: Allow repeated search parameters a.k.a AND search parameters (#62) (68f2173). e.g.
GET [base]/Patient?language=FR&language=EN
matches patients who speak English AND French. - search: Allow sorting by date type parameters (#60) (a7d9bf0)
- search: Support searching on Period type fields with date type params (#61) (d36e3af)
- Add DLQ for ddbToEs sync failures (#295) (eb7f51c)
- persistence:
meta
field was missing from update response even though it was persisted properly (#65) (a2b5206) - persistence: Improve error logging when sync from ddb to ElasticSearch fails (#68) (5774b34)
- search: Token search params were matching additional documents (#65) (046238a)
- Suppress deprecation warning when writing to Info_Output.yml during installation (#294) (462e146)
- fhir-works-on-aws-persistence-ddb v3.3.1 -> v3.3.3
- fhir-works-on-aws-routing v5.1.1 -> v5.2.0
- fhir-works-on-aws-search-es v2.3.0 -> v2.5.1
- 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
- Fixed a bug where the
meta
field was being overwritten. This allows to properly store meta fields such asmeta.security
,meta.profile
, etc.
-
Add support for Implementation Guides(IGs).
IG packages can now be included as part of the deployment. This enables search parameters and validation rules from profiles included in the IG. The capability statement is also updated to reflect those changes.
Check out our IGs documentation for more details.
- 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
- chore: Clean up CloudFormation template focusing on reducing reliance on sls
- feat(search): Implement "_include" and "_revinclude" search parameters
- feat(search): Support "_id" search parameter
- fix: Update CloudFormation template to change DynamoDB table key schema
- BREAKING CHANGE - Without running the required scripts the existing data will not be accessible via the FHIR APIS
- Please see sort-key-migration script for instructions
- If not interested in keeping your data feel free to delete your existing stack and deploy a fresh one
- feat: Enable X-ray tracing
- fix: Updated scripts to give correct instructions & clearer READMEs
New committers 🎉 @arthuston & @rb2010
- Initial launch! 🚀