Difference between revisions of "White Paper- Mapping RadLex Codes into the IHE Radiology Scheduled Workflow Data Model"

Revision as of 09:08, 10 August 2012

1. Proposed Workitem: Brief Proposal: White Paper- Mapping RadLex Codes into the IHE Radiology Scheduled Workflow Data Model

Proposal Editor: Teri Sippel Schmidt, David Clunie
Editor: Teri Sippel Schmidt, David Clunie, more pending their formal agreement
Date: N/A (Wiki keeps history)
Version: N/A (Wiki keeps history)
Domain: Radiology

2. The Problem

Integration Problem:

RSNA members have spent several years creating a comprehensive radiology coding scheme called RadLex (www.radlex.org and playbook.radlex.org ) which includes both a radiology lexicon as well as a procedure playbook (procedure codes). Currently, RadLex is a standalone list of values, codes and definitions, albeit a comprehensive list.
At the RSNA 2012 Image Sharing demonstration, a significant effort was undertaken to use only RadLex codes throughout the entire demonstration including all of Scheduled Workflow, RSNA Report Templates, XDS/XDS-I, REM and TCE. There is little to no documented guidance on how and where to use the various RadLex codes in the IHE world. A concerted effort was made to get these mappings working for the trade show, and, for the most part, it seemed to work (well). In retrospect, however, several of the mappings were probably not quite correct.

Value Statement: We would like to take what we learned at the trade show, refine it, document and publish it for two reasons: the next group(s) of vendors or clinicians trying to implement RadLex codes should not need to start from scratch again and to promote the adoption of RadLex in the vendor and clinical communities.

3. Key Use Case

A referring physician creates a fairly generic radiology order. A tech refines the order to a specific procedure. This procedure code should get mapped into the IHE data model properly so that it can be transmitted directly to the modality via DMWL and perhaps the modality can even directly convert it to a protocol (as was done in the demo). But, wait, the tech at the modality modifies the procedure (PPS). And so it continues down the line.

Which types of RadLex codes get used and where? There is an appendix to Scheduled Workflow that goes into excrutiating detail regarding data element mappings, but this would be more specific to RadLex.

4. Standards and Systems

Systems: Maybe the Order Placer, but doubtful Department System Scheduler/Order Filler (DSS/OF) PACS Reporting system Modality

Standards: RadLex IHE Radiology Scheduled Workflow reporting - not exactly sure yet tangentially XDS

5. Discussion

This is a white paper proposal, not a profile proposal. The intent to align two RSNA initiatives more closely and increase adoption by making the subject less overwhelming/giving IHE developers a better starting point.

@@ Line 8: / Line 8: @@
 * Version: N/A (Wiki keeps history)
 * Domain: [[Radiology]]
 ==2. The Problem==
 Integration Problem:
-* RSNA members have spent several years creating a comprehensive radiology coding scheme called RadLex (www.radlex.  ) which includes both a procedure playbook (procedure codes) as well as a radiology lexicon.  Currently, RadLex is a standalone list of values, codes and definitions, albeit a comprehensive list.
+* RSNA members have spent several years creating a comprehensive radiology coding scheme called RadLex (www.radlex.org and playbook.radlex.org ) which includes both a radiology lexicon as well as a procedure playbook (procedure codes).  Currently, RadLex is a standalone list of values, codes and definitions, albeit a comprehensive list.
 * At the RSNA 2012 Image Sharing demonstration, a significant effort was undertaken to use only RadLex codes throughout the entire demonstration including all of Scheduled Workflow, RSNA Report Templates, XDS/XDS-I, REM and TCE.   There is little to no documented guidance on how and where to use the various RadLex codes in the IHE world.   A concerted effort was made to get these mappings working for the trade show, and, for the most part, it seemed to work (well).  In retrospect, however, several of the mappings were probably not quite correct.
 Value Statement:
@@ Line 21: / Line 23: @@
 ==3. Key Use Case==
-A referring physician creates a fairly generic order.   A tech refines the order to a specific procedure.  This procedure code should get mapped into the IHE data model properly so that it can be transmitted directly to the modality via DMWL and perhaps the modality can even directly convert it to a protocol (as was done in the demo).  But, wait, the tech at the modality modifies the procedure (PPS).  And so it continues down the line.
+A referring physician creates a fairly generic radiology order.   A tech refines the order to a specific procedure.  This procedure code should get mapped into the IHE data model properly so that it can be transmitted directly to the modality via DMWL and perhaps the modality can even directly convert it to a protocol (as was done in the demo).  But, wait, the tech at the modality modifies the procedure (PPS).  And so it continues down the line.
 Which types of RadLex codes get used and where?   There is an appendix to Scheduled Workflow that goes into excrutiating detail regarding data element mappings, but this would be more specific to RadLex.