Difference between revisions of "Scheduled Workflow"
Line 31: | Line 31: | ||
'''Profile Status:''' [[Comments| Final Text]] | '''Profile Status:''' [[Comments| Final Text]] | ||
− | |||
'''Documents:''' | '''Documents:''' | ||
− | |||
− | |||
− | |||
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:] | [http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:] | ||
− | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section | + | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 3 documents the profile |
− | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 2] - Sections 4.8 to 4. | + | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 2] - Sections 4.1 to 4.8, 4.10 to 4.14, 4.16, 4.18, and 4.20 to 4.21, document specific transactions. Appendices A, B and D provide additional requirements and suggestions on mapping information to ensure consistent flow of information throughout the department. |
− | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 3] - | + | :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 3] - Sections 4.42, and 4.48 to 4.49 document specific transactions. |
'''Underlying Standards:''' | '''Underlying Standards:''' | ||
− | |||
:* [http://dicom.nema.org DICOM] | :* [http://dicom.nema.org DICOM] | ||
:* [http://www.hl7.org HL7] | :* [http://www.hl7.org HL7] | ||
− | |||
− | |||
==See Also== | ==See Also== |
Revision as of 17:19, 7 March 2008
Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.
Summary
Scheduled Workflow establishes a seamless flow of information that supports efficient patient care workflow in a typical imaging encounter. It specifies transactions that maintain the consistency of patient information from registration through ordering, scheduling, imaging acquisition, storage and viewing. This consistency is also the foundation for subsequent workflow steps, such as reporting.
Benefits
<Crib material from the user handbook>
Details
<A few paragraphs, if appropriate, providing more details (in user-speak, not tech-speak) on what the profile does and how it works.>
Systems Affected
Systems involved in this profile are:
- Enterprise-wide information systems that manage patient registration and services ordering (i.e., admit-discharge-transfer (ADT)/registration system and hospital information system (HIS ))
- Radiology departmental information systems that manage department scheduling (i.e., radiology information system (RIS))
- Radiology image management/archiving (i.e., picture archiving and communication system (PACS))
- Acquisition modalities
Specification
Profile Status: Final Text
Documents: IHE Radiology Technical Framework:
- Vol. 1 - Section 3 documents the profile
- Vol. 2 - Sections 4.1 to 4.8, 4.10 to 4.14, 4.16, 4.18, and 4.20 to 4.21, document specific transactions. Appendices A, B and D provide additional requirements and suggestions on mapping information to ensure consistent flow of information throughout the department.
- Vol. 3 - Sections 4.42, and 4.48 to 4.49 document specific transactions.
Underlying Standards:
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one>
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Scheduled Workflow FAQ answers typical questions about what the Profile does.
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile.
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >
The Cross-Enterprise Document Sharing Implementation provides additional information about implementing this Profile (well XDS actually) in software.
This page is based on the Profile Template