DSTU2 FHIR Release 3 (STU)

This page is part of the FHIR Specification (v1.0.2: DSTU (v3.0.2: STU 2). 3). 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 R3 R2

6.10 2.43 Resource DocumentManifest - Content

Structured Documents Work Group Maturity Level : 1 2   Trial Use Compartments : Device , Patient , Practitioner , RelatedPerson

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

6.10.1 2.43.1 Scope and Usage

A document manifest gathers a set of DocumentReference resources into a single package that may be the subject of workflow such as access control, auditing, and targeted delivery.

Typically, DocumentManifest resources are used in document indexing systems, such as IHE XDS (see the XDS specific profile ). .

6.10.2 2.43.2 Resource Content

Structure

0..1 The subject 0..* Intended to get notified about this Kind of 0..1 When status ?! Σ 1..1 code current | superseded | entered-in-error DocumentReferenceStatus ( Required )
Name Flags Card. Type Description & Constraints doco
. . DocumentManifest Σ DomainResource A manifest list that defines a set of documents
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . masterIdentifier Σ 0..1 Identifier Unique Identifier for the set of documents
. . . identifier Σ 0..* Identifier Other identifiers for the manifest
. . subject . status ?! Σ 1..1 Reference ( Patient code current | Practitioner superseded | Group entered-in-error
DocumentReferenceStatus | Device ( Required )
. . . type Σ 0..1 CodeableConcept Kind of the document set of documents
Document Type Value Set ( Preferred )
. . recipient . subject Σ 0..1 Reference ( Patient | Practitioner | RelatedPerson Group | Organization Device ) The subject of the set of documents
. . type . created Σ 0..1 CodeableConcept dateTime When this document set Document Type Value Set ( Preferred ) manifest created
. . . author Σ 0..* Reference ( Practitioner | Organization | Device | Patient | RelatedPerson ) Who and/or what authored the manifest
. . created . recipient Σ 0..* dateTime Reference ( Patient | Practitioner | RelatedPerson | Organization ) Intended to get notified about this document manifest created set of documents
. . . source Σ 0..1 uri The source system/application/software
. . . description Σ 0..1 string Human-readable description (title)
. . . content Σ 1..* BackboneElement The items included
. . . . p[x] Σ 1..1 Contents of this set of documents
. . . . . pAttachment Attachment
. . . . . pReference Reference ( Any )
. . . related Σ 0..* BackboneElement Related things
. . . . identifier Σ 0..1 Identifier Identifiers of things that are related
. . . . ref Σ 0..1 Reference ( Any ) Related Resource

doco Documentation for this format

UML Diagram ( Legend )

DocumentManifest ( DomainResource ) A single identifier that uniquely identifies this manifest. Principally used to refer to the manifest in non-FHIR contexts masterIdentifier : Identifier [0..1] Other identifiers associated with the document manifest, including version independent identifiers identifier : Identifier [0..*] The status of this document manifest (this element modifies the meaning of other elements) status : code [1..1] The status of the document reference. (Strength=Required) DocumentReferenceStatus ! 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 type : CodeableConcept [0..1] Precise type of clinical document. (Strength=Preferred) Document Type Value Set ? 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) subject : Reference [0..1] « Patient | Practitioner | Group | Device » A patient, practitioner, or organization When the document manifest was created for which this set of documents is intended recipient : Reference [0..*] « Patient | Practitioner | RelatedPerson | Organization » Specifies submission to the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be server (not necessarily the same thing as one of the documents in it - especially if there is only one - but actual resource last modified time, since it may be wider modified, replicated, etc.) type created : CodeableConcept dateTime [0..1] « Precise type of clinical document. (Strength=Preferred) Document Type Value Set ? » Identifies who is responsible for creating the manifest, and adding documents to it author : Reference [0..*] « Practitioner | Organization | Device | Patient | RelatedPerson » When the document manifest was created A patient, practitioner, or organization for submission to the server (not necessarily the same thing as the actual resource last modified time, since it may be modified, replicated, etc.) which this set of documents is intended created recipient : dateTime Reference [0..1] [0..*] Patient | Practitioner | RelatedPerson | Organization Identifies the source system, application, or software that produced the document manifest source : uri [0..1] The status of this document manifest (this element modifies the meaning of other elements) status : code [1..1] « The status of the document reference. (Strength=Required) DocumentReferenceStatus ! » Human-readable description of the source document. This is sometimes known as the "title" description : string [0..1] Content The list of references to document content, 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 p[x] : Type [1..1] « Attachment | Reference ( Any ) » Related Related identifier to this DocumentManifest. For example, Order numbers, accession numbers, XDW workflow numbers identifier : Identifier [0..1] Related Resource to this DocumentManifest. For example, Order, DiagnosticOrder, ProcedureRequest, Procedure, EligibilityRequest, etc ref : Reference [0..1] « Any » The list of Documents included in the manifest content [1..*] Related identifiers or resources associated with the DocumentManifest related [0..*]

XML Template 

<

<DocumentManifest xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</masterIdentifier>
 <</identifier>
 <</subject>
 <</recipient>
 <</type>
 <|

 <masterIdentifier><!-- 0..1 Identifier Unique Identifier for the set of documents --></masterIdentifier>
 <identifier><!-- 0..* Identifier Other identifiers for the manifest --></identifier>
 <status value="[code]"/><!-- 1..1 current | superseded | entered-in-error -->
 <type><!-- 0..1 CodeableConcept Kind of document set --></type>
 <subject><!-- 0..1 Reference(Patient|Practitioner|Group|Device) The subject of the set of documents --></subject>
 <created value="[dateTime]"/><!-- 0..1 When this document manifest created -->
 <author><!-- 0..* Reference(Practitioner|Organization|Device|Patient|

   RelatedPerson) Who and/or what authored the manifest --></author>
 <
 <
 <
 <
 <
  <</p[x]>

 <recipient><!-- 0..* Reference(Patient|Practitioner|RelatedPerson|Organization) Intended to get notified about this set of documents --></recipient>
 <source value="[uri]"/><!-- 0..1 The source system/application/software -->
 <description value="[string]"/><!-- 0..1 Human-readable description (title) -->
 <content>  <!-- 1..* The items included -->
  <p[x]><!-- 1..1 Attachment|Reference(Any) Contents of this set of documents --></p[x]>

 </content>
 <
  <</identifier>
  <</ref>

 <related>  <!-- 0..* Related things -->
  <identifier><!-- 0..1 Identifier Identifiers of things that are related --></identifier>
  <ref><!-- 0..1 Reference(Any) Related Resource --></ref>

 </related>
</DocumentManifest>

Turtle Template 


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DocumentManifest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DocumentManifest.masterIdentifier [ Identifier ]; # 0..1 Unique Identifier for the set of documents
  fhir:DocumentManifest.identifier [ Identifier ], ... ; # 0..* Other identifiers for the manifest
  fhir:DocumentManifest.status [ code ]; # 1..1 current | superseded | entered-in-error
  fhir:DocumentManifest.type [ CodeableConcept ]; # 0..1 Kind of document set
  fhir:DocumentManifest.subject [ Reference(Patient|Practitioner|Group|Device) ]; # 0..1 The subject of the set of documents
  fhir:DocumentManifest.created [ dateTime ]; # 0..1 When this document manifest created
  fhir:DocumentManifest.author [ Reference(Practitioner|Organization|Device|Patient|RelatedPerson) ], ... ; # 0..* Who and/or what authored the manifest
  fhir:DocumentManifest.recipient [ Reference(Patient|Practitioner|RelatedPerson|Organization) ], ... ; # 0..* Intended to get notified about this set of documents
  fhir:DocumentManifest.source [ uri ]; # 0..1 The source system/application/software
  fhir:DocumentManifest.description [ string ]; # 0..1 Human-readable description (title)
  fhir:DocumentManifest.content [ # 1..* The items included
    # DocumentManifest.content.p[x] : 1..1 Contents of this set of documents. One of these 2
      fhir:DocumentManifest.content.pAttachment [ Attachment ]
      fhir:DocumentManifest.content.pReference [ Reference(Any) ]
  ], ...;
  fhir:DocumentManifest.related [ # 0..* Related things
    fhir:DocumentManifest.related.identifier [ Identifier ]; # 0..1 Identifiers of things that are related
    fhir:DocumentManifest.related.ref [ Reference(Any) ]; # 0..1 Related Resource
  ], ...;
]

Changes since DSTU2

DocumentManifest
  • No Changes

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 Conversion Maps (status = 1 test that all execute ok. 1 fail round-trip testing and all r3 resources are valid.).

Structure

0..1 The subject 0..* Intended to get notified about this Kind of 0..1 When status ?! Σ 1..1 code current | superseded | entered-in-error DocumentReferenceStatus ( Required )
Name Flags Card. Type Description & Constraints doco
. . DocumentManifest Σ DomainResource A manifest list that defines a set of documents
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . masterIdentifier Σ 0..1 Identifier Unique Identifier for the set of documents
. . . identifier Σ 0..* Identifier Other identifiers for the manifest
. . subject . status ?! Σ 1..1 Reference ( Patient code current | Practitioner superseded | Group entered-in-error
DocumentReferenceStatus | Device ( Required )
. . . type Σ 0..1 CodeableConcept Kind of the document set of documents
Document Type Value Set ( Preferred )
. . recipient . subject Σ 0..1 Reference ( Patient | Practitioner | RelatedPerson Group | Organization Device ) The subject of the set of documents
. . type . created Σ 0..1 CodeableConcept dateTime When this document set Document Type Value Set ( Preferred ) manifest created
. . . author Σ 0..* Reference ( Practitioner | Organization | Device | Patient | RelatedPerson ) Who and/or what authored the manifest
. . created . recipient Σ 0..* dateTime Reference ( Patient | Practitioner | RelatedPerson | Organization ) Intended to get notified about this document manifest created set of documents
. . . source Σ 0..1 uri The source system/application/software
. . . description Σ 0..1 string Human-readable description (title)
. . . content Σ 1..* BackboneElement The items included
. . . . p[x] Σ 1..1 Contents of this set of documents
. . . . . pAttachment Attachment
. . . . . pReference Reference ( Any )
. . . related Σ 0..* BackboneElement Related things
. . . . identifier Σ 0..1 Identifier Identifiers of things that are related
. . . . ref Σ 0..1 Reference ( Any ) Related Resource

doco Documentation for this format

UML Diagram ( Legend )

DocumentManifest ( DomainResource ) A single identifier that uniquely identifies this manifest. Principally used to refer to the manifest in non-FHIR contexts masterIdentifier : Identifier [0..1] Other identifiers associated with the document manifest, including version independent identifiers identifier : Identifier [0..*] The status of this document manifest (this element modifies the meaning of other elements) status : code [1..1] The status of the document reference. (Strength=Required) DocumentReferenceStatus ! 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 type : CodeableConcept [0..1] Precise type of clinical document. (Strength=Preferred) Document Type Value Set ? 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) subject : Reference [0..1] « Patient | Practitioner | Group | Device » A patient, practitioner, or organization When the document manifest was created for which this set of documents is intended recipient : Reference [0..*] « Patient | Practitioner | RelatedPerson | Organization » Specifies submission to the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be server (not necessarily the same thing as one of the documents in it - especially if there is only one - but actual resource last modified time, since it may be wider modified, replicated, etc.) type created : CodeableConcept dateTime [0..1] « Precise type of clinical document. (Strength=Preferred) Document Type Value Set ? » Identifies who is responsible for creating the manifest, and adding documents to it author : Reference [0..*] « Practitioner | Organization | Device | Patient | RelatedPerson » When the document manifest was created A patient, practitioner, or organization for submission to the server (not necessarily the same thing as the actual resource last modified time, since it may be modified, replicated, etc.) which this set of documents is intended created recipient : dateTime Reference [0..1] [0..*] Patient | Practitioner | RelatedPerson | Organization Identifies the source system, application, or software that produced the document manifest source : uri [0..1] The status of this document manifest (this element modifies the meaning of other elements) status : code [1..1] « The status of the document reference. (Strength=Required) DocumentReferenceStatus ! » Human-readable description of the source document. This is sometimes known as the "title" description : string [0..1] Content The list of references to document content, 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 p[x] : Type [1..1] « Attachment | Reference ( Any ) » Related Related identifier to this DocumentManifest. For example, Order numbers, accession numbers, XDW workflow numbers identifier : Identifier [0..1] Related Resource to this DocumentManifest. For example, Order, DiagnosticOrder, ProcedureRequest, Procedure, EligibilityRequest, etc ref : Reference [0..1] « Any » The list of Documents included in the manifest content [1..*] Related identifiers or resources associated with the DocumentManifest related [0..*]

XML Template 

<

<DocumentManifest xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</masterIdentifier>
 <</identifier>
 <</subject>
 <</recipient>
 <</type>
 <|

 <masterIdentifier><!-- 0..1 Identifier Unique Identifier for the set of documents --></masterIdentifier>
 <identifier><!-- 0..* Identifier Other identifiers for the manifest --></identifier>
 <status value="[code]"/><!-- 1..1 current | superseded | entered-in-error -->
 <type><!-- 0..1 CodeableConcept Kind of document set --></type>
 <subject><!-- 0..1 Reference(Patient|Practitioner|Group|Device) The subject of the set of documents --></subject>
 <created value="[dateTime]"/><!-- 0..1 When this document manifest created -->
 <author><!-- 0..* Reference(Practitioner|Organization|Device|Patient|

   RelatedPerson) Who and/or what authored the manifest --></author>
 <
 <
 <
 <
 <
  <</p[x]>

 <recipient><!-- 0..* Reference(Patient|Practitioner|RelatedPerson|Organization) Intended to get notified about this set of documents --></recipient>
 <source value="[uri]"/><!-- 0..1 The source system/application/software -->
 <description value="[string]"/><!-- 0..1 Human-readable description (title) -->
 <content>  <!-- 1..* The items included -->
  <p[x]><!-- 1..1 Attachment|Reference(Any) Contents of this set of documents --></p[x]>

 </content>
 <
  <</identifier>
  <</ref>

 <related>  <!-- 0..* Related things -->
  <identifier><!-- 0..1 Identifier Identifiers of things that are related --></identifier>
  <ref><!-- 0..1 Reference(Any) Related Resource --></ref>

 </related>
</DocumentManifest>

Turtle Template 


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DocumentManifest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DocumentManifest.masterIdentifier [ Identifier ]; # 0..1 Unique Identifier for the set of documents
  fhir:DocumentManifest.identifier [ Identifier ], ... ; # 0..* Other identifiers for the manifest
  fhir:DocumentManifest.status [ code ]; # 1..1 current | superseded | entered-in-error
  fhir:DocumentManifest.type [ CodeableConcept ]; # 0..1 Kind of document set
  fhir:DocumentManifest.subject [ Reference(Patient|Practitioner|Group|Device) ]; # 0..1 The subject of the set of documents
  fhir:DocumentManifest.created [ dateTime ]; # 0..1 When this document manifest created
  fhir:DocumentManifest.author [ Reference(Practitioner|Organization|Device|Patient|RelatedPerson) ], ... ; # 0..* Who and/or what authored the manifest
  fhir:DocumentManifest.recipient [ Reference(Patient|Practitioner|RelatedPerson|Organization) ], ... ; # 0..* Intended to get notified about this set of documents
  fhir:DocumentManifest.source [ uri ]; # 0..1 The source system/application/software
  fhir:DocumentManifest.description [ string ]; # 0..1 Human-readable description (title)
  fhir:DocumentManifest.content [ # 1..* The items included
    # DocumentManifest.content.p[x] : 1..1 Contents of this set of documents. One of these 2
      fhir:DocumentManifest.content.pAttachment [ Attachment ]
      fhir:DocumentManifest.content.pReference [ Reference(Any) ]
  ], ...;
  fhir:DocumentManifest.related [ # 0..* Related things
    fhir:DocumentManifest.related.identifier [ Identifier ]; # 0..1 Identifiers of things that are related
    fhir:DocumentManifest.related.ref [ Reference(Any) ]; # 0..1 Related Resource
  ], ...;
]

  Changes since DSTU2

DocumentManifest
  • No Changes

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 Conversion Maps (status = 1 test that all execute ok. 1 fail round-trip testing and all r3 resources are valid.).

 

Alternate definitions: Schema / Schematron , Resource Profile Master Definition ( XML , JSON ), Questionnaire XML Schema / Schematron (for ) + JSON Schema , ShEx (for Turtle )

6.10.2.1 2.43.2.1 Terminology Bindings

DocumentManifest.type DocumentManifest.status
Path Definition Type Reference
DocumentManifest.status Precise type The status of clinical document. the document reference. Preferred Required Document Type Value Set DocumentReferenceStatus
DocumentManifest.type The status Precise type of the document reference. clinical document. Required Preferred DocumentReferenceStatus Document Type Value Set

6.10.3 2.43.3 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Paths Expression In Common
author reference Who and/or what authored the manifest DocumentManifest.author
( Practitioner , Organization , Device , Patient , Organization , Practitioner , RelatedPerson )
content-ref reference Contents of this set of documents DocumentManifest.content.pReference DocumentManifest.content.p.as(Reference)
(Any)
created date When this document manifest created DocumentManifest.created
description string Human-readable description (title) DocumentManifest.description
identifier token Unique Identifier for the set of documents DocumentManifest.masterIdentifier, DocumentManifest.masterIdentifier | DocumentManifest.identifier 26 Resources
patient reference The subject of the set of documents DocumentManifest.subject
( Patient ) 		31 Resources
recipient reference Intended to get notified about this set of documents DocumentManifest.recipient
( Practitioner , Organization , Patient , Practitioner , RelatedPerson )
related-id token Identifiers of things that are related DocumentManifest.related.identifier
related-ref reference Related Resource DocumentManifest.related.ref
(Any)
source uri The source system/application/software DocumentManifest.source
status token current | superseded | entered-in-error DocumentManifest.status
subject reference The subject of the set of documents DocumentManifest.subject
( Device , Patient , Practitioner , Group , Device , Patient )
type token Kind of document set DocumentManifest.type 6 Resources