Repository navigation
0.0.31
·
8 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Added
- The ITI-93 sender authenticates to each Patient Identity Consumer named
in[[pmir.feed.consumers]], the family's endpoint table: a message to a
subscription whose channel endpoint lies under the entry'surlcarries
its IUA client credentials token (credentials.oauth), renewed once when
the Consumer answers401, and presents its client certificate for ATNA
mutual TLS (tls.client_identity_file), as PMIR 1.6.0 §2:3.93.5 asks.
The token replaces anyAuthorizationheader the subscription names,
and an endpoint under no entry gets no credential. A401or403after
the renewal is retried within[pmir.feed]and then sets the
subscription toerrornaming the refusal (#655). ihe-iti0.10.1 makespmir::subscription::Subscribed::atpublic: a
PMIR subscriber that keeps no state between requests rebuilds the
subscription handle from theLocationit stored, to read its status or
delete it. ALocationoff the Registry's[base]/Subscriptionis
refused as before, so the subscriber's credential never goes elsewhere (#658).
Changed
- FerroPIX moves to
ferrohealth-smart0.21,ferrohealth-session0.16,
ihe-atna0.15,ferrobridge-term0.8 andferrobridge-hl7v20.12, the
releases on the smart line that chooses the described SMART issuer by one
shared rule and adds the optionaldescribed_issuerkey toAuthSection(#647). - Breaking for crate users:
ihe-iti0.7.0 requiresferrohealth-smart
0.21 andihe-atna0.15, andnl-generic-functions0.7.0 requires
ferrohealth-smart0.21 andihe-iti0.7. Their public API carries the
types of those crates (the outbound client, the endpoint table and the
audit user), so a consumer moves to the same lines (#647). - FerroPIX moves to
ferrohealth-smart0.22,ferrohealth-session0.17,
ihe-atna0.16,ferrobridge-term0.9 andferrobridge-hl7v20.13, the
releases on the smart line whereDpopSectionno longer carries
external_url. FerroPIX sets no[auth.dpop], so no configuration key
changes (#649). - Breaking for crate users:
ihe-iti0.8.0 requiresferrohealth-smart
0.22 andihe-atna0.16, andnl-generic-functions0.8.0 requires
ferrohealth-smart0.22 andihe-iti0.8. Their public API carries the
types of those crates (the outbound client, the endpoint table and the
audit user), so a consumer moves to the same lines (#649). - Breaking: a Basic user's scopes move out of
[[auth.basic.users]],
which holds the credential alone (user,password_hash,
password_hash_file), into FerroPIX's own[basic_grants.<user-id>]
table withscopesandroles. Ascopesorroleskey in
[[auth.basic.users]]now refuses the start as an unknown key, and so
does a[basic_grants]table naming a user[[auth.basic.users]]does
not list. A grantedsystem/scope or role is refused as before, now
namingbasic_grants.<user-id>. Upgrade: move each user'sscopesline
into a[basic_grants.<user>]table named by itsuser(#651). - FerroPIX moves to
ferrohealth-smart0.24,ferrohealth-session0.19,
ihe-atna0.18,ferrobridge-term0.10 andferrobridge-hl7v20.14,
the releases on the smart line where the caller classification asks each
issuer's standing source. FerroPIX keeps its client lists in[auth],
the default source, so no further configuration key changes (#651). - Breaking for crate users:
ihe-iti0.9.0 requiresferrohealth-smart
0.24 andihe-atna0.18, andnl-generic-functions0.9.0 requires
ferrohealth-smart0.24 andihe-iti0.9. Their public API carries the
types of those crates (the outbound client, the endpoint table and the
audit user), so a consumer moves to the same lines (#651). - Breaking for crate users:
ihe-iti0.10.0 reads the state of every
Patient an ITI-93 message carries.pmir::feed::PatientIdentitynow has
activeand everyPatient.link, read aspmir::feed::Linkwith its
LinkType(FHIR R4link-type) and the other reference, and
Feed::readrefuses a created, updated or merged Patient that omits
active(FeedError::NoActive) or a link with an unknown type or no
reference (FeedError::Link). A subscriber reads an unmerge, an update
withactivetrue and noreplaced-bylink, from the message alone.
nl-generic-functions0.10.0 requiresihe-iti0.10 (#656). - The ITI-93 feed FerroPIX sends states
activeand the current links of
everyPatient, and a steward's revert of a merge is one message with
both patients as they now stand, eachactivetrue with no
replaced-bylink (PMIR 1.6.0 §2:3.93.4.1.3) (#656).
Support period
Only the newest release is supported: there are no maintenance branches, no long-term-support line and no backports, and upgrading is free. Under the Cyber Resilience Act, Cadasto B.V. commits to keep publishing security fixes for at least five years after each release (Art 13(8)) and ships them only in the newest release (Art 13(10)). For this release that commitment runs until the end of November 2031 (Regulation (EU) 2024/2847 Art 13(19)); see SECURITY.md.