Skip to content

Perfuse v0.1.8

Choose a tag to compare

View all tags
@firstmind-biodream firstmind-biodream released this 10 Oct 18:18
· 80 commits to main since this release
v0.1.8
eb76ced

FHIR: API tokens beside SMART tokens

A server with SMART apps configured (-smart-clients or -smart-issuer) accepts only SMART tokens on its FHIR endpoint, so every caller is held to its scopes. That is unchanged, and still the default.

New: Settings → FHIR → Accept Perfuse API tokens beside SMART tokens (or -fhir-api-tokens at start-up) lets Perfuse API tokens in as well, for an internal system that has no SMART client. It is off by default, takes effect at once in either direction, and is written to the audit log. An API token has a role and no scopes, so where you can, give such a system a SMART Backend Services client instead. The manual's Security chapter has a new section, "Who may call the FHIR endpoint".

Console

  • The console downloads about a fifth as much when it first opens: each screen, the channel builder and the script editor are fetched when first used. The first load is about 340 kB, down from 1.66 MB.
  • Every switch and slider on the Settings page is now named by its label, so a screen reader says what it controls.
  • When the channel builder refuses a save, it no longer lists the same problems twice.

Verification you can repeat

  • conformance/inferno/run.sh crd|dtr|pas|uscore runs ONC's Inferno test kits against Perfuse at the versions recorded in docs/verification.md. All four now pass with Perfuse's own authorization server, with the results recorded there: CRD 2.2.1 passes, DTR 2.2.0 43 of 46, PAS 2.2.1 82 of 84, and the US Core 7 SMART launch and granular-scope groups.
  • The strongSwan tunnel reader is tested against a live IKEv2 tunnel between two strongSwan gateways (scripts/strongswan-up.sh).

The manual covers all of the above: https://perfuse.health

Assets 10
Loading