XDW - IHE
XDW - IHE
XDW - IHE
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>IHE</strong> IT Infrastructure Technical Framework Supplement – Cross-Enterprise Document<br />
Workflow (<strong>XDW</strong>)<br />
______________________________________________________________________________<br />
650<br />
655<br />
660<br />
665<br />
670<br />
675<br />
680<br />
685<br />
5.4.2.1 <strong>XDW</strong> Workflow Document Elements from HL7 CDA Standard<br />
Some elements are incorporated directly from the HL7 CDA standard. This means that the<br />
elements, their definitions, and the rules for interpreting them are in the HL7 standard. These are<br />
summarized here for convenience.<br />
Patient and Author elements have been defined based upon the HL7 CDA R-MIM. The <strong>XDW</strong><br />
schema defines these elements using elements from CDA, and was derived by eliminating all<br />
elements that are not needed for workflow identification purposes. The R-MIM includes<br />
elements that are of clinical value. These have been removed for workflow use.<br />
5.4.2.2 <strong>XDW</strong> Workflow Document Elements defined by <strong>IHE</strong>_<strong>XDW</strong>Profile<br />
The <strong>XDW</strong> Workflow Document also has elements that are defined by <strong>IHE</strong>:<br />
• This identifier is common across all document instances for the same<br />
Workflow Document. It represents the Folder.uniqueId of the Workflow Content Folder<br />
in which the Workflow Document is contained. It must be globally unique, because it is<br />
shared by many organizations. Every version of the Workflow Document will have the<br />
same ID value.<br />
• This is used to simplify management of the changes to the<br />
Workflow Document as the work is performed. It shall be created as "1", and<br />
incremented for each update to the Workflow Document.<br />
• This shall be either<br />
OPEN – which means that further updates are expected for this Workflow Document.<br />
These could be modifications to existing tasks or addition of new tasks or<br />
update an existing task with a new . Tasks shall not be<br />
deleted.<br />
CLOSED – which means that further updates to this Workflow Document shall not<br />
be made. Further work should be managed by using a different or new<br />
Workflow Document.<br />
• . This is the reference to the documents that define the<br />
workflow. These are usually policy or procedure documents. They may also be<br />
references to medical articles. Because the policies and procedures will be shared by<br />
many organizations, so it should recommend being an OID referring to the copy of the<br />
document in the XDS Affinity Domain. It is assigned by the creator of the initial<br />
Workflow Document and shall be preserved in all subsequent versions of the document.<br />
5.4.2.3 <strong>XDW</strong> Workflow Document Elements from the OASIS Human Task<br />
The descriptions of a task and of are taken from the OASIS Human Task<br />
standard. This standard defines a way to describe a human task. It was defined as an extension<br />
to the BPEL and BPMN workflow standards. These standards are in use to manage the<br />
workflow of automated tasks under the control of an integrated task management system. It was<br />
___________________________________________________________________________<br />
26<br />
Rev. 2.0 – 2011-07-29<br />
Copyright © 2011: <strong>IHE</strong> International, Inc.