v3.0.0

⚠ BREAKING CHANGES

• 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

Features

• Use alias for all ES operations (#349) (0f512c2)

Bug Fixes

• Allow running sls offline with Hapi Validator (#343) (8b98da9)
• typo for passing in custom log level (#345) (83489a6)

v2.8.0

Features

• routing: add $docref implementation, see documentation here for more detail. (#86) (105790f), closes #78 #83 #85
• interface: add logging framework (#65) (aa99182)

v2.7.0

Features

• 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)

Bug Fixes

• 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 components detailed diff

• 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

v2.6.0

• Search now supports | as part of token parameters. e.g. GET [base]/Patient?identifier=http://acme.org/patient|2345
  Note: the | MUST be url encoded e.g. GET [base]/Patient?identifier=http://acme.org/patient%7C2345
• Search now supports using range prefixes for date parameters e.g. GET [base]/Patient?birthdate=ge2013-03-14 and searching for partial dates e.g. GET [base]/Patient?birthdate=2013
• Fixed a bug where the meta field was being overwritten. This allows to properly store meta fields such as meta.security, meta.profile, etc.

v2.5.0

• 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.

Special thanks to @emilhdiaz and @justinusmenzel for contributing to this release.

v2.4.0

• 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

v2.3.0

Merge a6f96a7 into mainline

v2.2.0

Merge 7b732ad into mainline

v2.1.1

Merge 4b7c87e58d7f58b05b6fc156452629cc43efa901 into mainline