Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

View Transaction

View Transaction Information

Id: 264

Keyword: ITI-57

Name: Update Document Set

Description: The Update Document Set transaction passes a collection of metadata updates from the Document Administrator actor to the Document Registry or Document Recipient actor.

TF Reference:

Status: Trial Implementation

Document Section :

None

Id
Keyword
Name
Description
Action
21 XDR Cross-Enterprise Document Reliable Interchange Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS.
39 XDS.b Cross-Enterprise Document Sharing The Cross-Enterprise Document Sharing (XDS.b) IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
368 XCMU_DEPRECATED Cross Community Meta Data Update Deprecated
386 CH:XDS.b Cross-Enterprise Document Sharing Swiss Extension
Id
Keyword
Name
Description
Action
43DOC_REGISTRYDocument RegistryThe Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.
76DOC_RECIPIENTDocument Recipient The Document Recipient receives documents and metadata sent by another actor.
89INIT_GATEWAYInitiating Gateway
184DOC_ADMINISTRATORDocument AdministratorThe Document Administrator actor supports metadata update by issuing the Update Document Set transaction [ITI-57] and Delete Document Set [ITI-61 ] transaction to the Document Registry actor.
Assertion Id
Description
ITI57-001 An Update Document Set Request message is an ebRS SubmitObjectsRequest containing ebRIM formatted metadata
ITI57-002 ITI TF-3: Table 4.3.1-3 details the requirements on metadata attributes for each actor submitting metadata
ITI57-003 The receiving actor shall be able to manage the following attributes on DocumentEntry, Folder, and Association objects: logicalID version availabilityStatus, which require special handling dictated by metadata update
ITI57-004 The receiving actor SHALL be capable of storing multiple versions of DocumentEntry and Folder metadata objects
ITI57-005 A Document Registry then it shall make stored versions of DocumentEntry and Folder metadata objects available through the Registry Stored Query [ITI-18] transaction
ITI57-006 An Update Document Set [ITI-57] request SHALL include a SubmissionSet object
ITI57-007 An Update Document Set request [ITI-57] shall not include initial versions of DocumentEntry or Folder objects. In a request, initial versions are recognized by having entryUUID = logicalID or logicalID missing
ITI57-008 An updated version of a DocumentEntry object, when included in an Update Document Set request [ITI-57], SHALL be a complete DocumentEntry object. Individual attributes cannot be submitted alone
ITI57-009 An updated version of a Folder object, when included in an Update Document Set request [ITI-57], shall be a complete Folder object. Individual attributes cannot be submitted alone
ITI57-010 All metadata objects in an Update Document Set Request [ITI-57] message shall have an entryUUID (id) attribute
ITI57-011 Metadata objects entryUUID (id) attribute MAY be coded as a UUID or symbolic nam
ITI57-012 Metadata objects entryUUID (id) attribute SHALL be used by the receiving actor when reporting errors
ITI57-013 The submission of metadata objects: DocumentEntries, Folders, Associations; in the support of metadata versioning follows the same rules as defined for the Register Document Set-b [ITI-42] transaction or Provide and Register Document Set-b [ITI-41] transaction. These rules are defined in ITI TF-3: 4.2 and 4.3
ITI57-014 A single Update Document Set transaction MAY contain both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry.
ITI57-015 When a single Update Document Set transaction contains both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry, the Document Registry or Document Recipient SHALL create the new DocumentEntry version and then apply the new availablityStatus value to this new version. The previous version, the one present before the processing of this transaction began, SHALL not be modified
ITI57-016 A single Update Document Set transaction MAY contain both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder
ITI57-017 When a single Update Document Set transaction contains both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder, the Document Registry or Document Recipient SHALL create the new Folder version and apply the new availablityStatus value to this new version
ITI57-018 A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder) Metadata operations targeting the same logical object
ITI57-019 A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder or Association) Status operations targeting the same logical object
ITI57-020 At any point in time there SHALL be at most one version of a logical DocumentEntry object with status Approved in the registry/recipient. If this version exists it shall always be the most recent version

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top