Referral Order Linking: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
Ejones (talk | contribs)
1,406 edits
No edit summary
JohnMoehrke (talk | contribs)
2,910 edits
 
(12 intermediate revisions by 2 users not shown)
Line 4: Line 4:


==Summary==
==Summary==
''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases). Don't get into how it works, leave that to the Details section.>''
One of the challenges for users of XD* based exchanges is that there is no profiled mechanism to indicate the order numbers associated with the outstanding orders. This makes it difficult to manage inbound and outbound referral, and /or order transactions for the same patient to and from the same providers exchanging information related to a referral or order.


''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
The Referral/Order Linking profile solves this problem by documenting specific locations and formats, which will facilitate programmatic matching and or linking of related documents for both outbound and inbound transactions for the same patient to and or from the same provider. XD* provides metadata, and CDA provides discrete elements when structured documents are used; both can be constrained for defining order and referral number locations.


''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
The referral, and or order number sent with one or more documents in an XD* submission set can be managed by receiving systems and returned in response fulfillments. This profile defines where these numbers are placed in XDS metadata for submissions and where fulfillments of orders are conveyed in CDA documents.
 
[[Image:ROLWorkflow.png|450px]]


==Benefits==
==Benefits==
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (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). Consider using a bullet list for readability.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
This profile facilitates programmatic matching and or linking of related documents for both outbound and inbound transactions for the same patient to and or from the same providers. It is intended to support care coordination in situations where outstanding requests for referrals, consultations, studies, lab tests or other services may need to be tracked or followed. These requests can be tracked using identifiers, often referred to as referral numbers or order numbers depending upon the type of service requested.


==Details==
==Details==


''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
The Referral/Order Linking Profile describes the content and bindings used to convey order numbers between systems. The matching of content to order numbers happens in two directions. For example:
# submitted content in support of a healthcare referral needs to be matched and or linked by receiving systems
# content in response to a referral needs to be matched and or linked by receiving systems


''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
==Systems Affected==
==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. and for each, how it would participate.>''
* EHR systems may provide and consume order numbers to support the referral/order workflow


<!--
'''Actors & Transactions:'''
* ''PACS systems may store, manage, and/or display Evidence Documents.''
* ''Display systems may query, retrieve and display Evidence Documents.''
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
-->


'''Actors & Transactions:'''
* [[Order Placer]]
* [[Order Filler]]


''<Insert an actor-transaction diagram, and or list of Content Definitions>''
[[Image:ROLOrderTransactions.png|450px]]


==Specification==
==Specification==


'''Profile Status:''' [[Comments| Final Text]]   
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''


'''Documents:'''  
'''Documents:'''  
Line 95: Line 91:
This page is based on the [[Profile Overview Template]]
This page is based on the [[Profile Overview Template]]


[[Category:Template]]
[[Category:Profiles]][[Category:Patient Care Coordination]][[Category:DocShare]][[Category:CDA]]

Latest revision as of 11:16, 4 November 2019

The Referral/Order Linking profile describes what is necessary to communicate and link the referral and/or order number in documentation and metadata associated with services requested by an order placer.

Summary

One of the challenges for users of XD* based exchanges is that there is no profiled mechanism to indicate the order numbers associated with the outstanding orders. This makes it difficult to manage inbound and outbound referral, and /or order transactions for the same patient to and from the same providers exchanging information related to a referral or order.

The Referral/Order Linking profile solves this problem by documenting specific locations and formats, which will facilitate programmatic matching and or linking of related documents for both outbound and inbound transactions for the same patient to and or from the same provider. XD* provides metadata, and CDA provides discrete elements when structured documents are used; both can be constrained for defining order and referral number locations.

The referral, and or order number sent with one or more documents in an XD* submission set can be managed by receiving systems and returned in response fulfillments. This profile defines where these numbers are placed in XDS metadata for submissions and where fulfillments of orders are conveyed in CDA documents.

Benefits

This profile facilitates programmatic matching and or linking of related documents for both outbound and inbound transactions for the same patient to and or from the same providers. It is intended to support care coordination in situations where outstanding requests for referrals, consultations, studies, lab tests or other services may need to be tracked or followed. These requests can be tracked using identifiers, often referred to as referral numbers or order numbers depending upon the type of service requested.

Details

The Referral/Order Linking Profile describes the content and bindings used to convey order numbers between systems. The matching of content to order numbers happens in two directions. For example:

  1. submitted content in support of a healthcare referral needs to be matched and or linked by receiving systems
  2. content in response to a referral needs to be matched and or linked by receiving systems

Systems Affected

  • EHR systems may provide and consume order numbers to support the referral/order workflow

Actors & Transactions:

Specification

Profile Status: Trial Implementation

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>


Underlying Standards:


<list all the standards on which the profile is based; if possible with links to sources>

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. Start with the name of the other profile as a link and then explain the relationship.>


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). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >


This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=Referral_Order_Linking&oldid=118081"