Patient Information Reconciliation: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Kevino (talk | contribs)
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
The Patient Information Reconciliation (PIR) Profile coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients.  
'''Patient Information Reconciliation (PIR)''' coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients.  


__TOC__
__TOC__


==Summary==
==Summary==
PIR augments [[Scheduled Workflow]] by providing the means to match images acquired for an unidentified patient with the patient's registration and order history. In the example of the trauma case, this allows subsequent reconciliation of the patient record with images acquired (either without a prior registration or under a generic registration) before the patient's identity could be determined.
PIR extends [[Scheduled Workflow]] to handle:
* unidentified/emergency patient
* demographic information updates
** patient name changes (marriage, etc.)
** correction of mistakes
** ID space mergers
 
Such changes are reliably propogated to all affected systems, which update all affected data.
The result is a complete patient record.
 
In the example of the trauma case, images can be acquired (either without a prior registration or under a generic registration), and read and then later merged with the patients record when their identity is determined.


[[Image:rad_pir_profile_diag.jpg|center|Patient Information Reconciliation]]  
[[Image:rad_pir_profile_diag.jpg|center|Patient Information Reconciliation]]  


==Benefits==
==Benefits==
''<List the key benefits the profile provides (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).>''


Enabling after-the-fact matching greatly simplifies exception-handling situations.
* Normal workflow proceeds even when the patient is unknown


''<Get additional details from Radiology Handbook>''
* The patient record reconciles itself into a whole when the patient is identified.
 
* Eliminates confusion over which system should reconcile what where.
 
* Reduction of errors
** Reduces incorrectly identified or “lost” studies
 
* More complete medical record
** Supports maintenance of demographics to maintain database correspondence


Extends Scheduled Workflow
* Flexible Trauma Workflow
Handle unidentified/emergency patient
Handle demographic information updates
Changes propagated to all affected systems, affected data updated


Reduction of errors
''<Get additional details from Radiology Handbook>''
Reduces incorrectly identified or “lost” studies
More complete medical record
Supports maintenance of demographics to maintain database correspondence
Flexible Trauma Workflow


==Details==
==Details==


''<A few paragraphs, if appropriate, providing more details (in user-speak, not tech-speak) on what the profile does and how it works.>''
''<Explain a few details about how ''
* ''the PACS is notified of demographics changes''
* ''the RIS backfills orders''
* ''the modality doesn't mess with anything''
>''


==Systems Affected==
==Systems Affected==
Line 34: Line 48:
* Radiology departmental information systems that manage department scheduling (RIS) and image management/archiving (PACS)
* Radiology departmental information systems that manage department scheduling (RIS) and image management/archiving (PACS)
* Acquisition modalities
* Acquisition modalities
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''


'''Actors & Transactions:'''
'''Actors & Transactions:'''
Line 43: Line 55:
==Specification==
==Specification==


'''Profile Status:''' [[Comments| Final Text]]   
'''Profile Status: ''' [https://wiki.ihe.net/index.php/Comments#Phases_of_Development Final Text]   


'''Documents:'''  
'''Documents:'''  


[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [https://profiles.ihe.net/RAD/ IHE Radiology Technical Framework]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 4 documents the profile, Appendix C discusses relavent information exchange between the Order Filler and the Image Manager, and Appendix G discusses issues of reconciliation when using XDS-I
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.5 to 4.7, 4.11 to 4.13, 4.16, 4.26, 4.27, and [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Section 4.46 document specific transactions
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Appendix D provides useful information for handling Patient Identifiers during a merge of records.


'''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==
Line 84: Line 92:


[[Category:Profiles]]
[[Category:Profiles]]
[[Category:RAD Profile]]
[[Category:DICOM]]
[[Category:HL7v2]]

Latest revision as of 09:01, 26 June 2024

Patient Information Reconciliation (PIR) coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients.

Summary

PIR extends Scheduled Workflow to handle:

  • unidentified/emergency patient
  • demographic information updates
    • patient name changes (marriage, etc.)
    • correction of mistakes
    • ID space mergers

Such changes are reliably propogated to all affected systems, which update all affected data. The result is a complete patient record.

In the example of the trauma case, images can be acquired (either without a prior registration or under a generic registration), and read and then later merged with the patients record when their identity is determined.

Patient Information Reconciliation
Patient Information Reconciliation

Benefits

  • Normal workflow proceeds even when the patient is unknown
  • The patient record reconciles itself into a whole when the patient is identified.
  • Eliminates confusion over which system should reconcile what where.
  • Reduction of errors
    • Reduces incorrectly identified or “lost” studies
  • More complete medical record
    • Supports maintenance of demographics to maintain database correspondence
  • Flexible Trauma Workflow

<Get additional details from Radiology Handbook>

Details

<Explain a few details about how

  • the PACS is notified of demographics changes
  • the RIS backfills orders
  • the modality doesn't mess with anything

>

Systems Affected

  • Enterprise-wide information systems that manage patient registration and services ordering (ADT/registration system, HIS)
  • Radiology departmental information systems that manage department scheduling (RIS) and image management/archiving (PACS)
  • Acquisition modalities

Actors & Transactions:

Specification

Profile Status: Final Text

Documents:

Underlying Standards:

See Also

Related Profiles

  • Scheduled Workflow provides the data handling framework and is a pre-requisite for PIR
  • Patient Identifier Cross Referencing and Patient Demographics Query can be useful to establish the demographics to reconcile
  • Systems implementing PIR are expected to operate on all relevant objects, including those created as part of Radiology Content Profiles.
  • Workflow profiles in other domains were developed after PIR was written and were able to embed the transactions directly.

Consumer Information

The Patient Information Reconciliation FAQ answers typical questions about what the Profile does.

Patient Information Purchasing describes considerations when purchasing equipment to deploy this Profile.

Implementer Information

Patient Information Reconciliation Implementation provides additional information about implementing this Profile in software.

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >


This page is based on the Profile Template