Difference between revisions of "White Paper- Mapping RadLex Codes into the IHE Radiology Scheduled Workflow Data Model"
Jump to navigation
Jump to search
Teri.sippel (talk | contribs) (Created page with "__NOTOC__ ''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don'...") |
Teri.sippel (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| + | ==1. Proposed Workitem: Brief Proposal: White Paper- Mapping RadLex Codes into the IHE Radiology Scheduled Workflow Data Model == | ||
| − | + | * Proposal Editor: Teri Sippel Schmidt/Karos Health, David Clunie | |
| − | + | * Editor: Teri Sippel Schmidt/Karos Health, David Clunie, Daniel Rubin/Stanford (RadLex chair), more pending their formal agreement | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * Proposal Editor: | ||
| − | * Editor: | ||
* Date: N/A (Wiki keeps history) | * Date: N/A (Wiki keeps history) | ||
* Version: N/A (Wiki keeps history) | * Version: N/A (Wiki keeps history) | ||
| − | * Domain: | + | * Domain: [[Radiology]] |
| − | |||
| − | [[ | ||
| − | |||
==2. The Problem== | ==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: (1) the next group(s) of vendors or clinicians trying to implement RadLex codes would have a better basis to start from and (2) to cross-promote the adoption of RadLex in the vendor and clinical communities. | ||
==3. Key Use Case== | ==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== | ==4. Standards and Systems== | ||
| − | + | Systems: | |
| + | * Maybe the Order Placer, but doubtful | ||
| + | * Department System Scheduler/Order Filler (DSS/OF) | ||
| + | * Modality Performed Procedure Step Manager (MPPS Mgr) | ||
| + | * PACS | ||
| + | * Reporting system | ||
| + | * Modality | ||
| − | + | Standards: | |
| + | * RadLex | ||
| + | * IHE Radiology Scheduled Workflow | ||
| + | * reporting - not exactly sure which profile yet | ||
| + | * tangentially XDS/XDS-I | ||
==5. Discussion== | ==5. Discussion== | ||
| − | + | This is a white paper proposal, not a profile proposal. The intent is to align two RSNA initiatives more closely and increase adoption by making the subject less overwhelming/giving IHE developers a better and more unified starting point. It is our intent to keep the RadLex committee members closely involved so that they are in agreement with the direction of the white paper. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 07:54, 14 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/Karos Health, David Clunie
- Editor: Teri Sippel Schmidt/Karos Health, David Clunie, Daniel Rubin/Stanford (RadLex chair), 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: (1) the next group(s) of vendors or clinicians trying to implement RadLex codes would have a better basis to start from and (2) to cross-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)
- Modality Performed Procedure Step Manager (MPPS Mgr)
- PACS
- Reporting system
- Modality
Standards:
- RadLex
- IHE Radiology Scheduled Workflow
- reporting - not exactly sure which profile yet
- tangentially XDS/XDS-I
5. Discussion
This is a white paper proposal, not a profile proposal. The intent is to align two RSNA initiatives more closely and increase adoption by making the subject less overwhelming/giving IHE developers a better and more unified starting point. It is our intent to keep the RadLex committee members closely involved so that they are in agreement with the direction of the white paper.