Skip to content

Notified pull documentation - #108

Draft
stevenvegt wants to merge 6 commits into
add-ta-np-specfrom
split-notification-and-workflow-page
Draft

Notified pull documentation#108
stevenvegt wants to merge 6 commits into
add-ta-np-specfrom
split-notification-and-workflow-page

Conversation

@stevenvegt

Copy link
Copy Markdown
Member

No description provided.

bramwesselo and others added 2 commits April 29, 2026 14:21
The COW-based profile moves from notified-pull.md to its own Clinical
Workflow page; notified-pull.md now describes the pure fire-and-forget
data-availability pattern. Adds the building-blocks overview page and a
working-group discussion page exploring SubscriptionTopic granularity
(L0-L4 scenarios on a BgZ subscriber anchor case, scoring table, R5/R6
forward compatibility), linked as a submenu entry under Notified Pull.

Assisted-by: AI
@stevenvegt stevenvegt changed the title seperate notification page (from local branch) Notified pull documentation Jun 5, 2026
Reworked with the working-group input of 1 September 2026 (workflow
requirements for the harmonized TA NP) so the page can serve as the
base for the COW mapping.

- Profiles now derive from COW's Coordination Task and Cancellation
  Request Task (hl7.fhir.uv.cow 1.0.0-ballot added as dependency);
  identifier 1..*, businessStatus with COW's example binding and an NL
  code system defining `selected`, focus widened to COW's six order
  types, Task.code dual-coded (fulfill + use-case code).
- Notification layer named as TTA Notifications v0.6; every Task write
  notifies the owner (echoes included); topics narrowing on Task.code
  must also match `abort`.
- State machine allows the full FHIR range; `received` added as an
  optional state for TA NP compatibility.
- Multi-Fulfiller solicitation correlates on Task.focus; groupIdentifier
  dropped; correlation searches documented.
- Per-order additions moved from Request.supportingInfo to Task.input
  (supplemental-resource, supplemental-query) so that additions notify
  and can differ per candidate; element table lists all slots.
- Outputs and completion per COW; Request.status revoked on withdrawal.
- BSN rules: Task.for references the Patient, BSN on Task.for.identifier
  only once the Fulfiller may know it; Request carries no BSN.
- Authorization basis recorded at the Placer (GF Authorization
  resource.consents) replaces the notification-authorization-hint,
  which becomes an open question.
- Impact on current TA NP and eOverdracht implementations listed.
- Em dashes removed; dead COW link corrected.

Assisted-by: AI
The IG auto-builder's sushi-config prescan does not strip inline
comments, so the hl7.fhir.uv.cow version became an invalid package URL.

Assisted-by: AI
Bring the TA NP and eOverdracht mapping rows in line with the decisions
on Task.input, BSN placement, the received state and Task.groupIdentifier.

Assisted-by: AI
- Appendix A lists every profile rule per element (source COW or NL),
  so a technical agreement can adopt them without the FHIR profiles.
- PlanDefinition demoted to one way of publishing a dataset query list;
  kept as example only.
- Task.input choice no longer described as a deviation from COW.
- BSN rule tied to the Task state: populated at selection at the
  latest, required from in-progress (new invariant).
- notification-authorization-hint out of the profile unless a use case
  is brought; element-table row removed.

Assisted-by: AI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants