A collection of documents compiled for a purpose together with metadata that applies to the collection.

A single identifier that uniquely identifies this manifest. Principally used to refer to the manifest in non-FHIR contexts.

Other identifiers associated with the document manifest, including version independent identifiers.

The status of this document manifest.

This element is labeled as a modifier because the status contains the codes that mark the manifest as not currently valid.

The code specifying the type of clinical activity that resulted in placing the associated content into the DocumentManifest.

Specifies the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be the same as one of the documents in it - especially if there is only one - but it may be wider.

Who or what the set of documents is about. The documents can be about a person, (patient or healthcare practitioner), a device (i.e. machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). If the documents cross more than one subject, then more than one subject is allowed here (unusual use case).

When the document manifest was created for submission to the server (not necessarily the same thing as the actual resource last modified time, since it may be modified, replicated, etc.).

Creation time is used for tracking, organizing versions and searching. This is the creation time of the document set, not the documents on which it is based.

An actor taking an active role in the manifest.

Several agents may be associated with the manifest.

Specification of the participation type the agent played.

Identifies who is the agent. Such as the author of the manifest, and adding documents to it.

Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant).

A patient, practitioner, or organization for which this set of documents is intended.

How the recipient receives the document set or is notified of it is up to the implementation. This element is just a statement of intent. If the recipient is a person, and it is not known whether the person is a patient or a practitioner, RelatedPerson would be the default choice.

Identifies the source system, application, or software that produced the document manifest.

Human-readable description of the source document. This is sometimes known as the "title".

Helps humans to assess whether the document is of interest.

What the document is about, rather than a terse summary of the document. It is commonly the case that records do not have a title and are collectively referred to by the display name of Record code (e.g. a "consultation" or "progress note").

The list of Resources that consist of the parts of this manifest.

Any Resources are allowed to be grouped in a Manifest. The manifest brings context to the group.

When used for XDS the intended focus of the DocumentManifest is for the reference to target to be a set of DocumentReference Resources. The reference is to "Any" to support EN 13606 usage, where an extract is DocumentManifest that references List and Composition resources.

Related identifiers or resources associated with the DocumentManifest.

May be identifiers or resources that caused the DocumentManifest to be created.

Related identifier to this DocumentManifest. For example, Order numbers, accession numbers, XDW workflow numbers.

If both identifier and ref elements are present they shall refer to the same thing.

Related Resource to this DocumentManifest. For example, Order, ServiceRequest, Procedure, EligibilityRequest, etc.

If both identifier and ref elements are present they shall refer to the same thing.