Changelog

0.1.0-draft.3 — 12 October 2026

Added 24 proposed operations, bringing the contract to 72 operations:

  • Immutable snapshots, patient timeline, source inventory and observation bundles.
  • Structured symptom catalogs and immutable assessments.
  • Snapshot-based pattern evaluation reads.
  • Document batches, detailed processing readiness and read-only review summaries.
  • Integration-applicable patient grant reads.
  • Public laboratory/collection-center directories and bounded reference graph queries.
  • Integration capabilities and durable asynchronous operation receipts.

Replaced the singular issuer string with read-only issuers[] objects containing name, type, optional address and verified, authorised organisation/practitioner references. Practitioner links are specific to the document; no organisation staff roster is exposed.

Moved language, issuers, title and documentDate out of upload inputs. They are read-only response fields, returned only after DIP completes and derives their values. Pending and processed response examples now show this distinction.

Added the scrubPII upload metadata flag, defaulting to true. extractData and scrubPII cannot both be false; the shared metadata schema encodes this constraint, with HTTP 422 for invalid requests.

Corrected document uploads: category is assigned by DIP classification, not supplied by the caller. Upload and returned metadata use separate schemas; the returned category is read-only and nullable until classification is available. Updated multipart, presigned and batch examples.

Processing requests may now optionally set scrubPII: true to enable scrubbing on stored documents. Omission preserves the existing policy, false is rejected, and operation receipts report the effective policy. New scrubbing must occur before downstream processing.

Added POST /documents/{documentId}/processing-runs for first-time processing and reprocessing of retained input, with documents:process, required idempotency and attempt checks, operation receipts and safe eligibility reads. This is proposed backend behaviour; existing operator redo does not establish public availability.

Added evidence-preserving schemas and scopes, with authorization and readiness notes. Export and account-erasure responses now describe pollable operation receipts.

The original eight-module roadmap and the additional launch candidates remain proposals. No new deployment dates or verified API/SDK availability are established by this revision.

The contract version was corrected from 1.0.0-draft.3 to 0.1.0-draft.3.

Partner API 0.1.0-draft.3 · Draft contract · Sandbox and SDK availability require confirmation.