XDW - IHE

More documents

Recommendations

Info

IHE IT Infrastructure Technical Framework Supplement – Cross-Enterprise Document Workflow (XDW) ______________________________________________________________________________ taskDetails element Standard Optionality Description Escaleted searchBy Outcome parentTaskId hasSubTasks OASIS_WS- HumanTask OASIS_WS- HumanTask OASIS_WS- HumanTask OASIS_WS- HumanTask OASIS_WS- HumanTask O O O XDW prohibits use of subTasks XDW prohibits use of subTasks. 785 • (type element tXDWeventHistory) taskEventHistory element taskEvent OASIS_WS-HumanTask R Standard Optionality Description • (type element taskEvent_type) taskEvent element Standard Optionality Description Id OASIS_WS-HumanTask R eventTime OASIS_WS-HumanTask R See XXX Identifier OASIS_WS-HumanTask R Principal OASIS_WS-HumanTask O eventType OASIS_WS-HumanTask R startOwner OASIS_WS-HumanTask O endOwner OASIS_WS-HumanTask O Status OASIS_WS-HumanTask R hasData OASIS_WS-HumanTask O eventData OASIS_WS-HumanTask O This structure includes the data elements that were changed by this event. faultName OASIS_WS-HumanTask O OASIS_WS-HumanTask ___________________________________________________________________________ 34 Rev. 2.0 – 2011-07-29 Copyright © 2011: IHE International, Inc.
IHE IT Infrastructure Technical Framework Supplement – Cross-Enterprise Document Workflow (XDW) ______________________________________________________________________________ 5.4.4 Complete Example 790 5.4.5 Workflow Document Management 795 800 805 810 815 820 5.4.5.1 Workflow Document Lifecycle Management The Cross-Enterprise Document Workflow profile takes advantage of the lifecycle management of XDS when used in an XDS environment. A Workflow Document shall be created and submitted in a Folder. The initial document shall include at least one task on the TaskList, and have a workflowStatus of OPEN. The Workflow Document is updated when: • The information about a task is modified. This may be due to a change in some other task related information like updating the output information. • A new task is added to the . • The workflow status is changed to CLOSED. Each update shall be done using the XDS document replace when in an XDS environment. The series of steps to be taken is: • Update the XDW document to reflect the desired changes. This is often replacement of the . It may also be a change such as adding a new task to the or a new to a Task. • Use the XDS Replace operation to substitute this modified document for the old document. This replacement document shall be in the same XDS Folder as the original Workflow document. • It is possible that this will generate an error from the XDS Registry if another actor has also done a replace in the time since the current contents were obtained. If so, new current contents must be obtained and updated. This kind of error should be very rare because updating is much faster than the rate that people perform tasks. When using XDR or XDM, the receiving actor shall perform an equivalent local update process. When it is time to stop work on this workflow, a final update to set the workflow status to CLOSED shall be performed. The specific rules for determining when work is completed are not specified by the XDW Profile. They may be determined by other IHE profiles, by the local administration, or some other source. This profile does not further constrain the rules for document lifecycle management, but other IHE profiles may add requirements requiring that certain kinds of tasks be created initially, ___________________________________________________________________________ 35 Rev. 2.0 – 2011-07-29 Copyright © 2011: IHE International, Inc.
Page 1 and 2: Integrating the Healthcare Enterpri
Page 3 and 4: IHE IT Infrastructure Technical Fra
Page 33: IHE IT Infrastructure Technical Fra
Page 43: IHE IT Infrastructure Technical Fra

XDW - IHE

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?