Difference between revisions of "Import Reconciliation Workflow"

From IHE Wiki
Jump to navigation Jump to search
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Import Reconciliation Workflow (IRWF)''' manages importing images from CDs, hardcopy, etc. and reconciling identifiers to match local values.
+
'''Import Reconciliation Workflow (IRWF)''' is an integration profile that manages importing images from CDs, hardcopy, etc. and reconciling identifiers to match local values.
  
  
Line 49: Line 49:
  
 
[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 21
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol1.pdf Vol. 1] - Section 21
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Section 4.10 and Appendix A.5
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol2.pdf Vol. 2] - Section 4.10 and Appendix A.5
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Sections 4.59, 4.60 and 4.61
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol3.pdf Vol. 3] - Sections 4.59, 4.60 and 4.61
  
 
[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework:]
 
[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework:]
Line 64: Line 64:
 
'''Related Profiles'''
 
'''Related Profiles'''
  
:* Scheduled Workflow Profile is the foundation upon which IRFW is based.  IRFW uses the existing workflow mechanisms for notification and storage of imported Evidence Objects.
+
* [[Scheduled Workflow]] is the foundation upon which IRFW is based.  IRFW uses the existing workflow mechanisms for notification and storage of imported Evidence Objects.
:* Patient Demographics Query [PDQ] provides a mechanism to retreive local Patient Demographics for use in the Patient Information importation.
+
* [[Patient Demographics Query]] [PDQ] retrieves local Patient Demographics for use in the Patient Information importation.
:* There are a number of "content profiles" describing the details of the DICOM Objects that may be imported into the Enterprise.  This includes:
+
* [[Portable Data for Imaging]] [PDI] specifies CDs that are particularly suited to importing.
:** Nuclear Medicine Image [NM] specifies Nuclear Medician images and result screens.
+
 
:** Mammography Image [MAMMO] specifies Mammgoraphy images and evidence objects.
+
Several "content profiles" specify DICOM data that may be imported, including:
:** Evidence Documents [ED{ specifies how data objects such as digital measuremens.
+
* [[Nuclear Medicine Image]] [NM] specifies Nuclear Medicine images and result screens.
:** Key Image Note [KIN] let users flag images as significant (e.g. for referring, for surgery, etc.) and adds notes.
+
* [[Mammography Image]] [MAMMO] specifies Mammography images and evidence.
:** Simple Image and Numberic Report [SINR] specifies Diagnostic Radiology Reports.
+
* [[Evidence Documents]] [ED] specifies digital measurements.
:* Portable Data for Imaging [PDI] provides reliable interchange of image data and diagnostic reports on CDs for importing.
+
* [[Key Image Note]] [KIN] let users flag images as significant (e.g. for referring, for surgery, etc.) and add notes.
 +
* [[Simple Image and Numeric Report]] [SINR] specifies Diagnostic Radiology Reports.
 +
 
  
 
'''References'''
 
'''References'''
  
van Ooijen, P.M.A, et al, ''Evaluation of the Use of CD-ROM Upload into the PACS or Institutional Web Server'', Journal of Digital Imaging, Vol 19, Suppl 1, 2006, pp 72-77
+
* ACR–AAPM–SIIM Technical Standard for Electronic Practice of Medical Imaging. J.T. Norweck, et al., [http://link.springer.com/content/pdf/10.1007%2Fs10278-012-9522-2.pdf SIIM & ACR Publication, Sept. 2012]
: Discusses experiences with a process similar to the Scheduled Import Option of IRWF.
+
 
 +
* van Ooijen, P.M.A, et al, ''Evaluation of the Use of CD-ROM Upload into the PACS or Institutional Web Server'', Journal of Digital Imaging, Vol 19, Suppl 1, 2006, pp 72-77
 +
:* Discusses experiences with a process similar to the Scheduled Import Option of IRWF.
 +
 
 +
* Lu, M.T, et al, ''Reducing the Rate of Repeat Imaging: Import of Outside Images to PACS'', American Journal of Roentgenology, Vol 198(3), March 2012, pp 628-634 - [http://www.ajronline.org/content/198/3/628.abstract Abstract] - [http://www.cmio.net/index.php?option=com_articles&view=article&id=32336:ajr-no-repeats-importing-outside-exams-to-pacs-cuts-imaging- Commentary in CMIO]
 +
:* "When outside images were not available, 72% (13/18) of patients underwent repeat imaging; when outside images were available but not imported, 52% (14/27); when outside images were imported to PACS, 11% (9/79)"
 
   
 
   
  

Revision as of 12:04, 28 May 2016

Import Reconciliation Workflow (IRWF) is an integration profile that manages importing images from CDs, hardcopy, etc. and reconciling identifiers to match local values.



Summary

Import Reconciliation Workflow Integration Profile establishes a flow of information that supports the efficient importation of DICOM patient data from an external enterprise. It provides specifies transactions that maintain the use of consistent patient/procedure information between the data being imported and the local enterprise, while maintaining the integrity of the original data. DICOM Patient data imported into the local enterprise can be used in the same manner as DICOM data created by the local enterprise, such as reporting.


Irwf-picture.JPG

Benefits

Reduce Errors and Enhance Patient Care

  • Prevents missing data from other sites because the PACS is able to import data sent on interchange media and integrate it with the patient’s record
  • Prevents mismatched patient identifiers in data imported from interchange media from other institutions because the PACS reconciles this information to local values at import time

Improve Data Accessibility

  • Improves access to other sites’ data—the PACS can import and reconcile patient and diagnostic information on interchange media from other institutions and clinics

Details

The Import Reconciliation Workflow Integration Profile:

  • Specifies both the data and workflow requirements for importing existing DICOM Evidence Objects and importing Hardcopy from an external Enterprise.
  • Provides a process to reconcile imported patient and procedure information with local patient and procedure information through the use of Worklists and Patient Demographics Query.
  • Specifies critical patient demographics (e.g. Patient Name, Patient ID) and order/procedure Information (e.g. Accession Number) which is important since the local Enterprise will typically have different identifiers (for patient, orders, etc.) from the Enterprise that created the Evidence Objects or Hardcopy being imported.
  • Specifies a mechanism for preserving a copy of the original values inside the imported DICOM Composite Objects when attribute values must be changed.
  • Ensures that DICOM images, reports and other evidence objects associated with a particular import have been archived.
  • Ensures that the status of importation workflow steps are known throughout the department by specifying the use of DICOM Performed Procedure Step to convey that status from the Evidence Creator to the RIS and the PACS.

Systems Affected

Systems which are expected to have implemented actors from this profile include:

  • Enterprise-wide information systems that manage patient registration and service ordering (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 and communication systems (PACS)
  • Importation Workstations that manage the reading and reconciliation of the data to be imported (e.g. CDs, digitized films, cross-enterprise networks).


Actors and Transactions

Irwf-actor-transaction.JPG

Specification

Profile Status: Final Text

Documents:

IHE Radiology Technical Framework:

  • Vol. 1 - Section 21
  • Vol. 2 - Section 4.10 and Appendix A.5
  • Vol. 3 - Sections 4.59, 4.60 and 4.61

IHE IT Infrastructure Technical Framework:

Underlying Standards:

See Also

Related Profiles

  • Scheduled Workflow is the foundation upon which IRFW is based. IRFW uses the existing workflow mechanisms for notification and storage of imported Evidence Objects.
  • Patient Demographics Query [PDQ] retrieves local Patient Demographics for use in the Patient Information importation.
  • Portable Data for Imaging [PDI] specifies CDs that are particularly suited to importing.

Several "content profiles" specify DICOM data that may be imported, including:


References

  • van Ooijen, P.M.A, et al, Evaluation of the Use of CD-ROM Upload into the PACS or Institutional Web Server, Journal of Digital Imaging, Vol 19, Suppl 1, 2006, pp 72-77
  • Discusses experiences with a process similar to the Scheduled Import Option of IRWF.
  • Lu, M.T, et al, Reducing the Rate of Repeat Imaging: Import of Outside Images to PACS, American Journal of Roentgenology, Vol 198(3), March 2012, pp 628-634 - Abstract - Commentary in CMIO
  • "When outside images were not available, 72% (13/18) of patients underwent repeat imaging; when outside images were available but not imported, 52% (14/27); when outside images were imported to PACS, 11% (9/79)"


<Replace the Template links below with links to the actual pages for the Profile>

The Profile FAQ Template answers typical questions about what the Profile does.

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile.

The Profile Implementation Template provides additional information about implementing this Profile in software.


This page is based on the Profile Template