Content Source Extension

Canonical	../StructureDefinition/nexus-content-source
Status	draft · 1.26.0
Base	Extension (constraint)
Context	DocumentReference.content (element)
Source	FSH · JSON

Origin metadata for the file behind one DocumentReference.content entry: the channel or system the file was delivered through.

Overview

On the content entry, not on the resource. A DocumentReference may hold several renditions of one document and only one of them is the file that arrived; the others are produced locally. The extension rides the delivered rendition, so derived renditions carry nothing.

source is an opaque token, naming the delivery channel as the receiving pipeline knows it. HRM -- Ontario Health's Health Report Manager -- is the channel this shape was drawn from and the value carried in this guide's example. No value set is bound: the set of channels is a deployment fact, and a binding published here would make a deployment nonconformant the day it adds a feed. Match the values your deployment produces and pass through the rest.

⚠ FIRST PASS -- do not treat this as a contract. The extension is published under a canonical minted for it, so nothing predates it: there is no earlier address for this shape and no legacy instance to reconcile against. A store holds instances of it from the point a delivery pipeline starts stamping them, and no sooner. Write only source, on the content entry holding the delivered file.