Mobile access to Health Documents (MHD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 4.2.2-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.MHD/ and changes regularly. See the Directory of published versions

1:33.2 Actor Options

Options that may be selected for each actor in this implementation guide, are listed in Table 1:33.2-1 below. Dependencies between options when applicable are specified in notes.

Table 1:33.2-1 Actor Options

Actor	Option Name
Document Source	Comprehensive Metadata
	UnContained Reference
	Simplified Publish
	Generate Metadata
	ITI-65 FHIR documents Publish
Document Recipient	Comprehensive Metadata
	XDS on FHIR
	UnContained Reference
	Simplified Publish
	Generate Metadata
	ITI-65 FHIR documents Publish
Document Consumer	UnContained Reference
Document Responder	XDS on FHIR
	UnContained Reference

The options in this guide are described in more detail in the sections below.

1:33.2.1 Comprehensive Metadata Option

Support of this option assures that the Document Source will provide comprehensive metadata. Comprehensive metadata fulfill the cardinality requirements of XDS.

A Document Source that supports this option will provide metadata consistent with the additional document sharing requirements for an XDS Document Source described in ITI TF-3: 4.3.1- Submission Metadata Attribute Optionality and ITI TF-3: 4.5.1 Metadata Object Types mapped to FHIR.

A Document Recipient that supports this option will require that any metadata provided is consistent with the additional document sharing requirements for an XDS Document Source described in ITI TF-3: 4.3.1- Submission Metadata Attribute Optionality.

1:33.2.2 XDS on FHIR Option

The Document Recipient that supports this option shall be able to be grouped with an XDS Document Source so that any publication request is passed on to that XDS environment. See the transaction specific requirements outlined in ITI-65 XDS on FHIR Option. The grouped XDS Document Source shall implement the Document Replacement Option, Document Addendum Option, Document Transformation Option, and Folder Management Option to ensure that these functionalities can be transferred from the MHD Document Source through to the XDS Document Registry.

The Document Responder that supports this option shall be able to be grouped with an XDS Document Consumer so that any query or retrieve requests can be passed on to, and responded to, by an XDS environment. The transaction specific requirements are outlined in ITI-66 XDS on FHIR Options and ITI-67 XDS on FHIR Option.

The XDS on FHIR Option is not compatible with the UnContained Reference Option. A system may be able to support both options, but only one will be able to be used at a given deployment.

1:33.2.3 UnContained Reference Option

The UnContained Reference Option recognizes that a Community may choose to longitudinally maintain their provider and patient directories, for example, an mCSD Care Services Selective Supplier and PMIR Patient Identity Registry. When this longitudinal consistency is managed, then the author, authenticator, sourcePatientInfo, and author entries do not need to be a contained copy of the information known at the time of publication ITI-65 since a Reference to the information in these directories will be valid over the full lifecycle of the entries.

The actors that support the UnContained Reference Option shall be able to create and consume full URL values in the DocumentReference.author, the DocumentReference.authenticator, the DocumentReference.context.sourcePatientInfo, and the List.source. This requirement encourages the persisting of the information at the time the document is published.

The UnContained Reference Option is not compatible with the XDS on FHIR Option. A system may be able to support both options, but only one will be able to be used at a given deployment.

1:33.2.4 Simplified Publish Option

The Simplified Publish Option recognizes that there are Document Source Actors that have simple publication needs that can be automated on the Document Recipient. The simplifications include:

• Publishing one document at a time
  • Any mime-type is supported
• The document must be included
• The Document Source can create the DocumentReference metadata and has some need to control the element values provided
• No support for On-Demand or Delayed Document Assembly
• No support for Replace
• No support for Folders
• No support for a defined SubmissionSet metadata, the Document Recipient can deterministically create the SubmissionSet from the provided DocumentReference
• No support to target a publication to a given intended recipient

The “need” may be simply that the Document Source is not capable to understand these features or does not need them.

The Document Source claiming the Simplified Push Option shall implement use of ITI-105 transaction to publish document content. The Document Source may also use ITI-65.

The Document Recipient claiming the Simplified Push Option shall implement the ITI-105 transaction. The Document Recipient will extract the document, translate the DocumentReference metadata elements into a SubmissionSet following the PCC TF-2: 4.1.1 XDSSubmissionSet Metadata, and may have further metadata translation requirements specified by the local Document Sharing Community policy.

1:33.2.5 Generate Metadata Option

The Generate Metadata Option recognizes that there are Document Source Actors that have a structured and coded format of a document (CDA or FHIR-Document) and simple publication needs that can be automated on the Document Recipient. The simplifications include:

• Only the document is provided
  • must be CDA or FHIR Document
• Publishing one document at a time
• The document must be included
• The Document Recipient can deterministically create the DocumentReference metadata
• No support for On-Demand or Delayed Document Assembly
• No support for Replace
• No support for Folders
• No support for a defined SubmissionSet metadata
• No support to target a publication to a given intended recipient

The “need” may be simply that the Document Source is not capable to understand these features or does not need them.

The Document Source claiming the Generate Metadata Option shall implement use of ITI-106 transaction to submit a document content. The Document Source may also use ITI-65.

The Document Recipient claiming the Generate Metadata Option shall implement the ITI-106 transaction. The Document Recipient will interpret the document, create or update a DocumentReference metadata, convert DocumentReference elements into a SubmissionSet. The metadata derivation shall following the PCC TF-2: 4.1.1 XDSSubmissionSet Metadata, and may have further metadata translation requirements specified by the local Document Sharing Community policy.

1:33.2.6 ITI-65 FHIR Documents Publish Option

The ITI-65 FHIR Documents Publish Option adds support to ITI-65 to carry a FHIR-Document encoded within the ITI-65, rather than needing this FHIR-Document encoded within a Binary. Actors not declaring this option are expected to only support Binary documents in ITI-65.

The Document Recipient will process the FHIR-Document accordingly to the persistance needs that it supports (e.g., XDS, MHDS).