XDW - IHE

More documents

Recommendations

Info

IHE IT Infrastructure Technical Framework Supplement – Cross-Enterprise Document Workflow (XDW) ______________________________________________________________________________ 650 655 660 665 670 675 680 685 5.4.2.1 XDW Workflow Document Elements from HL7 CDA Standard Some elements are incorporated directly from the HL7 CDA standard. This means that the elements, their definitions, and the rules for interpreting them are in the HL7 standard. These are summarized here for convenience. Patient and Author elements have been defined based upon the HL7 CDA R-MIM. The XDW schema defines these elements using elements from CDA, and was derived by eliminating all elements that are not needed for workflow identification purposes. The R-MIM includes elements that are of clinical value. These have been removed for workflow use. 5.4.2.2 XDW Workflow Document Elements defined by IHE_XDWProfile The XDW Workflow Document also has elements that are defined by IHE: • This identifier is common across all document instances for the same Workflow Document. It represents the Folder.uniqueId of the Workflow Content Folder in which the Workflow Document is contained. It must be globally unique, because it is shared by many organizations. Every version of the Workflow Document will have the same ID value. • This is used to simplify management of the changes to the Workflow Document as the work is performed. It shall be created as "1", and incremented for each update to the Workflow Document. • This shall be either OPEN – which means that further updates are expected for this Workflow Document. These could be modifications to existing tasks or addition of new tasks or update an existing task with a new . Tasks shall not be deleted. CLOSED – which means that further updates to this Workflow Document shall not be made. Further work should be managed by using a different or new Workflow Document. • . This is the reference to the documents that define the workflow. These are usually policy or procedure documents. They may also be references to medical articles. Because the policies and procedures will be shared by many organizations, so it should recommend being an OID referring to the copy of the document in the XDS Affinity Domain. It is assigned by the creator of the initial Workflow Document and shall be preserved in all subsequent versions of the document. 5.4.2.3 XDW Workflow Document Elements from the OASIS Human Task The descriptions of a task and of are taken from the OASIS Human Task standard. This standard defines a way to describe a human task. It was defined as an extension to the BPEL and BPMN workflow standards. These standards are in use to manage the workflow of automated tasks under the control of an integrated task management system. It was ___________________________________________________________________________ 26 Rev. 2.0 – 2011-07-29 Copyright © 2011: IHE International, Inc.
IHE IT Infrastructure Technical Framework Supplement – Cross-Enterprise Document Workflow (XDW) ______________________________________________________________________________ 690 695 700 705 recognized that while they do not have the ability to control human tasks, they needed a way to describe tasks to be performed by humans and other organizations. The element groups all information about one task in the workflow, the is structured in two sub elements: and . • describes a single task. This is a long list of details about the task, a description, the inputs to the task (e.g., documents), the outputs from the task (e.g., documents), fault descriptions, comments, and attachments (other documents that do not represent outputs). The include elements like the task ID, description, state, etc. • contains a list of the elements that describe the changes of the task. For each task we can have one or more that described the history of the task. There is a long list of details about the : an , a description, the inputs to the (e.g., documents), the outputs from the (e.g., documents), fault descriptions, comments, and attachments (other documents that do not represent outputs). The details include elements like the task ID, description, state, etc. The definitions and rules such as the state machine that defines states are in the Human Task standard. There are other datatypes and web services also defined in that standard. This profile incorporates those only to the extent needed to define the meaning of the elements in tTaskInstanceData. 5.4.2.3-1 XDW Workflow elements derived from OASIS WS-HumanTask 710 5.4.2.4 Relationship between Task and When a Task is generated it has a first . A Task can have only one if the status of the task is not modifiable and it is born just completed or it can have more status. In this case at any time the task changed a new is created and the Workflow Document must be updated. ___________________________________________________________________________ 27 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 25: IHE IT Infrastructure Technical Fra
Page 43: IHE IT Infrastructure Technical Fra

XDW - IHE

Create successful ePaper yourself

Delete template?

Save as template?