View scope

keyword
XDM
Description
This scope gathers the assertions which apply in the context of the Cross-Enterprise Document Media Interchange (XDM) domain above all integration profiles

34 Assertions in Scope

net.ihe.gazelle.assets.SearchCriteria

Id scheme
Assertion id
Predicate
ITI32ITI32-001If the ZIP over Email Response Option is supported, the Portable Media Importer shall detect whether the Import was successful or not.
ITI32ITI32-002The Portable Media Creator shall be able to include one or multiple Submission Set(s), including document(s) and associated metadata
ITI32ITI32-003Additionally it shall include a README.TXT file and an INDEX.HTM and associated files for use to display the media content using a simple browser. It may include other files and directories that the Portable Media Importer will ignore.
ITI32ITI32-004The media shall contain at the root directory level an IHE_XDM directory.
ITI32ITI32-005The media shall contain at the root directory level two files for helping access the content of the media : README.TXT and INDEX.HTM.
ITI32ITI32-006The media shall contain at the root directory level an Autorun file or equivalent shall not be present in the root directory. Executable files may be present, but shall not be configured to start automatically.
ITI32ITI32-007The IHE_XDM directory shall contain one sub-directory per submission set included on the media.
ITI32ITI32-008Each submission set directory shall contain a METADATA.XML file containing the XDS Registry metadata
ITI32ITI32-009Each submission set directory shall contain one file for each simple part document referenced in the metadata as an XDSDocumentEntry.
ITI32ITI32-010Each submission set directory shall contain one sub-directory for each multipart document referenced in the metadata as an XDSDocumentEntry.
ITI32ITI32-011Each submission set directory shall contain potentially other files and directories that are ignored by the Portable Media Importer.
ITI32ITI32-012The multipart document shall be structured as one sub-directory containing all the parts as file, including the start part corresponding to the main file to be open by the multipart document viewer.
ITI32ITI32-013The URI element of the metadata describing a file that is present on this media shall point to the file containing the document, through a relative URI where the base URI is the directory holding the METADATA.XML file that contains the DocumentEntry.URI attribute.
ITI32ITI32-014If the ZIP over Email Response Option is supported and a response was requested, the Portable Media Importer shall send a response, based on the [MDN] mechanism, depending of the success of the Import operation.
ITI32ITI32-015If the ZIP over Email Response Option is supported, Portable Media Creator shall be configurable to include in its message header the request for a response Disposition-Notification-To, followed by the email address to which Portable Media Importer shall send the response
ITI32ITI32-016The Portable Media Importer shall acknowledge this operation by sending a MDN response to the email address included in the message.
ITI32ITI32-017The Portable Media Creator shall consider that the import is successful unless the disposition-modifier contains the word error or failure, case insensitive.
ITI32ITI32-018If the ZIP over Email Option is supported, the subject line of the email shall contain the phrase XDM/1.0/DDM
ITI32ITI32-019The Portable Media Importer shall verify the integrity of the media by comparing their size and hash with the value of the corresponding entries in the METADATA.XML file of the relevant submission set directory. Mismatching documents shall be indicated to the user. Media faults shall be indicated to the user.
ITI32ITI32-020If the Basic Patient Privacy Enforcement Option is implemented, the Portable Media Creator shall populate the confidentialityCode in the document metadata with the list of values that identify the sensitivity classifications that apply to the associated document. All documents submitted shall have confidentiality codes. The confidentiality codes for different documents in the same submission may be different.