Changelog

v0.4.0

Released date: 2026-06-15

Motivation

Clients need to retrieve a specific historical version of a plan, not just the latest one. This complements the History endpoint (which returns metadata only) by returning the full plan object at a given version.

Changes

• Added GET /plan/{id}/version/{version} endpoint returning full Response object
• Returns 400 for invalid UUID or version format, 404 for plan or version not found

v0.3.0

Released date: 2026-06-12

Motivation

The API now supports retrieving the full version history of a plan, enabling audit trail use cases. Additionally, the Search endpoint now requires the patient parameter to prevent unintended broad queries.

Changes

• Added GET /plan/{id}/history endpoint returning []HistoryResponse
• Added HistoryResponse model with fields: version, status, updated_at, updated_by, comment
• patient query parameter is now mandatory in Search endpoint (returns 400 when missing)

v0.2.0

Released date: 2026-06-12

Motivation

The API model has been refactored to separate request and response. This provides a cleaner public API where server-assigned fields (id, version, updated_at) are not exposed in request bodies, and consumers receive dedicated response objects.

Additionally, the API now enforces optimistic locking via version checking on updates.

Changes

• Split single Request model into CreateRequest, UpdateRequest, and Response
• Renamed plan field to clinical_content in all requests and responses
• Renamed Plan model to Content / Clinical Content
• CreateRequest no longer accepts version — assigned by server
• UpdateRequest requires version — must match current server version for optimistic locking
• Update endpoint returns 409 Conflict on version mismatch, 422 Unprocessable Entity on missing version
• Updated active status description to clarify it does NOT imply the plan is approved

v0.1.0

Released date: 2026-06-12

Motivation

Based of the feedback from work meeting 2026-06-11, we have revised which FHIR statuses to include as of now.

Furthermore, we have updated the documentation for the active status to not imply the plan is approved. This does not currently cause any behavioural changes in the API.

Changes

• Added Request.status option revoked
• Removed Request.status options completed and on-hold