Patient Information Reconciliation

Summary

Patient Information Reconciliation

Patient Information Reconciliation extends Scheduled Workflow by providing the means to match images acquired for an unidentified patient (for example, during a trauma case) 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.

Benefits

Enabling after-the-fact matching greatly simplifies exception-handling situations.

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

See Also

<Tell a user in one sentence what the profile is about (including the acronym) so they can decide if they're on the right page (and copy this one sentence description into the Profiles page as well), e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams. >

}}}

Summary

<Describe the profile in about a paragraph using user-oriented language.>

<Insert a simple graphic that, at a glance, gives an impression of what the profile is about. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. Do not use an actor/transaction diagram here.>

<See Help - Tips and Tricks for details on inserting an image/graphic.>

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).>

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

<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:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. E.g.>

IHE Radiology Technical Framework:

• Vol. 1 - Section 5 documents the profile
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23 document specific transactions
• Vol. 3 - Appendix E provides additional informative text

Underlying Standards:

• <list standards on which this profile is based; if possible with links to sources>
• DICOM
• HL7
• ...

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 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>

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) >

This page is based on the Profile Template