DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

6.11.5 Resource DocumentManifest - Detailed Descriptions

Detailed Descriptions for the elements in the DocumentManifest resource.

DocumentManifest
Definition

A manifest that defines a set of documents.

Control1..1
DocumentManifest.masterIdentifier
Definition

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

Control0..1
TypeIdentifier
DocumentManifest.identifier
Definition

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

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
DocumentManifest.subject
Definition

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).

Control0..1
TypeReference(Patient | Practitioner | Group | Device)
DocumentManifest.recipient
Definition

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

Control0..*
TypeReference(Patient | Practitioner | Organization)
Comments

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.

DocumentManifest.type
Definition

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.

Control0..1
BindingDocumentC80Type: Preferred: See http://hl7.org/fhir/vs/c80-doc-typecodes (Precice type of clinical document)
TypeCodeableConcept
DocumentManifest.author
Definition

Identifies who is responsible for adding the information to the document.

Control0..*
TypeReference(Practitioner | Organization | Device | Patient | RelatedPerson)
Comments

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

DocumentManifest.created
Definition

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).

Control0..1
TypedateTime
Comments

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.

DocumentManifest.source
Definition

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

Control0..1
Typeuri
DocumentManifest.status
Definition

The status of this document manifest.

Control1..1
BindingDocumentReferenceStatus: Required: http://hl7.org/fhir/document-reference-status (The status of the document reference)
Typecode
Is Modifiertrue
DocumentManifest.description
Definition

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

Control0..1
Typestring
Requirements

Helps humans to assess whether the document is of interest.

Comments

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").

DocumentManifest.content
Definition

The manifest list.

Control1..*
DocumentManifest.content.p[x]
Definition

The list of DocumentReference or Media Resources, or Attachment that consist of the parts of this document manifest. Usually, these would be document references, but direct references to Media or Attachments are also allowed.

Control1..1
TypeAttachment|Reference(DocumentReference | Media)
DocumentManifest.related
Definition

Related identifiers or resources associated with the DocumentManifest.

Control0..*
Comments

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

DocumentManifest.related.identifier
Definition

Related identifier to this DocumentManifest. If both id and ref are present they shall refer to the same thing.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
Comments

Order numbers, accession numbers, XDW workflow numbers.

DocumentManifest.related.ref
Definition

Related Resource to this DocumentManifest. If both id and ref are present they shall refer to the same thing.

Control0..1
TypeReference(Any)
Comments

Order, DiagnosticOrder, Procedure, EligibilityRequest, etc.