As a practitioner, I can invite a colleague from a peer instance to my case

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

charles/koinos#19

claude-desktop commented

2026-04-14 20:43:05 +00:00

Collaborator

User story

As a practitioner, I want to invite a colleague hosted on another Koinos instance to my teleexpertise case, so that I can reach specialists beyond my own institution.

Acceptance criteria

Invitee lookup

/api/directory/search?q=...&peer=<host> queries the peer's directory (FHIR Practitioner search) through the backend.
Results limited to consenting, directory-listed practitioners.

Invitation

From the case detail page, Invite external colleague opens a search scoped to trusted peers (from #18).
Inviting creates a Matrix room invite to @them:peer-host and a FHIR-side ServiceRequest.performer update.
A scoped FHIR access grant (Consent resource) is issued, bound to:
- the case ServiceRequest,
- the invitee's did:web,
- a TTL matching the case lifetime + 30-day read window.
Invitee's home instance validates the invite (trust list check).

Resource access

The remote invitee can fetch the shared resources through the home instance's mediated endpoint (GET /api/federation/resources/{ref}?case={id}) — backend proxies to HAPI FHIR with the case's grant.
Access revoked immediately on case closure or explicit revocation; audited.

UI

Remote invitees clearly marked with their home-instance host.
Badge showing access expiry.

Tests

Integration test across two Compose stacks: create case on A, invite user on B, B reads shared DocumentReference through the proxy, case closes, subsequent B access returns 403.

Out of scope

Remote invitee signing a final report (later in v0.1 or v0.2).
ActivityPub directory (v0.4).

References

spec/03-architecture/02-federation.md.
spec/04-functional/02-teleexpertise.md §6.
spec/03-architecture/04-medical-data.md.
spec/08-roadmap-mvp.md — step #19.

## User story **As a practitioner**, I want to invite a colleague hosted on another Koinos instance to my teleexpertise case, **so that** I can reach specialists beyond my own institution. ## Acceptance criteria ### Invitee lookup - [ ] `/api/directory/search?q=...&peer=<host>` queries the peer's directory (FHIR `Practitioner` search) through the backend. - [ ] Results limited to consenting, directory-listed practitioners. ### Invitation - [ ] From the case detail page, *Invite external colleague* opens a search scoped to trusted peers (from #18). - [ ] Inviting creates a Matrix room invite to `@them:peer-host` and a FHIR-side `ServiceRequest.performer` update. - [ ] A scoped FHIR access grant (`Consent` resource) is issued, bound to: - the case `ServiceRequest`, - the invitee's `did:web`, - a TTL matching the case lifetime + 30-day read window. - [ ] Invitee's home instance validates the invite (trust list check). ### Resource access - [ ] The remote invitee can fetch the shared resources through the home instance's mediated endpoint (`GET /api/federation/resources/{ref}?case={id}`) — backend proxies to HAPI FHIR with the case's grant. - [ ] Access revoked immediately on case closure or explicit revocation; audited. ### UI - [ ] Remote invitees clearly marked with their home-instance host. - [ ] Badge showing access expiry. ### Tests - [ ] Integration test across two Compose stacks: create case on A, invite user on B, B reads shared `DocumentReference` through the proxy, case closes, subsequent B access returns `403`. ## Out of scope - Remote invitee signing a final report (later in v0.1 or v0.2). - ActivityPub directory (v0.4). ## References - `spec/03-architecture/02-federation.md`. - `spec/04-functional/02-teleexpertise.md` §6. - `spec/03-architecture/04-medical-data.md`. - `spec/08-roadmap-mvp.md` — step #19.

claude-desktop added this to the v0.1 milestone

claude-desktop added the

area:clinical

area:federation

type:user-story

labels

claude-desktop referenced this issue

2026-04-14 20:43:16 +00:00

As a patient, I can request my audit trail (AuditEvent for every case action) #20