fhirclient

# Changelog # v2.6.3 - Added missing authorization header to sub-request client methods like `update`, `create`, `delete`, etc. Fixes #201 # v2.6.2 - Forgot to include the built files in v2.6.1. This is the version that should be used instead! # v2.6.1 - Added `wellKnownRequestOptions` and `conformanceRequestOptions` to `authorize` options, allowing custom headers and fetch options for SMART discovery endpoints ([#200](https://github.com/smart-on-fhir/client-js/issues/200)) - Improved TypeScript types for `AuthorizeParams` and related interfaces - Enhanced test coverage for new options and fixed test environment compatibility issues - Updated documentation for new options and usage patterns - Fixed compatibility with newer versions of ChromeDriver and Chrome for Nightwatch/browser tests - Various bugfixes and internal refactoring for better maintainability ## v2.6.0 - Mark @types/hapi peer dependency as optional #193 - Auto-detect Chrome driver version in GitHub CI - Changes to support code and stateKey as ReadyOptions in auth flow #191 - Added new `FhirClient` base class to simplify usage with open servers. This can work without requiring request end response objects in Node. - npm audit fix - to fix some of the latest dependency issues ## v2.5.5 - Updated dependencies, browserlist db, CVEs... - Updated docs and links to examples - Add the ability to supply user-defined state key. #168 - Add refreshTokenWithClientId option, to send client_id when using a refresh token #175 ## v2.5.4 - Fixed double port issue preventing this library from working with NextJs - #186 - The `includeResponse` now works for update requests with empty response - #162 - Fixed some CVEs - #185 - Upgraded most dev dependencies to their latest usable version - Detect if the app is running without a secure context and throw an error to complain about it - #183 - Custom headers are now propagated to sub-requests for resolving references - #184 ## v2.5.3 - [non-functional] Created bug and feature issue templates in #177 - Added logic for using patientId & clientId URL parameters in calls to `smart.authorize` in #178 - [non-functional] Made documentation changes fixing small typos and removing unnecessary text in `docs/open_servers.md` in #178 - [non-functional] Added an .nvmrc file suggesting node v14.21.3, lts/fermium, in #178 ## v2.5.2 - Fix base64url encoding for PKCE #158 - Simplified the code and removed IE support for new SMART V2 features like PKCE and asymmetric authentication. ## v2.5.1 - Changed the architecture to avoid build issues #156. Version `2.5.0` cannot be use for client-side builds (but works in NodeJS or if loaded as a bundle) and `v2.5.1` provides a fix for that. - No other changes ## v2.5.0 - Added `PKCE` support - Added support for asymmetric authentication - Passing `onSuccess` and `onError` callbacks to `FHIR.oauth2.ready` (which was previously deprecated) is no longer supported - IE10 is no longer supported - Supports NodeJS versions 14 to 18 - Update all dependencies and dev tools. Zero audit issues at the time of release. - `.well-known/smart-configuration` is now the preferred source of metadata and `/metadata` is only fetched if smart-configuration is not found on the given server. - Fixed an issue that might prevent users from setting custom http headers (#153) - Added GitHub actions, e2e tests in headless browser and improved coverage reports ## v2.4.0 - Added `patch` method to the client - Added `noRedirect` authorize option - Some bug fixes: - Empty body response after create operation but no location header #118, #124 - Epic may return a full url #105 - Small documentation and type definition changes and improvements ## v2.3.11 - `HttpError` instances (which are thrown when a request has failed) now have a `response` property that is a reference to the Response object. This can be used to read response headers or inspect the response in some other way in case of error. - Client requests should now always fail with `HttpError`. Previously they were sometimes being rejected with custom `Error` objects which do not have the response or the status code information. - All the request methods (except for the ones used for refreshing) can now accept new `includeResponse` boolean option. The affected methods are `client.request`, `client.create`, `client.update`, `client.delete`, `client.patient.read`, `client.user.read`, `client.encounter.read` and `client.patient.request`. [Read More](http://docs.smarthealthit.org/client-js/client.html) - In case of EHR launch the `authorize` function can now be called with an array of options. This makes it possible to pre-configure an app to be launch-able from multiple EHRs. The right configuration will be picked based on the passed `iss` url parameter using the new `issMatch` option. [Read More](http://docs.smarthealthit.org/client-js/open_servers#2-using-multiple-launch-configurations) ## v2.3.10 - Fixed the way access token expiration is computed for non-jwt tokens (#101). - Added a `body` property to the `HttpError` instances (#100). It will contain the parsed response body from failed requests which can be JSON (typically an `OperationOutcome` resource), a string or `null`. ## v2.3.8 - Changed the way the "auto-refresh" flow works. Before `2.3.8` the client was obtaining new access token if a request fails with `401`. Since `2.3.8`, the client will check the access token expiration time before making a request. This is done to avoid CORS-related issues with servers that do not emit CORS headers in case of error. - The refresh token requests will now be sent without credentials. In the rare cases when the auth server requires the app to send cookies, developers will have to configure the client to do so. - Added support for the `..` path operator in `client.getPath`, `client.getState` and the `resolveReferences` option of `client.request`. This was done to allow paths like `identifier..assigner`, which will match if identifier is an array of objects having an assigner reference property. ## v2.3.5 - The `completeInTarget` authorize option defaults to `true` if the app was loaded in an iframe - The `redirectUri` option accepts absolute URLs and does not append "/" to them - The `refresh` client method will now use basic authorization for confidential clients - The `refresh` client method will now try to make its request both with and without credentials - The `request` client method will now return the response object if the response status is 201 (can get the `location` header after create) - Added the `getState` method of the `Client` for state introspections ## v2.3.1 - `client.create` and `client.update` are using `"Content-Type": "application/json"` header by default - `client.create` and `client.update` alow custom `Content-Type` to be specified - `node` and `hapi` type definitions are moved to peer dependencies to avoid build conflicts ## v2.3.0 - Added API documentation generated from source - http://docs.smarthealthit.org/client-js/typedoc/ - Added ability to authorize in different window or frame - http://docs.smarthealthit.org/client-js/targets.html - Fixed a Hapi.js issue with detecting the protocol of the request #69 ## v2.2.0 - Rewritten in TypeScript to improve readability and maintainability - Fixed some build errors (#68) - HapiJs users have new entry point `const smart = require("fhirclient/lib/entry/hapi")` - Better code coverage - Improved performance (#67) - Added ability to [abort requests](http://docs.smarthealthit.org/client-js/client.html#aborting-requests) ## v2.1.1 - Switched to ES modules (thanks to @kherock) - Updated type definitions to fix some issues with Angular projects - other minor bug fixes ## v2.1.0 - Added convenience wrappers for the FHIR create/update/delete operations #56 - Added patient context aware request wrapper #57 - Fixed a refresh issue in Firefox #58 - Improved fake token flow #59 - Added `getFhirVersion` and `getFhirRelease` client methods - Few other minor fixes and improvements ## v2.0.7 - See http://docs.smarthealthit.org/client-js/v2.html ## v0.1.15 - Included the last version of fhir.js - For previous page, bundle.link.relation can either have 'previous' or 'prev' value - Added getBundleByUrl api method - Added support for `le` and `ge` search parameters - Added support for `_include` and `_revinclude` - Added a warning if the launch URL is not loaded properly ## v0.1.14 - Fixed the structure of the released package broken in `0.1.13`. Only the `dist` folder is released now. ## v0.1.13 - The profile claim can be absolute URL - Examples use existing server and patient ID - Resolve all npm vulnerabilities by updating to the latest versions - Switch -g to -t for varify to resolve build issues - Update lib/jqFhir.js with the latest version from https://github.com/FHIR/fhir.js/tree/v0.0.21. - Added the changelog file